The target of an operator is the host on which the operator runs. A host that can be the target of an operator must be configured with a touchpoint, a proxy touchpoint, or a host group. When determining the run settings for an operator, content designers typically base target host selection on how that target is configured.
Specify the target as indicated in the following list when the appropriate conditions are met:
The target host has an Orchestrator or agent installed. When you specify a touchpoint as the target for an operator, and that touchpoint is enabled and associated with an active orchestrator or agent, CA Process Automation executes the operator on the specified touchpoint. If a targeted touchpoint is associated with only one agent or with an orchestrator, each execution targets the same host. If a targeted touchpoint is associated with multiple agents with the same priority, each execution could target a different agent on a different host.
The operator is to run on all of the hosts that are associated with touchpoints in the specified touchpoint group.
Exception to touchpoint: Specify the same AgentID for consecutive operators when the process requires the operator to run on the same host as the previous operator. Specify a specific AgentID when the process requires the operator to run on the same host each time it is run. A test run of the operator displays the AgentID string in the system dataset. You copy the AgentID string from the dataset into the Target field.
The target host is specified as the remote host in a proxy touchpoint configuration. Typically, this host does not have an installed agent or an Orchestrator.
The target host has an IP address or FQDN that can be matched to a pattern in a configured host group. Typically, this host does not have an installed agent or an Orchestrator.
Note: The host name can be used, but FQDN is preferred.
Important! Unexpected results can occur if you specify the target with a touchpoint that is named the same as a host in the environment. Unexpected results also occur if the agent associated with that touchpoint is inactive when you run the operator. In this case, CA Process Automation does not run the operator on the touchpoint. Instead, CA Process Automation tries to resolve the target (intended to be the touchpoint) to the name of a host in the environment. If it finds such a host name, CA Process Automation searches for another touchpoint, Orchestrator, proxy touchpoint, or host group that runs its operators on this host. CA Process Automation runs the operator on the first occurrence it finds.
|
Copyright © 2014 CA.
All rights reserved.
|
|