HCL Workload Automation, Version 9.4

Job definition - OSLC Automation

An OSLC Automation job invokes any OSLC provider that is implementing the OSLC Automation Specification. Automation resources define automation plans, automation requests and automation results of the software development, test and deployment lifecycle. For detailed information, see http://open-services.net/wiki/automation/OSLC-Automation-Specification-Version-2.0/.

This section describes the required and optional attributes for OSLC Automation jobs. Each job definition has the following format and arguments:
Table 1. Required and optional attributes for the definition of an OSLC Automation job.
Attribute Description and value Required
Registry Services URI The address of the Registry Services (for example, https://myhost.mydomain:16311/oslc/pr).  
Registry Services User name The user connecting to the Registry Services.  
Registry Services Password The password associated with the user connecting to the Registry Services.  
Service Provider URI The address of the Service Provider.
Service Provider User name The user connecting to the Service Provider.  
Service Provider Password The password associated with the user connecting to the Service Provider.  
Request The RDF representation of the automation request.
The following example shows a job that schedules an HCL Workload Automation job stream:
    <?xml version="1.0" encoding="UTF-8"?>
<jsdl:jobDefinition xmlns:jsdl="http://www.ibm.com/xmlns/prod/scheduling/1.0/jsdl" 
http://www.ibm.com/xmlns/prod/scheduling/1.0/jsdloslcautomation" name="OSLCAUTOMATION">
  <jsdl:application name="oslcautomation">

<!-- add the rdf representation of the resource -->     


Scheduling and stopping a job in HCL Workload Automation

You schedule HCL Workload Automation OSLC Automation jobs by defining them in job streams. Add the job to a job stream with all the necessary scheduling arguments and submit it.

You can submit jobs using the Dynamic Workload Console or the conman command line.

After submission, when the job is running and is reported in EXEC status in HCL Workload Automation, you can stop it if necessary, by using the kill command from the command line or the Dynamic Workload Console. However, this action is effective only on the HCL Workload Automation job, and it does not affect any processes running on the OSLC Automation workstation. When you stop the HCL Workload Automation job, HCL Workload Automation assigns the Error or ABEND status with return code 0 to the HCL Workload Automation job, regardless of the status of the OSLC Automation job.

Monitoring the job

If the HCL Workload Automation agent stops when you submit the OSLC Automation job or while the job is running, HCL Workload Automation begins monitoring the job from where it stopped.

See also

From the Dynamic Workload Console you can perform the same task as described in

Creating job definitions.

For more information about how to create and edit scheduling objects, see

Designing your Workload.