Previous Topic: Item Procedures in Batch ProgramsNext Topic: Defining Added Item Procedures


Item Procedure Task Types

The tasks performed by an item procedure fall into one of four categories of which Install is the most common.

The other tasks are Activate, Configure, and Uninstall, which are also called noninstall tasks.

ACTIVATE

Triggers the product to run. For example, an ACTIVATE task can be used to remotely trigger the start of a backup or archive program. You should identify an item procedure as an ACTIVATE task if it does not fall under any of the other three categories or if it performs a combination of any or all of the other three tasks.

CONFIGURE

Reconfigures an existing installation.

INSTALL

Installs the product.

UNINSTALL

Removes the installation.

Note: ACTIVATE, CONFIGURE, and UNINSTALL procedures can be performed only on computers on which the item has already been installed, that is, installed using any of the procedures of type INSTALL. Most packages contain only an INSTALL and an UNINSTALL procedure. CONFIGURE, and customized INSTALL and ACTIVATE tasks can be created by registering site-written scripts, command, or batch files. For more information on customized item procedures, see Optional Customization Tools.

Unlike other software delivery agents, NOS-less agents do not have access to the manager's local library. Therefore, the software delivery component cannot determine which item procedures are necessary for noninstall task types, and the whole library item is transmitted to the agent. In the case of a large library item, this process may be time and resource consuming. Use external procedures to avoid delivering the package.