If you have written an item procedure before registering a program, you can include it during the registration as an embedded item procedure; however, most customized procedures are defined as added item procedures.
Added item procedures are created and registered in the Software Package Library after registration of the program they concern. They can be created from scratch or they can be copied from existing item procedures.
Added item procedures are not automatically delivered from the enterprise manager to the domain managers along with the software product. However, when you are adding a registration order for a software item containing added item procedures to a distribution container, you can use software delivery functionality to try to automatically add registration orders for associated item procedures to the distribution container. You can also determine that registration orders are created only for selected procedures. If a failure occurs during automatic generation of a registration order for one of the added item procedures, you can decide to continue with automatic generation of registration orders for the remaining procedures.
Added procedures can only be registered to the enterprise and domain manager libraries. They cannot be registered to scalability server libraries. This is important as when added procedures with new files are scheduled to be installed on agents connecting through remote scalability servers the entire original software item and the added files will be delivered from the domain manager's library rather than reusing any files registered to the scalability server. Take this into account before deciding on using added procedures.
The alternative to added procedures is creation of new independent software items that can be stored in the scalability server libraries.
|
Copyright © 2013 CA.
All rights reserved.
|
|