Better strategy to export custom EEM policies from an older WCC/WebUI environment to a newer version of WCC/WebUI in a different environment

Products

• Autosys Workload Automation

Issue/Introduction

If a new WebUI environment is being created using a newer version (example: 12.1.01), but there is a need to import EEM Policies from older (example: 12.0.1) environment to the newer environment, the order of import of the policies makes a difference.

Environment

AutoSys Workload Automation

Resolution

Take an example of old WebUI version to be 12.0.1 where custom policies were created.  Goal is to setup the same policies on a different newer version based WebUI environment, say 12.1.01.

From the source EEM URL (associated to AutoSys 12.0.1), WebUI Policies can be backed up using the steps from Export and Import AutoSys / WCC (WebUI) EEM Policies (using the GUI)  Then copy the extracted XML file to the destination WebUI Server.
Note:  If EEM is tied to LDAP, do not select the option export Global Users.   Most times the option  Override The Max Search Size should be selected as the default 2000 might not be enough.  Something like 50,000 or higher could be used if there is a lot of objects being exported

On the Destination WebUI Server, Stop WCC Services first.

• If it is a Microsoft Windows OS, open a Windows command prompt (Run as Administrator),  and change directory to %CA_WCC_INSTALL_LOCATION%\safex directory
• If it is a Unix OS, change directory to $CA_WCC_INSTALL_LOCATION\safex at a shell prompt
• Run the following command to backup current EEM policies being used:
• Unix:

./safex.sh -f UWCCUnregister.xml    ## to unregister the WCC application

./safex.sh -f UWCCRegister.xml     

./safex.sh  -f  <The_12.0.01_custom_policies_file_created_from_the_export_using_source_EEM_URL>

• Then follow the steps in Regenerate EEM certificates for WCC
• Login to the destination EEM URL to using WCC0004 application to verify that the custom  policies and new policies exist.
• Start WCC services