Suppose you want an operator to target the same host every time it runs. In such a case, you can specify the AgentID data as a target. Unique AgentID data is set during the installation of each orchestrator and each agent. At runtime, CA Process Automation retrieves the ID for the orchestrator or agent and saves it to the AgentID field in the system dataset.
After a test execution of an operator, you can copy the AgentID string that is displayed in the system dataset into the Target field.
When you need two consecutive operators to run on the same agent host, specify the same AgentID as the target for both operators. You can use AgentID as an alternative target for any given touchpoint.
Important! Use of AgentID refers to the local host where the agent or orchestrator is installed. When you specify AgentID, CA Process Automation does not use any proxy touchpoint or host group running on the agent to run on remote hosts. Consider the case where Operator_1 executes on a proxy touchpoint that is configured on an agent with a specified AgentID. Do not use this AgentID as the target for Operator_2. If the AgentID is specified, CA Process Automation does not execute on that proxy touchpoint for Operator_2.
CA Process Automation fails the operator when encountering any of the following conditions:
Message could not be posted to the node.
Node is disabled.
Note: The Invoke Java operator can target only agents. The Invoke Java operator cannot run on an Orchestrator. An ID in the Target field of the Invoke Java operator must resolve to an agent (not an Orchestrator), or the operator fails.
|
Copyright © 2014 CA.
All rights reserved.
|
|