Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Adding components to servers manually

You can add a component to a single server without running a Component Discovery Job.

This procedure is useful as a way to quickly add a single component, particularly if the discovery operation is not activated for a component template.

This procedure is also useful if you want to create a component on a server and bypass the use of local property sets when one or more local property sets are defined for a component template. For example, suppose you create a component template with an INSTALL_DIR property, and you define values for this property using multiple instances of local property sets. One instance sets the value of INSTALL_DIR to /opt/qa while another sets it to /opt/dev. If you run a Component Discovery job, it substitutes the /opt/qa and /opt/dev values from the two local property set instances. However, if you want to provide a different value for one server, you can insert that value using this procedure.

To manually create a component

  1. In the Component Templates folder, right-click the component template that you want to use to create the component. Then select New > Component.
    The New Component wizard opens.

  2. Define the new component on the wizard panels, as described in the following topics:

  3. Click Finish after completing the last step of the wizard.
    The component that you defined is associated with the designated server.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*