253_WA_AE_r11-3-6_Cookbook

CA Workload Automation AE r11.3.5 / r11.3.6 Support Cookbook

TECHNICAL PAPER: CA Workload Automation AE r11.3.5 / r11.3.6 Support Cookbook


The information in this document is usable on all WA AE certified Linux, UNIX, and Windows platforms.

SEPTEMBER 2013

David W. Martin

Joseph E. Neumann

Lee Peterson

Chinni Krishna

CA Workload Automation Development and Support Teams


Updated September 20, 2013, 16:53 CST.

This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the Documentation) is for your informational purposes only and is subject to change or withdrawal by CA at any time.

This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and CA.

Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy.

The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.

TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION AS IS WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, 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 LOSS OR DAMAGE.

The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice.

The manufacturer of this Documentation is CA.

Provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors.

Copyright 2013 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their

respective companies.


Table of Contents

EXECUTIVE SUMMARY 4

Challenge 4

Opportunity 4

Benefits 4

Information Application With r11.3.5 and r11.3.6 4

Section 1: CACDF Topic 5

CA CDF Usage with AE r11.3.5 5

CA CDF Example 6

CA Remote Engineer Usage with AE r11.3.6 9

Section 2: Install Caveats To Be Aware Of 10

EEM Install and a Non-root User 10

EEM Install and IPv6 11

Section 3: AE Topics 12

AE Directory and File Permissions 12

Upgrade AutoSys and WCC 14

General Principles 14

Upgrade Steps 14

Upgrade the CA EEM Server 16

Upgrade from AutoSys 4.5x or r11 to AE r11.3.5 17

Upgrade AutoSys 4.5x or r11 to AE r11.3.5 (Oracle) 17

Upgrade from AE r11.3 to AE r11.3.5 34

Upgrade AE r11.3 to AE r11.3.5 (Oracle) 35

Upgrade AE r11.3 to AE r11.3.5 (Sybase) 43

Migrate an AE r11.3 Database Manually to AE r11.3.5 52

AE r11.3.5 Port Architecture 54

Repair an AE r11.3.5 Installation 55

Use the DataMover Application for Data Migrations 62

Unattended AE Install Failure Return Code Meanings 64

Create Oracle Tablespaces, Users, and Roles 66

Configure an Agent to be Compatible with AE 68

Clean Up After a Catastrophic Install or Uninstall Failure on UNIX 71

Clean Up After a Catastrophic Install or Uninstall Failure on Windows 77

80

Debug Options, Environment Variables, and Tracing 81

AE Installation Environment Variables 81

AE Installation Tracing 83

AE Interview Forward and Backward Navigation Logic Flow 86

AE Interview Database Connection Test 88

Section 4: Benefits 90

Assist the Customer Enable Technical Support 90

Assist the Customer 90

Enable Technical Support 90

Section 5 90

Conclusions 90

Section 6 90

References 90

Section 7 91

About the Authors 91


Executive Summary

Challenge New releases of the WA AE product have had a number of significant architectural changes to the product to improve its performance and robustness. These changes have resulted in differences in production installation and migration including an increase in information that is required to be specified. Though the bulk of the information is listed in the various platform Installation Guides, User Reference Manuals and specific Release Notes, an overall walkthrough of the install has not always been readily available in one place. This direct walkthrough document is being made available here.

This document will not only help customers prepare for and perform installs, but it will help provide discussion points for CA Technologies Technical Support (Level 1 support) staff when customers call in with problems they encountered. By indicating where specifically in the install a problem arose, and what it was, Level 1 Support will better able to resolve installation and migration issues in less time.

Opportunity As opportunities are discovered that can improve product installation and migration, they will be incorporated within this document. Thus this document is expected to be updated over time to continue to provide the most current steps to successfully complete an installation and migration.

Benefits Creating the CA Workload Automation AE r11.3.5 / r11.3.6 cookbook before the product is released as generally available gives customers and Technical Support an important advantage, as a new set of questions and concerns will begin to emerge. Being equipped with knowledge and results from those who have already experienced these situations, or who have answered the questions, gives Technical Support the tools to resolve concerns and answer questions. The end result is a satisfied customer and a confident and helpful Technical Support representative.

Information Application With r11.3.5 and r11.3.6 All CA Workload Automation AE r11.3.5 information in this cookbook applies to r11.3.6. In the few instances where r11.3.6 is specified, the information applies only to r11.3.6.


Section 1: CACDF Topic

CA CDF Usage with AE r11.3.5

The CA Common Diagnostic facility (CA CDF) is a tool provided by CA Technologies to automate the collection of problem-

Note: CA Workload Automation AE r11.3.6 ships the next version of CA CDF, renamed to CA Remote Engineer. See section CA Remote Engineer Usage with AE r11.3.6 for more information.

CA Workload Automation AE (AE) r11.3.5 leverages the capabilities of CA CDF, and therefore, is shipped on the DVD. The intent of CA CDF is to:

Minimize the amount of time required to collect the appropriate data

Standardize the type of data collected

Reduce the amount of customer skills required to process diagnostic data

This section provides the essential information to gather AE diagnostic data and log files. The latest version of CA CDF can be downloaded at: http://cacdf.ca.com. For additional information about CA CDF, including design documents, please refer to the official guide, CA CDF Script File Command Syntax Guide, located at the following link: https://km.ca.com/technicalsupport/advisors/CACDF/Shared%20Documents/CACDF%20Docs/cacdf_internal_support_guide_2012Dec16.docx

To use CA CDF to gather diagnostic information about AE

1. CA CDF is not installed on the server when the AE components are installed. Rather, CA CDF is located on the DVD in the CACDF directory. For example:

# [/bld/dev/prod/WAAE/11.3.5/build/unix/D VD] ls

acknowledgements.txt AIX CACDF Documentation HP- UX HP- UX_IA64 Linux Solaris - Sparc VendorEULA.txt

wa_setup.sh

In the CACDF directory is a gz tar file. For example:

# [/bld/dev/prod/WAAE/11.3.5/build/unix/DVD] ls CACDF

cacdf.tar.gz

To use CA CDF, you must copy the cacdf.tar.gz file to a directory on the server and extract it. For example, to copy the file to /tmp and extract it, run the following commands:

# cp CACDF/cacdf.tar.gz /tmp

# cd /tmp

# gunzip cacdf.tar.gz

# tar xf cacdf.tar

2. The contents of the extracted tar file are listed below.

# ls

cacdf cacdf.tar README.txt

# cd /tmp/cacdf

# ls

ac.txt d2d.txt mswin32 SCC.txt

aix docfile.txt NSM_ADEM.txt scriptpw.exe

apm.txt drivearray.vbs NSM_ATECH.txt ServerAutomation.txt

arcserve.txt dsm.txt NSM_DIA.txt Service_Desk.txt

Audit.txt DVS.txt NSM_DSM.txt SOI.txt

CACDF_Automation_File_Gen.vbs EEM.txt NSM_EM_UNIX.txt solaris
http://cacdf.ca.com/https://km.ca.com/technicalsupport/advisors/CACDF/Shared%20Documents/CACDF%20Docs/cacdf_internal_support_guide_2012Dec16.docxhttps://km.ca.com/technicalsupport/advisors/CACDF/Shared%20Documents/CACDF%20Docs/cacdf_internal_support_guide_2012Dec16.docx


cacdf.cmd GenCACDFTemplate.sh NSM_JMO.txt sso.txt

CACDF_Keys_Extractor_32b it.vbs getdrwatson.vbs NSM_WEBGUI.txt treeview.css

CACDF_Keys_Extractor_64bit.vbs getevents.vbs NSM_WORLDVIEW.txt treeview.dtd

CACDF_Keys_Extractor.vbs gethwinfo.vbs osdoc_AIX.txt treeview - explorer.xml

cacdf.sh getprod.vbs osdoc_HPUX.txt treeview.js

CAPC.txt getsoftfeat.vbs osdoc_Linux.txt treeview.xslt

cappm.txt hpux osdoc_Solaris.txt UCMonitor.txt

caprodreg.vbs httpget.cmd osdoc_Windows 2000.txt version.txt

caprodregxml.vbs httpget.sh osdoc_Windows 2003.txt WAAE.txt

Catalyst_CACDF_T emplate.txt Hyperformix_CCC.sql osdoc_Windows.txt WCC.txt

catalystpost.cmd Hyperformix_CCC.txt osdoc_Windows Vista.txt wily.txt

catalystpost.sh IMDataAggregator.txt osdoc_Windows XP.txt xosoft.txt

catalys tpre.cmd imgs PAM.txt

catalystpre.sh ini_it.vbs pw.vbs

cca.txt linux README.txt

The two files of interest are cacdf.sh and WAAE.txt. The cacdf.sh script collects the information based on what is contained in WAAE.txt. If you edit WAAE.txt, you will see a number of commands and a number of files. One of the commands, as_info -a is the gathers most of the information.

To run CA CDF, first set the AE environment and then run the cacdf.sh script. For example:

# . /opt/CA/WorkloadAutomationAE/autouser.ACE/*bash*

# ./cacdf.sh

You are prompted to enter the following information so that the proper information can be gathered and compressed into the zip file:

CA Support Contact Number CA Support Issue Number CA Site ID CA Product for which problem was opened

To gather diagnostic information for AE, enter WAAE when you are prompted for the name of the CA product that is affected. Also, you can gather information for Embedded Entitlements Manager or Workload Command Center diagnosis by entering, respectively, EEM or WCC.

Once this information has been entered and validated, the utility may take several minutes to scan the environment and collect files. It builds a zip file with the name generated based on the contact number and the issue number, with an added sequence number in case another zip file has already been created for that issue. The cacdf.sh script then uses secure FTP to connect to the CA Technologies support FTP site and upload the zip file.

Note: Before running cacdf.sh (to use the FTP option), you must have reported the issue to CA Technologies support and have a directory created on the CA Technologies support FTP site to receive the data.

CA CDF Example

The following example illustrates running cacdf.sh and supplying the appropriate command line input to gather diagnostic information for AE. In this example, the zip file is not sent to the CA FTP site.

# cd /tmp/cacdf

# . /opt/CA/WorkloadAutomatio nAE/autouser.ACE/*bash* # Set the AE environment.

# ./cacdf.sh # Run the collector.

CA Problem Documentation Collection Utility

Enter your CA Contact Number > 2 601

Enter CA issue number (01) > 21109890

Enter your CA Site ID number > 012

Do you want to send the zip file to the CA FTP site? (y|N) > N


Enter the name of the CA product that is affected > WAAE

Contact number is 2601

Issue number is 21109890

Site ID number is 012

CA Product is WAAE

DO NOT Send file to CA FTP site.

Is this correct?(Y|n) > Y

Answers are correct

Version 1.59

Date/Time is Fri Nov 2 15:51:31 2012

Creating ZIP file with doc for CA Contact 2601 Issue 21109890 SiteID 012

Adding file to list: /etc/services

Adding file to list: /etc/profile

Adding file to list: /etc/auto.*

Adding file to list: /etc/profile.CA

Adding file to list: /tmp/as_info_dir/waae_file_collection.tar

Adding file to list: /opt/CA/WorkloadAutomationAE/autouser.ACE/autosys.*

Adding file to list: /opt/CA/WorkloadAutomationAE/a utouser.ACE/config.ACE

Adding file to list: /opt/CA/WorkloadAutomationAE/autouser.ACE/*.config

Adding file to list: /opt/CA/WorkloadAutomationAE/autouser.ACE/out/DBMaint.out

Adding file to list: /opt/CA/WorkloadAutomationAE/autouser.ACE/out/event_demon.ACE

Adding file to list: /opt/CA/WorkloadAutomationAE/autouser.ACE/out/Num*

Adding file to list: /opt/CA/WorkloadAutomationAE/autouser.ACE/out/as_server.ACE

Adding file to list: /opt/CA/WorkloadAutomationAE/autouser.ACE/webserver/conf/server.xml

Adding file t o list: /opt/CA/WorkloadAutomationAE/autouser.ACE/webserver/conf/wrapper.conf

Adding file to list: /opt/CA/WorkloadAutomationAE/autouser.ACE/webserver/conf/logon.conf

Adding file to list: /opt/CA/WorkloadAutomationAE/autouser.ACE/out/waae_webservices*

Addi ng file to list: /opt/CA/WorkloadAutomationAE/autosys/../SystemAgent/*/agentparm.txt

Adding file to list: /opt/CA/WorkloadAutomationAE/autosys/../SystemAgent/*/log/*

Adding file to list: /opt/CA/SharedComponents/iTechnology/iGateway.log

Adding file to list: /opt/CA/SharedComponents/iTechnology/igwInstall.log

Adding file to list: /opt/CA/SharedComponents/iTechnology/logs/install/*.log

Adding file to list: /opt/CA/SharedComponents/Csam/SockAdapter/version.txt

Adding file to list: /opt/CA/SharedComponents/ Csam/SockAdapter/log/*

Adding file to list: autosys_dir.txt

Adding file to list: autouser_dir.txt

Adding file to list: webserver_dir.txt

Adding file to list: agent_dir.txt

Adding file to list: csam_dir.txt

Adding file to list: treeview.css

Adding file to l ist: treeview.dtd

Adding file to list: treeview.js

Adding file to list: treeview.xslt

Adding file to list: imgs/*.gif

Adding file to list: probinfo.txt

Preparing to execute diagnostic command: cat /proc/version

Preparing to execute diagnostic command: cat /proc/cpuinfo

Preparing to execute diagnostic command: cat /proc/meminfo

Preparing to execute diagnostic command: cat /proc/devices

Preparing to execute diagnostic command: cat /proc/interrupts

Preparing to execute diagnostic command: cat /proc/diskstats

Preparing to execute diagnostic command: cat /proc/partitions

Preparing to execute diagnostic command: cat /proc/modules

Preparing to execute diagnostic command: cat /proc/swaps

Preparing to execute diagnostic command: cat /proc/vmstat

Preparing to execute diagnostic command: cat /proc/iomem


Preparing to execute diagnostic command: cat /proc/ioports

Preparing to execute diagnostic command: cat /proc/zoneinfo

Preparing to execute diagnostic command: cat /proc/loadavg

Preparing to execute diagnostic command: cat /proc/config.gz

Preparing to execute diagnostic command: /bin/df k

Preparing to execute diagnostic command: /sbin/ifconfig a

Preparing to execute diagnostic command: uname a

Preparing to execute diagnostic command: /bin/netstat a

Preparing to execu te diagnostic command: /bin/ps ef

Preparing to execute diagnostic command: /sbin/lspci vvv

Preparing to execute diagnostic command: /sbin/lsusb vvv

Preparing to execute diagnostic command: /bin/rpm q a

Preparing to execute diagnostic command: /bin/dme sg

Preparing to execute diagnostic command: /usr/bin/env

Preparing to execute diagnostic command: /opt/CA/WorkloadAutomationAE/autosys/bin/as_info a

Preparing to execute diagnostic command: /opt/CA/SharedComponents/bin/unisrvcntr status

Preparing to execu te diagnostic command: ps ef

Preparing to execute diagnostic command: ulimit a

Preparing to execute diagnostic command: df

Preparing to execute diagnostic command: ls l /opt/CA/WorkloadAutomationAE/autosys/bin

Preparing to execute diagnostic command: ls lR /opt/CA/WorkloadAutomationAE/autosys > autosys_dir.txt

Preparing to execute diagnostic command: ls lR /opt/CA/WorkloadAutomationAE/autouser.ACE > autouser_dir.txt

Preparing to execute diagnostic command: ls lR /opt/CA/WorkloadAutomationAE/autouser.A CE/webserver >

webserver_dir.txt

Preparing to execute diagnostic command: ls lR /opt/CA/WorkloadAutomationAE/autosys/../SystemAgent >

agent_dir.txt

Preparing to execute diagnostic command: ls lR /opt/CA/SharedComponents/Csam/SockAdapter > csam_dir.txt

Pr eparing to execute diagnostic command: /opt/CA/WorkloadAutomationAE/autosys/bin/autoflags a

Preparing to execute diagnostic command: /opt/CA/WorkloadAutomationAE/autosys/bin/chk_auto_up r 111

Preparing to execute diagnostic command: /opt/CA/WorkloadAutom ationAE/autosys/bin/autoping m localhost

Preparing to execute diagnostic command: /opt/CA/WorkloadAutomationAE/autosys/bin/autoping m localhost S

Preparing to execute diagnostic command: /opt/CA/WorkloadAutomationAE/autosys/bin/event_demon x

Preparing to execute diagnostic command: /opt/CA/WorkloadAutomationAE/autosys/bin/as_server x

Preparing to execute diagnostic command: /opt/CA/WorkloadAutomationAE/autosys/bin/autorep M ALL

Preparing to execute diagnostic command: /opt/CA/WorkloadAutomat ionAE/autosys/../SystemAgent/WA_AGENT/cybAgent v

Preparing to execute diagnostic command: /opt/CA/SharedComponents/Csam/SockAdapter/bin/ csampmuxf status

Preparing to execute diagnostic command: /opt/CA/SharedComponents/Csam/SockAdapter/bin/csamconfigedit display

Preparing to execute diagnostic command: /opt/CA/SharedComponents/Csam/SockAdapter/bin/csamconfigedit port=9000

display

Preparing to execute diagnostic command: /opt/CA/SharedComponents/Csam/SockAdapter/bin/csamconfigedit

portrange=49152 - 50176 disp lay

Adding file to list: diaginfo.txt

The output is stored in a generated zip file in the current directory. (See below for an example of the naming conventions of the zip file.) This file contains the results of all commands and all specified files by WAAE.txt.

# cd /tmp/cacdf

# ls *zip

2601- 21109890 - 1.zip


CA Remote Engineer Usage with AE r11.3.6

CA Remote Engineer is the next generation of CA CDF provided by CA Technologies to automate the collection of problem-

Note: CA Workload Automation AE r11.3.5 ships an earlier version of CA Remote Engineer called CA CDF. See section CA CDF Usage with AE r11.3.5 for more information.

CA Workload Automation AE (AE) r11.3.6 leverages the capabilities of CA Remote Engineer, and therefore, is installed on the machine when other AE components are installed. The intent of CA Remote Engineer is to:

Minimize the amount of time required to collect the appropriate data

Standardize the type of data collected

Reduce the amount of customer skills required to process diagnostic data

This section provides the essential information to gather AE diagnostic data and log files. The latest version of CA Remote Engineer can be downloaded from: http://RemoteEngineer.ca.com. For additional information about CA Remote Engineer, refer to the How To guide, located at the following link: ftp://ftp.ca.com/caproducts/tools/Documentation/CA_RemoteEngineer_How_To.htm

To use CA Remote Engineer to gather diagnostic information about AE

UNIX

1. From the command line, run the following commands:

# cd $AUTOSYS/install/RemoteEngineer

#./re.sh

Windows

1. Change folders to %AUTOSYS%/install/RemoteEngineer

2. Run the command: re.cmd

You are prompted to enter the following information so that the proper information can be gathered and compressed into the zip file:

CA Support Contact Number CA Support Issue Number CA Site ID CA Product for which problem was opened

To gather diagnostic information for AE, enter WAAE when you are prompted for the name of the CA product that is affected. Also, you can gather information for Embedded Entitlements Manager or Workload Command Center diagnosis by entering, respectively, EEM or WCC.

Once this information has been entered and validated, the utility may take several minutes to scan the environment and collect files. It builds a zip file with the name generated based on the contact number and the issue number, with an added sequence number in case another zip file has already been created for that issue. The re.sh or re.cmd script then uses secure FTP to connect to the CA Technologies support FTP site and upload the zip file.

Note: Before running re.sh or re.cmd (to use the FTP option), you must have reported the issue to CA Technologies support and have a directory created on the CA Technologies support FTP site to receive the data.
http://remoteengineer.ca.com/ftp://ftp.ca.com/caproducts/tools/Documentation/CA_RemoteEngineer_How_To.htm


Section 2: Install Caveats to Be Aware Of

EEM Install and a Non-root User

EEM embeds CA Directory and CA iGateway The EEM installer requires the root login to perform certain OS operations required by CA Directory and iGateway. There is no way to go around this, except have a 'sudo' to root after being logged in as a non-root user.

Solution

The CA Directory installer requires 'root' privileges to perform a number of installation functions. A lot of these cater for legacy situations, such as upgrading from CA Ingres to the newer DXgrid back-end, whereas others are required in all cases. The CA Directory installer can be run under 'sudo' if the user is unable to login interactively as the root user. 'root' privileges are required for the following:

Setting file ownership and the setuid bit on 'dxserver' and 'ssld' (ssld is only present prior to r12.0 SP2) to allow registering ports below 1024.

Setting file and directory permissions.

Switching environments and effective userids between 'root', 'dsa' and 'ingres' when upgrading from non-DXgrid releases.

Determining the existence of, or creating, the userid 'dsa'.

Installing CA Shared Components (ETPKI, CA-OpenSSL, etc...).

Installing system startup scripts (/etc/init.d, /etc/rc?.d).

Rollback in the event of an installation failure.

iGateway server is a daemon and installs run level scripts so that it can start/stop with the system. It also modifies a file called /etc/profile.CA which is sourced in /etc/profile file which gets invoked during system startup. Modifying these files requires root credentials during installation.

On a side note iGateway provides a host based authentication mechanism as well which requires querying shadow password files which are not allowed for normal users (only allowed for root or equivalent user).

Sudoers has a configurable option to not prompt the user for password. If considering this, be aware that your IT security organization may have a concern -- of not having a secondary user password challenge. If they do, then they should configure sudoers to just allow the no password option for the installation command instead of an unqualified switch user. For example:

less secure --

more secure --
http://www.linuxforums.org/forum/miscellaneous/138695-solved-nopasswd-etc-sudoers.html


EEM Install and IPv6

As part of the EEM install process, it attempts to get all localhost addresses by using the getaddrinfo command. If a machine is not configured for IPV6, but it contains ::1 in its /etc/hosts file, the EEM install will fail with the following error:

IPv6: ::1

bind call for host [localhost] resolving to address [::1] failed: Cannot assign requested address

CA has a program that retrieves all localhost addresses. This program is also contained in EEM. You may need to install EEM in house and send the program to the user to run. For example:

#./testSysIP localhost

IP addresses for localhost:

IPv4: 127.0.0.1

bind suceede d for host: 127.0.0.1

IPv6: ::1

bind call for host [localhost] resolving to address [::1] failed: Cannot assign requested address

Some systems (e.g. Solaris) come with both IPv4 and IPv6 support. However, the user may not want to activate IPv6. If the EEM install fails with the above error, the user has two options:

1. Completely disable IPv6

2. Activate IPv6

After the user performs one of the above actions, EEM should install.


Section 3: AE Topics

AE Directory and File Permissions In AE r11.3.5, some directories and files are set with excessive permissions or as owner root. The following describes the current permission setting and what the directories and files can be set to to increase security.

1. The following directories do not require world-writeable permissions.

drwxrwxrwx /opt/CA/SharedComponents/csutils/log

drwxrwxrwx /opt/CA/SharedComponents/tmp

They can be altered to 775.

2. The following files must have root permission to allow non-root users to run unisrvcntr commands. These permissions must stay as is.

- r - sr - xr - x /opt/CA/SharedComponents/bin / casrvc

- r - sr - xr - x /opt/CA/SharedComponents/bin / uniregister

- r - sr - xr - x /opt/CA/SharedComponents/bin / unisrvcntr

- r - sr - xr - x /opt/CA/SharedComponents/bin / ustat

- r - sr - xr - x /opt/CA/SharedComponents/csutils/bin / casrvc

- r - sr - xr - x /opt/CA/SharedComponents/csutils/bin / unisrvcntr

3. The world-writeable permissions are not required for the PIF-related directories.

drwxrwxrwx /opt/CA/SharedComponents/installer/administration/admi/CA:CCS

drwxrwxrwx /opt/ CA/SharedComponents/installer/administration/admi/CA:CCS/1.0.0.0

They can be altered to 775.

4. The files listed below do not require the SETUID flag set.

- r - sr - xr - x /opt/CA/SharedComponents/ca_lic / CAmtype

- r - sr - xr - x /opt/CA/SharedComponents/ca_lic / lic98fds

5. Regarding the CADirectory SETUID settings, to start and stop CA Directory services when it listens to ports less than or equal to 1024, which ports are restricted by the OS, the SETUID settings are required. By default the CA Directory default port is 509. However, if CA Directory is installed with a port greater than 1024, the SETUID settings are not required.

- rwsr - x--- /opt/CA/SharedComponents/CADirectory/dxserver/bin / dxadmind

- rwsr - x--- /opt/CA/SharedComponents/CADirectory/dxserv er/bin / dxserver

- rwsr - x--- /opt/CA/SharedComponents/CADirectory/dxserver/bin / dxserver32

- rwsr - x--- /opt/CA/SharedComponents/CADirectory/dxserver/bin / dxserver64

6. The csampmux binary must have the SETUID bit set so that non-root users can run the broker. (Since the non-root user cannot make any configuration changes in SSA, allowing them to run the broker service alone will not create any problems.)

- rwsr - xr - x /opt/CA/SharedComponents/Csam/SockAdapter/bin/csampmux


Object Name Type Old

Permission

New

Permission

Old

Owner/Group

New

Owner/Group

/opt/CA/WorkloadAutomationAE Dir 777 775 root/root autosys/autosys

/opt/CA/WorkloadAutomationAE/webserver Dir 777 750 - -

$AUTOSYS/install/CAPKI Dir 777 755 - -

$AUTOSYS/install/eiam.server.config File 666 600 - -

$AUTOSYS/install/eiam.client.config File 666 655 - -

$AUTOSYS/install/eiam.ws.config File 666 600 - -

$AUTOSYS/install/logger.server.config File 666 600 - -

$AUTOSYS/install/logger.client.config File 666 655 - -

$AUTOSYS/install/logger.ws.config File 666 600 - -

$AUTOSYS/install/data Dir 777 775 - -

$AUTOSYS/install/webserver Dir 777 750 - -

$AUTOSYS/install/webserver/AEWS Dir 777 750 - -

/opt/CA/WorkloadAutomationAE/CommandSponsor Dir 777 750 - -

/opt/CA/WorkloadAutomationAE/JRE_WA Dir 777 750 root/root autosys/autosys

/opt/CA/WorkloadAutomationAE/JRE_WA/1.6.0_33 Dir 777 750 root/root autosys/autosys

/opt/CA/WorkloadAutomationAE/JRE_WA/1.6.0_33/* Dir & File - - root/root autosys/autosys

/opt/CA/WorkloadAutomationAE/JRE64_WA Dir 777 750 root/root autosys/autosys

/opt/CA/WorkloadAutomationAE/JRE64_WA/1.6.0_33 Dir 777 750 root/root autosys/autosys

/opt/CA/WorkloadAutomationAE/JRE64_WA/1.6.0_33/* Dir & File - - root/root autosys/autosys

$AUTOUSER Dir 777 775 - -

$AUTOUSER /audit Dir 777 +t - -

$AUTOUSER/webserver/webapps/AEWS Dir 777 750 - -

$AUTOUSER/eiam.server.config File 666 600 root/root autosys/autosys

$AUTOUSER/eiam.client.config File 666 655 root/root autosys/autosys

$AUTOUSER/logger.server.config File 666 600 root/root autosys/autosys

$AUTOUSER/logger.client.config File 666 655 root/root autosys/autosys


Upgrade AutoSys and WCC

General Principles

When upgrading or migrating from a previous release of AutoSys (including WCC), it is good to follow general principles. Doing so will reduce the number of problems associated with a typical upgrade or migration. The general principles are listed below:

1. Read and understand the documentation. with product upgrades. Make sure that you read and understand all steps associated with upgrading the product, whether it is AutoSys 4.5x, AutoSys r11, AE r11.3, WCC r11, or WCC r11.3.

2. Take a backup of the product. In case problems are experienced, it is essential that you backup the existing AutoSys or AE system, including the database, EEM server system, and WCC system before you begin the upgrade process.

3. Be methodical and take your time. Verify that each step was successful. For example, if the AE r11.3 to r11.3.5 calls for the upgrade of EEM, verify that EEM upgraded successfully before proceeding on with the AE r11.3 to r11.3.5 upgrade.

4. Perform a product verification after the upgrade. Run a test automated workload to validate the upgrade. Report any discrepancies to determine if they are new behavior or a problem.

Upgrade Steps

The steps and order of upgrade depends on what products you are using. For example, if you are only using AutoSys 4.5x with no eTrust security or CA Common Components such as CA Event Management, then the upgrade is very simple. The table below outlines the preferred order of upgrade. NSM refers to CA Common Components in the table. Also, note that all steps may not be required, depending on which dependent products are installed.

Product to Upgrade

Dependent Products Upgrade Steps to AE r11.3.5, Including WCC r11.3.5

AutoSys 4.5x NSM 3.1, eTrust 1. Upgrade NSM 3.1 to NSM r11.2 SP1 CUM1. (See CA Common Components Implementation Guide, Release 11.3.5, Chapter 6, for more information.)

2. Upgrade eTrust to EEM r12. (Update to explain the steps in upgrading from eTrust to EEM r12. There may not be a direct migration path.)

3. Install AE r11.3.5 and select to migrate the AutoSys 4.5x database data to the AE r11.3.5 database. (See section Upgrade From AutoSys 4.5x or r11 to AE r11.3.5 in this document for more information.)

4. Install WCC r11.3.5. (See CA Workload Control Center Implementation Guide, Release 11.3.5, Chapter 4, for more information.)

References:

1. CA Common Components Implementation Guide, Release 11.3.5, Chapter 6.

2. CA Embedded Entitlements Manager Implementation Guide, Release 12.0, Chapter 5.

3. CA Workload Automation AE UNIX Implementation Guide, Release 11.3.5, Chapter 21.

4. CA Workload Control Center Implementation Guide, Release 11.3.5, Chapter 4.


Product to Upgrade

Dependent Products Upgrade Steps to AE r11.3.5, Including WCC r11.3.5

AutoSys r11.0

NSM r11, eIAM, WCC r11

1. Upgrade NSM r11 to NSM r11.2 SP1 CUM1. (See CA Common Components Implementation Guide, Release 11.3.5, Chapter 6 for more information.)

2. Upgrade eIAM to EEM r12. (See section Upgrade the CA EEM Server in this document for more information. Also, see CA Embedded Entitlements Manager Implementation Guide, Release 12.0, Chapter 5.)

3. Install AE r11.3.5 and select to migrate the AutoSys r11 database data to the AE r11.3.5 database. (See section Upgrade From AutoSys 4.5x or r11 to AE r11.3.5 in this document for more information.)


4. Perform the steps to migrate the WCC r11 objects to WCC r11.3.5. (See CA Workload Control Center Implementation Guide, Release 11.3.5, Chapter 4 and 5, for more information.)

References:




4. CA Workload Control Center Implementation Guide, Release 11.3.5, Chapter 4 and 5.

CA AE r11.3 NSM r11.2, EEM 8.4, WCC r11.3

1. Upgrade NSM r11.2 to NSM r11.2 SP1 CUM1. (See CA Common Components Implementation Guide, Release 11.3.5, Chapter 6 for more information.)

2. Upgrade EEM 8.4 to EEM r12, depending on the operating system. (See section Upgrade the CA EEM Server in this document for more information. Also, see CA Embedded Entitlements Manager Implementation Guide, Release 12.0, Chapter 5.)

3. Install AE r11.3.5 and select upgrade. (See section Upgrade From AE r11.3 to AE r11.3.5 in this document for more information.)


5. Perform the steps to migrate the WCC r11.3 objects to WCC r11.3.5. (See CA Workload Control Center Implementation Guide, Release 11.3.5, Chapter 4 and 5, for more information.)

References:




4. CA Workload Control Center Implementation Guide, Release 11.3.5, Chapter 4 and 5.


Upgrade the CA EEM Server

Before upgrading to AE r11.3.5, you must upgrade the CA EEM Server. The normal EEM upgrade path is from EEM 8.4 to r12. However, several platforms that EEM 8.4 supported are not supported by EEM r12. The following table identifies the possible upgrade paths (in green). All other operating systems will require that EEM r12 be installed and the EEM 8.4 information be imported into the r12 database.

CA EEM Server Supported Platforms

Operating System EEM r8.4 EEM r12

Red Hat Linux 3 X (32-bit)


Red Hat Linux 5 X (32-bit) X (64-bit)


SUSE Linux 9 X (32-bit)

SUSE Linux 10 X (32-bit) X (64-bit)

SUSE Linux 11 X (64-bit)

SunOS 5.9 X X

SunOS 5.10 X X

SunOS 5.11

AIX 5.3 X X

AIX 6.1 X X

AIX 7

HP-UX 11.11 X

HP-UX 11.23 X

HP-UX 11.31 X X

Windows 2003 SP2 X

Windows 2003 R2 SP2 X

Windows 2008 SP2 X X

Windows 2008 R2 X

- EEM upgrade from r8.4 to r12 is not supported

- EEM upgrade from r8.4 to r12 is supported

- EEM is not supported on this operating system

If, for example, the EEM server is installed on an HP-UX 11.23 system, you must first export the EEM information from the HP-UX system because EEM r12 cannot be installed on HP-UX 11.23. Next, you must install EEM r12 on an HP-UX 11.31 system. And, finally, you must import the EEM information to the EEM r12 server. Exporting and importing the EEM information requires that you perform the following steps. The steps are fully described in CA Embedded Entitlements Manager Implementation Guide, Release 12.0, p. 63-68.

1. Export the CA EEM database to an LDIF file from the existing CA EEM server.

2. Install CA EEM r12.0 on a supported operating system.

3. Import the LDIF file on the CA EEM r12.0 server.

4. Configure the user store. For information about configuring user store, see the CA EEM Server User Stores Configuration section in CA Embedded Entitlements Manager Implementation Guide, Release 12.0, p. 23.

5. Issue new certificate for each registered application using safex.


Upgrade from AutoSys 4.5x or r11 to AE r11.3.5

This section applies only to upgrading from AutoSys 4.5x and r11 to AE r11.3.5. This section supplements the CA Workload Automation AE UNIX Implementation Guide, Release 11.3.5, pp. 373-383, by showing the panels you will encounter. Upgrading from AE r11.3 is documented in the next section.

The panels that you navigate when upgrading from AutoSys 4.5x and r11 to AE r11.3.5 are similar to the previous release (r11.3) with the exception that the Data Migration panels have been simplified. There is only one Data Migration panel with the AE r11.3.5 upgrade process. The following example shows the panels for an AutoSys r11 upgrade with an Oracle database. The panels are similar when upgrading with a Sybase database.

Note: Make sure that if you have EEM security activated, you should upgrade the EEM server first. See the section Upgrade the EEM Server in this document for more information.

Upgrade AutoSys 4.5x or r11 to AE r11.3.5 (Oracle)

# ./wa_setup.sh

Click Next.


If there are active AutoSys processes, the Active Components panel displays. Click Next. Otherwise, the License Agreement panel displays.

Scroll down to the end of the License Agreement, click I Accept the Terms of the License Agreement radio button, and click Next.


Select Upgrade and click Next.

Select the instance to upgrade and click Next.

Note: You can only upgrade one AutoSys 4.5x or r11 instance at a time.


A warning is displayed indicating that if you upgrade the selected AutoSys instance, it will no longer be usable as an AutoSys 4.5x or r11 instance. It will be upgraded to an AE r11.3.5 instance. Click Next.

Select the components to install and click Next.


Specify the installation directories and click Next. Note that AE r11.3.5 is installed into another directory and not the directory that AutoSys 4.5x or r11 is in.

Specify the Application Server information. If you selected to install the AE web server, you must also select Activate CA EEM and Create/Recreate Instance Policy from the CA EEM Security dropdown selection. Click Next.


If you selected to use CA EEM security, the CA EEM Properties panel displays. Specify the EEM server name and EEM EiamAdmin user password. Click Next.

Click Test. If the test is successful, you will see the following panel. Otherwise, an error will display. In this case, click Back and verify that you specified the correct EEM server name and EiamAdmin user password.


Click OK.

Select which application server properties you want and click Next.


Select the Migrate the Legacy Unicenter AutoSys Job Management Database check box if you want the AE installer to migrate the data. In this example, we will select this option to show the Data Migration panel. If you do not select this check box, you will need to manually migrate the database data using the uajmdatamover.pl utility.

Specify the Oracle database information and click Next.


Specify the SYS (or other database administrator) user password and click Next.

Click Test. If the database connection test is successful, the Database Tests panel shows a success message. Otherwise, the SQL error statements are displayed. In this case, click Back and make sure you have specified the correct Oracle database information.


Click OK.


Specify the Oracle tablespace information. Note that the data and index tablespace paths must exist on the Oracle server. Currently, there is no validation to see if the directories are present and writable. Click Next.

Specify the scheduler properties and click Next.


Specify the agent properties and click Next.

By default, when upgrading from AutoSys 4.5x or r11, the Configure Agent with Legacy Remote Agent Compatibility check box is selected. (See section Configure an Agent to be Compatible with AE for information on what the AE installer does to configure the agent in this manner.) Click Next.


Specify the source database information.

user and specify its password. Click Next. If the specified database information does not allow the AE interviewer to connect to the source database, the following panel displays.

Scroll down to see the error message. Click Back and correct the information, then click Next again.


Specify the owner and group information and click Next.

Review the settings and click Install to install AE r11.3.5 and migrate the legacy database data.


After AE r11.3.5 has been installed and the AutoSys database data has been migrated, the following panel displays.

Click Finish. The installation log is found at /opt/CA/installer/log and is called CAWorkloadAutomationAE.install.log. Looking at the log shows that the Oracle database was created and uajmdatamover.pl was used to successfully migrate the AutoSys r11 database data.


perl CreateAEDB.pl SYBASE **sa_user** **sa_pswd** **aedbadmin_pswd** **autosys_pswd**

/opt/CA/WorkloadAutomationAE/JRE_WA/1.6.0_33 /tmp/ora_createaedb_pri Y AE DB_DATA

/home/oracle/app/oracle/oradata/ SYBASE 800 AEDB_INDEX /home/oracle/app/oracle/oradata/ SYBASE 80

CreateAEDB: Data tablespace name is AEDB_DATA.

CreateAEDB: Data tablespace path is /home/oracle/app/oracle/oradata/ SYBASE.

CreateAEDB: Data ta blespace physical name is /home/oracle/app/oracle/oradata/ SYBASE/AEDB_DATA.DBF.

CreateAEDB: Data tablespace size is 800.

CreateAEDB: Index tablespace name is AEDB_INDEX.

CreateAEDB: Index tablespace physical name is /home/oracle/app/oracle/oradata/ SYBASE/A EDB_INDEX.DBF.

CreateAEDB: Index tablespace size is 80.

CreateAEDB: Creating the AEDB_DATA tablespace.

CreateAEDB: Creating the AEDB_INDEX tablespace.

CreateAEDB: Creating user autosys.

CreateAEDB: Creating the database tables.

CreateAEDB: Creating public synonyms.

CreateAEDB: Creating the database stored procedures.

CreateAEDB: Writing 421 rows of initial database data.

CreateAEDB: Writing 2489 rows of read - only database data.

CreateAEDB: CA Workload Automation AE database created successfully.

Invo king Autosys Migration utility. This may take a while based on the size of your installation.

Running CA Workload Automation AE version 11.3.5.408

Testing source connection credentials

Successful.....

The connection string for the source database is: jdbc: oracle:thin:@ anyhost - rh55 - 64:1521: SYBASE with mdbadmin

The source database is version VER_11_0

Retrieved the source security information

Testing target connection credentials

Successful.....

The connection string for the target database is: jdbc:oracle:thin:@ anyhost - rh55 - 64:1521: SYBASE with aedbadmin

The target database is version VER_11_3_5

The target user aedbadmin can truncate

Fri Dec 28 12:28:14 EST 2012 Start Data Copy process using 6 copiers

Fri Dec 28 12:28:14 EST 2012 Creating Connect ion pool...

Fri Dec 28 12:28:17 EST 2012 Creating Copy threads

Fri Dec 28 12:28:17 EST 2012 Counting rows...

Table ujo_timezones has 366 rows

Table ujo_job_status has 2 rows

Table ujo_keymaster has 3 rows

Table ujo_machine has 1 rows

Table ujo_job_cond has 2 rows

Table ujo_job has 2 rows

Table ujo_last_Eoid_counter has 1 rows

Table ujo_config has 1 rows

Fri Dec 28 12:28:18 EST 2012 There are 378 rows to read

Fri Dec 28 12:28:18 EST 2012 Truncating 88 tables

Fri Dec 28 12:28:20 EST 2012 Tables are truncated

Fri Dec 28 12:28:20 EST 2012 Copying data...

Using copier 0 for transferring job

Using copier 5 for transferring timezones

Using copier 1 for transferring keymaster

Using copier 3 for transferring job_status

Using copier 2 for transferring job_cond

Using c opier 4 for transferring machine


JobReader Task 0 read 2 from table ujo_job

Reader Task 3 read 2 from table ujo_job_status

Reader Task 4 read 1 from table ujo_machine

UninotifyReader Task 1 read 3 from table ujo_keymaster

AsextReader Task 2 read 2 from tab le ujo_job_cond

Reader Task 5 read 366 from table ujo_timezones

Writer task 0.1 copied ujo_job read 2 inserted 2 and ignored 0 duplicates.

Writer task 0.3 copied ujo_command_job read 1 inserted 1 and ignored 0 duplicates.

Writer task 0.2 copied ujo_sched_i nfo read 2 inserted 2 and ignored 0 duplicates.

Writer task 0.4 copied ujo_file_watch_job read 0 inserted 0 and ignored 0 duplicates.

Writer task 3.1 copied ujo_job_status read 2 inserted 2 and ignored 0 duplicates.

Using copier 0 for transferring eoid_counter

JobReader Task 0 read 1 from table ujo_last_Eoid_counter

Using copier 3 for transferring config

Read 0 rows out of 0, and wrote 7 rows

Reader Task 3 read 1 from table ujo_config

Writer task 0.1 copied ujo_last_eoid_counter read 1 inserted 1 and ignored 0 duplicates.

Writer task 4.1 copied ujo_machine read 1 inserted 1 and ignored 0 duplicates.

Writer task 1.1 copied ujo_keymaster read 3 inserted 3 and ignored 0 duplicates.

Writer task 3.1 copied ujo_config read 1 inserted 1 and ignored 0 dupl icates.

Writer task 2.1 copied ujo_job_cond read 2 inserted 2 and ignored 0 duplicates.

Writer task 5.1 copied ujo_timezones read 366 inserted 15 and ignored 351 duplicates.

Fri Dec 28 12:28:21 EST 2012 Copying data complete

Fri Dec 28 12:28:21 EST 2012 Da ta is copied...

Total rows to read 378

Total rows read 378

Total rows written 30

Total duplicate rows 351

Fri Dec 28 12:28:21 EST 2012 Running post processing functions...

Fri Dec 28 12:28:21 EST 2012 Updating Virtual machines...

Fri Dec 2 8 12:28:21 EST 2012 Virtual machines updated

Fri Dec 28 12:28:21 EST 2012 Updating keymaster table...

Fri Dec 28 12:28:21 EST 2012 Updated keymaster table.

Fri Dec 28 12:28:21 EST 2012 Post processing complete

Fri Dec 28 12:28:21 EST 2012 Synchronizing tab les...

Fri Dec 28 12:28:21 EST 2012 Updating OverrideJobs...

Fri Dec 28 12:28:21 EST 2012 OverrideJobs updated 0 rows

Fri Dec 28 12:28:21 EST 2012 Updating Box Joids...

Fri Dec 28 12:28:21 EST 2012 Box Joid updated 0 rows

Fri Dec 28 12:28:21 EST 2012 Update Job Flags

Fri Dec 28 12:28:21 EST 2012 Job Flags updated 8 rows

Fri Dec 28 12:28:21 EST 2012 Creating job tree table

Fri Dec 28 12:28:22 EST 2012 Created job tree table

Fri Dec 28 12:28:22 EST 2012 Start Update TriggerType...

Fri Dec 28 12:28:22 EST 2012 TriggerType updated

Fri Dec 28 12:28:22 EST 2012 Updating Virtual Type values...

Fri Dec 28 12:28:22 EST 2012 Updated Virtual Type

Fri Dec 28 12:28:22 EST 2012 Synchronizing complete

Fri Dec 28 12:28:22 EST 2012 Releasing Connection pool...

Fri Dec 2 8 12:28:22 EST 2012 Released Connection pool

End Data Copy process. Fri Dec 28 12:28:22 EST 2012


Upgrade from AE r11.3 to AE r11.3.5

This section applies only to upgrading from AE r11.3 to AE r11.3.5. Upgrading from 4.5x or r11 is documented in the previous section and also in the CA Workload Automation AE UNIX Implementation Guide, Release 11.3.5, pp. 373-383. This section is provided to show the panels that you will encounter, and descriptions of the input you will provide. (Also, see CA Workload Automation AE UNIX Implementation Guide, Release 11.3.5, pp. 384-388.)

It is important to note that if you have AE r11.3 installed, and you start the AE r11.3.5 installer, you are presented with only two possibilities: upgrade and remove. In other words, you are not permitted to add features or instances to an AE r11.3 system using the AE r11.3.5 installer. Also, all installed r11.3 components are upgraded to r11.3.5, which is normal. But, only installed r11.3 components are upgraded. In other words, if an AE r11.3 client is installed, you are not permitted to upgrade the client and install the scheduler in one step. To accomplish that, you must first upgrade the AE r11.3 client to r11.3.5, and then run the AE r11.3.5 installer again and select Modify, Add Features, and Scheduler.

Note: Make sure that if you have EEM security activated, you should upgrade the EEM server first. See the section Upgrade the EEM Server in this document for more information.

The following examples show the panels when upgrading an AE r11.3 server using Oracle to AE 11.3.5. Note that the EEM security was enabled on the AE r11.3 server using autosys_secure prior to upgrading to AE r11.3.5. The procedure to enable EEM security is shown next, followed by the upgrade panels.

Enable EEM security

1. Log in as the EXEC super user.

2. Source the AE environment by running the following commands.

# [/] cd /opt/CA/WorkloadAutomationAE/autouser.ACE

# [/opt/CA/WorkloadAutomationAE/autouser.ACE] . ./*bash*

3. Run autosys_secure to activate EEM security.

# [/opt/CA/WorkloadAutomationAE/autouser.ACE] autosys_secure

CA WAAE Security Utility

Please select from the following options:

[1] Activate CA EEM instance security.

[2] Manage EDIT/EXEC superusers.

[3] Change database password.

[4] Change rem ote authentication method.

[5] Manage user@host users.

[6] Get encrypted password.

[0] Exit CA WAAE Security Utility.

> 1

Are you sure you wish to activate EEM security? [1(yes)/0(no)]: 1

Input the EEM server name (or hit enter to cancel): arhel55

CAUAJM_I_60201 EEM instance security successfully set.

Please select from the following options:

[1] Revert to NATIVE instance security.

[2] Manage CA EEM server settings.

[3] Change database password.

[4] Change remote authentication method.

[5] Manage u ser@host users.

[6] Get encrypted password.

[0] Exit CA WAAE Security Utility.

> 0

[/opt/CA/WorkloadAutomationAE/autouser.ACE]


Upgrade AE r11.3 to AE r11.3.5 (Oracle)

# ./wa_setup.sh

Click Next.




If there are active AE processes, the Active Components panel displays. Click Next. Otherwise, the Instance Upgrade Information panel displays.


By default, all information that is necessary for the AE r11.3.5 installer to connect to Oracle for this AE instance is retrieved from the previous AE r11.3 installation, except for the Oracle database user aedbadmin password. You should not have to change any of this information. Also, notice the instance name is supplied. If you are upgrading multiple AE instances, you will be prompted to supply this information for each AE instance.

Specify the aedbadmin database user password and click Next.


If the AE r11.3 server does not have EEM security activated, you get this panel informing you of this fact. Click OK. Otherwise, you get the CA EEM Properties panel.

There is no option to skip upgrading EEM policies if AE r11.3 has EEM security enabled. If you need to skip the EEM security policy upgrade, you must run autosys_secure and set security to NATIVE. Specify the CA EEM administrator (EiamAdmin) user password and click Next.

Click Test to verify that the password is correct.


If the password is invalid, you get the CAUAJM_E_60246 error message. Click Back to retype the EiamAdmin user password. If the password is valid, the CA EEM Server Connection Test panel shows with a Success message.

Click OK.

If you are upgrading muInstance Information panel.


On an upgrade, the default behavior is for the AE r11.3.5 installer to reuse the existing agent configuration files and instance profile files. The reason why this option is needed during the upgrade is because the agent does not have the ability to upgrade . In other words, when the AE r11.3.5 installer upgrades the agent, it uninstalls the agent, then installs the new agent. In the process of uninstalling, the configuration files and profile files are removed.

If you choose not to use the default behavior, and deselect the Reuse Existing Configuration File check box, the Configure Agent with Legacy Remote Agent Compatibility check box is enabled. You may want the agent to behave similarly to the legacy agent (pre-r11.3 release). If you do, then select the Configure Agent with Legacy Remote Agent Compatibility check box. See the section, Configure the Agent to be Compatible with AE, in this document, for more information on how the AE r11.3.5 installer configures the agent for legacy behavior.

After you have made your configuration selections, click Next.


Click Upgrade to begin the upgrade process.

The Monitor Process panel displays until the upgrade completes, at which time the Upgrade Complete panel displays.


Click Finish to exit the AE r11.3 to AE r11.3.5 upgrade.

The upgrade log is stored in /opt/CA/installer/log/CAWorkloadAutomationAE.update.log. You will see that the Oracle database is upgraded in place using CreateAEDB.pl. The log shows the following:

perl CreateAEDB.pl SYBASE **sa_user** **sa_pswd** **aedbadmin_pswd** **autosys_pswd**

/opt/CA/WorkloadAutomationAE/JRE_WA/1.6.0_33 /tmp/ora_upgradeaedb_pri N AEDB_DATA 0 AEDB_INDEX 0

CreateAEDB: Base version 11.3.0 found. CreateAEDB will upgrade the CA Workload Automat ion AE database.

CreateAEDB: Upgrading the database tables where required.

CreateAEDB: Creating the database stored procedures.


CreateAEDB: CA Workload Automation AE database is updated.


Upgrade AE r11.3 to AE r11.3.5 (Sybase)

# ./wa_setup.sh

Click Next.




If there are active AE processes, the Active Components panel displays. Click Next. Otherwise, the Instance Upgrade Information panel displays.


By default, all information that is necessary for the AE r11.3.5 installer to connect to Sybase for this AE instance is retrieved from the previous AE r11.3 installation, except for the Sybase database administrator user and password. You should not have to change any of this information. Also, notice the instance name is supplied. If you are upgrading multiple AE instances, you will be prompted to supply this information for each AE instance.

Specify the Sybase database administrator user name and password. Click Next. If you supply the incorrect information, the following error displays.


Click Back and specify the correct Sybase connection information. When the database connection test succeeds, the following panel displays if you do not have CA EEM security active on the r11.3 system.

If the AE r11.3 server does not have EEM security activated, you get this panel informing you of this fact. Click OK. Otherwise, you get the CA EEM Properties panel.


There is no option to skip upgrading EEM policies if AE r11.3 has EEM security enabled. If you need to skip the EEM security policy upgrade, you must run autosys_secure and set security to NATIVE. Specify the CA EEM administrator (EiamAdmin) user password and click Next.

Click Test to verify that the password is correct.

If the password is invalid, you get the CAUAJM_E_60246 error message. Click Back to retype the EiamAdmin user password. If the password is valid, the CA EEM Server Connection Test panel shows with a Success message.


Click OK.

Instance Inf


On an upgrade, the default behavior is for the AE r11.3.5 installer to reuse the existing agent configuration files and instance profile files. The reason why this option is needed during the upgrade is because the agent does not have the ability to upgrade . In other words, when the AE r11.3.5 installer upgrades the agent, it uninstalls the agent, then installs the new agent. In the process of uninstalling, the configuration files and profile files are removed.

If you choose not to use the default behavior, and deselect the Reuse Existing Configuration File check box, the Configure Agent with Legacy Remote Agent Compatibility check box is enabled. You may want the agent to behave similarly to the legacy agent (pre-r11.3 release). If you do, then select the Configure Agent with Legacy Remote Agent Compatibility check box. See the section, Configure the Agent to be Compatible with AE, in this document, for more information on how the AE r11.3.5 installer configures the agent for legacy behavior.

After you have made your configuration selections, click Next.

Click Upgrade to begin the upgrade process.


The Monitor Process panel displays until the upgrade completes, at which time the Upgrade Complete panel displays.

Click Finish to exit the AE r11.3 to AE r11.3.5 upgrade.


The upgrade log is stored in /opt/CA/installer/log/CAWorkloadAutomationAE.update.log. You will see that the Sybase database is upgraded in place using CreateAEDB.pl. The log shows the following:

perl ./CreateAEDB.pl SYBASE AEDB sa **sa_pswd** **autosys_pswd** /opt/CA/WorkloadAutomationAE/JRE_WA/1.6.0_33

/tmp/syb_upgradeaedb_pri N 0 0

CreateAEDB : Base version 11.3.0 found. CreateAEDB will upgrade the CA Workload Automation AE database.

CreateAEDB: Creating CA Workload Automation AE users.

CreateAEDB: Upgrading the database tables where required.

CreateAEDB: Creating the database stored procedures .


CreateAEDB: CA Workload Automation AE database is updated.


Migrate an AE r11.3 Database Manually to AE r11.3.5

This section applies only to migrating an AE r11.3 database to be used by AE r11.3.5. Migrating database data from 4.5x or r11 is documented in the CA Workload Automation AE UNIX Implementation Guide, Release 11.3.5, pp. 314-317.

One of the features of the CA Workload Automation AE r11.3 to r11.3.5 upgrade is that it automatically makes the necessary database table changes. This process is called upgrade-in-place. No database data migration occurs.

There may be a case where you want to create a new database, and then migrate the r11.3 data to the new database, thereby keeping the original r11.3 database intact. The manual procedure (see below) keeps the r11.3 database intact and creates a copy of the r11.3 database that the CA Workload Automation AE installer can then upgrade-in-place.

The manual procedure to migrate database data from r11.3 to r11.3.5 includes the execution of the CA Workload Automation AE r11.3.5 Installer. The steps are listed below.

1. Create a mirror copy of the existing r11.3 database. You can use a database vendor copy utility or use the following steps to create the mirror copy of the database.

a. (For Oracle only) Create an Oracle instance.

b. (For Oracle only) Create directories on the database machine for the Oracle data and index tablespace, if they do not exist. The directories must have write access for the user running the database-create script (see (e.)).

c. Create a directory to store the output from CreateAEDB.pl. Note: This directory must be empty before running the CreateAEDB script. It also must have write access for the user running the database-create script (see (e.)).

d. Verify that the database environment is set up properly to connect to the database and run SQL queries by sourcing the CA Workload Automation AE instance environment files. For example, run the following command from the command line:

. /opt/CA/WorkloadAutomationAE/autouser.ACE/autouser.bash.aehost1

After the CA Workload Automation AE environment is set, do the following:

On UNIX, change to the following directory by running the following command:

For Oracle: cd $AUTOSYS/dbobj/ORA For Sybase: cd $AUTOSYS/dbobj/SYB

On Windows, change to the following folder:

For MS SQL: %AUTOSYS%\dbobj\MSQ For Oracle: %AUTOSYS%\dbobj\ORA For Sybase: %AUTOSYS%\dbobj\SYB

e. Run the CreateAEDB script using one the these methods:

Run the CreateAEDB script in console mode (see page 129 in the CA Workload Automation AE UNIX Implementation Guide r11.3 or page 107 in the CA Workload Automation AE Windows Implementation Guide r11.3).

Note: To use Windows Authentication, specify null values for the sa_user and sa_password values (third and fourth parameters). For example, run the following command from the command prompt:

perl CreateAEDB.pl server database java - home

Run the CreateAEDB script in interactive mode (see page 135 in the CA Workload Automation AE UNIX Implementation Guide r11.3 or page 111 in the CA Workload Automation AE Windows Implementation Guide r11.3).

Note: Windows Authentication is not currently supported in interactive mode.

The mirror database is now created for CA Workload Automation AE r11.3.


2. Populate the mirror r11.3 database by running the autobcpDB utility. autobcpDB copies the database data from the existing r11.3 database to the newly-created r11.3 database. An autobcpDB script is included for each database vendor.

On UNIX, the script is included in the following directory:

$AUTOSYS/dbobj/ORA/autobcpORA.pl (for Oracle) $AUTOSYS/dbobj/SYB/autobcpSYB.pl (for Sybase)

On Windows, the script is included in the following folder:

%AUTOSYS%\dbobj\MSQ\autobcpMSQ.pl (for MS SQL) %AUTOSYS%\dbobj\ORA\autobcpORA.pl (for Oracle) %AUTOSYS%\dbobj\SYB\autobcpSYB.pl (for Sybase)

For detailed instructions on running autobcpDB, see page 270 in the CA Workload Automation AE UNIX Implementation Guide r11.3 or page 258 in the CA Workload Automation AE Windows Implementation Guide r11.3.

3. Run the CA Workload Automation AE r11.3.5 Installer as user root (for UNIX) or as the Administrator (for Windows). At the Primary Event Server Properties panel, do the following:

For MS SQL:

a. Specify the MS SQL Server and database name of the newly-created r11.3 database. b. Select the Create or Refresh the Database check box.

For Oracle:

a. Specify the Oracle SID of the newly-created r11.3 database. b. Clear the Create the Tablespaces, Database Users, and Roles check box. Select the Create or Refresh the

Database check box.

For Sybase:

a. Specify the Sybase Server and database name of the newly-created r11.3 database. b. Clear the Create New Database Devices check box. Select the Create or Refresh the Database check box.

4. Continue through the Install interview and click Install. The CA Workload Automation AE r11.3.5 will be installed and using the mirrored r11.3.5 database.


AE r11.3.5 Port Architecture


Repair an AE r11.3.5 Installation

The AE r11.3.5 repair process is much more sophisticated than previous AutoSys or AE releases. As such, the repair requires additional information from the user. The reasons are two-fold:

1. Not just anyone can perform a repair. Only a person with sufficient security clearance (because of password knowledge) can run a repair.

2. The repair now rebuilds multiple AE instances, including databases, and repairs EEM security policies.

Note: The repair process requires that AE r11.3.5 was previously successfully installed. In other words, if AE r11.3.5 was never fully installed, then the repair process may not work. Suppose the following:

a. AE r11.3 is installed.

b. An attempt is made to upgrade AE r11.3 to r11.3.5, but the upgrade fails.

Since the AE r11.3.5 upgrade failed, there is no guarantee that the AE r11.3.5 repair process will work. It depends on when the upgrade failed. If the upgrade failed during the binary upgrade portion, then the repair will likely work. If the upgrade failed during the database upgrade, then the repair may not work because the AE binaries access the database, and the database may be in an unusable state.

The following example illustrates repairing an AE dual server installation that is using an Oracle database with EEM security active. If you repair an AE installation that is using a Sybase database, the only difference from this example is the Instance Repair Information panel. You are asked for Sybase database connection information instead of Oracle database connection information.

# ./setup.sh

Click Next.


Select Repair and click Next.

Click Next.


the required information and click Next.

password and click Next.


Click Test.

Click OK.


Specify the Oracle database connection information for the second server. Click Next.

If you want to reuse the existing agent configuration file (agentparms.txt), select the Reuse Existing Agent Configuration File check box. If you want to reuse the AE instance profile files (WAAE.txt, ACE.txt, found in SystemAgent/WA_AGENT/profiles), then select the Reuse Existing Instance Profile Files. If these files are not corrupted, you probably want to reuse them. Otherwise, deselect the check boxes, which activates the Configure Agent with Legacy Remote Agent Compatibility check box. Select this check box to configure the agent to behave similar to the legacy remote agent. (See the section, Configure an Agent to be Compatible with AE, in this document for additional information on this check box.)


After making your selections, click Next.

Review the settings and then click Next to begin the repair process.

When the repair finishes, the following panel displays.


Click Finish. The output from the repair is stored in /opt/CA/installer/log in the file named CAWorkloadAutomationAE.reinstall.log. Notice in the log that RefreshAEDB.pl is called to repair the Oracle databases. If there are any database errors, they are logged in the /tmp/ora_repairaedb_pri and /tmp/ora_repairaedb_sec directories respectively.

perl RefreshAEDB.pl SYBASE **aedbadmin_pswd** /opt/CA/WorkloadAutomationAE/JRE_WA/1.6.0_33 /tmp/ora_repairaedb_pri

RefreshAEDB: Base version 11.3.5 found, RefreshAEDB to upgrade the CA Workload Automation AE database

RefreshAEDB: Upgrading the DB tables where required.

RefreshAEDB: Creating the DB stored procedures.

RefreshAEDB: Writing 2489 rows of read - only DB data.

CA Workload Automation AE database is refreshed.

perl RefreshAEDB.pl DWMS10 **aedbadmin_pswd** /opt/CA/WorkloadAutomationAE/J RE_WA/1.6.0_33 /tmp/ora_repairaedb_sec

RefreshAEDB: Base version 11.3.5 found, RefreshAEDB to upgrade the CA Workload Automation AE database

RefreshAEDB: Upgrading the DB tables where required.

RefreshAEDB: Creating the DB stored procedures.

RefreshAEDB: Writing 2489 rows of read - only DB data.

CA Workload Automation AE database is refreshed.


Use the DataMover Application for Data Migrations

Customers have used the AE DataMover application to migrate database data from AutoSys 4.5 and r11.0. This command has performed its designed tasks well on databases containing valid AutoSys data. However, it has encountered various problems when the database contains obsolete and out-of-date entries. Although problems were identified by the syntax checker, more often the problems and resolutions were not obvious when reviewing the log files. This section identifies problems encountered by customers and will need to be addressed for the planned AE r11.3.5 DataMover Application. (Also, see current documentation on migrating the database in CA Workload Automation AE UNIX Implementation Guide, Release 11.3.5, Chapter 22, p. 409-422.)

Note: Before performing any of the steps below, you should make sure you have a current backup of your database.

The problems have been separated into three categories:

Problems that stop the data migration process or generate errors

1. Incorrect version of the DataMover utility Verify that you have the most current version of the DataMover executable. (For example, an earlier version of the tool had a memory issue that was corrected.)

2. Active AutoSys or AE processes Verify that the AutoSys or AE applications are stopped prior to running (scheduler, application server, and agent) the DataMover utility. To verify that the AE applications are stopped, run the following command from the command line:

unisrvcntr status

If any AutoSys or AE processes are running, stop them using the unisrvcntr stop command.

3. Entries created when using the One-Time override option.

4. Invalid numbers specified in JIL keywords, such as:

Value set for the JIL keyword: term_run_time . This value could be higher than the maximum value allowed, 527040 . (ERROR: CAUAJM_E_18995)

Value set for the JIL Keyword: box_terminator . Accepted values are 0, 1, f, false, n, no, t, true, y, yes, encountered a number. (ERROR: CAUAJM_E_18902)

Problems that slow down the data migration process

1. All jobs associated with a BOX get the warning that the Box does not exist yet (CAUAJM_W_10282 ). This warning will later generate the error CAUAJM_E_50246 JIL syntax check FAILED. [Could there be a pre-parser that creates list of BOX jobs and uses this during check?]

2. Identify jobs referencing invalid calendars and use JIL to remove them.

3. Identify orphaned data and provide option to clean-up (ex. overrides and alarms).

4. Run the following SQL commands:

delete from job_cond where joid not in (select joid from job);

delete from job_status where joid not in (select joid from job);

delete from job2 where joid not in (select joid from job);

Things missed during the DataMover execution or that needs to be addressed afterwards

1. The DataMover does not copy user@host or edit/exec users (see STAR issue 21191984-02).

2. All machine definitions are migrated as legacy. This encourages/assumes that every migration will utilize legacy to do that. We DO want customers to use the 11.3.5 agents - so the

DataMover should include the option to move all machine definitions as legacy, current, or only export the converted machine jil.


3. Technical Support has found that the majority of customer migrations have required the customer to delete many machines and then insert them with appropriate definitions. Also, there have been issues caused by having to forcibly delete machines while orphaning the virtual machine names. This scenario has required the reinsertion of all machines and then the separation of virtual machines, then the removal of virtual machines.

Current limitations to the DataMover

The following are current known limitations to the DataMover which will be addressed in the future:

1. Scan the database for invalid data, such as is identified in #3 and #4 above. This includes adding the newer integrity checking, which identifies duplicate data rows. The DataMover should have a command line option to remove duplicate data rows.

2. The DataMover does not have the ability to modify the agent paramfile.txt file so that VERIFY=no. Add the ability to the DataMover to modify the agent paramfile.txt file so that VERIFY=no. This would be applicable for r11.0 migrations.

3. When a fatal occurs, the DataMover should write a more descriptive interpretation of the problem to the log, and perhaps the screen. For example:

Reading table job failed on input column 4 and output column 5

Reading table job failed on row 900 -- java.sql.SQLException: Numeric Ove rflow

Copy Task 0 copying job has faulted (3)

4. DataMover does not have the ability to scan for corrupt job names. Add the ability to the DataMover to scan for corrupt JOB names.

5. As part of the recommended automation, the script should perform a sanity test and verify that the required DataMover parameter file is in place and has the following entries (note the data is for an Oracle database):

SRCDBTYPE=oracle

SRCDBMACHINE=rex

SRCDBNAME=auto451p

SRCDBPORT=1865

SRCDBUSER=autosys

SRCDBPWD=xxxxxxxxxxxx

TGTDBTYPE=oracle

TGTDBMACHINE=tex

TGTDBNAME=autop

TGTDBPORT=1609

TGTDBUSER=aedbadmin

TGTDBPWD=xxxxxxxxxxxx

NATIVEJDBCJARPATH=/usr/orasys/11.2.0.3r2/jdbc/lib/ojdbc6.jar # Oracle 1.6 compatible JDBC .

JREPATH=/usr/java6_64/jre # Mixed or 64 - bit may give better performance .

VERIFY=yes # Note: You'll change this at Go time .

MAXMEMORYLIMIT=4096 # Note: Make sure the system has the RAM .


Unattended AE Install Failure Return Code Meanings

Unattended installation failures usually occur because something is wrong with the system environment or there are invalid values in the user-created response file. The following tables describe the return code errors from unattended installs.

Return codes from wa_setup.sh

Return Code Description

1 The Oracle or Sybase database connection test failed.

2

3 user definition failed.

4

5 There are not enough Sybase user connections.

6 The Sybase page size is too small.

7 The version of Sybase installed is not supported by AE.

8 The Sybase device is already created.

9 There is not enough free space to create the Sybase database.

10 There is not enough free space in the system temporary directory (e.g. /tmp).

11

12 Duplicate agent name. There is already an agent installed by the name in the response file.

13 Duplicate agent port. There is already an agent installed that is using the port specified in the response file.

15 $CASHCOMP is not specified correctly in the response file.

16 $ASI_AUTOSYS_INSTDIR is not specified correctly in the response file.

17 The AE web server must be installed on a 64-bit operating system.

18 There is already an AE instance on the server. An unattended install does not support upgrade or modify .

21 Dependent processes could not be shut down.

22 The installation directory specified in $ASI_AUTOSYS_INSTDIR or $CASHCOMP is not writable.

Return codes from agent_setup.sh


7 Duplicate agent name. There is already an agent installed by the name in the response file.

8 Duplicate agent port. There is already an agent installed that is using the port specified in the response file.

9 There is not enough free space in the system temporary directory (e.g. /tmp).



17 The machine is HP-ia64. The $Config_Agt_Port_2_SSA variable must be set to 0 in the response file.

19 The I option was not used when installing another agent instance.




Return codes from client_setup.sh






Return codes from sdk_setup.sh







Create Oracle Tablespaces, Users, and Roles

The AE r11.3.5 installer handles the Oracle database tablespace, user, and role creation differently than in AE r11.3. In r11.3, the installer without having to specify the database system administrator user and password.

To meet the customer need, the AE r11.3.5 installer was redesigned to allow the ability to skip all database operations requiring database system administer user privileges. In AE, there are three operations that require system-level user privileges:

1. Create tablespace 2. Create user 3. Create role

Early on in the r11.3.5 planning process, a decision was made by the R&D team to group these three database operations together to reduce complexities. In other words, the installer would not give control to the user to execute/not execute these three database operations individually.

An SQL script (waae_oracle.sql) was created, providing a simple utility (another requirement) so that the database administrator could perform all three database operations (not the installer); one major result being that the system-level database users/passwords required to perform the operations would remain secure.

The waae_oracle.sql script is shown below and fully described in the CA Workload Automation AE UNIX Implementation Guide, Release 11.3.5, p. 59.

Rem Parameters to this SQL are:

Rem

Rem 1 - Data tablespace name. For example: AEDB_DATA

Rem 2 - Data tablespace size in MB. For example: 800

Rem 3 - Data tablespace directory file. For example: /home/oracle/oradata/orcl/ AEDB_DATA.DBF

Rem 4 - Index tablespace name. For example: AEDB_INDEX

Rem 5 - Index tablespace size in MB. For example: 80

Rem 6 - Index tablespace directory file. For example: /home/oracle/oradata/orcl/AEDB_INDEX.DBF

Rem 7 - 'aedbadmin' database us er password.

Rem 8 - 'autosys' database user password.

Rem

Rem Create the Oracle tablespaces:

Rem Uncomment if using OMF:

Rem