How to create CA7/Autosys cross instance dependencies via the AAI Custom Condition API

book

Article ID: 210364

calendar_today

Updated On:

Products

Automic Automation Intelligence

Issue/Introduction

When you have both CA7 and Autosys in AAI with cross instance dependencies, you may need to define these Custom Condition dependencies through the REST API.

This depends on how your Autosys and CA7 instances are configured to support the cross instance dependencies.

If you run a "Download Now" from the Admin -> Schedulers tab from the AAI Client, it will download the latest definitions.

Once that completes you can click "View Log" to review a list of unresolved dependencies including cross instance dependencies.

You can use this log to determine if you have many cross instance dependencies.

 

Environment

Release : 6.2.0

Component : AUTOMIC AUTOMATION INTELLIGENCE INTEGRATION FOR CA-7

Resolution

If you need to create the custom conditions via the Custom Condition API which you can access via the url: http://<servername>:8080/aai/devPreview/#/

You would need the POST /customConditions to generate the custom conditions for the cross instance dependencies.

If you expand each select it will show the required fields.

 

 

 

First when doing anything through the API you need to authenticate using the POST /authentication/login api.

If you click the example on the right, it will copy it over to the white space on the left, and you can just update your username and password and click "Try it out" to authenticate.

If you get a 200 response code it was successful, any 400 code is a failure.

Once you authenticate it will generate a token that will allow you to make api calls for a period over time.

 

If you expand the POST /customConditions API you will see the required fields:

The following fields are required for all custom condition types: schedulerName, customConditionType, and jobIdentifier. Types jobDependency, datasetCreating, and jobTrigger require: dependantJobServerName, dependantJobIdentifier. Type jobDependency also requires field 'type'. Type hardStart requires fields: daysOfWeek and startTime.

 

There are 4 custom condition type values you can use:

  • jobDependency
  • hardStart
  • jobTrigger
  • datasetCreating
 
Here are some samples that you can use, you would have to update your scheduler name, jobidentifier, and other fields to match your environment.
 

Autosys to CA7 dataset custom condition:

{
        "schedulerName": "CA7",
        "customConditionType": "datasetCreating",
        "jobIdentifier": "ADCDMST.TRIGGERS.DSB3811",
        "dependantJobServerName": "Autosys scheduler",
        "dependantJobIdentifier": "jobA",
        "offset": "00:00:00",
        "rebuildJobStreams": false
}

CA7 to Autosys job dependency custom condition:

{
        "schedulerName": "Autosys scheduler",
        "customConditionType": "jobDependency",
        "jobIdentifier": "jobA",
        "dependantJobServerName": "CA7",
        "dependantJobIdentifier": "JOBM3811",
        "type": "Success"
}

Autosys to CA7 Trigger custom condition:

{
        "schedulerName": "CA7",
        "customConditionType": "jobTrigger",
        "jobIdentifier": "ZC2C0276",
        "schedId": "000",
        "dependantJobServerName": "Autosys scheduler",
        "dependantJobIdentifier": "jobA",
        "predSchedId": "000"
}

 
 

Below are some of the other attributes you can specify and what values are accepted.

schedulerName

Scheduler name of successor job

 

schedulerId

Any valid JAWS  schedulerId

Only Application Landscape is supported now

customConditionType

jobDependency, hardStart,jobTrigger,datasetCreating

Default is jobDependency

jobId

Job id

Only Application Landscape is supported now

jobIdentifier

Successor job identifier

 

dependantJobServerName

Predecessor job server name

 

dependantJobIdentifier

Predecessor job identifier

 

offset

 

 

duration

 

rebuildJobstreams

boolean

Must be called once for a set of added conditions for the conditions to be used when associating jobs in jobstreams

type

s,f,t,e,success,failure,terminated,exitcode

For Application Landscape, any valid state for the scheduler type is valid, and no abbreviation is allowed.

operator

<,<=,>,>=,=,!=

 

value

 

Value of exit code to compare to

lookbackSecs

Long value in String

 

 

 

 

Attachments