Working with Workload Objects › Remote Execution Jobs › Define a Remote Execution Job

Define a Remote Execution Job

You can define a Remote Execution (PROXY) job to run commands to a remote UNIX, HP Integrity NonStop, and OpenVMS computer through Telnet or Secure Shell (SSH2).

Notes:

• HP-UX supports only SSH2 protocol.
• To run these jobs, your system requires CA WA Agent for UNIX, Linux, or Windows and CA WA Agent for Remote Execution. The CA WA Agent for Remote Execution supports only remote target environments of UNIX, HP Integrity NonStop, and OpenVMS.

Follow these steps:

1. Open the Application that you want to add the job to in the Define perspective.

   The Application appears in the workspace.

2. Select the Remote Execution job in the Palette view, and drag the job to the workspace.

   The Remote Execution icon appears on the Application workspace view.

3. Right-click the Remote Execution icon, and select Edit from the pop-up menu.

   The Basic page of the Remote Execution dialog opens.

4. Complete the following required fields:

   Name

   Defines the name of the job that you want to schedule.

   Limits: 128 alphanumeric characters, plus the special characters commercial at (@), pound (#), dollar sign ($), underscore (_), square brackets ([]), brace brackets ({}), and percent sign (%) as a symbolic variable introducer character.

   Agent name

   Specifies the name of the agent that runs the Remote Execution job.

   Note: The drop-down list displays all the agents that are defined in the Topology for the specified job type.

   Remote target

   Specifies the name of the custom properties (remote_target.properties) file that is created on the agent for the remote system. The file contains the default user credentials that are used to monitor all jobs run on the target machine by the agent. The name should not include the .properties extension.

   Limits: Up to 128 characters; case-sensitive; valid characters are letters, numbers, and underscore (_); the first character must be a letter

5. Click Add in the Remote commands section, and specify a command or script to run on the remote computer.
6. (Optional) Repeat the previous step to specify additional commands or scripts to run.

   Note: You cannot run multiple UNIX commands in a Remote Execution job.

7. (Optional) Specify the following additional information:

   User

   Specifies the user ID that has the authority to run the job. The user must be defined in the Topology. This field supports the use of a namespace for a user that has more than one password. Contact your administrator for the user name defined in the Topology.

   Examples: Bob, Production:Bob

   Notes:

   • The drop-down list displays all the user IDs that are defined in the Topology for the specified agent. You must have at least Read access to the ADMIN.Network Topology permission to view this list.
   • Your agent administrator can specify a default setting for all Remote Execution jobs by setting the default.user property in the custom properties file for the remote system. The value you specify in the job definition overrides the default value in the custom properties file.

   Spool file

   Specifies the path to the spool file when you do not want to use the default location. If a spool file is specified, it overwrites a previous spool file with the same name unless you specify to append by beginning the name with >>.

   Limits: Up to 256 characters; case-sensitive; valid characters are a-z, A-Z, 0-9, and delimiters

   Notes:

   • Your agent administrator can specify a default setting for all Remote Execution jobs by setting the spoolHome property in the custom properties file for the remote system. The value you specify in the job definition overrides the default value in the custom properties file.
   • The operating system or file system may impose additional requirements on the value, such as using valid path and file name notation.

8. (Optional) Click Submit Modifier in the left pane to specify commands that you want to run prior to executing the commands on the remote system. Running these setup commands provides additional flexibility to pass additional information to commands executed on the target system.

   The Submit Modifier page opens in the right pane.

9. Click Add, and then enter the appropriate command or option.

   Note: The syntax and option requirements of the target system job apply.

10. (Optional) Repeat the previous step to specify additional setup commands.
11. Click OK.

    The Remote Execution job is defined.

Example: Run the ls Command on a Remote System

This example executes the ls command on the hpserver remote system. Additionally, it specifies a spool file location other than the agent default without overwriting previous spool files with the same name.

To run the command on a Remote System

1. Enter the following required information in the Basic page:
   • Name—ls_cmd
   • Agent name—PROXYAGENT
   • Remote command—ls
   • Remote target—hpserver

     Note: A properties file with the same name as the Remote target must exist on the agent machine.

2. Enter >>/home/user1/test/ls.out in the Spool file field.
3. Click Submit modifier in the left pane.
4. Click Add, and then enter pwd;set>/u1/user1/setTest.out in the table.
5. Click OK.

More information:

Remote Execution Jobs