Starting and Ending Server Processes

An AE system consists of server processes which run on one or several computers. You can easily start and end them by using the ServiceManager - Dialog Program, or by using the Automation Engine scripting language which also provides script elements for starting and ending server processes.

To Start Server Processes

It is recommended to start server processes with a time delay regardless if you cold-start or warm-start your system.

Start the work process (WP) that should serve as the primary work process (PWP). Wait until you see the following message printed in the log file:

U0003471 The Server 'AUTOMIC#WP001' has successfully been initialized, *** R E A D Y F O R R U N ***
Now start all other WPs with a time delay of about 10 seconds.
Start the communication processes (CPs).
Start all other components such as agents only when all server processes are active. Also keep a time delay of about 10 seconds between the individual starts.

Note: A time delay option is available for each component in the settings of the ServiceManager dialog.

Possible Messages

You will see many messages when you start the Automation Engine. Some of these messages refer to possible errors but most of them only log information about the starting procedure in the log file:

Starting a CP or WP causes several socket error messages that are output

Explanation: Each server process attempts to open one port number after the other until it finds an empty port as specified in the INI file. The server process name is then defined via this port. It is normal that some ports are already occupied when several server processes start at the same time. This fact causes socket error messages, but there is no error.
Following a cold start, database error messages referring to the MQCPnnn tables are always displayed.

Explanation: You can define several communication processes. The primary work process deletes their MQCPnnn tables one after the other when a cold start is made. This behavior is normal and there is no error.

To End Server Processes

You can either end server processes collectively or individually. Ending particular ones is especially useful when server processes are distributed on several computers and when you want to end only the server processes of a particular computer.

Ending a particular server process
- Context-menu command in the ServiceManager
  
  Immediately single process
- Available Scripting Element
  
  :TERMINATE

Ending all CPs and WPs
- Context-menu command in the ServiceManager
  
  Shutdown (AE system)
- Available Scripting Element
  
  :SHUTDOWN

It is recommended to use the following procedure if you want to end all server processes individually:

End all WPs except for the PWP
End all CPs
End thePWP

What happens when a particular server process ends?

Communication Process: The CP informs the connected instances of the Automic Web Interface and the agents so that these can establish a connection to a different CP. Then the process completes its report and ends.
Work Process: The WPs write their reports and then they end. If a PWP ends, one of the other WPs assumes the role of a PWP.

What happens when the AE system (all CPs and WPs) is shut down?

The PWP is instructed to shut down the system and it handles the smooth ending of all server processes. Basically, the same procedure applies as described above when you end a particular server process. Additionally, the PWP handles the message queue. It will end once the message queue has been processed. This includes that it may take some time until the PWP ends.

Important! You can also end server processes abnormally. In this case, they end immediately. The processes described above do not take place. Only use this way of ending server processes if you cannot end them by using one of the other options.