Application Services Jobs › HTTP Jobs › Defining HTTP Jobs

Defining HTTP Jobs

You can define an HTTP (HTTP_JOB) job to invoke a program over HTTP.

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

Required Statements

To define an HTTP job, you must specify the following statements:

• AGENT
• INVOCATIONTYPE
• SERVLET_URL

Optional Statements

You can specify the following optional statements for an HTTP job:

• ACTION
• AUTHORDER
• CONNECTIONDOMAIN
• CONNECTIONORIGIN
• CONNECTIONUSER
• FILTER
• JOBCLASS
• PARAMETER
• PROXYDOMAIN
• PROXYHOST
• PROXYORIGIN
• PROXYPORT
• PROXYUSER

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. In this example, the job uses the HTTP GET method to perform the Google search on "ca workload automation". When the job runs, the job's spool file includes all matches that contain the filter AE.

AGENT APPAGENT
INVOCATIONTYPE GET
SERVLET_URL http://google.com/search
PARAMETER KEYWORD(q) VALUE('ca workload automation')
AUTHORDER (BASIC, DIGEST, NTLM)
FILTER .*AE.*

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. The servlet path is /examples/servlets/servlet/TheServlet.

AGENT APPAGENT
INVOCATIONTYPE POST
SERVLET_URL http://localhost:8080
ACTION /examples/servlets/servlet/TheServlet
PARAMETER KEYWORD(key1) VALUE(subscribe)
PARAMETER KEYWORD(key2) VALUE(test@example.com)

Example: Define an HTTP Job to Perform an HTTP Query

This example performs an HTTP query using the HTTP GET method. The output of the invocation is returned in the job's spool file. In this example, the job specifies the connection domain and origin for NTLM authentication, overrides the global proxy defaults specified in the agentparm.txt file, and specifies the user and BASIC, DIGEST, and NTLM protocols for web server authentication.

AGENT APPAGENT
INVOCATIONTYPE GET
SERVLET_URL http://host.example.com/protected IGNORE
CONNECTIONORIGIN host.example.com    
CONNECTIONDOMAIN windows_domain  
AUTHORDER (BASIC, DIGEST, NTLM)
CONNECTIONUSER user1
PROXYDOMAIN http://host.domain.proxy   
PROXYHOST proxy.example.com 
PROXYORIGIN http://host.origin.proxy
PROXYPORT 90
PROXYUSER user01 domain(mydomain)