Inside Automation Engine > Multi-Server Operation > Starting and Ending Server Processes

Starting and Ending Server Processes

An AE system consists of server processes which run on one or several computers. They can easily be started and ended via the ServiceManager dialog program. AE Script also provides scriptA particular Automation Engine object type. elements for starting and ending server processes.

Starting Server Processes

Automic strongly recommends starting server processes with a time delay regardless if a normal or cold start is made.  

  1. Start the work processA part of the component Automation Engine. It is responsible for an Automation Engine system's processes (see also 'Primary work process'). which should serve as the primary work processIt is responsible for the execution of Automation Engine-internal tasks and work processes. (PWP) first. Wait until the following message is printed in the log file:

    U0003471 The Server 'UCGLOBAL#WP001' has successfully been initialized, *** R E A D Y   F O R   R U N ***
  2. Now start all other work processes with a time delay of about 10 seconds.
  3. Start the communication processes.
  4. Start all other components such as agents only when all server processes are already in operation. Also keep a time delay of about 10 seconds between the individual starts.

A time delay option is available for each componentA component is a single deployable application artifact. As an example, this can be yourfile.war to be deployed into a Tomcat container. Each component has different properties which determine where to get it from, how to configure it, etc. You will need one component per application artifact: e.g., one for the application tier and one for the database backend. in the settings of the ServiceManagerA program that facilitates the starts and stops of Automation Engine components. dialog.

Numerous messages are output when the Automation EngineThis component drives an Automation Engine system and consists of different types of server processes. starts. Some of them refer to possible errors but most of them only log information about the start procedure in the log file:

Explanation: Each server processThe core of the component Automation Engine. Different types are available: communication, work and dialog processes, as well as nonstop processes. 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.

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.

Ending Server Processes

Server processes can be ended collectively or individually. Ending particular ones is especially useful when server processes are distributed on several computers and only the server processes of a particular computer should be ended.

Ending

ServiceManager

AE Script

Ending a particular server process

Context menu command Immediately single process

:TERMINATE

Ending all communications and work processes

Context menu command Shutdown (AE system)

:SHUTDOWN

Automic recommends using the following procedure in order to end all server processes individually. First, terminate all work processes except for the primary work process. Then terminate all communication processes and, last but not least, the primary work process.

This is what happens when a particular server process is ended:

Shutting down the AE system:

Server processes can also be ended abnormally. Then they end immediately without the procedure described above. Only use this way of ending server processes if these could not be ended differently.

 

See also:

Server Processes
Number of Server Processes

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH