The dmstartup scripts no longer include the starting of the Tomcat server and is now moved into the Common directories and is referred to as Common Tomcat. In order to start Common Tomcat, you will need to do the following:
Deploying from stage "Unit test" back to "Development" (using standard Global stage lifecycle), Dimensions runs the post deploy script for Unit Test, Development and System Test.
When doing a deploy into a unix area with capturing logs of deploy post script by adding DM_REXECS_LOGS_* parameters in dm.cfg, it completes successfully when dmsys executes the deploy but when it is an other user who does the deploy then deploy fails as follow : 1 Deployed as a result of a promotion operation 2 Launching DEPLOY job 10181117
Halt on failure is used within an Expert chain to determine whether the rest of the chain can be processed. The step will check the result of the last expert run and if a failure has been returned any further processing in the chain will be halted and the expert chain will return a failure status back to Pulse.
For Dimensions 10.1.x: The recreateIndexes.sql script enables you to recreate and resize the indexes in a specified base database. The recreateIndexes.sql script is run under the dmdba utility, and is invoked by the command:
Running multiple scripts in parallel containing CI, FI and DI commands will give you ORA-00060 deadlocks. Taking the DI commands out of the scripts works around the problem.
Can you run a batch file or exe from the pre/post script defined in the deployment area? In addition: Can the customer create a log file of the items that are being deployed and then use the log file as reference when executing a batch command within one of the scripts available within the deployment process?
