Step 1 - Application Start
Before you can introduce a new application you should consider how it is started and all the actions required to make it operational.
Therefore it is important to know:
| Actions Required | Available Functionality |
|---|---|
| Are there any actions to complete before the application itself could be started? | To include these actions in automation, use the application's PRESTART policy. Any command specified there is issued prior to the insertion of the start command. |
| What is the application's start command? And are there different start commands depending on the startup mode of an application (for example, the normal and the light start for a DB2® database)? | The start command should be located in the STARTUP policy. It also provides the full flexibility for different start commands by specifying different start types. Once a start type is set, the specified command will be chosen. The start type easily can be chosen/changed at System Automation runtime. |
| Who starts the application when it is not started by System Automation? Is it started by another instance? | The APPLICATION INFO policy lets you specify an EXTERNAL STARTUP parameter. |
| Are there any actions to complete after the application initialization? | Use the POSTSTART policy to issue additional commands after the full initialization of the application. |
Note: All startup policies support flexible start types.