Tidal Workload Automation 6.3.3 Patch Installation Guide · tidalautomation.com 5 Preface This...

tidalautomation.com

Tidal Workload Automation Patch Installation Guide

Version 6.3.3First Published: February 2018

tidalautomation.com 2

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 PRODUCTS IN THIS MANUAL ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR STA GROUP REPRESENTATIVE FOR A COPY.

The 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. © 1981 Regents of the University of California. All rights reserved.

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 uncontrolled copies and the original online version should be referred to for latest version.

© 2018 STA Group LLC. All rights reserved.

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Obtaining Documentation and Submitting a Service Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Document Change History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Windows 6.3.3 Patch Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Pre-Installation Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Running the Patch Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Patching the Standalone TWA Java Client Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Post Installation Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

UNIX 6.3.3 Patch Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Pre-Installation Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Running the Patch Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Patching the Standalone TWA Java Client Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Manually Patching TWA 6.3.3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Manually Patching the TWA Master. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Manually Patching the TWA Backup Master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Manually Patching the TWA Fault Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Troubleshooting Missing Adapters after Patching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Manually Patching the TWA Client Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Patching the 6.3.3 Build Client Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Manually Patching the 6.3.3 Build TWA Java Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Manually Patching the 6.3.3 Build TWA Transporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Manually Patching the 6.3.3 Build TWA TES Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

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

Master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Client Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

MS Azure SQL Service Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Client Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23


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

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

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

Obtaining Documentation and Submitting a Service RequestFor information on obtaining documentation, submitting a service request, and gathering additional information, see What’s New in Tidal Product Documentation at:

https://docs.tidalautomation.com/rss

Subscribe to What’s New in Tidal Product Documentation, which lists all new and revised Tidal technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.

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

http://docs.tidalautomation.com/

Note: We sometimes update the documentation after original publication. Therefore, you should also review the documentation on tidalautomation.com for any updates.

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

Version Number Issue Date Reason for Change

6.3.3 Jan 2018 Rebranded Cisco Workload Automation (CWA) to Tidal Workload Automation (TWA).

New guide that describes how to apply 6.3.3 patch using the automated scripts provided for Windows and Unix, or alternatively how to manually patch TWA.


https://docs.tidalautomation.com/rss

http://docs.tidalautomation.com/

1Windows 6.3.3 Patch InstallationOverview

This chapter describes the automated process (sometimes called the mini-installer) to patch TWA 6.3.0, 6.3.1, or 6.3.2 to TWA 6.3.3. 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 TWA 6.3.3 chapter.

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

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

RequirementsTWA 6.3.0, 6.3.1 or 6.3.2 is mandatory to patch into 6.3.3 using TWA 6.3.3 patch installer.

Note: Upgrading to 6.3.3 is also possible using TWA 6.3.3 installer from version 6.3.0, 6.3.1, or 6.3.2. For complete installation and configuration instructions for all TWA components, see the Tidal 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”.


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:

<Tidal_Workload_Automation_6.3.3_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 TWA 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 TWA Master patching.

${TIDAL_HOME}\lib\mail.jar;

Note: If the backup master and fault monitor are installed, you need to upgrade the backup master and fault monitor separately, using the manual steps mentioned in the following sections:

Manually Patching the TWA Backup Master, page 14

Manually Patching the TWA Fault Monitor, page 15

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

<Tidal_Workload_Automation_6.3.3_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

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

4. After the TWA 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: Tidal_Workload_Automation_6.3.3_Patch_Installer_Release refers to the patch directory downloaded from the following location:

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

or

https://download.tidalautomation.com/

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

Post Installation ExceptionsAfter upgrading the 6.3.3 patch using patch installer, consider the following exceptions:

When you choose Start > All Programs, both CWA and TWA folders are present after upgrading 6.3.3 patch installer (both older and upgraded version folders are present).

In Control Panel, the older version and component names are not getting updated after upgrading process including Master, CM, Command Line, JC, and Transporter.

The Java Client icon in the Desktop shows the old branding name (CWA).

Please note that the old installer name and icon exists after upgrade to 6.3.3 patch installer.




2UNIX 6.3.3 Patch InstallationOverview

This chapter describes the automated process (sometimes called the mini-installer) to patch TWA 6.3.0, 6.3.1, or 6.3.2 to TWA 6.3.3 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 TWA 6.3.3 chapter.

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

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

RequirementsTWA 6.3.0, 6.3.1 or 6.3.2 is mandatory to patch into 6.3.3 using TWA 6.3.3patch installer.

Note: Upgrading to 6.3.3 is also possible using TWA 6.3.3 installer from version 6.3.0, 6.3.1, or 6.3.2. For complete installation and configuration instructions for all TWA components, see the Tidal 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”.



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:

<Tidal_Workload_Automation_6.3.3_Patch_Installer_Release>\master.

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

3. When prompted, provide the TWA 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 TWA 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:

<Tidal_Workload_Automation_6.3.3_Patch_Installer_Release>\cm.

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

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

4. After the TWA 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.



or


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




3Manually Patching TWA 6.3.3Overview

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

To use automated scripts to patch TWA 6.3.3, see the following chapters:

Chapter 1, “Windows 6.3.3 Patch Installation,”

Chapter 2, “UNIX 6.3.3 Patch Installation,”

RequirementsTWA 6.3.0, 6.3.1, or 6.3.2 is mandatory to patch into 6.3.3using TWA 6.3.3 patch installer.

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

Manually Patching the TWA 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

Note: Tidal_Workload_Automation_6.3.3_Patch_Installer_Release refers to the patch directory downloaded from CISCO.COM at:


or


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

2. Backup the adapter configuration files as follows:




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 <Tidal_Workload_Automation_6.3.3_Patch_Installer_Release>\master\ to MASTER_INSTALLED_DIR\Master\config.

UNIX example:

/opt/TIDAL/master/config

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

UNIX example:

/opt/TIDAL/master/lib/

5. Copy “tesclient.war” from Tidal_Workload_Automation_6.3.3_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 TWA Web Client or the TWA Java Client. If the version is not shown correctly, follow the troubleshooting instructions in Troubleshooting Missing Adapters after Patching.




Manually Patching the TWA 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



or


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

2. Copy “scheduler.jar”, “adapterhost.jar” from Tidal_Workload_Automation_6.3.3_Patch_Installer_Release\master\ to MASTER_INSTALLED_DIR\Master\lib.

3. Copy “tesclient.war” from Tidal_Workload_Automation_6.3.3_Patch_Installer_Release\master\ to MASTER_INSTALLED_DIR\Master\webapps.


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

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

5. Start the Backup Master service.

Manually Patching the TWA Fault MonitorIn 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: Tidal_Workload_Automation_6.3.3_Patch_Installer_Release refers to the patch directory downloaded from the location:


or






To patch the TWA Fault Monitor:

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

Troubleshooting Missing Adapters after Patching

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

2. Backup the adapter configuration files (if present) following the instructions in Manually Patching the TWA 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 TWA 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



or


Patching the 6.3.3 Build Client Manager

To patch the Client Manager on top of TWA 6.3.0, 6.3.1, or 6.3.2 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 Tidal_Workload_Automation_6.3.3_Patch_Installer_Release\cm to CM_INSTALLED_DIR\webapps.

5. Copy the files below from Tidal_Workload_Automation_6.3.3_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 Tidal_Workload_Automation_6.3.3_Patch_Installer_Release\cm to CM_INSTALLED_DIR\lib:

— ClientManager.jar

— 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 TWA 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.3 Build TWA Java ClientThis section explains the process to patch the standalone TWA Java Client application. The Java Client that uses the Web interface is patched when you patch the TWA Master.

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

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

Windows Example:

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


3. Copy “Framework.jar, SchedulerApi.jar, and tesclient.jar” from Tidal_Workload_Automation_6.3.3_Patch_Installer_Release\ tesclient to TWA Client_INSTALLED_DIR\lib.

Windows Example:

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

4. Start the TWA Java Client.


Manually Patching the 6.3.3 Build TWA TransporterThis section explains the process to patch the TWA Transporter application.

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

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

3. Copy "Transporter.jar" from Tidal_Workload_Automation_6.3.3_Patch_Installer_Release\Others to TWA Transporter_INSTALLED_DIR\lib.

Example path:

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

4. Open Transporter.

Manually Patching the 6.3.3 Build TWA TES Command LineThis section explains the process to patch the TWA TESCmdLine application.

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

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

3. Copy "TESCmdLine.jar" from Tidal_Workload_Automation_6.3.3_Patch_Installer_Release\Others to TWA TESCmdLine_INSTALLED_DIR\lib.

Example path:

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

4. Open TESCmdLine.


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

The following steps are applicable only when the TWA 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.

Tidal_Workload_Automation_6.3.3_Patch_Installer_Release\Others\CLOUD_SQL\AWS_SQLQuery\MSSQL\AWS_SQLQuery.sqlTidal_Workload_Automation_6.3.3_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.3 Patch Installation or Running the Patch Installer of Unix 6.3.3 Patch Installation. For manual patching, see Manually Patching the TWA Master.


Client Manager1. Create Client Manager database.

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


Tidal_Workload_Automation_6.3.3_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:

Tidal_Workload_Automation_6.3.3_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.3 Patch Installation or Running the Patch Installer of Unix 6.3.3 Patch Installation. For manual patching, see Patching the 6.3.3 Build Client Manager.

4. Start CM service.

MS Azure SQL Service SupportFollow the below steps only when the TWA 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:

Tidal_Workload_Automation_6.3.3_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.3 Patch Installation or Running the Patch Installer of Unix 6.3.3 Patch Installation. For manual patching, see Manually Patching the TWA Master.

5. Start Master service.


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

Tidal_Workload_Automation_6.3.3_Patch_Installer_Release\Others\CLOUD_SQL\Azure_SQLQuery\createcachedb-azure.sql Tidal_Workload_Automation_6.3.3_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.3 Patch Installation or Running the Patch Installer of Unix 6.3.3 Patch Installation. For manual patching, see Patching the 6.3.3 Build Client Manager.

5. Start CM service.


Tidal Workload Automation 6.3.3 Patch Installation Guide · tidalautomation.com 5 Preface This...

Documents

Transcript of Tidal Workload Automation 6.3.3 Patch Installation Guide · tidalautomation.com 5 Preface This...