Managing iIS Process Engines with Conductor Script
Changing Engine States
You can change the state of an engine by changing the state of an engine unit or by shutting down an engine component.
Changing Engine Unit States
You might want to change the state of an engine unit for a number of reasons. For example, you might want to close all client sessions with a primary engine unit (change its state from ONLINE to STANDBY) in order to perform administrative functions on the database. Or you might want to place a primary engine unit in STANDBY state so you can make its partner primary. When the partner goes from STANDBY to ONLINE, it recovers state information from the database.
➤To change the state of an engine unit
1.Use the FindEngine command to make the engine of interest current.
2.Use the FindUnit or FindPrimary command to make the component of interest current.
3.Use the SetState command to set the engine unit state.
If you want to place the primary unit on standby, and the backup unit online, you can perform this operation in a single command using the SetPrimary command.
The Conductor Script commands used to change engine states are documented in Appendix A, “Conductor Script Commands” and summarized in the following table:
Command | Arguments | Function | See… |
|
|
|
|
FindEngine | engine_name | Set specified engine as the “current” | page 284 |
|
| engine. The engine (nor any of its |
|
|
| components) does not have to be |
|
|
| running. |
|
FindUnit | unit_name | Set the specified engine unit for the | page 286 |
|
| current engine as the current component. |
|
|
| The engine unit must be running. |
|
FindPrimary | Set the primary engine unit for the | page 285 | |
|
| current engine as the current component. |
|
|
| The primary unit must be ONLINE. |
|
SetState | state | Set the state for the current engine unit to | page 302 |
|
| ONLINE or STANDBY. |
|
|
|
|
|
