Runid Data collector for Unix systems

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

Runid Data collector for Unix

Environment

Release: AOATAM99000-9.0-Automic-One Automation Tools-Application Manager
Component:

Resolution

A Video presentation of the Runid Data collector can be found here ->  Video

 Warning: Objects need to be tested in a test environment before put to use in a production environment!

                We strongly recommend to include the testing of these objects in your upgrade test procedures.

                The runid data collector uses the Utility tools to export Reports and Logfiles directly from the Database.

                See documentation page "Start Parameters - Utilities"  under Archive Utility and "Xunload" function and run tests from the command line"

                (Unix) In some cases you might need to adjust upper and lowercase commands in the script of the object if files are not found.

 Automic tool to export reports (activation, job, agent and server) and Objects as xml of a certain runid::

Attached you will find an object (as xml export) created in Automic Version 9  for an easier automated report capture and xml export.   

This tool will export activation, job, agent and server reports, and xml-export  of a certain runid to a location of your choice.

  Environment needs for objects to work:

.) Unix Agent located on/or access to  a Host where Automic - utilites are installed on

.) It is only possible to export information out of the same client and the client needs to contain a User Object with the same name used for the archive utility connection string.

 Import and adjust to your environment

Download the export from the attachment section at the end of the page !

1.) Import .xml file into your Automic System (the xml contains the objects: "JOBS.EXPORT.REPORTS.RUNID.TEMPLATE.UNIX" and "GET.JOB.INFO"

2.) Enter Host and Login Object into the Attributes tab o fthe object "JOBS.EXPORT.REPORTS.RUNID.TEMPLATE"

 

<Please see attached file for image>

align="baseline" class="documentation" style="display: inline;" border="0" alt=".png" src="http://ecmstage.ca.com/KB%20Asset%20Library/000008447_Embeded/.png" width="966" height="481">

3.) set the destination of the bin folder of the Utility as the Variable &PTOBIN#

 

<Please see attached file for image>

align="baseline" class="documentation" style="display: inline;" border="0" alt=".png" src="http://ecmstage.ca.com/KB%20Asset%20Library/000008447_Embeded/.png" width="967" height="483">

4.) Create a folder that you would like the reports to be exporterd into. (for example /export/data )

5.) Set output location of reports in process tab:

":set &outputlo# = /export/data"

 

<Please see attached file for image>

align="baseline" class="documentation" style="display: inline;" border="0" alt=".png" src="http://ecmstage.ca.com/KB%20Asset%20Library/000008447_Embeded/.png" width="967" height="483">            

Set Archive Utility location:

: Set &Utillo# =""                 
 

<Please see attached file for image>

align="baseline" class="documentation" style="display: inline;" border="0" alt=".png" src="http://ecmstage.ca.com/KB%20Asset%20Library/000008447_Embeded/.png" width="967" height="483">

Execute Objects:

 1.) Execute the object JOBS.EXPORT.REPORTS.RUNID.TEMPLATE"

2.) The Prompt "GET.JOB.INFO" will appear

<Please see attached file for image>

align="bottom" class="documentation" style="display: inline;" border="0" alt=".png" src="http://ecmstage.ca.com/KB%20Asset%20Library/000008447_Embeded/.png" width="448" height="488">

3.) Enter the runid of the Object that you would like to export reports of and click "Done"

4.) After the Job has completed successfully you can find the following data in the folder that you have set for the output.

The Job will export the following information:
All Agentlogfiles that were used by the Runid (Both sender and receiver if Job was a Filetransfer)
All Serverlogfiles that were active during the time of the execution
An xml export of the Job that belongs to the runid
An xml export of the parent Workflow If the job was part of a Workflow
All reports that were written by the Job that belongs to the runid
An xml export of Schedule if Parent object was a schedule that has already ended
Note! Does not work with C-Period Objects.
Note! Only works with Jobs that already have an endstatus.

<Please see attached file for image>

align="bottom" class="documentation" style="display: inline;" border="0" alt=".png" src="http://ecmstage.ca.com/KB%20Asset%20Library/000008447_Embeded/.png" width="816" height="247">