WATS 2014 WA Agents Overview

© 2014 CA. All rights reserved.

Unlocking the Potential of CA Workload Automation with Agents

October 7, 2014

John CrespinSnr. Principal Consultant

2 © 2014 CA. ALL RIGHTS RESERVED.

Agents and Job Types

System Tasks Application Services Application IntegrationsCommand HTTP ● SAPFTP/SFTP and Secure Copy POJO R/3SNMP Get/Set/Subscribe/Send RMI Job CopyWake-on-LAN JMS Publish/Subscribe BW Process Chain

● z/OS Session Bean BW InfoPackageBatch Job Entity Bean Data ArchivingManual Job MBean Create/Remove (JMX) Batch InputData Set Trigger MBean Get/Set Event Monitor

HP Integrity NonStop MBean Operation/Subscribe Process Monitori Series ● Oracle E-Business Suite

Web Services Single RequestMonitoring RPC/Encoded Request Set

File Trigger / Watcher Document/Literal Copy Single RequestText File Process Automation PeopleSoft PeopleToolsProcess Microsoft SQL ServerCPU Database Integrations Informatica PowerCenterDisk Database Monitor Micro FocusIP Database TriggerWindows Event Log Database Stored Procedure Remote ExecutionWindows Services SQL Remote Execution


Commands







Data Event Sensors







Other






How can you increase the use of the Data Event Sensors?


Many schedules are built with design/process delays

Design – Waiting for a specific time to poll for data(eg. every 2 minutes)

DataEvent

0 Time0 Time

Design



Design – Waiting for a specific time to poll for data(eg. every 2 minutes)Process – Execution of business logic to verify data existence

DataEvent

0 Time0 Time

Design Process



Design – Waiting for a specific time to poll for data(eg. every 2 minutes)Process – Execution of business logic to verify data existenceOther – Inherent Workload Automation product architecture

DataEvent

0 Time0 Time

Design Process Other



Design – Waiting for a specific time to poll for data(eg. every 2 minutes)Process – Execution of business logic to verify data existenceOther – Inherent Workload Automation product architectureData Process – Data being processed by application

DataEvent

0 Time0 Time

Design Process Other Data Process


Design – Waiting for a specific time to poll for data(eg. every 2 minutes)Process – Execution of business logic to verify data existenceOther – Inherent Workload Automation product architectureData Process – Data being processed by application

DataEvent

Data Latency


0 Time0 Time


The time between the data being created and the data being processed


DataEvent

Remove Design and Process delays by the use of Event Sensors

0 Time0 Time


Data Latency


DataEvent

Remove Design and Process delays by the use of Event Sensors

0 Time0 Time

Other Data Process

Data Latency

Using Event Sensors enables the data to be processed quickerwhich leads to more efficient use of production resources andbetter service to your customers.

Event Sensor use cases


Value of using a Database Trigger

Many times a job is run repeatedly to watch for a file or database update. Instead of running the job 1,000+ times per day, use a file monitor or a database trigger to initiate the jobs only when the update happens. This gives the application more of a “real time” feel and reduces the number of jobs run.

Initiating stored procedures directly allows them to be easily scheduled based on database updates


A Database Trigger to detect a table Update and then execute a DB Stored Procedure


Database Trigger with multiple conditions

Eliminate scripting Processing savings Trigger conditions

enable filtering for specific conditions

Can be defined by a scheduler


Approve and Mail Bills

User Action– When the bills are calculated and reviewed, our customer clicks an Approve Button.– When the Approve Button is clicked, the status of the Bills change from “Calculated” to

“Approved” Prior to the Database Agent

– User would contact Operations to have them run the Mail Bills process Using the Database Agent

– Database Monitor on the Bill table– As soon as the button is clicked and the table is updated, the Mail Bills Job is ready to run– Eliminated Manual Intervention and related errors– The system user controls when bills are mailed, without operator intervention


Approve and Mail Bills


Use a Database Trigger for passing messages

Adding a parameter in the agentparm enables passing results of some job types to successor jobs


Job Output Variables for passing results

Job type Return value names

CPU Monitoring counteravail

counterused

loadaverage1m

loadaverage5m

loadaverage15m

Disk Monitoring counteravail

counterused

DB Stored Procedure return

<stored procedure output parameters>

SQL tablerowcount

<selected column names>

SNMP Value Get <SNMP variable OIDs>

SNMP Value Set <updated variable SNMP OID>

JMX-MBean Attribute Get variable_jmx_mbeanattr

JMX-MBean Attribute Set variable_jmx_mbeanattrJMX-MBean Operation value


JMS Subscribe Wait for message to be published Save message to a specific location Pass location to another job to read msg


Monitor a file system for a certain amount of free space

Should free space left be within a certain range, launch a clean-up process on that server

Open up Service Desk ticket

Disk Monitor to monitor available space

Other use cases


Reduce FTP processing exceptions

IP Monitor to check if the FTP server is available instead of waiting for an FTP process to timeout

Text Monitor to verify file contents


Text File Monitor after FTP to check for Empty File


Verify the status of a Unix process or Windows Service

Does the process or service need to be in a certain status before a job executes?– Wait for that particular status; saves time

If a process changes status, do you need to run some procedure– Create a Service Desk ticket– Restart the service


After a SQL Select, get the table row count from the Select


SQL Server integration

Visibility into SQL Server Jobs Restart from a failed step


What’s MS SQL Server Agent? • Windows service that execute jobs in sql server

MS SQL Server Agent components– Job is a specific series of action that MS SQL Server Agent perform. A job can include

multiple job steps– Job step is a action in a job. A job step must be of one of following types,

• Microsoft ActiveX Script• Operating System (CmdExec)• PowerShell• Replication Distributor• Replication Merge• Replication Queue Reader• Replication Snapshot• Replication Transaction Log Reader• Analysis Services Command• Analysis Services Query• SSIS package execution• T-SQL Script (Transact-SQL)

– Schedules specifies when job run– Alerts is automatic response to specific event– Operator defines contact info of person who maintain sql server. Can be notified of alerts– Proxy defines security context for a job step

SQL Server integration integration


Informatica

Will replace many scripts presently being used


Developer’s view on using Web services

“My preference has been to use the scheduler to make web service calls as opposed to direct database stored procedure calls for a couple of reasons. First, it better choices for languages and technologies. My language of choice is C#, so I can use that to write functionality I want scheduled instead of writing in PL/SQL.

Along those same lines, separating the logic away from the data storage means more flexibility, so for instance, in web service code I can easily connect to multiple databases from different vendors, perform network file system I/O, call additional web services, etc. I can do that stuff with ease using a good language and web service framework whereas with database code in PL/SQL or T-SQL it would be difficult and in some cases impossible.

We also like the idea of a service-oriented architecture, where info and functionality is exposed in a standard way (SOAP over HTTP) so virtually any client can consume or execute functionality without having to know how to connect to a particular database, etc. For example, I could create a web service that processes some financial data, and have the scheduler set up to run that every night. If later on the need arises to allow a user to process the data on-demand using a smart phone, it would be trivial to wire up a mobile app or mobile web page to call that service. The same isn’t necessarily true if we were to set up database code and have the scheduler call into that directly every night.”


SoapUI example executing a Web Service


Executing a Web Service using the Web Service Agent


Web Services Operation Parameters


The Spoolfile output of the Application

Scripting best practices


Keep Track of the Highest return code

ESPmgr "%2/%ESPAPPL%.%ESPAPGEN%/MAIN State EXEC Status(Executing Phase 1)"

REM Phase 1c:/Scripts/sleep.exe %1

set highrc=%errorlevel%

ESPmgr "%2/%ESPAPPL%.%ESPAPGEN%/MAIN State EXEC Status(Phase 1 Complete - RC=%errorlevel%)"

REM Phase 2c:\Scripts\sleep.exe %1

set highrc=1

ESPmgr "%2/%ESPAPPL%.%ESPAPGEN%/MAIN State EXEC Status(Phase 2 complete - RC=%highRC%)"

REM Phase 3c:\Scripts\sleep.exe %1

if "%errorlevel%" EQU "0" (echo SUCCESS) else (set highrc=%errorlevel%)

ESPmgr "%2/%ESPAPPL%.%ESPAPGEN%/MAIN STATE EXEC Status(Phase 3 complete - RC=%errorlevel%)"

REM Script Endif "%highrc%" EQU "0" (exit) else (

ESPmgr "%2/%ESPAPPL%.%ESPAPGEN%/MAIN STATE EXEC Status(Script complete)"

"%ESPAGENTDIR%\SetExitC" %highrc%)


Use variable for Agent Directory when using custom scripts to execute an Agent executable To make sure there are no script changes when the Agent is

upgraded and the directory name is changed.


ESPAGENTDIR=C:\Program Files\CA\Workload Automation R11.3\ESPSystemAgentSP1


Include a “set” to “see” the environment variables----------------------------------------------------------------Output of messages for workload object SET_COMMAND/SET_COMMAND.2/MAINStart date Tue Mar 04 10:02:27 2014----------------------------------------------------------------

C:\Program Files\CA\Workload Automation R11.3\ESPSystemAgentSP1>echo on

C:\Program Files\CA\Workload Automation R11.3\ESPSystemAgentSP1>setALLUSERSPROFILE=C:\ProgramDataANT_HOME=C:\apache-ant-1.8.4APPDATA=C:\Windows\system32\config\systemprofile\AppData\Roamingasl.log=Destination=fileCAI_CAFT=C:\Program Files (x86)\CA\SC\CAMCAI_MSQ=C:\Program Files (x86)\CA\SC\CAMCASHCOMP=C:\Program Files\CA\SharedComponents\CommonProgramFiles=C:\Program Files\Common FilesCommonProgramFiles(x86)=C:\Program Files (x86)\Common FilesCommonProgramW6432=C:\Program Files\Common FilesCOMPUTERNAME=ROOJO02-W7ComSpec=C:\Windows\system32\cmd.exeCSAM_LOGGER_CONF=C:\Program Files (x86)\CA\SC\Csam\SockAdapter\\cfg\logger.cfgCSAM_SOCKADAPTER=C:\Program Files (x86)\CA\SC\Csam\SockAdapter\DEFLOGDIR=C:\ProgramData\McAfee\DesktopProtectionESPAGENT=AGENTESPAGENTDIR=C:\Program Files\CA\Workload Automation R11.3\ESPSystemAgentSP1ESPAGENTHASH=770B8D4CAA6A4DCC35DDCB75341C96327E2729BAESPAGENTPORT=7520ESPAGENTSPOOL=C:/Program Files/CA/Workload Automation R11.3/ESPSystemAgentSP1/spoolESPAGENTTOKEN=4A5052ESPAPGEN=2ESPAPPL=SET_COMMANDESPAPPLMGR=JavaAgent#tcpip@DSERIES113ESPOBJECT=SET_COMMAND/SET_COMMAND.2/MAINESPWOB=SET_COMMANDETPKIHOME=C:\PROGRA~1\CA\SHARED~1\FP_NO_HOST_CHECK=NOJAVA_HOME=C:\Program Files\Java\jdk1.6.0_30


Use Echo to see output

----------------------------------------------------------------Output of messages for workload object XCOM_TEST/XCOM_TEST.1/MAINStart date Tue Mar 04 10:38:03 2014----------------------------------------------------------------

C:\Program Files\CA\Workload Automation R11.3\ESPSystemAgentSP1>echo ECHO is on.

C:\Program Files\CA\Workload Automation R11.3\ESPSystemAgentSP1>XCOPY /y "c:\scripts\XCOM_Template.txt" "c:\Scripts\XCOM_xferparms.cnf" C:\scripts\XCOM_template.txt1 File(s) copied

C:\Program Files\CA\Workload Automation R11.3\ESPSystemAgentSP1>echo REMOTE_SYSTEM=141.202.65.31 1>>c:\Scripts\XCOM_xferparms.cnf

C:\Program Files\CA\Workload Automation R11.3\ESPSystemAgentSP1>echo FILE_OPTION=CREATE 1>>c:\Scripts\XCOM_xferparms.cnf

C:\Program Files\CA\Workload Automation R11.3\ESPSystemAgentSP1>echo REMOTE_FILE=XCOM.ROOJO02.NEW3 1>>c:\Scripts\XCOM_xferparms.cnf

C:\Program Files\CA\Workload Automation R11.3\ESPSystemAgentSP1>echo LOCAL_FILE=C:\Prod\XCOM\newdoc 1>>c:\Scripts\XCOM_xferparms.cnf

C:\Program Files\CA\Workload Automation R11.3\ESPSystemAgentSP1>CD C:\XCOMNT

C:\Xcomnt>xcomtcp.exe -c1 -f c:\Scripts\XCOM_xferparms.cnf XCOMN0650E XCOM_HOME is not set.

---------------- The end of the file ----------------


Set variables for Home before executing scripts


Spoolfile output showing the Home has been changed

----------------------------------------------------------------Output of messages for workload object D_DRIVE_TEST/D_DRIVE_SCRIPT_TEST.10/MAINStart date Tue Mar 04 11:08:21 2014----------------------------------------------------------------

D:\Scripts\dSeriesR113>Echo this is from drive D this is from drive D

D:\Scripts\dSeriesR113>Set

D:\Scripts\dSeriesR113>dir Volume in drive D is New Volume Volume Serial Number is F80D-5797

Directory of D:\Scripts\dSeriesR113

10/22/2013 08:37 AM <DIR> .10/22/2013 08:37 AM <DIR> ..08/29/2002 07:00 AM 114,688 calc.exe05/03/2012 10:43 PM 36 Clean-up_FTP_test_File.batt.exe06/06/2013 03:58 PM 7 setcc.bat06/06/2012 09:18 AM 91 sleep.bat04/09/2006 01:36 PM 28,432 Sleep.exe12/21/2011 10:48 AM 149 Trigger_test.bat02/28/2007 12:14 PM 65 xmit.bat 30 File(s) 196,443 bytes 2 Dir(s) 13,617,160,192 bytes free

D:\Scripts\dSeriesR113>sleep.bat 30

D:\Scripts\dSeriesR113>echo This is the whole argument that was passed = 30 This is the whole argument that was passed = 30

D:\Scripts\dSeriesR113>C:\Scripts\dSeriesR113\sleep.exe 30 ---------------- The end of the file ----------------


Copy Spoolfile to another directory

The Manager name is part of the environment variable ESPAPPLMGR. So, you will need to parse that variable to get the Manager name part. This is an example of the ESPAPPLMGR value. The Manager name is DSERIES113.

ESPAPPLMGR=JavaAgent#tcpip@DSERIES113

if "%highrc%" EQU "0" (exit) else (

ESPmgr "%2/%ESPAPPL%.%ESPAPGEN%/MAIN STATE EXEC Status(Script complete)"

For /f "tokens=2 delims==@" %%i in ("%ESPAPPLMGR%") do (set mgrname=%%i)

echo f | XCOPY /f /y "%ESPAGENTSPOOL%\%mgrname%\MAIN\%ESPAPPL%.%ESPAPGEN%\%ESPWOB%" "c:\Main\logs\%ESPWOB%%DATE%“


C:\Program Files\CA\Workload Automation R11.3\ESPSystemAgentSP1>For /F "tokens=2 delims==@" %i in ("JavaAgent#tcpip@DSERIES113") do (set mgrname=%i )

C:\Program Files\CA\Workload Automation R11.3\ESPSystemAgentSP1>(set mgrname=DSERIES113 )

C:\Program Files\CA\Workload Automation R11.3\ESPSystemAgentSP1>echo f | XCOPY /f /y "C:/Program Files/CA/Workload Automation R11.3/ESPSystemAgentSP1/spool\DSERIES113\MAIN\3_COPY_JOBLOG.3\JOB_WAITING_2" "c:\Main\logs\JOB_WAITING_2Thursday13thMar2014" Does C:\Main\logs\JOB_WAITING_2Thursday13thMar2014 specify a file nameor directory name on the target(F = file, D = directory)? fC:\Program Files\CA\Workload Automation R11.3\ESPSystemAgentSP1\spool\DSERIES113\MAIN\3_COPY_JOBLOG.3\JOB_WAITING_2 -> C:\Main\logs\JOB_WAITING_2Thursday13thMar20141 File(s) copied


php example using the API ESPMgr


php example using the API ESPMgr


Using the API ESPLMI example

Summary


Summary of CA Workload Automation Agent Capabilities

– Execute Commands– Detect data events– Verify application statuses– Visibility/integration to 3rd party applications– Industry Standard APIs to business application process servers– Secure connections to exchange data


Business Value of the CA Workload Automation Agent

– Data Event Sensors are always active Event can happen once a day or thousands of times

– Less job executions Jobs are run when data is created

– Reduced Application Development Time Fill in the blanks enable quick definitions for the Application Integration Job

Types Replaces some scripting


Please join the CA Communities

Sr. Principal Consultant

[email protected]

@Crespin_john

slideshare.net/CAinc

linkedin.com/company/ca-technologies

https://communities.ca.com/web/ca-workload-automation-mainframe-global-user-community/welcome

ca.com

John Crespin

Questions?


Copyright © 2014 CA. All rights reserved. IBM, System z, zEnterprise, zSeries, z/OS, z/VM, RACF, CICS, IMS and DB2 are trademarks of International Business Machines Corporation in the United States, other countries, or both. Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries. All trademarks, trade names, service marks and logos referenced herein belong to their respective companies.

This presentation was based on current information and resource allocations as of October 2014 and is subject to change or withdrawal by CA at any time without notice. Notwithstanding anything in this presentation to the contrary, this presentation shall not serve to (i) affect the rights and/or obligations of CA or its licensees under any existing or future written license agreement or services agreement relating to any CA software product; or (ii) amend any product documentation or specifications for any CA software product. The development, release and timing of any features or functionality described in this presentation remain at CA’s sole discretion. Notwithstanding anything in this presentation to the contrary, upon the general availability of any future CA product release referenced in this presentation, CA will make such release available (i) for sale to new licensees of such product; and (ii) to existing licensees of such product on a when and if-available basis as part of CA maintenance and support, and in the form of a regularly scheduled major product release. Such releases may be made available to current licensees of such product who are current subscribers to CA maintenance and support on a when and if-available basis. In the event of a conflict between the terms of this paragraph and any other information contained in this presentation, the terms of this paragraph shall govern.

Certain information in this presentation may outline CA’s general product direction. All information in this presentation is for your informational purposes only and may not be incorporated into any contract. CA assumes no responsibility for the accuracy or completeness of the information. To the extent permitted by applicable law, CA provides this presentation “as is” without warranty of any kind, including without limitation, any implied warranties or merchantability, fitness for a particular purpose, or non-infringement. In no event will CA be liable for any loss or damage, direct or indirect, from the use of this document, including, without limitation, lost profits, lost investment, business interruption, goodwill, or lost data, even if CA is expressly advised in advance of the possibility of such damages. CA confidential and proprietary. No unauthorized copying or distribution permitted.

CA does not provide legal advice. Neither this document nor any CA software product referenced herein shall serve as a substitute for your compliance with any laws (including but not limited to any act, statute, regulation, rule, directive, policy, standard, guideline, measure, requirement, administrative order, executive order, etc. (collectively, “Laws”)) referenced in this document. You should consult with competent legal counsel regarding any Laws referenced herein.

This Presentation IsFor Informational Purposes Only

Technology

WATS 2014 WA Agents Overview