Using Software Delivery › Software and Procedures › Defining Embedded Item Procedures

Defining Embedded Item Procedures

Item procedures are the means by which a program is installed, activated, configured, and uninstalled. There can be embedded item procedures or added item procedures. Embedded item procedures are registered automatically at the same time as the program. Added item procedures are registered separately, after the item is registered. For more information on added item procedures, see Defining Added Item Procedures.

Embedded item procedures are marked Original Delivery in the Created column of the Procedures detail display.

Item procedures identify the following:

• Operating system under which the item procedure executes
• Procedure type, such as command file, executable file, SWD file, MSI file, SXP file, PKG file, PIF file, RPM file, IPS file, Palm file, or WinCE file
• Startup procedure name, such as SETUP.EXE
• If the procedure is an external procedure (in other words, it already exists on a target computer, or somewhere accessible from the target computer), external procedures provides the means to refer to programs not registered to the Software Package Library, that is, present in an absolute path on each agent but still manage their execution using the product.
• Type of task being performed by the procedure, such as INSTALL, ACTIVATE, UNINSTALL, or CONFIGURE
• Parameters to be used when starting the procedure
• Additional files needed for the procedure to perform
• Whether the item is to be enabled for the Software Catalog

You can use the item procedures that are delivered with the program (such as SETUP.EXE), or you can create your own customized procedures using batch or command files. For example, you may want to create a customized install for all Windows computers that have disabled mouse devices.