Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved


Chapter 5 Administering iProcess Engine Server Processes : Using SWDIR\util\swsvrmgr to Administer Server Processes : Issue a Start-up Event

Issue a Start-up Event
To start the entire iProcess Engine node or start individual processes, you can issue a START event so that Process Sentinels receive the published event and start the required processes.
To issue a START event, use the following command:
swsvrmgr START [machine_name|machine_id [process_name [process_instance]]]
[-T timeout]
where:
machine_name is the name of the server.
machine_id is the unique identifier of the server. You can find a server’s identifier using the swsvrmgr status command.
process_name is the process name of the server process you want to start, and must be one of: BG, BGPREDICT, DBQD, DLMGR, IAPJMS, SPO or DIRECTOR. If any other process name is specified, the command fails and an error message is displayed.
process_instance is the instance of the process to start.
timeout is the optional timeout period that can be used to specify the time after which the command will terminate. If this is not specified, the default is 60 seconds.
When you issue a START event, the swsvrmgr utility will test events automatically. If the events do not work, Process Sentinels will not start processes. See Test Events for more information.
Notes
All foreground processes (see Server Processes) must run on the master server.
Example
To start the third instance of the background process (BG) that is operating on the computer called hercules using the default timeout, you would issue the following command:

 
swsvrmgr START hercules bg 3
BG 3 STARTED
Process(es) successfully started

 
 

Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved