IDK scripts

ISM scripts are Unix shell or Windows command-line scripts that reside in the ISM directory. The sections that follow describe the different type of ISM scripts:

• Installation Hooks: Bundled into the ISM’s control package by the ISMTool --build command, the installation hooks are run by the native packaging engine (such as rpm) on the managed server. Installation hooks may invoke control scripts.
• Control Hooks: Also bundled into the ISM’s control package, the control scripts perform day-to-day, application-specific tasks such as starting software servers.
• Installation Scripts: Not contained in the control package, but instead stored in the Software Repository, installation scripts can be viewed on the Properties of a package in the SA Client.

The overall process for developing and running installation hooks and control scripts follows:

1. Invoke the ISMTool --new command, which creates the default installation hooks.
2. With a text editor, create the control scripts.
3. With a text editor, modify the default installation hooks, which may call control scripts.
4. With the ISMTool, build and upload the ISM.
5. In the SA Client, install the application contained in the ISM onto a managed server. During the installation, the pre-installation and post-installation hooks are run on the managed server.
6. During the production lifetime of the application, run or schedule the control scripts.
7. At the end of the application’s life cycle, with the SA Client, uninstall the application. During the uninstallation, the pre-uninstallation and post-uninstallation hooks are executed on the managed server.

Installation scripts have a different overall process than installation hooks and control scripts. For more information, see Installation scripts.

An ISM script cannot call program (such as rpm or pkgadd) that locks the package associated with the script.