Cisco Workload Automation 6.3.2 Patch Installation Guide the Standalone CWA Java Client Application...

Cisco Workload Automation 6.3.2 Patch Installation Guide

Version 6.3.2

First Published: Nov 17, 2017Last Updated: January 12, 2018

Cisco Systems, Inc. www.cisco.com

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

All printed copies and duplicate soft copies are considered un-Controlled copies and the original on-line version should be referred to for latest version.

Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices.Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL:www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationshipbetween Cisco and any other company. (1721R)

© 2017 Cisco Systems, Inc. All rights reserved.

2

http://www.cisco.com/go/offices

https://www.cisco.com/go/trademarks

https://www.cisco.com/go/trademarks

Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iObtaining Documentation and Submitting a Service Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iRelated Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iDocument Change History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i

Windows 6.3.2 Patch Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Pre-Installation Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Running the Patch Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Patching the Standalone CWA Java Client Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

UNIX 6.3.2 Patch Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Pre-Installation Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Running the Patch Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Patching the Standalone CWA Java Client Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Manually Patching CWA 6.3.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Manually Patching the CWA Master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Manually Patching the CWA Backup Master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Manually Patching the CWA Fault Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Troubleshooting Missing Adapters after Patching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Manually Patching the CWA Client Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Patching the 6.3.2 Build Client Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Manually Patching the 6.3.2 Build CWA Java Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Manually Patching the 6.3.2 Build CWA Transporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Manually Patching the 6.3.2 Build CWA TES Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Migrating to AWS/MS Azure Database Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13AWS - RDS Service Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

1


Client Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14MS Azure SQL Service Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Master. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Client Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2

PrefaceThis guide describes how to patch Cisco Workload Automation (CWA) 6.3.2 on Windows and UNIX machines using automated scripts (sometimes referred to as “mini-installers”). It also describes how to manually patch CWA 6.3.2 using the command line.

See the Cisco Workload Automation Installation Guide for comprehensive documentation on the full installation and configuration of each CWA components using the installers provided with the base product.

AudienceThis guide is for administrators who install and configure CWA patches and hot fixes, and who troubleshoot CWA installation and configuration issues.

Obtaining Documentation and Submitting a Service RequestFor information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.

Related DocumentationYou can access the list of all Cisco Workload Automation guides on Cisco.com at:

http://www.cisco.com/c/en/us/support/cloud-systems-management/tidal-enterprise-scheduler/products-documentation-roadmaps-list.html

Document Change HistoryThe table below provides the revision history for the Cisco Workload Automation 6.3.2 Patch Installation Guide.

Version Number Issue Date Reason for Change

6.3.2 Nov 2017 New guide that describes how to apply 6.3.2 patch using the automated scripts provided for Windows and UNIX, or alternatively how to manually patch CWA.

i


http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

http://www.cisco.com/c/en/us/support/cloud-systems-management/tidal-enterprise-scheduler/products-documentation-roadmaps-list.html

Preface

Document Change History

ii

1Windows 6.3.2 Patch InstallationOverview

This chapter describes the automated process (sometimes called the mini-installer) to patch CWA 6.3.0 or 6.3.1 to CWA 6.3.2. This patch process explains how to backup the existing files and run the script to perform the patch. ADMIN access is required to perform the patch update.

To perform this patch manually instead of using the scripts, see the Manually Patching CWA 6.3.2 chapter.

The CWA Java Client Web interface is updated as part of the CWA Master patch process described below. To learn how to update the standalone CWA Java Client, see Patching the Standalone CWA Java Client Application.

Note: For complete installation and configuration instructions for all CWA components, see the Cisco Workload Automation Installation Guide.

RequirementsCWA 6.3.0 or 6.3.1 is mandatory to patch into 6.3.2 using CWA 6.3.2 patch installer.

Note: Upgrading to 6.3.2 is also possible using CWA 6.3.2 installer from version 6.3.0 or 6.3.1. For complete installation and configuration instructions for all CWA components, see the Cisco Workload Automation Installation Guide.

Pre-Installation StepsFollow the below procedures to prepare the Master and Client Manager for the patch installation on Windows.

To prepare the Master before running the patch installer:1. Stop the Master service before running the patch installer.

2. Note that during installation:

A backup folder will be created inside the same directory from where the installer runs and the following Master directories will be backed up: “services”, “lib”, and “webapps”.

An installer log file will be created inside the aforementioned backup directory.

To prepare the Client Manager before running the patch installer:1. Stop the Client Manager service before running the patch installer.


A backup folder will be created inside the same directory from where the installer runs and the following Client Manager directories will be backed up: “cache”, “config”, “lib”, and “webapps”.

1


Windows 6.3.2 Patch Installation

Running the Patch Installer


The following folder will be deleted: “plugins”.

Running the Patch InstallerFollow the below procedures to run the patch installer for the Master and Client Manager.

To run the patch installer for the Master:1. Locate the files installScheduler.vbs and installScheduler.bat in the folder:

<Cisco_Workload_Automation_6.3.2_Patch_Installer_Release>\master.

2. Run the install script using either of the following methods:

a. Click on installScheduler.bat.

OR

b. Open a command prompt and change the directory to where installScheduler.vbs is located. Type any one of the following commands and press the “ENTER” key:

— “installScheduler.vbs” (invokes the script in default mode)

— “cscript.exe installScheduler.vbs” (invokes the script in console mode)

— “wscript.exe installScheduler.vbs” (invokes the script in GUI mode)

Note: For more information on the different modes in which the script can run, refer to:

http://technet.microsoft.com/en-us/library/ee156587.aspx

3. When prompted, provide the CWA Master installed path so that the existing files can be backed up and new files installed.

4. Update the mail.jar location in CLASSPATH in the master.props file as given below, after the CWA Master patching.

{TIDAL_HOME}\lib\mail.jar;

To run the patch installer for the Client Manager:1. Locate the files installCM.bat and installCM.vbs in the folder:

<Cisco_Workload_Automation_6.3.2_Patch_Installer_Release>\cm.

2. Run the install script using either of the following methods:

a. Click on installCM.bat.

OR

b. Open a command prompt and change the directory to where installCM.vbs is located. Type any one of the following commands and press the “ENTER” key:

— “installCM.vbs” (invokes the script in default mode)

— “cscript.exe installCM.vbs” (invokes the script in console mode)

— “wscript.exe installCM.vbs” (invokes the script in GUI mode)

Note: For more information on the different modes in which the script can run, refer to:

http://technet.microsoft.com/en-us/library/ee156587.aspx

2


Patching the Standalone CWA Java Client Application

3. When prompted, provide the CWA Client Manager installed path so that existing files can be backed up and new files installed.

4. After the CWA Client Manager patching, execute the clearcache.sql query provided in the installed location.

For MSSQLC:\Program Files\TIDAL\ClientManager\mssql\clearcache.sql

For Oracle C:\Program Files\TIDAL\ClientManager\oracle\clearcache.sql

5. Start the Client Manager.

Note: Cisco_Workload_Automation_6.3.2_Patch_Installer_Release refers to the patch directory downloaded from CISCO.COM at:

https://software.cisco.com/download/release.html?i=!y&mdfid=283340354&softwareid=283343734&release=6.3.2&os=

Patching the Standalone CWA Java Client ApplicationThe CWA Java Client Web interface is updated as part of this CWA Master patch process. However, if you are using the standalone CWA Java Client application, you can update it by manually patching the standalone CWA Java Client application. Follow the instructions in Manually Patching the 6.3.2 Build CWA Java Client.

3



Patching the Standalone CWA Java Client Application

4

2UNIX 6.3.2 Patch InstallationOverview

This chapter describes the automated process (sometimes called the mini-installer) to patch CWA 6.3.0 or 6.3.1 to CWA 6.3.2 on UNIX. This patch process explains how to backup the existing files and run the script to perform the patch. ROOT access is required to perform the patch update.

To perform this patch manually instead of using the scripts, see the Manually Patching CWA 6.3.2 chapter.

The CWA Java Client Web interface is updated as part of the CWA Master patch process described below. To learn how to update the standalone CWA Java Client, see Patching the Standalone CWA Java Client Application.

Note: For complete installation and configuration instructions for all CWA components, see the Cisco Workload Automation Installation Guide.


Note: Upgrading to 6.3.2 is also possible using CWA 6.3.2 installer from version 6.3.0 or 6.3.1. For complete installation and configuration instructions for all CWA components, see the Cisco Workload Automation Installation Guide.

Pre-Installation StepsFollow the below procedures to prepare the Master and Client Manager for the patch installation on UNIX.

To prepare the Master before running the patch installer:1. Stop the Master service before running the patch installer.


A backup folder will be created inside the same directory from where the installer runs and the following Master directories will be backed up: “services”, “lib”, and “webapps”.


To prepare the Client Manager before running the patch installer:1. Stop the Client Manager service before running the patch installer.


A backup folder will be created inside the same directory from where the installer runs and the following Client Manager directories will be backed up: “cache”, “config”, “lib”, and “webapps”.

5


UNIX 6.3.2 Patch Installation

Running the Patch Installer


Running the Patch InstallerFollow the below procedures below to run the patch installer for the Master and Client Manager on UNIX.

To run the patch installer for the Master:1. Locate the file install_master.sh in the directory:

<Cisco_Workload_Automation_6.3.2_Patch_Installer_Release>\master.

2. Run the install script using “./install_master.sh” command.

3. When prompted, provide the CWA Master installed path so that the existing files can be backed up and new files installed.

4. Update mail.jar location in CLASSPATH in master.props file as given below, after the CWA Master patching.

${TIDAL_HOME}/lib/mail.jar

To run the patch installer for the Client Manager:1. Locate the file install_cm.sh in the directory:

<Cisco_Workload_Automation_6.3.2_Patch_Installer_Release>\cm.

2. Run the install script using “./install_cm.sh” command.

3. When prompted, provide the CWA Client Manager installed path so that existing files can be backed up and new files installed.

4. After the CWA Client Manager patching, execute the clearcache.sql query provided in the installed location.

For Oracle /opt/TIDAL/ClientManager/oracle/clearcache.sql

5. Start the Client Manager.



Patching the Standalone CWA Java Client ApplicationThe CWA Java Client Web interface is updated as part of this CWA Master patch process. However, if you are using the standalone CWA Java Client application, you can update it by manually patching the standalone CWA Java Client application. Follow the instructions in Manually Patching the 6.3.2 Build CWA Java Client.

6


3Manually Patching CWA 6.3.2Overview

This chapter describes how to manually apply the CWA 6.3.2 patch on top of CWA 6.3.0 or 6.3.1. Specific instructions are provided for the CWA Master, the Client Manager, and the CWA Java Client.

To use automated scripts to patch CWA 6.3.2, see the following chapters:

Chapter 1, “Windows 6.3.2 Patch Installation,”

Chapter 2, “UNIX 6.3.2 Patch Installation,”


Note: Upgrading to 6.3.2 is also possible using CWA 6.3.2 installer from version CWA 6.3.0 or 6.3.1. For complete installation and configuration instructions for all CWA components, please see the Cisco Workload Automation Installation Guide.

Manually Patching the CWA MasterIn the text below, MASTER_INSTALLED_DIR refers to the path where the master is installed on your operating system. For example:

Windows

C:\Program Files\TIDAL\Scheduler\

UNIX

/opt/TIDAL/master



To patch the CWA Master:1. Stop the Master service.

2. Backup the adapter configuration files as follows:

7



Manually Patching CWA 6.3.2

Manually Patching the CWA Backup Master

Copy and backup MASTER_INSTALLED_DIR\Master\Services\YOUR SPECIFIC ADAPTER GUIDE FOLDER\Config.

For example, if you are licensed for an SAP Adapter, copy and backup:

Windows

C:\Program Files\TIDAL\Scheduler\Master\services\{51C57049-3215-44b7-ABE1-C012FF786010}\config

UNIX

/opt/TIDAL/master/services/{51C57049-3215-44b7-ABE1-C012FF786010}\config

3. Copy your specific .pkg adapter files from <Cisco_Workload_Automation_6.3.2_Patch_Installer_Release>\master\ to MASTER_INSTALLED_DIR\Master\config.

UNIX example:

/opt/TIDAL/master/config

4. Copy “scheduler.jar”, “adapterhost.jar” from Cisco_Workload_Automation_6.3.2_Patch_Installer_Release\master\ to MASTER_INSTALLED_DIR\Master\lib.

UNIX example:

/opt/TIDAL/master/lib/

5. Copy “tesclient.war” from Cisco_Workload_Automation_6.3.2_Patch_Installer_Release\master\ to MASTER_INSTALLED_DIR\Master\webapps.

UNIX example:

/opt/TIDAL/master/webapps/


For Windows{TIDAL_HOME}\lib\mail.jar;

For Unix${TIDAL_HOME}/lib/mail.jar:

7. Start the Master service.

8. Check for the adapter version you are patching using either the CWA Web Client or the CWA Java Client. If the version is not shown correctly, follow the troubleshooting instructions in Troubleshooting Missing Adapters after Patching.

Manually Patching the CWA Backup MasterIn the text below, the BACKUP_MASTER_INSTALLED_DIR refers to the path where the master is installed on your operating system.

For example:

For WindowsC:\Program Files\TIDAL\Scheduler\

For Unix/opt/TIDAL/master

8


Manually Patching the CWA Fault Monitor

Note: Cisco_Workload_Automation_6.3.2_Patch_Installer_Release refers to the patch directory downloaded from Cisco.com at:


To patch the CWA Backup Master:1. Stop the Backup Master service.

2. Copy “scheduler.jar from Cisco_Workload_Automation_6.3.2_Patch_Installer_Release\master\ into MASTER_INSTALLED_DIR\Master\lib.


For Windows{TIDAL_HOME}\lib\mail.jar;

For Unix${TIDAL_HOME}/lib/mail.jar:

4. Start the Backup Master service.

Manually Patching the CWA Fault Monitor

In the text below, FAULT_MONITORINSTALLED_DIR refers to the path where the master is installed on your operating system.For example:

For WindowsC:\Program Files\TIDAL\Scheduler\

For UNIX/opt/TIDAL/master

Note: Cisco_Workload_Automation_6.3.2_Patch_Installer_Release refers to the patch directory downloaded from Cisco.com at:


To patch the CWA Fault Monitor:

1. Stop the Fault Monitor service.2. Copy “scheduler.jar from Cisco_Workload_Automation_6.3.2_Patch_Installer_Release\master\ into MASTER_INSTALLED_DIR\Master\lib.3. Start the Fault Monitor service.

9




Troubleshooting Missing Adapters after Patching

Troubleshooting Missing Adapters after Patching

To troubleshoot the patch if an adapter does not appear in your CWA Client:1. Stop the Master service.

2. Backup the adapter configuration files (if present) following the instructions in Manually Patching the CWA Master.

3. Delete the specific adapter guide folder at

MASTER_INSTALLED_DIR\Master\Services\ADAPTER_GUID_FOLDER as well as the .pkg file in MASTER_INSTALLED_DIR\Master\Config.

4. If the \Config folder mentioned in step #3 above exists, restore the same inside MASTER_INSTALLED_DIR\Master\Services\ADAPTER_GUID_FOLDER.


Manually Patching the CWA Client ManagerIn the text below, CM_INSTALLED_DIR refers to the path where the Client Manager is installed on your operating system. For example:

Windows

C:\Program Files\TIDAL\ClientManager\

UNIX

/opt/TIDAL/ClientManager



Patching the 6.3.2 Build Client Manager

To patch the Client Manager on top of CWA 6.3.0 or 6.3.1 GA build:1. Stop the Client Manager service.

2. Delete the directory named “plugins” present inside CM_INSTALLED_DIR.

3. Delete all files inside CM_INSTALLED_DIR\webapps directory.

4. Copy “client.war” from Cisco_Workload_Automation_6.3.2_Patch_Installer_Release\cm to CM_INSTALLED_DIR\webapps.

5. Copy the files below from Cisco_Workload_Automation_6.3.2_Patch_Installer_Release\cm to CM_INSTALLED_DIR\cache\tes-6.0.0.0:

— tes-6.0.0.0.war

— tes-6.0.0.0.jar

6. Copy the files below from Cisco_Workload_Automation_6.3.2_Patch_Installer_Release\cm to CM_INSTALLED_DIR\lib:

— ClientManager.jar

10



Manually Patching the 6.3.2 Build CWA Java Client

— activemq-all.jar

— activemq-web.jar

— derby.jar

— derbyclient.jar

— derbynet.jar

— httpcore-4.2.jar

— httpclient-4.2.6.jar

— mail.jar

7. After CWA Client Manager patching, execute clearcache.sql query provided in the installed location.

For MSSQLC:\Program Files\TIDAL\ClientManager\mssql\clearcache.sql

For OracleC:\Program Files\TIDAL\ClientManager\oracle\clearcache.sql

8. Start the Client Manager service.

9. Clear your browser's cache before accessing the Web Client.

Manually Patching the 6.3.2 Build CWA Java ClientThis section explains the process to patch the standalone CWA Java Client application. The Java Client that uses the Web interface is patched when you patch the CWA Master.

To patch the CWA Java Client on top of 6.3.0 or 6.3.1 build:1. Stop the CWA Java Client.

2. Backup the existing “Framework.jar, SchedulerApi.jar and tesclient.jar” present inside CWAClient_INSTALLED_DIR\lib.

Windows Example:

“C:\Program Files\TIDAL\TES Java Client\lib”

3. Copy “Framework.jar, SchedulerApi.jar, and tesclient.jar” from Cisco_Workload_Automation_6.3.2_Patch_Installer_Release\ tesclient to CWAClient_INSTALLED_DIR\lib.

Windows Example:

“C:\Program Files\TIDAL\TES Java Client\lib”

4. Start the CWA Java Client.

11


Manually Patching the 6.3.2 Build CWA Transporter

Manually Patching the 6.3.2 Build CWA TransporterThis section explains the process to patch the CWA Transporter application.

To patch the CWA Transporter on top of 6.3.0 or 6.3.1 build:1. Close the CWA Transporter window.

2. Backup the existing "Transporter.jar”, present inside the CWATransporter_INSTALLED_DIR\lib.

3. Copy "Transporter.jar" from Cisco_Workload_Automation_6.3.2_Patch_Installer_Release\Others to CWATransporter_INSTALLED_DIR\lib.

Example path:

"C:\Program Files\TIDAL\Transporter\lib"

4. Open Transporter.

Manually Patching the 6.3.2 Build CWA TES Command LineThis section explains the process to patch the CWA TESCmdLine application.

To patch the CWA TESCmdLine on top of 6.3.0 or 6.3.1 build:1. Close the CWA TESCmdLine window.

2. Backup the existing "TESCmdLine.jar”, present inside the CWATESCmdLine_INSTALLED_DIR\lib.

3. Copy "TESCmdLine.jar" from Cisco_Workload_Automation_6.3.2_Patch_Installer_Release\Others to CWATESCmdLine_INSTALLED_DIR\lib.

Example path:

"C:\Program Files\TIDAL\TESCmdLine\lib"

4. Open TESCmdLine.

12

4Migrating to AWS/MS Azure Database ServiceAWS - RDS Service Support

The following steps are applicable only when the CWA Master and Client Manager database are migrated to AWS RDS service.

Master1. Restore the backup of Master database.

a. For AWS RDS SQL service, follow the below steps:

— Restore the database in RDS SQL server.

— Execute the below SQL queries provided in the patch Installer.

Cisco_Workload_Automation_6.3.2_Patch_Installer_Release\Others\CLOUD_SQL\AWS_SQLQuery\MSSQL\AWS_SQLQuery.sqlCisco_Workload_Automation_6.3.2_Patch_Installer_Release\Others\CLOUD_SQL\AWS_SQLQuery\MSSQL\upgradegrant.sql

b. For AWS RDS Oracle service, the database restoration and query execution are not required.

2. Update the RDS SQL/Oracle server name in master.props located under Master installation directory.

Examples:

For MSSQL:

JdbcURL=jdbc:sqlserver://MSSQLDBServer:1433;selectMethod=cursor

For Oracle:

JdbcURL=jdbc:oracle:thin:@OracleDBServer:1521:orcl

3. Run the patch installer for Master. For patch installation, see Running the Patch Installer of Windows 6.3.2 Patch Installation or Running the Patch Installer of Unix 6.3.2 Patch Installation. For manual patching, see Manually Patching the CWA Master.


13


Migrating to AWS/MS Azure Database Service

MS Azure SQL Service Support

Client Manager1. Create Client Manager database.

a. For AWS RDS SQL service, execute the query provided in the patch installer path below:

Cisco_Workload_Automation_6.3.2_Patch_Installer_Release\Others\CLOUD_SQL\AWS_SQLQuery\MSSQL\createcachedb-mssql.sql

b. For AWS RDS Oracle service, execute the query provided in the patch installer path below:

Cisco_Workload_Automation_6.3.2_Patch_Installer_Release\Others\CLOUD_SQL\AWS_SQLQuery\Oracle\createcachedb-oracle.sql

2. Update the RDS SQL/Oracle server name in *.dsp file located under Client Manager installation directory.

Examples

For MSSQL,

CacheJdbcURL=jdbc:sqlserver://MSSQLDBServer:1433;databaseName=TESCache;SelectMethod=cursor

For Oracle,

CacheJdbcURL=jdbc:oracle:thin:@OracleDBServer:1521:orcl

3. Run the patch installer for Client Manager. For patch installation, see Running the Patch Installer of Windows 6.3.2 Patch Installation or Running the Patch Installer of Unix 6.3.2 Patch Installation. For manual patching, see Patching the 6.3.2 Build Client Manager.

4. Start CM service.

MS Azure SQL Service SupportFollow the below steps only when the CWA Master and Client Manager DB are migrated to MS Azure SQL service.

Master1. To restore the backup of SQL Database, execute the query provided in the below patch installer path:

Cisco_Workload_Automation_6.3.2_Patch_Installer_Release\Others\CLOUD_SQL\Azure_SQLQuery\Azure_SQLQuery.sql

Note: For the above step, the password of Tidal user is changed to Control@1234.

2. Update the MSSQL service name in the master.props located in the Master installation directory.

Example:

JdbcURL=jdbc:sqlserver://MSSQLDBServer:1433;selectMethod=cursor

3. Update DB user name, password and DB server name in master.props file as given below:

dbpwd=biSQQ#u&vj?Mk9LSWYRSdbuser=tidal@dbservername

Note: Replace dbservername with actual DB server name per the environment.

4. Run the patch installer for Master. For patch installation, see Running the Patch Installer of Windows 6.3.2 Patch Installation or Running the Patch Installer of Unix 6.3.2 Patch Installation. For manual patching, see Manually Patching the CWA Master.

14



5. Start Master service.

Client Manager1. To create Client Manager database, execute the queries provided in the patch installer path given below:

Cisco_Workload_Automation_6.3.2_Patch_Installer_Release\Others\CLOUD_SQL\Azure_SQLQuery\createcachedb-azure.sql Cisco_Workload_Automation_6.3.2_Patch_Installer_Release\Others\CLOUD_SQL\Azure_SQLQuery\cm_tescahe.sql

Note: For the above step, the password of TES user is changed to Control@1234.

2. Update the MSSQL Service name in *.dsp file located under Client Manager installation directory.

Example:

CacheJdbcURL=jdbc:sqlserver://MSSQLDBServer:1433;databaseName=TESCache;SelectMethod=cursor

3. Update DB user name, password and DB server name in *.dsp file located under Client Manager installation directory.

CachePassword=biSQQ#u&vj?Mk9LSWYRSCacheUserName=TES@dbservername

Note: Replace dbservername with actual DB Server name per the environment.

4. Run the patch installer for Client Manager. For patch installation, see Running the Patch Installer of Windows 6.3.2 Patch Installation or Running the Patch Installer of Unix 6.3.2 Patch Installation. For manual patching, see Patching the 6.3.2 Build Client Manager.

5. Start CM service.

15



16

Cisco Workload Automation 6.3.2 Patch Installation Guide the Standalone CWA Java Client Application...

Documents

Transcript of Cisco Workload Automation 6.3.2 Patch Installation Guide the Standalone CWA Java Client Application...