How to Deploy a Component by Using a Direct-Run Procedure

Most components include install, uninstall, and snapshot procedures. A component might also include control procedures that manage the installed component. For example, a control procedure might to start or stop the application.

You might be able to use one of the direct-run procedures that the provisioning system automatically generated when you checked in your component. Use this method for straightforward deployments that do not involve more than one component or synchronization between hosts.

Steps

1. From the navigation menu, choose Components.

   The Components page lists the components that are already checked in.

2. Click Change Folder.

3. Specify the name of the folder in which to create the component, and click Change to Selected Folder.

   The Components page now lists the components in the specified folder.

4. Click the name of the component that you want.

   The Details page for that component appears.

5. In the Component Procedures table, determine which procedure to run, and click Run.

   The provisioning system generates a plan, which is stored in the /system/autogen folder.

   The Run page for the generated plan appears.

6. In the Plan Parameters area, select the variable settings for the component you want to deploy.

   • If the variable settings have been established for this component, choose the appropriate settings from the menu.

   • If the settings are not available from the menu, click Select From List.

     The Select Variable Settings From List window appears.

     • If you want to use another component's variable settings, click Import Set.

       The Import Variable Settings window appears.

       1. If necessary, go to the folder that contains the component with the variable settings you want to import.

       2. Select the component version.

          ---

          Note –

          Variable settings can vary between component versions.

          ---

       3. Click Import Variable Settings.

          The imported variable settings appear in the table.

       4. Click Select.

     • If you want to create new variable settings, click Create Set.

       The Select Variable Settings From List window appears.

       1. In the text field at the top of the table, type a name to use for the new variable settings.

       2. Select the component variable you want to change.

          The table cell is highlighted and a text field appears.

       3. Type a new value for the component variable.

       4. (Optional) Repeat the previous substeps b and c for each variable value you want to change.

       5. After updating the variable settings values, click Save.

          The new variable settings appear in the table.

       6. Click Select.

7. Specify where to deploy the component.

   • To select a host, type the host name in the Target Host field or click Select From List and select a host.

   • To select a target host set, choose one from the Target Host Set menu.

8. In the Plan Variables area, configure the variables you want to set.

   Whether there are variables to configure depends on the contents of the component procedure you select.

9. In the Options area, select whether to perform a detailed preflight.

   The detailed preflight attempts to simulate every step of the plan that will run on the remote agent. The detailed preflight tests the following functions.

   • Resource installation

   • <execNative> calls

   • File transformations

   • File deletion, when uninstalling resources

   Running a detailed preflight increases the amount of time the preflight takes.

10. (Optional) To limit the number of hosts running at the same time, type the number of hosts on which to run a plan in the field provided.

    When a plan is run on several hosts simultaneously, all hosts must complete a particular step before any host can begin the next step. If the number of hosts is too high, the network connection can time out between steps.

    For example, the time interval between Host A finishing the first step and being able to run the second step might be too long. In this case, the length of the time interval causes the network connection to time out.

11. (Optional) To limit the overall running time of a plan or of native calls, type a number in the fields provided, then choose the time unit, such as minutes, from the menu.

    By limiting the runtime of a plan or native call, you prevent a nonresponsive host from tying up the progress of a running plan.

    If you set up a notification rule to alert you to plan failures, when the plan times out, you will be notified that the plan was unsuccessful.

    For information about setting up notification rules, see Configuring Email Notification in N1 Grid Service Provisioning System 5.0 System Administration Guide.

12. Specify whether to deploy the component.

    • To run just the preflight test of the procedure, click Run Preflight Only.

    • To run the preflight test and then the procedure itself, click Run Plan (Includes Preflight).

      Note that the procedure is not run if the preflight fails.