You can use direct-run component procedures and generated plans to manage your applications.
You can update a component to a newer version of that component. The newer component might reflect a product revision, a change to a file, or a directory that has new files added to it.
If you need to update a simple component, you only need to run the direct run install procedure. The install procedure will overwrite the old component version with the new version.
If you need to update a composite component (a component that references more than one simple component) and the set of referenced components are the same in each component version, you can run the direct run install procedure. The install procedure will overwrite each of the old simple components with the new versions.
If you need to update a composite component and the new version of the component contains a different set of referenced components, you will need to uninstall the old component version and install the new version. By uninstalling the old version, you prevent components that are no longer used or updated from cluttering your work space.
Sometimes the upgrade of a component fails or you experience problems with the upgraded application. In such cases, you can downgrade to a reliable version of the component while you troubleshoot the new component version.
To redeploy a reliable component version, you must have Run Component Procedure and Allow on Host Set permissions on the folder that contains the component.
Uninstall the broken component.
From the component's Details page, click Run for the Default: Uninstall component procedure.
From the plan's Run page, select the host from which you want to uninstall the component.
Click Run Select Installations.
Click Run Plan (Includes Preflight).
By uninstalling the broken component version you ensure that old, unwanted files are removed from the system you deployed to.
Select the component version that you need to roll back to.
Install the reliable version of the component.
You can migrate a component from one server to another by simply uninstalling the component you want to move from its current host and reinstalling the component on the new host.
You might want to create a container component if you need to deploy multiple simple components as a group to the same host or host set. Grouping simple components speeds deployment time and ensures that no component is forgotten when the set of components is deployed.
To create a container component, you must have Create, Edit, Delete permission on the folder in which you want to create the component.
From the Components page, create a new component.
In the Referenced Components section, add components to the container.
If the components you need to reference already exist, click Reference Existing.
The Reference Existing Components in Current Component window appears.
Select the component that you want to reference in the container component and click Reference Checked Components.
If you reference a component that contains component variables, the component variables are listed in a table before they are added to container component.
If necessary, set the component variable's default value in the text field next to the component variable name.
Click Continue to Reference Components.
You are returned to the container component's Edit page. The referenced component is displayed in the Referenced Components table.
If the component you need to reference does not exist, click Check In New.
Create the new component.
For information about how to create a new component, see Chapter 2, Components, in Sun N1 Service Provisioning System 5.1 Plan and Component Developer’s Guide.
After you have created the new component, the container component's Referenced Components table refreshes with the new component listed.
If necessary, provide values for the component variables that need to be defined by the container component.
If a component has a :[container....] substitution variable, the container component needs to define the value.