Pre-Con Ed: Configuring CA Workload Automation AE for optimal results

World®
’16
Configuring CA Workload Automation AE
for optimal results
Mike Woods, CA Technologies, Principal Engineering Services Architect
MFX10E
MAINFRAME AND WORKLOAD AUTOMATION

2 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
© 2016 CA. All rights reserved. All trademarks referenced herein belong to their respective companies.
The content provided in this CA World 2016 presentation is intended for informational purposes only and does not form any type of
warranty. The information provided by a CA partner and/or CA customer has not been reviewed for accuracy by CA.
For Informational Purposes Only
Terms of this Presentation

Abstract
As CA Workload Automation AE (CA WLA AE) administrators, providing a robust
and efficient environment is critical. This session will cover managing configuration
parameters in the scheduling engine as well as the UI to ensure smooth operation.
This session will discuss how to configure CA Workload Automation AE (AutoSys®)
to improve efficiency and reduce problems related to configuration.
Michael
Woods
CA Technologies
Principal Engineering
Services Architect

Agenda
WHAT ARE BEST PRACTICES
WORKLOAD AUTOMATION AE
WORKLOAD CONTROL CENTER
EMBEDDED ENTITLEMENTS MANAGER
Q & A
1
2
3
4
5

What is a Best Practice?
Normally reduces issues
§ Not always the same as taking the defaults
§ Has a greater usage in client base
§ Less chance for issues going forward
Not always best for you
§ You may have unique requirements
§ One size does not always fit all

CA Workload Automation AE
§ DBMAINT – Deletes old data from the database
– Default is to run at 3:30
– Should be set to run at a low period
– High volume shops may want to run more than once a day
– Controlled by DBMaintTime setting
– When submitted via scheduler will throw an alarm if errors occur
– DBMaintCmd
§ Default $AUTOSYS/bin/DBMaint
§ Will not pick up any changes to DBMaint script
Configuration Settings

§ IP Caching – Default behavior is to cache the IP address for
agents to improve performance.
– Controlled with EnableIPCaching=0|1
0 means that a dns lookup will occur for each job run. Same as older
releases
1 means that the initial lookup result will be saved and reused.
– as_server impact
0 means that a dns lookup will be used for outbound communication
1 means to use the same IP address used for inbound will be used for
outbound communication

§ LOCALHOST Jobs defined with localhost run where the active
scheduler is located
– That machine must be defined.
– Can be controlled by LocalMachineDefinition=name
§ If not defined defaults to the hostname output

§ Instance Wide Encryption
§ Used for any communication to the Application Server
– WCC
– CLI
– SDK
§ Unrelated to encryption key used for agent communication

§ UseEncryption=0|1|2
0 Specifies that no encryption is used
1 Specifies that a default encryption key is used, the default
2 Specifies that a custom 32 hex key or 16 character pass phrase is used
§ Best practice for a production environment is to use a custom
key.

– Must be set to 0 (None) when R11 agents are used
– Client and WCC configuration must match in order to communicate
– Recommend using a different key per tier to prevent accidental test
jobs running in production

§ Statistical aggregation – used to report on scheduler, event
and job statistics
– Used by WCC reports
– Used by autoaggr to generate cli reports
– Stores data by hour, daily, weekly and monthly units
– Set with AggregateStatistics=0|1
0 Do not aggregate statistics
1 statistics are aggregated, this is the default since 11.3.6 SP2

§ Security modes
– Internal Security – Same model as legacy releases
– External Security – Uses Embedded Entitlements Manager (EEM)
§ Recommended to provide granular security to meet compliance
requirements.
§ Work with your security team to create the best filters to improve
performance. User and Group filters are available.
Implementation

§ Global Variables
– Use same naming convention as jobs to make securing easier
– Do not assign as conditions to too many jobs
§ Changes to value drive the scheduler to validate all associated jobs
§ Can impact performance
– Could a Threshold resource work better?
Implementation

Workload Control Center
§ Views
– Create global views that meet the needs of your different users:
Operations, Application teams
– Restrict views to views < 5000
– Limit who can create views
– Duplicate or wildcard for ALL can hurt performance
Implementation

§ If 11.3 or higher, go to 11.4 for new features and better
performance
– Requires EEM 12.51
§ If 11.3.6 CA WLA AE and using EEM, use a global ECLI user and
restrict access to the Credentials tab
Implementation

Workload Control Center Continued
§ Let users have self-service in production to relieve Operations
from getting overwhelmed and potentially less error prone
– Must be auditable
– Must be secured
§ EEM can audit this activity, your policy secures it

§ Check tuning guide for specific instructions
– Java.Maxmemory is major one
– Two tomcats
– 32 bit – should not exceed 1G
– 64 bit – can be set larger, check what is available on your system
Performance Tuning

Workload Control Center Performance Tuning
§ Linux
install_dir/tomcat/conf/wrapper.conf
# Uncomment this line if the entropy of the UNIX machine is low to speed up
encryption
# The dot between /dev and /urandom is not a mistake
wrapper.java.additional.101=-Djava.security.egd=file:/dev/./urandom
Is now the default setting

Creating the Environment For Users
Define the roles you need:
§ Admin
§ Operations
§ Scheduler
§ Application developer
§ Line or business user

Creating the Environment For Users Continued
§ Define what tabs (applications) each role should have
§ What servers should they have access to?
– Development, UAT, Production
§ What tabs per server?
– Edit for dev, but not for prod?
– Sendevent/monitoring in prod, but no edit
§ What views should they have?

One security mode available:
§ Security is used to determine what will be displayed
– Remove unused tabs
– Reduce questions/issues on features not used or wanted
§ Use security to protect what needs protection and also to
reduce the noise
– Show what they are interested in
Using Security

There are 50+ job types.
§ How many are required?
§ Do you have Oracle® E Business?
§ Do you have SAP®?
§ Do you have PeopleSoft?
§ Do you have z/OS?
§ Do you allow FTP?
Configuration Options

§ General notes for running commands for job types:
— User_name: EEM user, local user with access
— Password: Users EEM password
— Application_name: qedit or appedit
§ Command must be run with a userid able to update log files
§ Use the userid designated at install as the run as user
§ The default is root
Batch Interfaces

Creating a list of desired job types:
§ List available job types to see what is currently available and not
available:
filter_jobtypes -u user_name -p password -t application_name -l
§ Remove job types from being displayed:
filter_jobtypes -u user_name -p password -t application_name –r
all|jobtype1[,jobtype2,…,jobtypex]
Batch Interfaces Continued

Creating a list of desired job types:
§ Add job types to available list:
filter_jobtypes -u user_name -p password -t application_name -a
all|jobtype1[,jobtype2,…,jobtypex]

Creating views in batch:
§ Export a sample view that has your standards
– wcc_monitor -u user_name -p password –x export_file –view
sampleView
§ Edit exported view to replace view name to ‘XXXX’
§ Create script to ‘sed’ template and replace ‘XXXX’ with your application
prefix using your naming convention
§ Import views:
wcc_monitor -u user_name -p password –i input_file

CA Workload Automation Agents
§ Defined Managers
– Do not add unused managers
§ Increases unsent messages if manager does not recognize agent
§ Makes the manager deal with unwanted message (Junk mail)
§ Legacy settings
– If coming from a pre 11.3, use them to get the same behavior
– If brand new, then not as important, but you need to set standards on
how the agents will behave for your end users. Using common settings
will make life easier
Implementation

Questions?

Recommended Sessions
SESSION # TITLE DATE/TIME
MFX12E
Critical Path Analysis with CA Workload Automation (AE)
iDash – Overview
11/14/2016 at 10:00 am
Banyan A/B
MFX20E
Beyond the CA Workload Automation AE CLI –
Leveraging CA WLA AE Web Services
11/14/2016 at 5:00 pm
Jasmine C
MFX27E
Planning Disaster Recovery for CA Workload Automation
AE
11/15/2016 at 9:00 am
Jasmine C
MFX122S Vision and Roadmap: CA Workload Automation AE
11/16/2016 at 12:45pm
Banyan A/B

Must See Demos
Modern
Workload
Automation
CA WLA DE
MF and Workload
Automation
Seamless
Application
Automation
Agents & Advanced
Integrations
MF and Workload
Automation
CA Conversion
as a Service
CA Workload
Automation
MF and Workload
Automation
Innovations:
Cross Enterprise
Workload
Automation
CA WLA AE & DE
MF and Workload
Automation

@CAWORLD #CAWORLD © 2016 CA. All RIGHTS RESERVED.32 @CAWORLD #CAWORLD
Mainframe and Workload Automation
For more information on Mainframe and Workload Automation,
please visit: http://cainc.to/9GQ2JI

Thank you
Stay connected at communities.ca.com

Pre-Con Ed: Configuring CA Workload Automation AE for optimal results

More Related Content

What's hot (20)

Similar to Pre-Con Ed: Configuring CA Workload Automation AE for optimal results (20)

More from CA Technologies (20)

Recently uploaded (20)

Pre-Con Ed: Configuring CA Workload Automation AE for optimal results