Note: If you are installing the agent plug-in to work with CA Workload Automation DE, you must set up an alias. Setting up an alias for use with other scheduling managers is optional.
You install an agent plug-in into the agent installation directory to extend the core functionality of the agent. By default, the agent plug-in operates under the same agent name that is assigned to the agent. An alias lets you create a unique agent name for an agent plug-in, which is useful for controlling agent security or for setting up clustered environments.
Suppose you have installed an agent named AGT10 on a UNIX computer. Users who have access to that agent through their security permissions specify AGT10 as the agent name in their job definitions. Now suppose that you install an agent plug-in into the installation directory for AGT10. You can create an alias for the agent plug-in, for example, AGT10_DB. You can then restrict access to that alias to only those users that run database workload. Those specific users then must specify AGT10_DB as the agent name in their job definitions.
Each agent plug-in has a default alias that you can enable during installation. For example, the agent plug-in for CA WA Agent for Databases has the default alias agentname_DB. You can enable or change the default alias name after installation. To work, you must also configure the alias on the scheduling manager.
To configure agent aliasing for clustered environments, see the CA Workload Automation Agent for UNIX, Linux, or Windows Implementation Guide.
|
Copyright © 2010 CA.
All rights reserved.
|
|