Adding agent and integration server names and trigger nodes for an application

Before you can use the IBM® UrbanCode® Deploy Selfserv tool to control the Agents and integration servers for your IBM Sterling® Order Management System, you must first configure the IBM UrbanCode Deploy Selfserv tool to include the agent names and integration servers. If you need to use the IBM UrbanCode Deploy Selfserv tool to trigger agents you must also add trigger nodes to agents.

The lists of agent and integration server names are each stored in resource level properties:

The list of agent names is stored in the agentName resource property. Whenever the agent component is mapped to an agent, add the agent name to the list of agent names for the component.
Note: If you want to start multiple instances of same agent, enter the name of the agent server multiple times as a comma-separated list in the agentName resource property. For example, if you want to start three instances of ScheduleOrder agent server, enter the value as ScheduleOrder,ScheduleOrder,ScheduleOrder in the agentName resource property.
The list of integration server names is stored in the intgName resource property. Whenever the integration component is mapped to an agent, or integration server, add the integration server name to the list of integration server names for the component.

A trigger node is set as a resource level property for an agent and indicates that the agent is a trigger node. The trigger node is used to determine which machine is used for the trigger agent process to run.

Before you begin

Ensure that you complete the following tasks:

Create the agent and integration servers in your Applications Manager.

Procedure

Access the IBM UrbanCode Deploy Selfserv tool dashboard.
From the Dashboard tab, click the main Resources tab.
Click the Resource Tree tab and find your IBM Sterling Order Management System application.
Expand the collapsible sections within the resource tree for your application and the environments within the application.
Add your agent server names to the list of agent names for the agent component for the environment.
1. From the list of environment resources, expand the collapsible sections to find where the agent component (OMS-AGENT) is mapped to an agent for the environment.
2. Click the OMS-AGENT tag for the agent.
  The resource page for the agent component opens.
3. Click the Configuration tab. Then, click the Resource Properties tab.
4. Click Edit for the agentName property. This property includes the list of agent names for the environment. Include the names of the agents that you want to add to the list within the value for the property and click Save.
  Use a comma-separated list to enter multiple names.
  If the agentName property does not exist, you must add the property.
  1. Click Add Property.
  2. Enter agentName for the Name field.
  3. Enter the list of agent names for the Value field. Use a comma-separated list to enter multiple names.
  4. Click Save.
5. Repeat the preceding steps for each agent that is mapped to the OMS-AGENT agent component.
Add your integration server names to the list of integration servers for the integration component for the environment.
1. From the list of environment resources, expand the collapsible sections to find where the integration component (OMS-INTG) is mapped to a resource for the environment.
2. Click the OMS-INTG tag for the resource.
  The resource page for the integration component opens.
3. Click the Configuration tab. Then, click the Resource Properties tab.
4. Click Edit for the intgName property. This property includes the list of integration server names for the environment. Include the names of the integration servers that you want to add to the list within the value for the property and click Save.
  Use a comma-separated list to enter multiple names.
  If the intgName property does not exist, you must add the property.
  1. Click Add Property.
  2. Enter intgName for the Name field.
  3. Enter the list of integration server names for the Value field. Use a comma-separated list to enter multiple names.
  4. Click Save.
5. Repeat the preceding steps for each resource that is mapped to the OMS-INTG integration component.
Add any trigger nodes that you need for your application.
Since there are multiple agent components that can be mapped to different machines, consider dedicating one machine to run the trigger agent process, instead of running the process on all machines.
1. From the list of environment resources, expand the collapsible sections to find where the agent component (OMS-AGENT) is mapped to an agent for the environment.
2. Click the OMS-AGENT tag for the agent.
  The resource page for the agent component opens.
3. Click the Configuration tab. Then, click the Resource Properties tab.
4. Click Edit for the triggerNode property. Set the value for this property to true and click Save.
  If the triggerNode property does not exist, you must add the property.
  1. Click Add Property.
  2. Enter triggerNode for the Name field.
  3. Enter the value true for the Value field.
  4. Click Save.
5. Repeat the preceding steps for each agent that is mapped to the OMS-AGENT agent component, but set the value for the Value field to false.