Automic Workload Automation

A COLD start allows you to start the Automation Engine server and purge the queues at the same time. We mostly recommend to perform a cold start when facing performance issues, and when updating your AE server.

Here are 3 different ways to do a cold start:

1 - Via the Service Manager Dialog (Windows only):

This is the simplest way of doing it. Just right click on a work process (WP) and choose Start Service with > Coldstart.

https://us.v-cdn.net/5019921/uploads/editor/ez/pa61vqyr58ie.jpg" width="666">

Notes:
- This needs to be done on one WP only. Reason for this is that a COLD start results in emptying the message queues (MQ tables in the database). Hence it should only be done once. Other processes may be started in "NORMAL" mode : just right click > StartService.
- a Coldstart with Systemstop is slightly different : all clients will be stopped after the server has started. You will need to manually set them to "Client GO".

2 - Via the server's configuration file (ucsrv.ini)

Just set "StartMode=COLD" in the [GLOBAL] section.
You may as well want to set SystemStop=YES if you want all clients to be stopped.
Please note that these settings will only be taken into account for the next start of the server. They will automatically be set back to StartMode=NORMAL and SystemStop=NORMAL in ucsrv.ini after the server has started.

3 - Via the Service Manager in batch mode

The command line program of the Service Manager can be used to start, stop or get the list of active processes on a given host.

A server process should be started like this : UCYBSMCL[.EXE]  -c START_PROCESS -h computer name -n phrase -s name of the service [-sm start mode] [-p password]

Example: UCYBSMCL -c START_PROCESS -h VMSTM2K12R2AE3 -n AEV11 -s UC4WP1 -sm Coldstart

Thanks for the clarification in that way how to perform a COLD start.

Please Note that a coldstart is not the "magic bullet" in any cases of performance issues, it more should be the "ultima ratio" and only should only be performed after checking back with support. Dont use it in any case you face a job is running too slow or a search within UserInterface took long for one time.

To perform this in a proper way, you need to know what exactly the coldstart is doing and what side-effects it may cause. The explaination in detail what it is doing, would blast this comment, but it definetly should only be done after talking with us from Support, and if other alternatives did not work.

Basically I - maybe call me old fashioned - am always using the COLD start method by changing the parameter in .ini File. Not because the others are not working - they are all working fine, but it gives me the proof of what i was doing in detail.

Harald_Heidinger_152 thanks for these additional considerations.

The explaination in detail what it is doing, would blast this comment

True, besides further information can be found here : https://community.automic.com/discussion/7218/the-cold-start-hot-topic