Agent configuration in a design environment is typically limited to configuring a small set of touchpoints, each mapped to a single agent. If hosts are in short supply, you can associate multiple touchpoints to the same agent.
More robust agent configurations are typical of production environments. Six options are first presented separately, then on a summary table for reference. Use these details to plan and implement agent configuration in the production environment.
This option is the easiest to implement when running an operator on one host with an agent. This option is acceptable in a development or test environment.
Host name or IP address of the target.
Install an agent on the target host.
Define a touchpoint that associates an agent with the production environment.
Enter the touchpoint name. Alternatively, you can enter the agent ID.
This option lets you specify that the operator run on the most desirable host if it is available, and if not the next most desirable. You decide what makes one host more desirable than another. You can configure a touchpoint so that a given operator always runs on the host with the largest capacity. Or, you can reserve such hosts and only run on them if all other candidates are busy.
Unknown. Record the host names of the candidate target hosts, with preference order.
Install an agent on each candidate target host.
Define a touchpoint and associate it with each of the candidate target hosts. In the touchpoint definition, specify the rank of priority for each.
Enter the touchpoint name.
This option takes longer to implement than a touchpoint associated with one agent, but is a robust option when targeting a host with an agent. This option is designed for a production environment where it is important that the process runs at the scheduled time.
Unknown. Record the host names of the candidate target hosts.
Install an agent on each candidate target host.
Define a touchpoint and associate it with each of the candidate target hosts. In the touchpoint definition, enter the same number as the priority for each association. This implementation is for load balancing.
Enter the touchpoint name.
Use of the touchpoint group lets you run an operator simultaneously on all hosts that are associated with touchpoints in the group.
Record the host name of each target host.
Install an agent on each target host.
Enter the touchpoint group name.
Sometimes, you cannot install an agent on a host you want to target for an operator. In this case, define an agent as the proxy touchpoint. Create an SSH connection from the host with the agent to the target remote host.
Record the host name or IP address of the remote host that is the target.
Record the host name of the source host that can connect to the target with an SSH connection.
Create the SSH connection from the source host to the remote host.
Install an agent on the source host.
Define a proxy touchpoint on the source host and specify details of connection to the remote target host.
Enter the proxy touchpoint name.
This option lets you decide what remote host to target immediately before runtime, when you specify the target with its host name or IP address. The target must be a member of a host group. A host group is a group with either a common host name pattern or a common IP address pattern. Hosts with a common IP address pattern belong to the same subnet.
Unknown. Record the host names of the candidate target remote hosts.
Record the host name of the source host that can connect to each of the candidate targets with an SSH connection.
Create the SSH connection from the source host to each remote host.
Install an agent on the source host.
Define a host group on the source host with a pattern that remote hosts have in common.
Enter the host name or IP address of the target remote host. Express the operator target in a dataset. You can modify datasets, even when imported with a non-modifiable process.
Use the following table as a guide for creating summary tables for yourself. Documentation in the form of summary tables can help others find this information when you are not available.
|
Target Type |
Agent Association |
Other Configuration |
Operator Target |
|---|---|---|---|
|
A single host |
A new touchpoint |
N/A |
Touchpoint name |
|
One of multiple hosts, in priority order |
An existing touchpoint |
Specify priority in which to select the target host. |
Touchpoint name |
|
One of multiple hosts (no priority) |
An existing touchpoint |
Assign same priority to each candidate target host. |
Touchpoint name |
|
Multiple hosts at once |
A new touchpoint |
Create a touchpoint group with all touchpoints. |
Touchpoint group name |
|
A single remote host |
A proxy touchpoint |
Create an SSH connection from the agent host to the remote target host. |
Proxy touchpoint name |
|
One of multiple remote hosts |
A host group |
Create an SSH connection from the agent host to each remote target host. |
Target host name or IP address |
|
Copyright © 2014 CA.
All rights reserved.
|
|