Distributed Operating Environment › Applications

Applications

Verify that all applications, commands, scripts, and so forth, are available that the agent requires.

To control application executions on the agent, define a set of job classes that represent the workload. These job classes must be known on the CA WA CA 7 Edition side, because each job can define a JOBCLASS parameter in the parameter definitions. The job classes are defined to the agent using the following:

initiators.class_n=classname,number 

n

Specifies a sequential number starting at 1 and incremented by 1.

classname

Specifies the name of the job class.

number

Represents how many “initiators” of that class are permitted to run concurrently.

Another method exists by which you can assign a job class to a job based on the Verb/Subverb passed in the message to the agent. The message is referred to as an Automated Framework Message (AFM) and has the following general format:

header VERB SUBVERB data

Set up a class name that is based on the VERB and SUBVERB. The AFMs are shown in the receiver log in the log directory where the agent is installed. You can assign a class name that is based on the VERB SUBVERB combination, and then assign to that class name a number of initiators to permit concurrent execution. The assignment of the class occurs through the agentparm.txt parameter:

initiators.afmjobclassmap_n=verb,subverb,name

where verb and subverb are the verb and subverb of the AFM, and name is the class name to which these types of AFMs are assigned. After you define this statement, assign the number of initiators for that class using the initiators.class_n. The _n between the AFM job class map does not need to correspond to the _n of the class parameter.

For example, one reason to assign a number is to limit the concurrent number of monitoring jobs executing. Monitors have the verb/subverb as OBJTRIG DEFINE. You can want to limit the number of concurrent monitors executing on an agent to 5, for example. Next, you can set up the initiators as the following:

initiators.class_1=Default,100 
initiators.class_2=Monitors,5 
initiators.class_3=Prod,1000 
initiators.afmjobclassmap_1=OBJTRIG,DEFINE,Monitors 

Establish a Default class for jobs and commands that are submitted without a class specification. With CA WA CA 7 Edition, commands do not have an associated job class and execute under the Default class initiator.

Note: We recommend that you set up a job class and possibly a job class map in the agentparm.txt file. Set the number of initiators to match the proxy.maxSubmitConnections value, which limits the number of simultaneous active jobs on the agent (default of four). This setting causes the waiting jobs to have a status of ‘Waiting for Initiator’. Without the job class, the waiting jobs appear to hang in the ready queue. For more information, see the CA Workload Automation Agent for Remote Execution Implementation Guide and the CA Workload Automation Agent for UNIX, Linux, or Windows Implementation Guide.