
Managing iIS Process Engines with Conductor Script
The Conductor Script commands used to monitor engines 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. |
|
ListEngines | Display a list of all running and | page 289 | |
|
| configured iIS process engines in the |
|
|
| environment. |
|
ShowEngine | engine_name | Display status of the specified engine. | page 306 |
ShowStatus | [short] | Display status of the current engine. | page 309 |
|
| (No engine components need be |
|
|
| running for this command to work.) |
|
|
|
|
|
Monitoring Individual Engine Components
You can get more information about individual engine components.
➤To monitor individual engine components
1.Use the ListEngines command to see which engines are running in your environment.
2.Use the FindEngine command to make a particular engine current.
3.Use the appropriate FindComponent command to make a component current.
4.Use the ShowStatus command to display information about the current component.