You must specify the input and output properties that are used for the tasks associated with a component (plug-in or other service template).
A service template defines a generic operating procedure. For this reason, properties that store the input values required to run the service, such as host names and resource limits, are defined when services are added from a service template. These are called service input properties. The results of running a service are output to the Ops Center Automator user interface as the values of service output properties. Input properties that store the input values required for running a step and output properties that store results are defined through the plug-ins. You can enter values in plug-in input properties directly, or pass values to them by linking them to a service input property or variable. By linking a service output property to a plug-in output property, you can review the run results of a plug-in from the Ops Center Automator user interface. Linking properties in this way and passing values between them is called property mapping.
You must map the component input and output properties for every step with the input and output properties and variables of the service template. Associate the input properties of the components used in a service template with the input properties or variables, or output properties of other component steps associated with a service template. The service template input properties store the input values required to run a service. The service template output properties store the run results of the service.
The value of the plug-in input property can be the value that was previously set for the property, or directly set for the service template. The input property can also be a variable. You can apply the service share properties to the input properties.
The output property content depends on the type of component. You can store the results of running a step as output properties. Variables temporarily hold the values that are passed between components.
The input and output properties of the components are set from the Property tab in the Service Builder Edit window. The input and output properties and variables for the service template are set in the Property tab of the Service Builder Edit window.
The following figure shows a typical mapping between the service template properties and the corresponding plug-in step properties.
In this figure:
- The value input to Input property 1 of the service is input to Input property 1 of Plug-in A.
- The value input to Input property 2 of the service is input to Input property 2 of Plug-in B.
- The unmapped Input property 2 of Plug-in A is assigned the value entered when the service template was created or edited.
Because Output property 1 of Plug-in A is mapped to Variable 1, and Variable 1 is mapped to Input property 1 of Plug-in B. Values output as Output property 1 of Plug-in A are stored in Variable 1 then input to Input property 1 of Plug-in B. This passes the run results of Plug-in A to an input property of Plug-in B, so it can be used in the processing of Plug-in B. Because of this mapping, the following results are achieved:
- The run results of Plug-in A (standard command output and standard error output, and output properties) output as Output property 2 of Plug-in A are also output to Output property 2 of the service. This enables you to review the run results of Plug-in A in the Ops Center Automator user interface.
- The run results of Plug-in B (standard command output and standard error output, and output properties) output as Output property 1 of Plug-in B are also output to Output property 1 of the service. You can also review the results of Plug-in B through the Ops Center Automator user interface.