Working with Workload Objects › Application and Web Services Jobs › HTTP Jobs › Define an HTTP Job

Define an HTTP Job

You can define an HTTP job to invoke a program over HTTP. If the host you are connecting to requires user authentication, you must complete the Connection Information page.

Note: To run these jobs, your system requires CA WA Agent for UNIX, Linux, or Windows and CA WA Agent for Application Services.

To define an HTTP job

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 HTTP job from the Application and Web Services group in the Palette view, and drag the job to the workspace.

   The HTTP icon appears on the Application workspace view.

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

   The Basic page of the HTTP 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 lets you invoke a program over HTTP.

   Invocation type

   Indicates the HTTP method type, which can be either GET or POST.

   Default: POST

   URL

   Specifies the host where the program you want to invoke resides. The URL has the following format:

   http://host:port/action

   • host is the name of the computer running the application server.
   • port is the port the host uses to listen for HTTP requests. The default port is 80.
   • (optional) action is the name of the program or servlet to be invoked. If you omit the action, you must enter a value in the Action field.

     Example: http://localhost/cgi-bin/test.sh

     Note: HTTP and HTTPS are supported.

5. (Optional) Specify the following additional information:

   Action

   Specifies the path to the servlet to be invoked.

   Example: /cgi-bin/test.sh

   Note: If you omit this field, you must specify the action in the URL field.

   Filter

   Defines the regular expression to use as a filter. The job spool file will contain lines from the HTTP response that match the filter.

6. Click Action Parameters in the left pane.

   The Action Parameters page opens in the right pane.

7. Complete the following fields for each parameter.

   Parameter Type

   Specifies the variable that the agent passes to the program the job invokes.

   Parameter Value

   Defines a value for the variable specified in the Parameter Type field.

   Note: Click Add to enter a parameter type and parameter value pair.

8. Click Connection Information in the left pane if connection authentication is required.

   The Connection Information page opens in the right pane.

9. Complete the following fields that are required by a website with connection authentication. Speak to your agent administrator for details.

   User

   Specifies the user name required by a website for connection authentication. 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.

   Example: Bob, Production:Bob

   Origin

   Specifies the origin host name for NTLM connection authentication. If unspecified, the origin defaults to the computer name where the agent is running.

   Domain

   Specifies the domain for NTLM connection authentication.

   Don't use global proxy defaults

   Ignores the global proxy configuration specified by the proxy parameters in the agentparm.txt file. Select this option if you want to ignore the proxy for this job only. For example, you might ignore the proxy if the request is going to a server on the LAN that does not require the proxy.

   Authentication order

   Defines a list of protocols to be used by a web server for authentication. If you are connecting to a web server that cannot negotiate authentication protocol, enter the following list in the specified order: BASIC, DIGEST and NTLM.

   Example: BASIC, DIGEST, NTLM

10. Click OK.

    The HTTP job is defined.

Example: Define an HTTP Job to Perform a Google Search

Suppose that you want to define a job to perform a Google search and have the results returned to the job's spool file. You also want to refine your search results by specifying a filter.

To define an HTTP job to perform a Google search

1. Enter the following required information in the Basic page:
   • Name—google
   • Agent name—AGENT
   • Invocation type—GET
   • URL—http://google.com/search
2. Enter .*AutoSys.* in the Filter field.
3. Add the following parameter in the Action Parameters page:
   • Parameter Type—q
   • Parameter Value—ca workload automation
4. Click OK.

   When the job runs, the job spool file will contain all matches that contain the filter AutoSys.

Example: Define an HTTP Job to Subscribe to a Mailing List

Suppose that you want to define a job to subscribe to a mailing list located on a local server. You want to add the email address test@abc.com to the list.

To define an HTTP job to subscribe to a mailing list

1. Enter the following required information in the Basic page:
   • Name—LIST
   • Agent name—AGENT
   • Invocation type—GET
   • URL—http://localhost:8080
   • Action—/examples/servlets/servlet/TheServlet
2. Add the following parameters in the Action Parameters page:
   • Parameter Type—string
   • Parameter Value—subscribe
   • Parameter Type—string
   • Parameter Value—test@abc.com
3. Click OK.

More information:

HTTP Jobs

Configure the Client for a Proxy

Payload Producing and Payload Consuming Jobs

Using a Namespace for a User that has Different Passwords