WATS 2014 WA Agents Overview - CA Workload Automation Technology Summit (WATS) 2014

Unlocking the Potential of CA
Workload Automation with
Agents
October 7, 2014
John Crespin
Snr. Principal Consultant
© 2014 CA. All rights reserved.

Agents and Job Types
System Tasks Application Services Application Integrations
Command HTTP ● SAP
FTP/SFTP and Secure Copy POJO R/3
SNMP Get/Set/Subscribe/Send RMI Job Copy
Wake-on-LAN JMS Publish/Subscribe BW Process Chain
● z/OS Session Bean BW InfoPackage
Batch Job Entity Bean Data Archiving
Manual Job MBean Create/Remove (JMX) Batch Input
Data Set Trigger MBean Get/Set Event Monitor
HP Integrity NonStop MBean Operation/Subscribe Process Monitor
i Series ● Oracle E-Business Suite
Web Services Single Request
Monitoring RPC/Encoded Request Set
File Trigger / Watcher Document/Literal Copy Single Request
Text File Process Automation PeopleSoft PeopleTools
Process Microsoft SQL Server
CPU Database Integrations Informatica PowerCenter
Disk Database Monitor Micro Focus
IP Database Trigger
Windows Event Log Database Stored Procedure Remote Execution
Windows Services SQL Remote Execution
2 © 2014 CA. ALL RIGHTS RESERVED.

Commands
IP Database Trigger

Data Event Sensors
IP Database Trigger

Other
IP Database Trigger

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

Many schedules are built with design/process delays
Design
0 Time
Design – Waiting for a specific time to poll for data(eg. every 2 minutes)
Data
Event

Design Process
0 Time
Process – Execution of business logic to verify data existence
Data
Event

Design Process Other
0 Time
Other – Inherent Workload Automation product architecture
Data
Event

Design Process Other Data Process
0 Time
Data Process – Data being processed by application
Data
Event

Data Latency
The time between the data being
created and the data being processed
0 Time
Data Process – Data being processed by application
Data
Event

Remove Design and Process delays by the use of Event
Sensors
Data
Event
Data Latency
0 Time

Remove Design and Process delays by the use of Event
Sensors
Data
Event
Data Latency
Other Data Process
0 Time
Using Event Sensors enables the data to be processed quicker
which leads to more efficient use of production resources and
better service to your customers.

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_mbeanattr
JMX-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

Disk Monitor to monitor available space
 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

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

SQL Server integration integration
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

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

Keep Track of the Highest return code
ESPmgr "%2/%ESPAPPL%.%ESPAPGEN%/MAIN State EXEC Status(Executing Phase 1)"
REM Phase 1
c:/Scripts/sleep.exe %1
set highrc=%errorlevel%
ESPmgr "%2/%ESPAPPL%.%ESPAPGEN%/MAIN State EXEC Status(Phase 1 Complete - RC=%errorlevel%)"
REM Phase 2
c:Scriptssleep.exe %1
set highrc=1
ESPmgr "%2/%ESPAPPL%.%ESPAPGEN%/MAIN State EXEC Status(Phase 2 complete - RC=%highRC%)"
REM Phase 3
c:Scriptssleep.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 End
if "%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 FilesCAWorkload Automation R11.3ESPSystemAgentSP1

Include a “set” to “see” the environment variables
----------------------------------------------------------------
Output of messages for workload object SET_COMMAND/SET_COMMAND.2/MAIN
Start date Tue Mar 04 10:02:27 2014
----------------------------------------------------------------
C:Program FilesCAWorkload Automation R11.3ESPSystemAgentSP1>echo on
C:Program FilesCAWorkload Automation R11.3ESPSystemAgentSP1>set
ALLUSERSPROFILE=C:ProgramData
ANT_HOME=C:apache-ant-1.8.4
APPDATA=C:Windowssystem32configsystemprofileAppDataRoaming
asl.log=Destination=file
CAI_CAFT=C:Program Files (x86)CASCCAM
CAI_MSQ=C:Program Files (x86)CASCCAM
CASHCOMP=C:Program FilesCASharedComponents
CommonProgramFiles=C:Program FilesCommon Files
CommonProgramFiles(x86)=C:Program Files (x86)Common Files
CommonProgramW6432=C:Program FilesCommon Files
COMPUTERNAME=ROOJO02-W7
ComSpec=C:Windowssystem32cmd.exe
CSAM_LOGGER_CONF=C:Program Files (x86)CASCCsamSockAdaptercfglogger.cfg
CSAM_SOCKADAPTER=C:Program Files (x86)CASCCsamSockAdapter
DEFLOGDIR=C:ProgramDataMcAfeeDesktopProtection
ESPAGENT=AGENT
ESPAGENTDIR=C:Program FilesCAWorkload Automation R11.3ESPSystemAgentSP1
ESPAGENTHASH=770B8D4CAA6A4DCC35DDCB75341C96327E2729BA
ESPAGENTPORT=7520
ESPAGENTSPOOL=C:/Program Files/CA/Workload Automation
R11.3/ESPSystemAgentSP1/spool
ESPAGENTTOKEN=4A5052
ESPAPGEN=2
ESPAPPL=SET_COMMAND
ESPAPPLMGR=JavaAgent#tcpip@DSERIES113
ESPOBJECT=SET_COMMAND/SET_COMMAND.2/MAIN
ESPWOB=SET_COMMAND
ETPKIHOME=C:PROGRA~1CASHARED~1
FP_NO_HOST_CHECK=NO
JAVA_HOME=C:Program FilesJavajdk1.6.0_30

Use Echo to see output
----------------------------------------------------------------
Output of messages for workload object XCOM_TEST/XCOM_TEST.1/MAIN
----------------------------------------------------------------
C:Program FilesCAWorkload Automation R11.3ESPSystemAgentSP1>echo
ECHO is on.
C:Program FilesCAWorkload Automation R11.3ESPSystemAgentSP1>XCOPY /y "c:scriptsXCOM_Template.txt"
"c:ScriptsXCOM_xferparms.cnf"
C:scriptsXCOM_template.txt
1 File(s) copied
C:Program FilesCAWorkload Automation R11.3ESPSystemAgentSP1>echo REMOTE_SYSTEM=141.202.65.31
1>>c:ScriptsXCOM_xferparms.cnf
C:Program FilesCAWorkload Automation R11.3ESPSystemAgentSP1>echo FILE_OPTION=CREATE 1>>c:ScriptsXCOM_xferparms.cnf
C:Program FilesCAWorkload Automation R11.3ESPSystemAgentSP1>echo REMOTE_FILE=XCOM.ROOJO02.NEW3
C:Program FilesCAWorkload Automation R11.3ESPSystemAgentSP1>echo LOCAL_FILE=C:ProdXCOMnewdoc
C:Program FilesCAWorkload Automation R11.3ESPSystemAgentSP1>CD C:XCOMNT
C:Xcomnt>xcomtcp.exe -c1 -f c:ScriptsXCOM_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/MAIN
----------------------------------------------------------------
D:ScriptsdSeriesR113>Echo this is from drive D
this is from drive D
D:ScriptsdSeriesR113>Set
D:ScriptsdSeriesR113>dir
Volume in drive D is New Volume
Volume Serial Number is F80D-5797
Directory of D:ScriptsdSeriesR113
10/22/2013 08:37 AM <DIR> .
10/22/2013 08:37 AM <DIR> ..
08/29/2002 07:00 AM 114,688 calc.exe
05/03/2012 10:43 PM 36 Clean-up_FTP_test_File.bat
t.exe
06/06/2013 03:58 PM 7 setcc.bat
06/06/2012 09:18 AM 91 sleep.bat
04/09/2006 01:36 PM 28,432 Sleep.exe
12/21/2011 10:48 AM 149 Trigger_test.bat
02/28/2007 12:14 PM 65 xmit.bat
30 File(s) 196,443 bytes
2 Dir(s) 13,617,160,192 bytes free
D:ScriptsdSeriesR113>sleep.bat 30
D:ScriptsdSeriesR113>echo This is the whole argument that was passed = 30
This is the whole argument that was passed = 30
D:ScriptsdSeriesR113>C:ScriptsdSeriesR113sleep.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:Mainlogs%ESPWOB%%DATE%“
C:Program FilesCAWorkload Automation R11.3ESPSystemAgentSP1>For /F "tokens=2 delims==@" %i in ("JavaAgent#tcpip@DSERIES113") do (set
mgrname=%i )
C:Program FilesCAWorkload Automation R11.3ESPSystemAgentSP1>(set mgrname=DSERIES113 )
C:Program FilesCAWorkload Automation R11.3ESPSystemAgentSP1>echo f | XCOPY /f /y "C:/Program Files/CA/Workload Automation
R11.3/ESPSystemAgentSP1/spoolDSERIES113MAIN3_COPY_JOBLOG.3JOB_WAITING_2" "c:MainlogsJOB_WAITING_2Thursday13thMar2014"
Does C:MainlogsJOB_WAITING_2Thursday13thMar2014 specify a file name
or directory name on the target
(F = file, D = directory)? f
C:Program FilesCAWorkload Automation R11.3ESPSystemAgentSP1spoolDSERIES113MAIN3_COPY_JOBLOG.3JOB_WAITING_2 ->
C:MainlogsJOB_WAITING_2Thursday13thMar2014
1 File(s) copied

php example using the API ESPMgr

Using the API ESPLMI example

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

John Crespin
Sr. Principal Consultant
John.Crespin@ca.com
@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

This Presentation Is
For Informational Purposes Only
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.

WATS 2014 WA Agents Overview - CA Workload Automation Technology Summit (WATS) 2014

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (13)

Similar to WATS 2014 WA Agents Overview - CA Workload Automation Technology Summit (WATS) 2014

Similar to WATS 2014 WA Agents Overview - CA Workload Automation Technology Summit (WATS) 2014 (20)

More from Extra Technology

More from Extra Technology (8)

Recently uploaded

Recently uploaded (20)

WATS 2014 WA Agents Overview - CA Workload Automation Technology Summit (WATS) 2014