| |
Results |
|
DA: After upgrade to DA 6.3.3 we cannot see options for Execution or Deployment History Cleanup
|
4) In the right-hand, click on the pencil icon to the right of the group you are using, e.g., Admin 5) If it is not already checked, check the box next to " Clean Execution History", then click Save 6) Repeat steps 3 through 5 for Environments and "Web UI".
|
|
|
|
Cleanup obsolete security fields in CMN990 report
|
Cleanup obsolete security fields in CMN990 report
|
|
|
|
Configuring the Execution History Cleanup sweep for hung cleanup requests
|
Configuring the Execution History Cleanup sweep for hung cleanup requests
|
|
|
|
SBM: About the "Clear History" feature used to schedule Common Log cleanup (Delete Common Logger)
|
SBM: About the "Clear History" feature used to schedule Common Log cleanup (Delete Common Logger)
|
|
|
|
Doc update: potential promotion cleanup problems after upgrade from 5.3.x to 5.6.
|
Doc update: potential promotion cleanup problems after upgrade from 5.3.x to 5.6.
|
|
|
|
TeamTrack 6.3 for Solaris and Linux Release Notes
|
1. If you are upgrading TeamTrack for Solaris, you no longer need to start with a clean TeamTrack installation. 2. Text CLOB fields are now supported in TeamTrack 6.3 for Solaris and TeamTrack 6.3 for Linux. 3. You can now change configuration settings such as user ID, password, and port
|
|
|
|
SRA: Rollback configuration - How to remove files as part of rollback
|
In situations where a failure in a process triggers a rollback process and if the deployment area contains files that are not part of the snapshot being used for the rollback, how can we clean up and/or remove the files that do not belong to the snapshot being used for the rollback?
|
|
|
|
General maintenance for slow deploys or hanging deploys or take longer than usual in the initializing stage.
|
The following items can be used for general clean up and troubleshooting of deploys hanging or not starting. After using Collage for a while more and more deploy activity is stored in the administration database with not a real automatic way of cleaning it up. Over time you may see deploys hanging, not starting or generally taking a long time in the initializing stage.
|
|
|
|
SBM user licenses, laptop and mobile/fixed devices
|
A license will be set for clean up once the user clicks the Exit link in the interface; in SBM 11.4, simply closing the web browser will act like clicking the Exit link in the UI. Clicking this link should return the user to a landing page. If clicking this link logs the user back in (because you are using Windows Authentication), then we need to change in setting in [1]
|
|
|
|
How can I make Configurator ask to do the Orchestration Engine database upgrade again after I chose to stop showing warnings?
|
You might first go into this directory and move the log files that start with "upgrade..." to another folder just so you have clean ones for the next upgrade. C:\Program Files\Serena\SBM\Common\Tomcat 7.0\server\default\logs Make sure Configurator is not running
|
|
|
