Automic Workload Automation

Rapid Automation (RA) jobs have attributes that are specific to each particular RA solution. To list all of the job attributes for a given RA solution, run the following query. Replace JobName with the name of a job that uses the solution you’re interested in.

select OCV_VName as Attribute,OCV_Value as Value
from OH join OCV on OH_Idnr=OCV_OH_Idnr
where OH_Name='JobName'

For example, RA Informatica (PowerCenter) jobs have the following attributes:

Just as with other AE object attributes, RA job attributes can be read using GET_ATT and set using :PUT_ATT.

To use the Automation Engine DB change program (ucybchng) to change RA job attributes, just insert the prefix CVALUE: or JPCVALUE: before the name of the attribute:

• CVALUE:attribute changes attributes of stand-alone RA job definitions. E.g., CVALUE:repository
• JPCVALUE:atttribute0 changes attributes of RA job tasks within workflows. E.g., JPCVALUE:repository

If you want to change both a stand-alone RA job and the instances of that job inside workflows, you must define two rules:

1. A rule that changes the attribute of the stand-alone jobs (JOBS objects) using the CVALUE: prefix:
2. Another rule that changes the attribute of the workflow tasks (instances of the jobs inside JOBP objects) using the JPCVALUE: prefix.

For example:

REPLACE JOBS, UC0.MAL.*, CVALUE:repository, UC0.PCE.CONN_DEV, UC0.PCE.CONN_TESTREPLACE JOBP, UC0.MAL.*, JPCVALUE:repository, UC0.PCE.CONN_DEV, UC0.PCE.CONN_TESTREPLACE_PART JOBS, UC0.MAL.*, CVALUE:workFlowName, DEV, TESTREPLACE_PART JOBP, UC0.MAL.*, JPCVALUE:workFlowName, DEV, TEST

If you execute RA jobs from an external application using the AE Java Application Interface, you can also override RA job attributes using the setInstanceParameter() method of the ExecuteObject class. E.g., if you run

exeObj.setInstanceParameter("runInstanceName", "test_run_01");

when submitting an RA Informatica (PowerCenter) job, then this will set the run instance name of the job when it is submitted to PowerCenter.

Attribute values set in this way take precedence over values set in any other way. The order of precedence is:

1. Value set using ExecuteObject.setInstanceParameter()
2. Value set using :PUT_ATT
3. Value set in workflow task
4. Value set in RA job definition

If you want to get a list of all RA job attributes currently defined in an AE system, this query will do the trick:

select distinct JBA_JobType,OCV_VName
from JBA left join OCV on OCV_OH_Idnr=JBA_OH_Idnr
order by JBA_JobType,OCV_VName

This shows only RA attributes for RA solutions for which at least one job exists.

We are in the process of switching from the transport case to XML for moving batches of scheduling objects from one AE system to another. As a part of this, we are developing our own XML change program to replace the role of the AE DB Change program (ucybchng).

Here’s an Xpath that can be used to find (& change) RA job attributes in an AE XML file:

/uc-export//CIT/citcont/cit/component[@xmlName='attribute_name' and @value='old_attribute_value']/@value

See also:

Transport case unload/load vs. XML export/import 

AE XML schema 

XML schema description for AE export file format