Resiliency Orchestration Installation Guide 7.1 SP7(English)

Installation Guide Version 7.1 SP7

© Copyright IBM, an IBM Company 2003, 2017 Resiliency Orchestration - Installation Guide 2

DISCLAIMER

IBM, an IBM Company believes that the information in this publication is accurate as of its publication date. The information is subject to change without notice.

COPYRIGHT

© Copyright IBM, an IBM Company 2003, 2017.

Printed August 2017. Use, copy, and distribution of any IBM, an IBM Company software described in this publication needs an applicable software license. No part of this product or document may be reproduced, stored in a retrieval system, or transmitted, in any form by any means, electronic, mechanical, photocopy, recording, or otherwise, without prior written authorization of IBM, an IBM Company and its licensers, if any.


CONTENTS PREFACE ........................................................................................................................................................................ 12

Purpose ......................................................................................................................................................................... 12Audience ...................................................................................................................................................................... 12Conventions ................................................................................................................................................................. 13Acronyms ..................................................................................................................................................................... 13

1. INSTALLATION OVERVIEW ................................................................................................................................. 14

New version in FTP ..................................................................................................................................................... 14IBM Resiliency Orchestration Client Agent Support .................................................................................................. 15Client Browser Prerequisite ......................................................................................................................................... 16Prerequisites ................................................................................................................................................................. 16GPL Dependencies for RESILIENCY ORCHESTRATION ...................................................................................... 16GPL Dependencies for RESILIENCY FILE REPLICATOR ...................................................................................... 16Java Tools Prerequisite ................................................................................................................................................ 17

2. RESILIENCY ORCHESTRATION SERVER INSTALLATION ON LINUX USING GRAPHICAL MODE 19

System Requirements - for Agents configured on Resiliency Orchestration Server ................................................... 19System Requirements – when Agents installed/configured on Managed Systems ..................................................... 19System Requirements – for Site Controller ................................................................................................................. 20Installation of Resiliency Orchestration Server ........................................................................................................... 20Installation of Linux Enterprise Server OS .................................................................................................................. 21

Installation of MySQL ............................................................................................................................................. 23Installation of Resiliency Orchestration Server Software ....................................................................................... 27

Post Installation Steps .................................................................................................................................................. 37Configuring Resiliency Orchestration Server .............................................................................................................. 39

Server Memory Management .................................................................................................................................. 39Recommended Settings ............................................................................................................................................ 39MySQL connectivity configuration for Resiliency Orchestration Server ................................................................ 39Configuring Resiliency Orchestration with different MySQL user ......................................................................... 39Configuring Resiliency Orchestration with different MySQL user password ......................................................... 40Configuration Changes in Tomcat .......................................................................................................................... 41Steps to Enable Compression in Tomcat Server ..................................................................................................... 43Configuring Current Events .................................................................................................................................... 44Fetch Logs ............................................................................................................................................................... 44

Server Hardening ......................................................................................................................................................... 44Starting and Stopping Resiliency Orchestration Server ............................................................................................... 45

Starting Resiliency Orchestration Server ................................................................................................................ 45Starting Resiliency Orchestration Server in Recover Mode ................................................................................... 45Stopping Resiliency Orchestration Server .............................................................................................................. 45Restarting Resiliency Orchestration Server ............................................................................................................ 45Checking Resiliency Orchestration Server Status ................................................................................................... 46Checking Resiliency Orchestration Server available Modes .................................................................................. 46

3. RESILIENCY ORCHESTRATION SERVER INSTALLATION ON LINUX CLUSTER USING GRAPHICAL MODE ..................................................................................................................................................... 47

System Requirements ................................................................................................................................................... 47Installation of Resiliency Orchestration Server ........................................................................................................... 48

Installation of Linux Enterprise Server OS ............................................................................................................. 48Installation of Linux Cluster ................................................................................................................................... 49Installation of MySQL ............................................................................................................................................. 50Upgrade of MySQL ................................................................................................................................................. 50Installation of Resiliency Orchestration Server Software ....................................................................................... 51


Starting and Stopping Resiliency Orchestration Server ............................................................................................... 52Configuring Linux Cluster ........................................................................................................................................... 53

4. RESILIENCY ORCHESTRATION INSTALLATION .......................................................................................... 55

5. INSTALLING AGENT NODE SERVER ON LINUX ............................................................................................ 57

6. INSTALLING AGENTS ON WINDOWS SERVER ............................................................................................... 64

Pre-requisites for Installing Resiliency Orchestration Agents ..................................................................................... 64Windows Server Requirements ................................................................................................................................ 64

Installation of supported JRE. To know the supported JRE, refer to Prerequisites ..................................................... 65GPL Dependencies for RESILIENCY ORCHESTRATION ....................................... Error! Bookmark not defined.GPL Dependencies for RESILIENCY FILE REPLICATOR ....................................... Error! Bookmark not defined.

Host Machines with Virtual IP Address .................................................................................................................. 66Specific Prerequisites .............................................................................................................................................. 66

Installation of Agents ................................................................................................................................................... 67Debugging Agent Installation on Windows Server ..................................................................................................... 77

Starting and Stopping of Agent Services on Windows Server ................................................................................. 77

7. INSTALLING AGENTS ON SOLARIS SERVER .................................................................................................. 79

Pre-requisites for Installing Resiliency Orchestration Agents ..................................................................................... 79Solaris Server Requirements ................................................................................................................................... 79Host Machines with Virtual IP Address .................................................................................................................. 80

Installation of Agents ................................................................................................................................................... 80Debugging Agent Installation on Solaris Server .......................................................................................................... 88

Starting and Stopping Agents on Solaris Server ..................................................................................................... 88

8. INSTALLING AGENTS ON LINUX SERVER ...................................................................................................... 91

Installation of Agents ................................................................................................................................................... 91Debugging Agent Installation on Linux Server ......................................................................................................... 100

Starting and Stopping Agents on Linux Server ..................................................................................................... 100

9. INSTALLING AGENTS ON HPUX SERVER ...................................................................................................... 102

Installation of Agents ................................................................................................................................................. 102Debugging Agent Installation on HPUX Server ........................................................................................................ 110

Starting and Stopping Agents on HPUX Server .................................................................................................... 110

10. INSTALLING AGENTS ON AIX SERVER ......................................................................................................... 112

Pre-requisites for Installing Resiliency Orchestration Agents ................................................................................... 112AIX Server Requirements ...................................................................................................................................... 112Host Machines with Virtual IP Address ................................................................................................................ 112

Installation of Agents ................................................................................................................................................. 113Starting and Stopping of Agents on AIX Server .................................................................................................... 121

11. INSTALLING RESILIENCY ORCHESTRATION ADVANCED REPORTER .............................................. 123Pre-requisite ............................................................................................................................................................... 123GUI Mode Installation of Resiliency Orchestration Advanced Reporter ................................................................. 123

12. INSTALLATION OF RESILIENCY ORCHESTRATION UPGRADE ASSIST ............................................. 131

Pre-requisites .............................................................................................................................................................. 131Installation .................................................................................................................................................................. 131Steps to Upgrade Agent from Resiliency Orchestration. ........................................................................................... 137Agent/RESILIENCY FILE REPLICATOR Auto-Rollback Functionality ............................................................... 139

13. SILENT MODE INSTALLATION OF RESILIENCY ORCHESTRATION ADVANCED REPORTER ..... 140

Editing Properties File .......................................................................................................................................... 140Installing Resiliency Orchestration Advanced Reporter on Linux ........................................................................ 140

14. INSTALLING RESILIENCY ORCHESTRATION USING SILENT MODE INSTALLATION .................. 141


Editing Properties File ............................................................................................................................................... 142Resiliency Orchestration Agent Server Silent Mode Installation .............................................................................. 145

Starting Silent Mode Installation on Windows System .......................................................................................... 145Starting Silent Mode Installation on Solaris/Linux/HPUX/AIX Servers ............................................................... 145

Vault Configuration: .................................................................................................................................................. 14615. UPGRADING RESILIENCY ORCHESTRATION SERVER ........................................................................... 147

Resiliency Orchestration Server Upgrade .................................................................................................................. 147Upgrading Resiliency Orchestration Server in GUI mode ........................................................................................ 148License Management ................................................................................................................................................. 156Post Upgrade tasks ..................................................................................................................................................... 156Server Memory Management ..................................................................................................................................... 157Backup and Fallback Plan .......................................................................................................................................... 157

Backup Plan .......................................................................................................................................................... 157Fallback Plan ........................................................................................................................................................ 157

16. UPGRADING RESILIENCY ORCHESTRATION ADVANCED REPORTER .............................................. 159

17.UPGRADING RESILIENCY ORCHESTRATION AGENTS ............................................................................ 160

Resiliency Orchestration Agent Upgrade [Optional] ................................................................................................. 160Prerequisites: ........................................................................................................................................................ 160Steps: ..................................................................................................................................................................... 160

18. UPGRADING AGENTS ON WINDOWS SERVER ........................................................................................... 161

Pre-requisites before upgrading Agents on Windows Server .................................................................................... 161Limitations ................................................................................................................................................................. 161Upgrading Agents on Windows Server in GUI mode ............................................................................................... 161

19. UPGRADING AGENTS ON SOLARIS SERVER .............................................................................................. 171

Pre-requisites before upgrading agents on Solaris Server ......................................................................................... 171Limitations ................................................................................................................................................................. 171Upgrading Agents on Solaris Server in GUI mode .................................................................................................... 171

20. UPGRADING AGENTS ON LINUX SERVER ................................................................................................... 180

Pre-requisites before upgrading agents on Linux Server ........................................................................................... 180Limitations ................................................................................................................................................................. 180Upgrading Agents on Linux Server in GUI mode ..................................................................................................... 180

21. UPGRADING AGENTS ON HPUX SERVER .................................................................................................... 190

Pre-requisites before upgrading agents on HPUX Server .......................................................................................... 190Limitations ................................................................................................................................................................. 190Upgrading Agents on HPUX Server in GUI mode .................................................................................................... 190

22. UPGRADING AGENTS ON AIX SERVER ........................................................................................................ 199

Pre-requisites before upgrading agents on AIX Server ............................................................................................. 199Limitations ................................................................................................................................................................. 199Upgrading Agents on AIX Server in GUI mode ........................................................................................................ 199

23. UPGRADING RESILIENCY ORCHESTRATION AGENTS USING SILENT MODE INSTALLATION . 209

Pre-requisites before upgrading agents on AIX Server ............................................................................................. 209Limitations ................................................................................................................................................................. 209Editing Properties File ............................................................................................................................................... 209

Starting Silent Mode Upgrade on Windows System .............................................................................................. 211Starting Silent Mode Installation on Solaris/Linux/HPUX/AIX Servers ............................................................... 211

24. UPGRADING VAULT TO VAULT ....................................................................................................................... 212

Pre-requisites .............................................................................................................................................................. 212


Vault to Vault Upgrade Steps .................................................................................................................................... 212Steps to Apply patch. .............................................................................................................................................. 213

25. UPGRADING NON VAULT TO VAULT ............................................................................................................. 214

Steps to Apply patch .................................................................................................................................................. 214

26. UPGRADING RESILIENCY ORCHESTRATION 7.1 GA TO RESILIENCY ORCHESTRATION 7.1 P2 LICENSE PATCH ......................................................................................................................................................... 215

Steps to Apply patch .................................................................................................................................................. 21627. RESILIENCY FILE REPLICATOR THIRD PARTY INSTALLATION ......................................................... 219

Third Party Binary Installation For Windows-32/64-Bit .......................................................................................... 219Third Party Binary Installation For Linux-32-Bit ..................................................................................................... 219Third Party Binary Installation For Linux-64-Bit ..................................................................................................... 219Third Party Binary Installation For AIX ................................................................................................................... 220Third Party Binary Installation For HPUX-64-BIT Itanium .................................................................................... 221Third Party Binary Installation For HPUX-64-BIT Parisac ..................................................................................... 221Third Party Binary Installation For Solaris_Sparc .................................................................................................... 222Third Party Binary Installation For Solaris_Intel ..................................................................................................... 223

28. UPGRADING RESILIENCY ORCHESTRATION 7.1 P2 TO RESILIENCY ORCHESTRATION 7.1 SP1 LICENSE PATCH ......................................................................................................................................................... 225

Steps to Apply patch .................................................................................................................................................. 225

29. UPGRADING RESILIENCY ORCHESTRATION 7.1 SP1 TO RESILIENCY ORCHESTRATION 7.1 SP2......................................................................................................................................................................................... 227




33. UPGRADING RESILIENCY ORCHESTRATION 6.3 SP5, SP6, AND SP7 TO RESILIENCY ORCHESTRATION 7.1 SP6 ........................................................................................................................................ 231

34. UNINSTALLING RESILIENCY ORCHESTRATION AGENT NODE .......................................................... 232

Uninstallation of Resiliency Orchestration Agent Node ............................................................................................ 232

35. UNINSTALLING RESILIENCY ORCHESTRATION SERVER AND AGENTS .......................................... 234

Uninstallation of Resiliency Orchestration Server ..................................................................................................... 234GUI ........................................................................................................................................................................ 234Command Prompt ................................................................................................................................................. 237

Uninstallation of Agents ............................................................................................................................................ 237Windows ................................................................................................................................................................ 238Solaris .................................................................................................................................................................... 238Linux ...................................................................................................................................................................... 238HPUX .................................................................................................................................................................... 239AIX ......................................................................................................................................................................... 239

36. INSTALLING RESILIENCY ORCHESTRATION OS COMMAND PROCESSOR ..................................... 240

Prerequisites ............................................................................................................................................................... 240Overview .................................................................................................................................................................... 240Installing OS Command Processor ............................................................................................................................ 241

Extracting Installation File ................................................................................................................................... 241Authorizing APF for TCMD and ZCMD ............................................................................................................... 242Defining Userid IBM to RACF/Other Security Program ...................................................................................... 243


Verifying Sz/OS CP (Command Processor) Install ................................................................................................... 24337. INSTALLING RESILIENCY ORCHESTRATION SCLM CL BINARIES FOR MIMIX WITH AS400 .... 246

Overview .................................................................................................................................................................... 246Installing IBM cl Binaries for Mimix ........................................................................................................................ 246Verifying the IBM Cl Binaries for Mimix Installation .............................................................................................. 247

38. MIGRATING RESILIENCY ORCHESTRATION SERVER TO NEW SERVER WITH SAME IP ........... 248

39. MIGRATING RESILIENCY ORCHESTRATION SERVER TO NEW SERVER WITH NEW IP ............. 250

40. TROUBLESHOOTING ......................................................................................................................................... 252

Agent Not Starting on Windows Server .................................................................................................................... 252Agent Not Stating on Solaris Server .......................................................................................................................... 253Agent Not Stating on Linux Server ........................................................................................................................... 254Agent Not Starting on AIX Server ............................................................................................................................. 256Agent Not Starting on HPUX Server ......................................................................................................................... 257Nat IP ......................................................................................................................................................................... 257Web Browser displays certificate error ...................................................................................................................... 258Server/Advanced Reporter installation fails with UnsatisfiedLinkError ................................................................... 259

41. LICENSE INFORMATION .................................................................................................................................. 260

GPL License Information ........................................................................................................................................... 260INDEX ............................................................................................................................................................................ 261


LIST OF FIGURES Figure 1: IBM Resiliency Orchestration Installer ............................................................................................... 28Figure 2: IBM Resiliency Orchestration Server Installation - MySQL root password ...................................... 28Figure 3: IBM Resiliency Orchestration Server Installation - Tomcat Home .................................................... 29Figure 4: IBM Resiliency Orchestration Server Installation - Introduction ....................................................... 29Figure 5: IBM Resiliency Orchestration Server Installation - License Agreement ............................................ 30Figure 6: IBM Resiliency Orchestration Server Installation - Choose Install Folder ......................................... 31Figure 7: IBM Resiliency Orchestration Server Installation – User Management System ................................ 31Figure 8: IBM Resiliency Orchestration Server Installation - Pre-Installation Summary .................................. 32Figure 9: IBM Resiliency Orchestration Server Installation - Installing IBM Resiliency Orchestration Server 32Figure 10: IBM Resiliency Orchestration Server Installation - Confirmation message ..................................... 33Figure 11: IBM Resiliency Orchestration Server Installation - Advanced User Server Details 1 ..................... 34Figure 12: IBM Resiliency Orchestration Server Installation - Advanced User Server Details 2 ..................... 34Figure 13: IBM Resiliency Orchestration Server Installation - Support User Account ..................................... 35Figure 14: IBM Resiliency Orchestration Server Installation - System Configuration ...................................... 36Figure 15: IBM Resiliency Orchestration Server Installation – Update mysql configuration file ..................... 36Figure 16: IBM Resiliency Orchestration Server Installation - Installation Completed .................................... 37Figure 17: IBM Resiliency Orchestration Agent Node Installer ........................................................................ 58Figure 18: IBM Resiliency Orchestration Agent Node Installation on Linux - Introduction ............................. 58Figure 19: IBM Resiliency Orchestration Agent Node Installation on Linux - Choose Install Folder .............. 59Figure 20: IBM Resiliency Orchestration Agent Node Installation on Linux - IBM Resiliency Orchestration Agent Node IP Address Configuration .......................................................................................................................... 59Figure 21: IBM Resiliency Orchestration Agent Node Installation on Linux - Pre - Installation Summary ..... 60Figure 22: IBM Resiliency Orchestration Agent Node Installation on Linux - Installing IBM Resiliency Orchestration Agent Node ......................................................................................................................................................... 61Figure 23: IBM Resiliency Orchestration Agent Node Installation on Linux - Starting IBM Resiliency Orchestration Agent Node ......................................................................................................................................................... 61Figure 24: IBM Resiliency Orchestration Agent Node Installation on Linux - Installation Completed ............ 62Figure 25: IBM Resiliency Orchestration Agent Installer .................................................................................. 68Figure 26: IBM Resiliency Orchestration Agents Installation on Windows Server - Introduction .................... 69Figure 27: IBM Resiliency Orchestration Agents Installation on Windows Server - Choose Install Folder ..... 69Figure 28: IBM Resiliency Orchestration Agents Installation on Windows Server - Choose Agents - Windows70Figure 29: IBM Resiliency Orchestration Agents Installation on Windows Server - Choose Shortcut Folder . 71Figure 30: IBM Resiliency Orchestration Agents Installation on Windows Server - Agent Configuration ...... 72Figure 31: IBM Resiliency Orchestration Agents Installation on Windows Server - IBM Resiliency Orchestration IP Address Configuration ........................................................................................................................................ 73Figure 32: IBM Resiliency Orchestration Site Controller IP Address Configuration on Windows server ........ 73Figure 33: IBM Resiliency Orchestration Agents Installation on Windows Server - Pre-Installation Summary74Figure 34: IBM Resiliency Orchestration Agents Installation on Windows Server - Installing IBM Resiliency Orchestration Agents .......................................................................................................................................... 74Figure 35: IBM Resiliency Orchestration Agents Installation on Windows Server - Starting Agents .............. 75Figure 36: IBM Resiliency Orchestration Agents Installation on Windows Server - Install Complete ............. 76Figure 37: IBM Resiliency Orchestration Agent Installer .................................................................................. 81Figure 38: IBM Resiliency Orchestration Agents Installation on Solaris Server - Introduction ........................ 81Figure 39: IBM Resiliency Orchestration Agents Installation on Solaris Server - Choose Install Folder ......... 82Figure 40: IBM Resiliency Orchestration Agents Installation on Solaris Server - Choose Agents - Solaris ..... 82Figure 41: IBM Resiliency Orchestration Agents Installation on Solaris Server - Choose Link Folder ............ 83Figure 42: IBM Resiliency Orchestration Agents Installation on Solaris Server - Agent Configuration .......... 84Figure 43: IBM Resiliency Orchestration Agents Installation on Solaris Server - Agent Configuration .......... 84Figure 44: IBM Resiliency Orchestration Agents Installation on Solaris Server - IBM Resiliency Orchestration IP Address Configuration ........................................................................................................................................ 85Figure 45: IBM Resiliency Orchestration Site Controller IP Address Configuration on Solaris Server ........... 86Figure 46: IBM Resiliency Orchestration Agents Installation on Solaris Server - Pre-Installation Summary .. 86Figure 47: IBM Resiliency Orchestration Agents Installation on Solaris Server - Installing IBM Resiliency Orchestration Agents .......................................................................................................................................... 87Figure 48: IBM Resiliency Orchestration Agents Installation on Solaris Server - Starting Agents ................... 87Figure 49: IBM Resiliency Orchestration Agents Installation on Solaris Server - Install Complete ................. 88Figure 50: IBM Resiliency Orchestration Agent Installer .................................................................................. 92


Figure 51: IBM Resiliency Orchestration Agents Installation on Linux Server - Introduction ......................... 92Figure 52: IBM Resiliency Orchestration Agents Installation on Linux Server - Choose Install Folder ........... 93Figure 53: IBM Resiliency Orchestration Agents Installation on Linux Server - Choose Agents - Linux ........ 93Figure 54: IBM Resiliency Orchestration Agents Installation on Linux Server - Choose Link Folder ............. 94Figure 55: IBM Resiliency Orchestration Agents Installation on Linux Server - Agent Configuration ............ 95Figure 56: IBM Resiliency Orchestration Agents Installation on Linux Server - Agent Configuration ............ 95Figure 57: IBM Resiliency Orchestration Agents Installation on Linux Server - Agent Configuration ............ 96Figure 58: IBM Resiliency Orchestration Agents Installation on Linux Server - IBM Resiliency Orchestration IP Address Configuration ........................................................................................................................................ 96Figure 59: IBM Resiliency Orchestration Site Controller IP Address Configuration on Linux server .............. 97Figure 60: IBM Resiliency Orchestration Agents Installation on Linux Server - Pre - Installation screen ....... 97Figure 61: IBM Resiliency Orchestration Agents Installation on Linux Server - Installing IBM Resiliency Orchestration Agents ................................................................................................................................................................. 98Figure 62: IBM Resiliency Orchestration Agents Installation on Linux Server - Starting Agents .................... 98Figure 63: IBM Resiliency Orchestration Agents Installation on Linux Server - Install Complete ................... 99Figure 64: IBM Resiliency Orchestration Agent Installer ................................................................................ 103Figure 65: IBM Resiliency Orchestration Agents Installation on HPUX Server - Introduction ...................... 103Figure 66: IBM Resiliency Orchestration Agents Installation on HPUX Server - Choose Install Folder ....... 104Figure 67: IBM Resiliency Orchestration Agents Installation on HPUX Server - Choose Agents - HPUX ... 104Figure 68: IBM Resiliency Orchestration Agents Installation on HPUX Server - Choose Link Folder .......... 105Figure 69: IBM Resiliency Orchestration Agents Installation on HPUX Server - Agent Configuration ......... 106Figure 70: IBM Resiliency Orchestration Agents Installation on HPUX Server - Agent Configuration ......... 106Figure 71: IBM Resiliency Orchestration Agents Installation on HPUX Server - Agent Configuration ......... 107Figure 72: IBM Resiliency Orchestration Agents Installation on HPUX Server - IBM Resiliency Orchestration IP Address configuration ....................................................................................................................................... 107Figure 73: IBM Resiliency Orchestration Site Controller IP Address Configuration on HPUX server .......... 108Figure 74: IBM Resiliency Orchestration Agents Installation on HPUX Server - Pre-Installation Summary . 108Figure 75: IBM Resiliency Orchestration Agents Installation on HPUX Server - Installing IBM Resiliency Orchestration Agents ........................................................................................................................................ 109Figure 76: IBM Resiliency Orchestration Agents Installation on HPUX Server - Starting Agents ................. 109Figure 77: IBM Resiliency Orchestration Agents Installation on HPUX Server - Install Complete ............... 110Figure 78: IBM Resiliency Orchestration Agent Installer ................................................................................ 113Figure 79: IBM Resiliency Orchestration Agents Installation on AIX Server - Introduction .......................... 114Figure 80: IBM Resiliency Orchestration Agents Installation on AIX Server - Choose Install Folder ........... 114Figure 81: IBM Resiliency Orchestration Agents Installation on AIX Server - Choose Agents - AIX ........... 115Figure 82: IBM Resiliency Orchestration Agents Installation on AIX Server - Choose Link Folder .............. 115Figure 83: IBM Resiliency Orchestration Agents Installation on AIX Server - Agent Configuration ............ 116Figure 84: IBM Resiliency Orchestration Agents Installation on AIX Server - Agent Configuration ............ 117Figure 85: IBM Resiliency Orchestration Agents Installation on AIX Server - IBM Resiliency Orchestration IP Address configuration ..................................................................................................................................................... 118Figure 86: IBM Resiliency Orchestration Site Controller IP Address Configuration on AIX server .............. 118Figure 87: IBM Resiliency Orchestration Agents Installation on AIX Server - Pre-Installation Summary .... 119Figure 88: IBM Resiliency Orchestration Agents Installation on AIX Server - Installing IBM Resiliency Orchestration Agents ............................................................................................................................................................... 119Figure 89: IBM Resiliency Orchestration Agents Installation on AIX Server - Starting Agents ..................... 120Figure 90: IBM Resiliency Orchestration Agents Installation on AIX Server - Install Complete ................... 121Figure 91: IBM Resiliency Orchestration Advanced Reporter Installer .......................................................... 124Figure 92: IBM Resiliency Orchestration Advanced Reporter Installation - MySQL root password .............. 124Figure 93: IBM Resiliency Orchestration Advanced Reporter Installation - Tomcat Home ........................... 125Figure 94: IBM Resiliency Orchestration Advanced Reporter Installation - Tomcat Path .............................. 125Figure 95: IBM Resiliency Orchestration Advanced Reporter Installation - Introduction .............................. 126Figure 96: IBM Resiliency Orchestration Advanced Reporter Installation - Choose IBM Resiliency Orchestration Server Folder ..................................................................................................................................................... 126Figure 97: IBM Resiliency Orchestration Advanced Reporter Installation - Pre-Installation Summary ......... 127Figure 98: IBM Resiliency Orchestration Advanced Reporter Installation - Installing IBM Resiliency Orchestration Advanced Reporter ........................................................................................................................................... 128Figure 99: IBM Resiliency Orchestration Advanced Reporter Installation - Confirmation message .............. 128Figure 100: IBM Resiliency Orchestration Advanced Reporter Installation - Installation Completed ............ 129Figure 101: IBM Resiliency Orchestration Upgrade Assist - Introduction ..................................................... 131Figure 102: IBM Resiliency Orchestration Upgrade Assist – Choose Installer File ........................................ 132


Figure 103: IBM Resiliency Orchestration Upgrade Assist - Choose Link Folder .......................................... 132Figure 104: IBM Resiliency Orchestration Upgrade Assist – Choose Installed Agents .................................. 133Figure 105: IBM Resiliency Orchestration Upgrade Assist – Choose IBM Resiliency Orchestration Agents Installation........................................................................................................................................................................... 134Figure 106: IBM Resiliency Orchestration Upgrade Assist – RESILIENCY FILE REPLICATOR Service Installation........................................................................................................................................................................... 134Figure 107: IBM Resiliency Orchestration Upgrade Assist – Pre Installation Summary ................................ 135Figure 108: IBM Resiliency Orchestration Upgrade Assist – Installing IBM Resiliency Orchestration Upgrade Assist........................................................................................................................................................................... 135Figure 109: IBM Resiliency Orchestration Upgrade Assist – Starting IBM Resiliency Orchestration Upgrade Assist........................................................................................................................................................................... 136Figure 110: IBM Resiliency Orchestration Upgrade Assist – Install Complete ............................................... 137Figure 111: IBM Resiliency Orchestration Installer ......................................................................................... 148Figure 112: IBM Resiliency Orchestration Server Upgrade - MySQL root password ..................................... 149Figure 113: IBM Resiliency Orchestration Server Upgrade - Tomcat Home .................................................. 149Figure 114: IBM Resiliency Orchestration Server Upgrade - Introduction ..................................................... 150Figure 115: IBM Resiliency Orchestration Server Upgrade - License Agreement .......................................... 150Figure 116: IBM Resiliency Orchestration Server Upgrade - Choose Install Folder ....................................... 151Figure 117: IBM Resiliency Orchestration Server Upgrade - Choose Install Set ............................................ 152Figure 118: IBM Resiliency Orchestration Server Upgrade - Pre-Installation Summary ................................ 153Figure 119: IBM Resiliency Orchestration Server Upgrade - Installing IBM Resiliency Orchestration Server154Figure 120: IBM Resiliency Orchestration Server Upgrade - Backing up the Metadata ................................. 154Figure 121: IBM Resiliency Orchestration Server Upgrade - Upgrade of the Metadata Scheme .................... 155Figure 122: IBM Resiliency Orchestration Server Upgrade - Upgrade Complete ........................................... 155Figure 123: Upgrade IBM Resiliency Orchestration Advance Reporter - Metadata refresh screen for Advanced Reporter ............................................................................................................................................................. 159Figure 124: IBM Resiliency Orchestration Agent Installer .............................................................................. 162Figure 125: Upgrade Agents on Windows Server - Introduction ..................................................................... 162Figure 126: Upgrade Agents on Windows Server - Choose Install Folder ...................................................... 163Figure 127: Upgrade Agents on Windows Server - Choose Install Set ............................................................ 164Figure 128: Upgrade Agents on Windows Server - Agents Running Error Message ...................................... 164Figure 129: Upgrade Agents on Windows Server - Choose Agents - Windows .............................................. 165Figure 130: Upgrade Agents on Windows Server - Choose Shortcut Folder ................................................... 165Figure 131: Upgrade Agents on Windows Server - Agent Configuration ........................................................ 166Figure 132: Upgrade Agents on Windows Server – NAT IP Address Configuration ...................................... 167Figure 133: Upgrade Agents on Windows Server – Site Controller Configuration ......................................... 167Figure 134: Upgrade Agents on Windows Server - Pre-Installation Summary ................................................ 168Figure 135: Upgrade Agents on Windows Server - Installing IBM Resiliency Orchestration Agents ............ 168Figure 136: Upgrade Agents on Windows Server - Starting Agents ................................................................ 169Figure 137: Upgrade Agents on Windows Server - Upgrade Complete .......................................................... 170Figure 138: IBM Resiliency Orchestration Agent Installer .............................................................................. 172Figure 139: Upgrade Agents on Solaris Server - Introduction ......................................................................... 172Figure 140: Upgrade Agents on Solaris Server - Choose Install Folder ........................................................... 173Figure 141: Upgrade Agents on Solaris Server - Choose Install Set ................................................................ 174Figure 142: Upgrade Agents on Solaris Server - Choose Agents - Solaris ...................................................... 174Figure 143: Upgrade Agents on Solaris Server - Choose Link Folder ............................................................. 175Figure 144: Upgrade Agents on Solaris Server – NAT IP Address Configuration .......................................... 176Figure 145: Upgrade Agents on Solaris Server – Site Controller Configuration ............................................. 176Figure 146: Upgrade Agents on Solaris Server - Pre-Installation Summary .................................................... 177Figure 147: Upgrade Agents on Solaris Server - Installing IBM Resiliency Orchestration Agents ................ 177Figure 148: Upgrade Agents on Solaris Server - Starting Agents .................................................................... 178Figure 149: Upgrade Agents on Solaris Server - Upgrade Complete ............................................................... 179Figure 150: IBM Resiliency Orchestration Agent Installer .............................................................................. 181Figure 151: Upgrade Agents on Linux Server - Introduction ........................................................................... 181Figure 152: Upgrade Agents on Linux Server - Choose Install Folder ............................................................ 182Figure 153: Upgrade Agents on Linux Server - Choose Install Set ................................................................. 183Figure 154: Upgrade Agents on Linux Server - Choose Agents - Linux ......................................................... 183Figure 155: Upgrade Agents on Linux Server - Choose Link Folder ............................................................... 184Figure 156: Upgrade Agents on Linux Server - Agent Configuration ............................................................. 185Figure 157: Upgrade Agents on Linux Server - Agent Configuration ............................................................. 185


Figure 158: Upgrade Agents on Linux Server – NAT IP Address Configuration ............................................ 186Figure 159: Upgrade Agents on Linux Server – Site Controller Configuration ............................................... 186Figure 160: Upgrade Agents on Linux Server - Pre-Installation Summary ..................................................... 187Figure 161: Upgrade Agents on Linux Server - Installing IBM Resiliency Orchestration Agents .................. 187Figure 162: Upgrade Agents on Linux Server - Starting Agents ...................................................................... 188Figure 163: Upgrade Agents on Linux Server - Upgrade Complete ................................................................ 189Figure 164: IBM Resiliency Orchestration Agent Installer .............................................................................. 191Figure 165: Upgrade Agents on HPUX Server - Introduction ......................................................................... 191Figure 166: Upgrade Agents on HPUX Server - Choose Install Folder ........................................................... 192Figure 167: Upgrade Agents on HPUX Server - Choose Install Set ................................................................ 193Figure 168: Upgrade Agents on HPUX Server - Choose Agents - HPUX ....................................................... 193Figure 169: Upgrade Agents on HPUX Server - Choose Link Folder ............................................................. 194Figure 170: Upgrade Agents on HPUX Server – NAT IP Address Configuration .......................................... 195Figure 171: Upgrade Agents on HPUX Server – Site Controller Configuration ............................................. 195Figure 172: Upgrade Agents on HPUX Server - Pre-Installation Summary .................................................... 196Figure 173 Upgrade Agents on HPUX Server - Installing IBM Resiliency Orchestration Agents .................. 197Figure 174: Upgrade Agents on HPUX Server - Starting Agents .................................................................... 197Figure 175: Upgrade Agents on HPUX Server - Upgrade Complete ............................................................... 198Figure 176: IBM Resiliency Orchestration Agent Installer .............................................................................. 200Figure 177: Upgrade Agents on AIX Server - Introduction ............................................................................. 200Figure 178: Upgrade Agents on AIX Server - Choose Install Folder ............................................................... 201Figure 179: Upgrade Agents on AIX Server - Choose Install Set .................................................................... 202Figure 180: Upgrade Agents on AIX Server - Choose Agents - AIX .............................................................. 202Figure 181: Upgrade Agents on AIX Server - Choose Link Folder ................................................................. 203Figure 182: Upgrade Agents on AIX Server - Agent Configuration ................................................................ 204Figure 183: Upgrade Agents on AIX Server - Agent Configuration ................................................................ 204Figure 184: Upgrade Agents on AIX Server - Agent Configuration ................................................................ 205Figure 185: Upgrade Agents on Linux Server – NAT IP Address Configuration ............................................ 205Figure 186: Upgrade Agents on Linux Server - Pre-Installation Summary ..................................................... 206Figure 187: Upgrade Agents on Linux Server - Installing IBM Resiliency Orchestration Agents .................. 207Figure 188: Upgrade Agents on Linux Server - Starting Agents ...................................................................... 207Figure 189: Upgrade Agents on Linux Server - Upgrade Complete ................................................................ 208Figure 190: Uninstall IBM Resiliency Orchestration Agent Node ................................................................... 232Figure 191: Uninstall Complete screen ............................................................................................................. 233Figure 192: Uninstall IBM Resiliency Orchestration Server – Introduction screen ......................................... 235Figure 193: Uninstall IBM Resiliency Orchestration Server – Uninstalling… screen ..................................... 236Figure 194: Uninstall IBM Resiliency Orchestration Server – Uninstall Complete screen ............................. 237Figure 195: Uninstall Complete screen ............................................................................................................. 238Figure 196: Resiliency Orchestration RESILIENCY ORCHESTRATION Workflow ................................... 241Figure 197: SzCPIVP ........................................................................................................................................ 244Figure 198: IBM Resiliency Orchestration Workflow Example ...................................................................... 246Figure 199: MimixAS400SclM Workflow ....................................................................................................... 247

Disaster Recovery Management Software


Preface The Resiliency Orchestration Installation Guide provides concepts and procedures to install the Resiliency Orchestration product. Although this guide is intended for administrators responsible for installing, configuring and maintaining the product, advanced users will also benefit from the information it contains.

Note

• The product name Resiliency Orchestration, IBM Resiliency Orchestration and Resiliency Orchestration are used interchangeably.

• The company name IBM, an IBM Company, IBM, IBM Technologies Corporation, IBM Technologies and IBM CORPORATION are used interchangeably.

Purpose

This manual helps you to install and uninstall Resiliency Orchestration and its services, by providing the detailed procedure for the following:

§ Installation and upgrade of Resiliency Orchestration server

§ Installation and upgrade of Resiliency Orchestration agents on:

o Windows

o Solaris

o Linux

o HPUX

o AIX

§ Uninstallation of Resiliency Orchestration server and agents.

Note For Installation, Upgrade and Uninstallation of IBM File Replicator 7.1, refer to IBM File Replicator Installation Guide (version 7.1).

Audience

This manual is for administrators who are responsible for installation, configuration and uninstallation of Resiliency Orchestration Software and its services.



Conventions

Typeface/Font Usage Boldface Boldface font is used in table headings and in

paragraphs, to convey especially strong events. Italic Italics are used to emphasis special information, or

additional information and examples. Courier New Terminal input and output.

Acronyms

Acronyms Definition CSA Client Side Agent. DR Disaster Recovery.

GHz GigaHertz IP Internet Protocol

JDK Java Development Kit JSDK Java Software Development Kit JRE Java Runtime Environment JVM Java Virtual Machine LAN Local Area Network PFR Panaces File Replicator

RAID Redundant Array of Independent Disk RAM Random Access Memory ROM Read Only Memory RPO Recovery Point Objective RTO Recovery Time Objective

RESILIENCY FILE

REPLICATOR

IBM File Replicator

URL Uniform Resource Locator GPL General Public License



1. Installation Overview

IBM Resiliency Orchestration Software has the following components for installation:

§ IBM Resiliency Orchestration Server

§ IBM Resiliency Orchestration Server Silent mode installation

§ IBM Resiliency Orchestration Agents

§ RESILIENCY FILE REPLICATOR service installation

§ Advanced Reporter

New version in FTP

The software is available in ftp.IBM.com where the credentials are sent to customer, which contain the following installation packages:

§ IBM Resiliency Orchestration Server available in Server folder.

§ IBM Resiliency Orchestration Agents & IBM File Replicator for Windows, Solaris, Linux, HPUX and AIX. available in Agents folder.

§ IBM Resiliency Orchestration Advanced Reporter server available in AdvancedReporter folder.

§ IBM Resiliency Orchestration Documentation available in Docs folder.

§ IBM Agent Node installation is available in AgentNode folder

§ IBM Upgrade kit is available in the IBMUpgradeKit folder.

§ IBM File Replicator (RESILIENCY FILE REPLICATOR) is available in the RESILIENCY FILE REPLICATOR folder.

IBM Resiliency Orchestration server installation requires IBM Resiliency Orchestration Server Platform to be installed. It is automatically installed during IBM Resiliency Orchestration Server installation.

The IBM Resiliency Orchestration Agent Software packages are provided for each supported application, protection software, and operating system. Agent Software requires IBM Resiliency Orchestration Agent Platform package to be installed on the same server, which happens at the time of agent installation on the respective servers involved in the Disaster Recovery solution.

The following tables provide information on interoperability matrix of IBM Resiliency Orchestration Server and Agents:



IBM Resiliency Orchestration Client Agent Support

Agent Platform Database/Application Version OS Version/Patch

Sybase Agent SUN/ Sparc, PA-RISC Sybase ASE 15.x Solaris 10, Solaris 11, AIX 6.*

OS Agent Intel, AMD,

SUN/Sparc, PA-RISC

Not Applicable

Solaris 10, Solaris 11, Windows 2008 Std,

Windows 2008 Enterprise Edition,


AIX6.*, HP-UX 11i, RHEL 4.0/5.0

Oracle Dataguard Intel, AMD,

SUN/Sparc, PA-RISC

Oracle 10g, Oracle 11g

Solaris 10, Soalris 11, Windows 2008 Std,



AIX 6.*, HP-UX 11i, RHEL 4.0/5.0

MS SQL Agent Intel, AMD MSSQL 2008, MSSQL 2012

Windows 2008 Std,

Windows 2008, Windows 2012

Enterprise Edition

SRS Agent SUN/Sparc, PA-RISC

Sybase 15 with embedded RSSD

Solaris 10, Solaris 11 AIX 6.*/7.*

Oracle Agent Intel, AMD, Sun/Sparc, AIX

Oracle 10g, Oracle 11g

Solaris 10, Solaris 11 Windows 2008 Std,

Windows 2008 Enterprise Edition, Windows 2012 Std,

Windows 2012 Enterprise Edition, AIX

6.*/7.*, HP-UX 11i, RHEL 5.x,6.x

Hitachi Replication Agent

SUN/ Sparc, PA-RISC Sybase ASE 15.x Solaris 10, Solaris 11 AIX

6.*/7.*

DB2 Agent Intel, AMD, DB2 9.x AIX /6.*,7.*,windows, linux

EMC SRDF Agent Intel,AMD,SUN/SPARC

Symmetrix CLI (SYMCLI)

Version : V7.3.0.1 (Edit Level: 1214)

Solaris 10, Solaris 11Window 2003

IBM Global Mirror using OS Agent SUN/Sparc,AIX

IBM DSCLI Version: 6.6.0.345

Solaris 10, AIX 5



Agent Platform Database/Application Version OS Version/Patch

PostgreSQL Agent Intel PostgreSQL 9.2 Linux RHEL 5.3 and Linux

RHEL 5.6, Windows 2008 R2 Standard

MySQL Agent Intel MySQL 5.5 Linux RHEL 6

MS Exchange Agent Intel Not Applicable Windows 2008 SP2

Enterprise/Windows 2008 R2 Enterprise

MSSQL Agent Intel/AMD MSSQL 2005, MSSQL 2008, MSSQL 2012

Windows 2008 Std,

Windows 2008, Windows 2012

Enterprise Edition

Client Browser Prerequisite

Browser OS Version/Patch Remarks Firefox 26 and above

and Google chrome 32 and above

Windows 7 and Windows 8

Note

1. IBM Resiliency Orchestration GUI does not support multiple tabs/ windows for pages requiring user inputs such as Discovery or configuration for single logged on session and Group assignment for a particular user.

2. IBM Resiliency Orchestration GUI (Dashboards and Landing page) requires Flash Player 25 or later to be installed in a client browser.

Prerequisites

Commercial Dependencies The Revival_SwitchXlog.jar file must be downloaded by the customer for Postgress.

GPL Dependencies for RESILIENCY ORCHESTRATION

Based on the features, download the GPL dependent binaries from this link GPL dependent binaries before RESILIENCY ORCHESTRATION installation and perform the steps mentioned in the chapter, Upgrading RESILIENCY ORCHESTRATION 7.1 GA to RESILIENCY ORCHESTRATION 7.1 GA P2 License Patch.

GPL Dependencies for RESILIENCY FILE REPLICATOR

Based on the features, download the GPL dependent binaries from this link GPL dependent binaries before starting RESILIENCY FILE REPLICATOR and perform the steps mentioned in the chapter, RESILIENCY FILE REPLICATOR Third Party Installation.



Refer to GPL License information for more information on GPL licenses. Tar and Rsync Version Details Platform Tar Version Rsync Version Windows-32/64-Bit tar1.16 rsync3.0.7 Linux-32-Bit RHEL 5.6 tar1.19 rsync3.0.5 Linux-64-Bit RHEL 5.5 rsync3.0.9 Linux-64-Bit RHEL 5.7 rsync3.0.9 Linux-64-Bit RHEL 6.X tar1.23 rsync3.0.9 Linux-64-Bit RHEL 7.X tar1.23 rsync3.0.9 AIX tar1.14 rsync3.0.5 HPUX-64-BIT Itanium tar1.26 rsync3.0.9 HPUX-64-BIT Parisac tar1.26 rsync3.0.9 Solaris_Sparc tar1.18 rsync3.0.5 Solaris_Intel tar1.26 rsync3.0.5

Java Tools Prerequisite

Java Tools OS Version/Patch Remarks

j2re_1.6.0_01 Windows 2008,windows 2012 J2re_1.6.0_20 HPUX j2re_1.6.0_20 Solaris 10 j2re_1.6.0 Aix v7 j2re_1.6.0 Linux 5.0, 6.0 Enterprise Server Edition Database Agent System j2re_1.6.0_21 Linux 6.0 Enterprise Server Edition IBM Resiliency Orchestration

Server System j2re_1.6.0_45 Linux 6.0 Enterprise Server Edition IBM Resiliency Orchestration

Server System You can install IBM Resiliency Orchestration Software by any of the methods given below:

• Graphical Mode: Graphical mode installation is an interactive, GUI-based method for installing IBM Resiliency Orchestration Software. It is supported on Windows, Linux, Solaris, HPUX and AIX platforms. For more information, refer to Chapter 2:



2. Resiliency Orchestration Server Installation on Linux Using Graphical Mode.

• Silent Mode: Silent mode installation is a non-interactive method of installing IBM Resiliency Orchestration Software. This method requires the use of .properties file for selecting installation options. It is supported on Linux, Solaris, HPUX and AIX platforms. For more information, refer to Chapter 14: 14. Installing Resiliency Orchestration Using Silent Mode Installation.



2. Resiliency Orchestration Server Installation on Linux Using Graphical Mode

You can install the IBM Resiliency Orchestration Server on Linux and Linux Cluster. This chapter outlines the procedures for installing IBM Resiliency Orchestration server on Linux platform. For information on the procedures for installing IBM Resiliency Orchestration server on Linux Cluster, refer to Chapter 3: Resiliency Orchestration Server Installation on Linux Cluster.

System Requirements - for Agents configured on Resiliency Orchestration Server

Minimum hardware configuration for the Linux Server to install IBM Resiliency Orchestration:

Processor: Intel Xeon 2.6Ghz, 6 Cores

No of Servers No of Agents

Memory Hard disk

20 Servers 50 12 GB 160Gb 40 Servers 100 16 GB 320Gb 100 Servers 300 32 GB 500Gb

§ Dual Network interfaces

Sample partitions shown below, please make sure that they are created during the installation of Linux:

§ /opt - 50 GB

§ /var - 50 GB (Recommended to use separate disk for performance)

§ /backup - 50 GB

§ /boot - 500 MB

§ /swap - 2 times the RAM size

System Requirements – when Agents installed/configured on Managed Systems

No of Servers

Managed RESILIE

NCY ORCHESTRATI

ON Server

Memory

RESILIENCY

ORCHESTRATION

Server CPU Intel Xeon 2.27GHz

100 Servers 8 GB 4 250 Servers 8 GB 6 500 Servers 8 GB 8



1000 Servers 16 GB 8 1500 Servers 20 GB 12 2000 Servers 24 GB 12

As a best, practice make sure that storage and network has no single point of failure. For example, RAID protected Storage, Dual Network interfaces and so on.

Make sure that the following partitions are created during the Linux installation:

§ /opt - 100 GB (RESILIENCY ORCHESTRATION Volume) § /var - 50 GB ( MySQL Volume) § /backup - 50 GB (MySQL Backup) § /boot - 500 MB § /swap - 2 times the RAM size

Note According to the server numbers, increase the MySQL data partition.

System Requirements – for Site Controller

No of Agents Memory CPU 2.6 GHz 100 8 GB 2 200 16 GB 2

Make sure that the following partitions are created during the Linux installation: • /opt – 50 GB (RESILIENCY ORCHESTRATION Volume) • /boot – 500 MB • /swap – 2 times the RAM size

As a best practice, make sure that storage and network has no single point of failure. For example, RAID protected Storage, Dual Network interfaces and so on. Keep adding more Site Controllers for every 100 or 200 agents.

Installation of Resiliency Orchestration Server

Perform the following steps on dedicated Linux server, to install and set up the IBM Resiliency Orchestration Server:

1. Install the Linux Enterprise Server OS (RHEL 6.x).

2. Install the MySQL 5.5.34 standard software.

3. Install the Tomcat 7.0.30

4. Install the IBM Resiliency Orchestration Server Software.



5. Set up the environment.

Follow the sections given below to complete the IBM Resiliency Orchestration Server installation.

Installation of Linux Enterprise Server OS

1. Install the Linux Enterprise Server OS without firewall settings and MySQL database package. Refer to Linux OS Installation guide for the detailed instruction to install the Linux OS.

Refer to the System Requirements section to make sure that required partitions are created.

2. Select “No Firewall” option, as IBM Resiliency Orchestration uses ports 8443, 8080, 1099, 45000, 46000 and 46001 for GUI and agent communication with the IBM Resiliency Orchestration Server. If agentless method is used, then, additional ports mentioned below needs to be open. There should not be any firewall block related issues for these ports.

§ Ports used for ssh communication (default port is 22).

3. RESILIENCY FILE REPLICATOR must be enabled on port 46443 for security purposes.

4. If Agentless method is being used then the following additional pre-requisites have to be met on the managed host:

§ Enabling SSH on Unix/ Linux subsystem: Configuration requirement:

1. Firewall setting: ssh port should be open for access from Resiliency Orchestration Server.

2. ssh server should be running on target server that allows connections from Resiliency Orchestration server for the configured user. Sftp module should be enabled for ssh.

§ Enabling WMI on Windows subsystem ( High level)

Prerequisites: The target system should meet the following pre-requisites for IBM Resiliency Orchestration to work in Agentless model:

1. Add permissions for Administrator (WMI user) at Component Services > Computers > My Computer > COM Security ( command: dcomcnfg)

2. Add permissions for Administrator (WMI User) at WMI Control > Security > Root > CIMV2 > Security ( command: wmimgmt.msc)

3. Modify Registry:

§ For HKEY_CLASSES_ROOT > CLSID > {76A64158-CB41-11D1-8B02-00600806D9B6}, create String AppID with value as {76A64158-CB41-11D1-8B02-00600806D9B6}

§ For HKEY_CLASSES_ROOT > AppID Create Key {76A64158-CB41-11D1-8B02-00600806D9B6}



§ For the created Key, in the right hand pane, create empty String DllSurrogate.

4. Open Ports between Resiliency Orchestration Server and Windows Servers.

§ Open Ports 135, 137, 138, 139, 445 and Port Range 49152-65535 [No reboot required].

§ If you don’t want to open Port Range 49152-65535 , then you can also open range say 50000-50200 ,as IBM may use 5-10 ports max in parallel , however many Microsoft services ( like Active Directory/ file sharing/ named pipes etc.) uses RPC extensively and hence good range is required. And to configure this custom range you need to change registry and server reboot is required.

For detailed info, please refer online help at IBM Resiliency Orchestration online help

Additional settings on IBM File Replicator subsystem

Firewall setting: Port 46000 and 46001, where IBM File Replicator service is listening should be open for access from Resiliency Orchestration Server.

Note If Firewall settings are “Yes”, then the above ports should not be blocked.

Allow software to install packages selected by default and choose all packages available under ‘Development’ list, and make sure that "PostgreSQL Database and MySQL Database" are not selected under ‘Server’ list. Do not click “Details” hyperlink to make further selections.

Additional Settings for Linux Installation

§ Edit the file /etc/sysconfig/selinux to include the option "SELINUX=permissive".

Check /etc/hosts file to ascertain if localhost alias exists or not. If it doesn’t exist, add the localhost alias, and the IP address of the IBM Resiliency Orchestration Server system. For example: 127.0.0.1 localhost localhost

<ip-address> <localhost> <hostname>

§ Open a terminal, log in as root and issue the following command, whenever the server is rebooted:

# /sbin/sysctl -w net.ipv4.tcp_retries2=4

§ You can avoid this by performing the following steps. This is recommended.

o Open sysctl.conf file in any editor with the following command:

vi /etc/sysctl.conf

o This opens a conf file. Add the following line and save it:

net.ipv4.tcp_retries2=4



o Reboot the system.

Additional Package Installation for Linux Installation

The following are the steps for Shellshock vulnerability fix:

1. Run #rpm –qa bash to view the current version of Bash to identify the affected system. 2. Specify the package name with the #yum update bash command and run the command in

order to update the Bash. For example, run the following command to update a Red Hat Enterprise Linux 6.4 system:

# yum update bash-4.1.2-15.el6_5.2

3. Download RPM bash-4.1.2-15.e|6_5.2 for RHEL 6.x from the Red Hat site to install the Bash using rpm.

4. Copy the Bash to /tmp location of the Resiliency Orchestration server. 5. Run the following command to install the Bash.

#rpm –ivh bash-4.1.2-15.e|6_5.2

Installation of MySQL

For information on installing MySQL 5.5.34 Server and client software on RHEL 6, refer to the MySQL 5.5.34 documentation. Enabling proxy from http daemon service(Apache Http server) for low touch agent upgrade Note For HTTPS, the RESILIENCY ORCHESTRATION machine should have the mod_ssl module loaded. Verification Steps /etc/httpd/modules should have the mod_ssl.so /etc/httpd/conf.d should have the configuration file ssl.conf By default, the httpd service will be enabled. Below are the manual steps to be done by a user with root privileges if firewall enabling is required:

1. On RESILIENCY ORCHESTRATION machine: 1) Below ports are to be opened. 22,80,45000,45443, 46000, 46001,8443,1099,443, 8081, 8082, 8083 Note 45443 is the default secure port on the RESILIENCY ORCHESTRATION local agent. At one time, either port 45000 or port 45443 must be open. Both cannot be open at the same time. 2) Enable firewall on RESILIENCY ORCHESTRATION Server. service iptables start Check the status



service iptables status [root@fed14devt conf]# service iptables status

Table: filter Chain INPUT (policy ACCEPT) num target prot opt source destination 1 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,

ESTABLISHED 2 ACCEPT icmp -- 0.0.0.0/0 0.0.0.0/0 3 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 4 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:22 5 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:22 6 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:45000 7 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:45443 8 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:46000 9 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:80 10 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:8083 11 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited 12 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:46001 13 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:8443 14 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:1099 15 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:443 Chain FORWARD (policy ACCEPT) num target prot opt source destination 1 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited Chain OUTPUT (policy ACCEPT) num target prot opt source destination

2. On Local Agent machine: 1) Below ports are to be opened with root user . 22,80,45000,45443 Note: 45443 is the default secure port. At one time, either port 45000 or port 45443 must be open. Both cannot be open at the same time. 2) Start the firewall service iptables start Check the status service iptables status



[root@oemfitln7 target]# service iptables status Table: filter Chain INPUT (policy ACCEPT) num target prot opt source destination 1 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,

ESTABLISHED 2 ACCEPT icmp -- 0.0.0.0/0 0.0.0.0/0 3 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 4 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:22 5 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:80 6 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:45000 7 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:45443 8 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited Chain FORWARD (policy ACCEPT) num target prot opt source destination 1 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited Chain Output (policy ACCEPT) num target prot opt source destination

Note A) Above steps are for IPV4 network addressing:

For port opening, we use the command system-config-firewall, which updates /etc/sysconfig/iptables (IPV4) and /etc/sysconfig/ip6tables (IPV6) by default. In case of IPV6 network addressing usage, perform the following steps:

1. Check that /etc/sysconfig/ip6tables has the entries for the ports opened. 2. Run the following command to start the firewall:

service ip6tables start3. Run the following command to check the firewall status service ip6tables status NoteTheoutputforthisissimilartotheoutputoftheiptables

The“/etc/sysconfig/ip6tables”fileonlocalagentmachineshouldhavethefollowingcontents.

[root@oemfitln7opt]#cat/etc/sysconfig/ip6tables#Firewallconfigurationwrittenbysystem-config-firewall#Manualcustomizationofthisfileisnotrecommended.*filter:INPUTACCEPT[0:0]:FORWARDACCEPT[0:0]



:OUTPUTACCEPT[0:0]-AINPUT-mstate--stateESTABLISHED,RELATED-jACCEPT-AINPUT-pipv6-icmp-jACCEPT-AINPUT-ilo-jACCEPT-AINPUT-mstate--stateNEW-mtcp-ptcp--dport22-jACCEPT-AINPUT-mstate--stateNEW-mtcp-ptcp--dport45000-jACCEPT-AINPUT-mstate--stateNEW-mtcp-ptcp--dport45443-jACCEPT-AINPUT-mstate--stateNEW-mtcp-ptcp--dport80-jACCEPT-AINPUT-jREJECT--reject-withicmp6-adm-prohibited-AFORWARD-jREJECT--reject-withicmp6-adm-prohibitedCOMMITThe“/etc/sysconfig/ip6tables”fileonRESILIENCY ORCHESTRATION machineshouldhavethebelowcontents:[root@oemfitln10bin]#cat/etc/sysconfig/ip6tables#Firewallconfigurationwrittenbysystem-config-firewall#Manualcustomizationofthisfileisnotrecommended.*filter:INPUTACCEPT[0:0]:FORWARDACCEPT[0:0]:OUTPUTACCEPT[0:0]-AINPUT-mstate--stateESTABLISHED,RELATED-jACCEPT-AINPUT-pipv6-icmp-jACCEPT-AINPUT-ilo-jACCEPT-AINPUT-mstate--stateNEW-mtcp-ptcp--dport22-jACCEPT-AINPUT-mstate--stateNEW-mtcp-ptcp--dport45000-jACCEPT-AINPUT-mstate--stateNEW-mtcp-ptcp--dport46000-jACCEPT-AINPUT-mstate--stateNEW-mtcp-ptcp--dport22-jACCEPT-AINPUT-mstate--stateNEW-mtcp-ptcp--dport80-jACCEPT-AINPUT-mstate--stateNEW-mtcp-ptcp--dport8083-jACCEPT-AINPUT-mstate--stateNEW-mtcp-ptcp--dport45443-jACCEPT-AINPUT-jREJECT--reject-withicmp6-adm-prohibited-AFORWARD-jREJECT--reject-withicmp6-adm-prohibitedCOMMIT

B) The following exit codes will be logged in case of failure of the setup for httpd: $EAMSROOT/var/log/httpdconsole.log #ExitCodesmeaningsareasfollows:#10-/etc/hostsfilecouldnotbemodifiedwiththerequiredmapping[ipaddresslocalhosthostname]#11-Unabletoprocessthe/etc/hostsfiletosupport/checktherequired[ipaddresslocalhosthostname]mapping#12-/etc/hostsfilecouldnotbefound#13-setseboolcommandcouldnotrun#14-httpdprocesscouldnotberestarted#15-httpdprocesscouldnotbestarted#16-httpd.conffilecouldnotbemodified



#17-httpd.conffilenotfound#18-httpdnotinstalled

Installation of Resiliency Orchestration Server Software

This software is packaged into an image file called install.bin on IBM Resiliency Orchestration Distribution FTP in Server folder. It contains all the binaries and packages to run the IBM Resiliency Orchestration server software. This software installation involves installing IBM Resiliency Orchestration server binaries, BCS modules, IBM Resiliency Orchestration server agents, and a few miscellaneous software binaries.

Note

Before running IBM Resiliency Orchestration server software, installations of Linux Enterprise Server OS and MySQL must be completed. You must have root or root equivalent privileges to install IBM Resiliency Orchestration server. Perform the following steps for installation. The commands specified in the following points must be provided at the command prompt:

1. Download the server binaries from the given ftp path

2. Execute the following command: (Use whichever is applicable)

sh install.bin (or) ./install.bin

Note

§ Java will be installed automatically after execution of this command.

§ Make sure that you have free space of approximately 800 MB in /tmp directory, before executing the above command.

3. After extracting the files from the install.bin, IBM Resiliency Orchestration Server installation starts with the following screen. A progress bar at the bottom of the screen indicates the loading of the installer.



Figure 1: IBM Resiliency Orchestration Installer

4. After displaying the IBM Resiliency Orchestration installer screen, the MySQL root password window is displayed.

Figure 2: IBM Resiliency Orchestration Server Installation - MySQL root password

5. Enter the password for the MySQL root user.

6. Click Next. The Tomcat Home window is displayed.



Note Click the Cancel button to quit the installation.

Figure 3: IBM Resiliency Orchestration Server Installation - Tomcat Home

7. Click Choose… to browse and select the location of Tomcat. When Tomcat is located and then selected, the path appears in the Please Choose a Folder: box in Tomcat Home screen. Click Next, the Introduction window is displayed.

Figure 4: IBM Resiliency Orchestration Server Installation - Introduction

8. Click Next. The License Agreement window is displayed.



Figure 5: IBM Resiliency Orchestration Server Installation - License Agreement

9. Click the appropriate option button after perusal of the License Agreement. The options are:

Option Button Description I accept the terms of the

License Agreement Click this option button for acceptance of the License

Agreement.

I do NOT accept the terms of the License Agreement

Click this option button for rejection of the License Agreement. By default, this is selected.

The Next button is unavailable with this option.

10. Click Next to proceed with the installation. The Choose Install Folder window is displayed.



Figure 6: IBM Resiliency Orchestration Server Installation - Choose Install Folder

11. Select a path to install the software by clicking Choose. Choose the path where the Resiliency Orchestration is currently installed.

12. Click Next. The User Management System window is displayed.

Figure 7: IBM Resiliency Orchestration Server Installation – User Management System

13. Select the appropriate User Management System type. The two options are: Basic User Management System and Advanced User Management System.

14. Click Next. The Pre-Installation Summary window is displayed.



Figure 8: IBM Resiliency Orchestration Server Installation - Pre-Installation Summary

15. Go through the pre-installation summary to verify the inputs provided. If you want to change the inputs, click Previous and modify.

16. Click Install. The Installing IBM Resiliency Orchestration Server window is displayed.

Figure 9: IBM Resiliency Orchestration Server Installation - Installing IBM Resiliency Orchestration

Server

17. IBM Resiliency Orchestration Server Installation automatically uploads the IBM Resiliency Orchestration schema. If it already exists, a dialog box is displayed as shown below, that confirms if you want to drop the existing IBM Resiliency Orchestration schema and replace it through installer.



Figure 10: IBM Resiliency Orchestration Server Installation - Confirmation message

18. Click No to continue the installation with the existing schema. Click Refresh to drop and recreate the IBM Resiliency Orchestration schema.

Note

To replace the database schema manually, type the following command: # mysqldump –u root –-databases panaces pfr –R –-triggers -p > backup_file_name.sql # Drop the existing databases if they already exist

a. mysqladmin –u root drop panaces b. mysqladmin –u root drop pfr

# mysql -u root < $EAMSROOT/lib/mysql_schema_InnoDB.sql # mysql -u root < $EAMSROOT/lib/pfr.sql # $EAMSROOT/installconfig/importTemplateEvents.sh

19. The Advanced User Server Details screen will be displayed if Advanced User Management System was selected in Step 15. Select the server type and provide the required details for connecting to the external server, as shown in the following two figures.



Figure 11: IBM Resiliency Orchestration Server Installation - Advanced User Server Details 1

Figure 12: IBM Resiliency Orchestration Server Installation - Advanced User Server Details 2

20. Click Next. The Support User Account window is displayed.



Figure 13: IBM Resiliency Orchestration Server Installation - Support User Account

21. A user account with user name support is created for use by IBM Resiliency Orchestration Server. Enter the password for this account in the Password box. Re-enter the password in the Confirm Password box

Note For invalid passwords, a dialog box displays an error message.

22. Click Next. Once the metadata information is created by the installer, the IBM Resiliency Orchestration server will configure the system with events and events correlation template definitions.



Figure 14: IBM Resiliency Orchestration Server Installation - System Configuration

23. Click Next. In case you get an warning message saying ”Unable to find configuration file (my.cnf)”, than update max allowed packet to 16MB in my.cnf configuration file and restart the mysql service.

Figure 15: IBM Resiliency Orchestration Server Installation – Update mysql configuration file

24. Click Next. The Installation Completed window is displayed, indicating successful installation.



Figure 16: IBM Resiliency Orchestration Server Installation - Installation Completed

25. Click Done to complete the installation process.

Post Installation Steps

1. Download ThirdPartyJSLib.zip from the link GPL dependent binaries (https://sourceforge.net/projects/gnu-utils/files/binaries/). Copy ThirdPartyJSLib.zip to $TOMCAT_HOME/webapps/PanacesGUI/scripts/. Unzip ThirdPartyJSLib.zip in the $TOMCAT_HOME/webapps/PanacesGUI/scripts/. Remove ThirdPartyJSLib.zip from $TOMCAT_HOME/webapps/PanacesGUI/scripts/.

2. If you would like to use the vault integration feature of the product, complete the instructions given below:

a. Ensure that the required vault integration library files from your vault vendor are available with you.

b. Add all the vault integration library files to the following locations. o {TOMCAT_HOME}/webapps/PanacesGUI/WEB-INF/lib o {TOMCAT_HOME}//webapps/PanacesGUI/pages/classes/lib o {TOMCAT_HOME}//webapps/userPortal/WEB-INF/lib o {TOMCAT_HOME}//webapps/userPortal/pages/classes/lib o {EAMSROOT}/agents/vault/{yourVaultName}/lib o {EAMSROOT}/lib

c. Start the Resiliency Orchestration Services (panaces service) . See Starting and Stopping Resiliency Orchestration Server.

3. If you would like to use the Cisco UCS Director (Unified Computing System Director) integration feature of the product, procure the following library files and replace at the respective locations:

o {EAMSROOT}/lib/ucsd-oa-annotations.jar



o {EAMSROOT}/lib/ucsd-oa-api.jar o {EAMSROOT}/lib/ucsd-rest-api-sdk-v2.ja o {EAMSROOT}/lib/cuic-sdk-v2-0.jar o {EAMSROOT}/lib/inframgr.jar

4. Update the following parameters for optimal performance.

No. of groups

File name and Path Parameters Value

250 $EAMSROOT/installconfig/panaces.properties

panaces.mysql.maxconnection

500

$EAMSROOT/installconfig/panaces.properties

panaces.acp.server.concurrentRequestProcessCount

500

/etc/my.cnf max_connections

500


panaces.mysql.maxconnection

1000

$EAMSROOT/installconfig/panaces.properties


1000

/etc/my.cnf max_connections

1000

• The panaces.acp.server.concurrentRequestProcessCount parameter is to set the number of threads

that process the messages from Agents. • The panaces.mysql.maxconnection parameter is to set the number of open mysql connections to

DB.

Note: When the installation is carried on silent mode or GUI mode, restart with a Putty session for Unix.

5. Perform the following steps for MYSQL DB Changes: Note $EAMSROOT will point to the Resiliency Orchestration installation directory. For Example: /opt/panaces/ is the $EAMSROOT.

a. Run the following command to set the password for IBM user passwd sanovi

b. Run the following command to change to bin directory

cd $EAMSROOT/bin

c. Execute the following script to update the Mysql DB (mysql_schema_InnoDB.sql) ./ UpdateDBAfterInitialization.sh

i. For Example: $EAMSROOT/bin/UpdateDBAfterInitialization.sh start

d. Start Resiliency Orchestration services. For Example, you can execute the following command to start Resiliency Orchestration services: ./panaces start

6. Apply license key by perfoming the following steps:

e. License key file is available under /License folder inside the Docs package of the software

download. The name of the license file is RO_7.2_Generic_license.xml f. Copy the license file to the $EAMSROOT/cli folder of the Resiliency Orchestration Server.



g. Go to $EAMSROOT/cli directory and run ./ License.sh script. The following prompt will be displayed when the script is executed successfully: License>

h. Execute the following command on the prompt to apply the license key: License>upload licensekey -l RO_7.2_Generic_license.xml The following message is displayed when the script is executed successfully: License installed successfully.

Configuring Resiliency Orchestration Server

Server Memory Management

Depending on the expected number of groups that will be supported by IBM Resiliency Orchestration Software, Java maximum heap memory limit parameter needs to be specified. It is defined in the variable named RESILIENCY ORCHESTRATION_SERVER_JVM_MEM which is located at starting lines of the Resiliency Orchestration startup script IBM Resiliency Orchestration Install root/bin/panaces. Default value of this variable is set to -Xmx2048m.

Recommended Settings

It is recommended that Number of Processes for Resiliency Orchestration should be at least 10000. You can set this limit in /etc/security/limits.conf file. After installation of IBM Resiliency Orchestration Server, if Resiliency Orchestration Services are going to start with IBM user, then edit this file by altering or appending the following to set the limit: root soft nproc 10240

root hard nproc 10240

root soft nofile 20480

root hard nofile 20480

After updating limits.conf settings, reboot the server for these changes to take effect.

MySQL connectivity configuration for Resiliency Orchestration Server

IBM Resiliency Orchestration uses Mysql for persistence. During installation, default Mysql users panaces & pfrdmin with grant on all privileges will be created, and IBM Resiliency Orchestration will be configured to use this default user/password. The panaces user is used to by the IBM Resiliency Orchestration Server.

Configuring Resiliency Orchestration with different MySQL user

You can configure IBM Resiliency Orchestration software to use different Mysql user. Refer to MySQL 5.5 manual on how to create a new user. The Mysql user should have grants on all privileges for IBM Resiliency Orchestration Server to function. To configure IBM Resiliency Orchestration with new user, perform the following steps.



1. Navigate to user installation directory (where IBM Resiliency Orchestration Server is installed). To navigate to the installconfig directory, enter the following command at the command prompt:

# cd installconfig

2. To display IBM Resiliency Orchestration properties file, enter the following command at the command prompt:

# vi panaces.properties file

3. To provide MySQL user for Resiliency Orchestration Server, edit the value of following parameter in properties file. By default the parameter will have panaces as the value:

panaces.mysql.username = panaces

4. To provide MySQL user for RESILIENCY FILE REPLICATORGUI, edit the value of following parameter in properties file. By default the parameter will have pfradmin as the value:

pfr.db.username = pfradmin

5. Save and close panaces.properties file.

Configuring Resiliency Orchestration with different MySQL user password

When password(s) for the MySQL user(s) are changed, perform the following steps to configure IBM Resiliency Orchestration with the new password.

1. Navigate to user installation directory (where IBM Resiliency Orchestration Server is installed). To navigate to the bin directory, enter the following command at the command prompt:

# cd bin

2. To provide MySQL user password for Resiliency Orchestration Server, run the following command:

# ./changeDBPassword.sh panaces.mysql.password

3. To provide MySQL user password for RESILIENCY FILE REPLICATOR GUI, run the following command:

# ./changeDBPassword.sh pfr.db.password

4. Upon running the above command, you will be prompted to provide the password. Provide the password and press 'enter'. Password(s) provided will be encrypted and saved into panaces.properties file.

Note Default setting for IBM Resiliency Orchestration Server-Client communication is SECURE. To establish unsecure mode of communication, open panaces.properties file from installconfig directory and change panaces.acp.communicationType= SECURE to panaces.acp.communicationType= NONSECURE.



Configuration Changes in Tomcat

The following are the steps to enable secure mode of GUI access (also redirects nonsecure access to secure access):

1. Get the KEYSTORE file with the password. The default IBM KEYSTORE file/Password(Certificate) is shipped with product. To use a Customer certificate, get the KEYSTORE file and password from customer.

2. Open $TOMCAT_HOME/conf/server.xml

3. Add/edit the below connectors with the following details to update the file: (Assuming EAMSROOT as /opt/panaces)

a. Use the following details for nonsecure to secure redirection configuration:

<Connector executor="tomcatThreadPool" port="8080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" compression="on" compressionMinSize="2048" nocompressionUserAgents="gozilla, traviata"

compressableMimeType="text/html,text/xml,text/plain,text/css,text/javascri pt,text/json,application/x-javascript,application/javascript,application/json"/> <Connector port="8443" protocol="org.apache.coyote.http11.Http11NioProtocol" SSLEnabled="true" maxThreads="150" scheme="https" secure="true" minSpareThreads="25" maxSpareThreads="75" enableLookups="false" disableUploadTimeout="true" clientAuth="false" sslEnabledProtocols="TLSv1" keystoreFile="/opt/panaces/installconfig/keystore/IBM.keystore" keystorePass="^vMkT%678#4-06Gjue672Kwo95dzg" compression="on" compressionMinSize="2048" nocompressionUserAgents="gozilla,traviata"

compressableMimeType="text/html,text/xml,text/plain,text/css,text/javascri pt,text/json,application/x-javascript,application/javascript,application/json"/>

b. Use the following details for default port configuration: Note: The default port configuration requires the tomcat services to be started with root user.

<Connector executor="tomcatThreadPool" port="80" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="443" compression="on" compressionMinSize="2048" nocompressionUserAgents="gozilla, traviata"




<Connector port="443" protocol="org.apache.coyote.http11.Http11NioProtocol" SSLEnabled="true" maxThreads="150" scheme="https" secure="true" minSpareThreads="25" maxSpareThreads="75" enableLookups="false" disableUploadTimeout="true" clientAuth="false" sslEnabledProtocols="TLSv1" keystoreFile="/opt/panaces/installconfig/keystore/IBM.keystore" keystorePass="^vMkT%678#4-06Gjue672Kwo95dzg" compression="on" compressionMinSize="2048" nocompressionUserAgents="gozilla,traviata"


4. Open $TOMCAT_HOME/webapps/PanacesGUI/WEB-INF/web.xml a. Search for servlet-mapping --- at /app/*. The searched content displays the following

snippet: <servlet-mapping> <servlet-name>spring</servlet-name> <url-pattern>/app/*</url-pattern> </servlet-mapping>

b. Add the following content after </servlet-mapping> <security-constraint> <web-resource-collection> <web-resource-name>Entire Application</web- resource-name> <url-pattern>/*</url-pattern> </web-resource-collection> <user-data-constraint> <transport- guarantee>CONFIDENTIAL</transport-guarantee> </user-data-constraint> </security-constraint>

5. Restart the RO services , with command sudo $EAMSROOT/bin/panaces restart

Port number is not required in the URL while accessing Resiliency Orchestration GUI and RESILIENCY FILE REPLICATOR GUI through browser.

Example: If the user enters in weburl as http://192.168.20.15/PanacesGUI , it auto re-directs the weburl to https://192.168.20.15/PanacesGUI

Option 2 – Using IPTables

IPTables Configuration for HTTPS: Forwarding Incoming Port 443 requests to Port 8443 For Linux, run below command in shell terminal

iptables -A INPUT -i eth1 -p tcp --dport 443 -j ACCEPT iptables -A INPUT -i eth1 -p tcp --dport 8443 -j ACCEPT iptables -A PREROUTING -t nat -i eth1 -p tcp --dport 443 -j REDIRECT --to-port 8443



Note Any changes made in Server.xml using Option 1 must be reset.

Before executing the above command, check the Ethernet (eth0 or eth1) configured in the Resiliency Orchestration server IP. The above command works only for Ethernet configured as eth1. For Ethernet configured as eth0, replace eth1 with eth0 in the above command. Only root user can change iptable configuration.

Tomcat server can start with non-root user. If any other application is using port 443 on the same server, it may not work.

IPTables Configuration for HTTP: Forwarding Incoming Port 80 requests to Port 8080 For Linux, run below command in shell terminal

iptables -A INPUT -i eth1 -p tcp --dport 80 -j ACCEPT iptables -A INPUT -i eth1 -p tcp --dport 8080 -j ACCEPT iptables -A PREROUTING -t nat -i eth1 -p tcp --dport 80 -j REDIRECT --to-port 8080

Note Any changes made in Server.xml using Option 1 must be reset.

Before executing the above command, check the Ethernet (eth0 or eth1) configured in the Resiliency Orchestration server IP. The above command works only for Ethernet configured as eth1. For Ethernet configured as eth0, replace eth1 with eth0 in the above command. Only root user can change iptable configuration.

Tomcat server can start with non-root user. If any other application is using port 80 on the same server, it may not work.

Steps to Enable Compression in Tomcat Server

Below tag in the server.xml enables compression. Note: Compression will be enabled if the file size is more than 2KB.

Connector port=“8080” maxHttpHeaderSize=“8192” maxThreads=“150” minSpareThreads=“25” maxSpareThreads=“75” enableLookups=“false” redirectPort=“8443” acceptCount=“100” compressionMinSize=“2048” compression=“on” compressableMimeType=“text/html,text/xml,text/plain,text/css, text/javascript,text/json,application/x-javascript, application/javascript,application/json” connectionTimeout=“20000” disableUploadTimeout=“true” URIEncoding=“utf-8” />

<Connector port=“8443” maxHttpHeaderSize=“8192” maxThreads=“150” minSpareThreads=“25” maxSpareThreads=“75” enableLookups=“false” disableUploadTimeout=“true” acceptCount=“100” scheme=“https” secure=“true” compressionMinSize=“2048” compression=“on” compressableMimeType=“text/html,text/xml,text/plain,text/css, text/javascript,text/json,application/x-javascript,



application/javascript,application/json” clientAuth=“false” sslEnabledProtocols=“TLSv1” keystoreFile="/opt/panaces/installconfig/keystore/IBM.keystore" keystorePass="^vMkT%678#4-06Gjue672Kwo95dzg"/>

Note: To change security constraint in web.xml, user have to wait till war is extracted in the first start.

Configuring Current Events

User can view more/less events by changing the value of "IBM.events.displayDuration.hours" in $EAMSROOT/installconfig/panaces.properties file. If this parameter is not specified or invalid integer is specified, then it will be defaulted to 120hrs. Specifying zero might result in no events or very few events occurred within a past few seconds to be shown. It should be noted that changing this parameter will also affect the number of events shown in "Monitor->Continuity" listing page. User is expected to use "Event Reports" if he wants to see history of events for a longer duration (say months) as supposed to increasing this parameter. Changing this value does not require a server restart and this value will be taken when the next refresh of the page happens.

Something here The aging period can be configured by editing/adding "IBM.closeEventsInDays" property in $EAMSROOT/installconfig/panaces.properties file. The value for this property should be a numeric value representing number of days. If this property is not specified or invalid value is provided, the System default it to 5 days. Specifying zero will disable automatic Closure of events. Altering this property does not require restart of Resiliency Orchestration Server.

Fetch Logs

When the Resiliency Orchestration is running with non-root, the system logs will not be fetched until read permission is granted for the non-root user. The non-root user, by default, does not have read permission for the system logs (/var/log/messages etc.).

Server Hardening

Please follow steps to harden the Resiliency Orchestration server

a. Set the password for IBM user passwd IBM

b. Change to bin directory cd $EAMSROOT/bin

c. Execute the script to secure the server ./serverHardening.sh

c. Reboot the server to take effect of changes for server hardening with below command reboot

d. Since the root user is disabled, Login using IBM user e. Change directory to /opt/panaces/bin

cd /opt/panaces/bin



f. As the server is hardened now, the commands should use sudo as prefix Example to start Resiliency Orchestration services below command can be used

sudo ./panaces start

Starting and Stopping Resiliency Orchestration Server

Starting Resiliency Orchestration Server

To start the IBM Resiliency Orchestration Server, perform the following steps:

• Open a terminal using IBM user

• Enter the following command at the command prompt:

sudo $EAMSROOT/bin/panaces start

Starting IBM Resiliency Orchestration Server for the first time takes five minutes to register its components. IBM Resiliency Orchestration GUI operation will be available after the component registration. Wait till the GUI becomes available to you.

Starting Resiliency Orchestration Server in Recover Mode

To start IBM Resiliency Orchestration Server in recover mode, enter the following command:



sudo $EAMSROOT/bin/panaces recover

Stopping Resiliency Orchestration Server



sudo $EAMSROOT/bin/panaces stop

Restarting Resiliency Orchestration Server

To restart the IBM Resiliency Orchestration Server perform the following steps:





sudo $EAMSROOT/bin/panaces restart

Checking Resiliency Orchestration Server Status


Enter the following command at the command prompt:

sudo $EAMSROOT/bin/panaces status

Checking Resiliency Orchestration Server available Modes

To check the available modes of IBM Resiliency Orchestration Server, enter the following command:


Enter the following command at the command prompt:

sudo $EAMSROOT/bin/panaces help

This command will display the following options:

start: Start the IBM Resiliency Orchestration server and Tomcat server restart: Restart the IBM Resiliency Orchestration server and Tomcat server

stop: Stop the IBM Resiliency Orchestration server and Tomcat server recover: Starts the IBM Resiliency Orchestration server in recovery mode with Tomcat server status: Shows whether IBM Resiliency Orchestration Server and Tomcat is running or not

help: Shows this help debug: Runs Tomcat and IBM Resiliency Orchestration, with remote debugging enabled (To debug Tomcat, connect to port 8000. To debug IBM Resiliency Orchestration, connect to port 8001)

Note Do not stop IBM Resiliency Orchestration Server immediately after starting as this might not stop Tomcat, or event registration may not happen properly.



3. Resiliency Orchestration Server

Installation on Linux Cluster Using Graphical Mode

This chapter outlines the procedures for installing IBM Resiliency Orchestration server on Linux Cluster.

System Requirements

For the system requirements for installing IBM Resiliency Orchestration server on Linux Cluster, refer to the section System Requirements in Chapter 2:




Note

Ensure that IBM Resiliency Orchestration Server installation location is on the shared volume. This is the location of the installed software as explained in the sections below.

IBM Resiliency Orchestration 7.1 Interoperability Matrix

For the IBM Resiliency Orchestration 7.1 Interoperability Matrix, refer to IBM Resiliency Orchestration Client Agent Support table in Chapter 1: 1. Installation Overview.

Installation of Resiliency Orchestration Server

IBM Resiliency Orchestration server software is installed on a dedicated Linux server as the IBM Resiliency Orchestration Master. The server software requires the IBM Resiliency Orchestration Server Platform package and MySQL software to be installed on the same server.

The cluster management system features data integrity and application availability, using redundant hardware, shared disk storage, power management, robust cluster communication and application failover mechanisms. Perform the following steps on the dedicated Linux server to install and setup the IBM Resiliency Orchestration Master Server:

• Install the Linux Enterprise Server OS (RHEL 6.x).

Install Linux Cluster version 1.9.43 with these configurations: DLM mode, GFS Shared file system with a minimum of 30 GB, IP service and script service for MySQL, and IBM Resiliency Orchestration.

Install the MySQL 5.5.34 standard software.

The MySQL 5.5.34 database should be located in the shared disk.

Install the IBM Resiliency Orchestration Server Software.

Set up the environment.

Note Refer to Step 5 under Installation of IBM Resiliency Orchestration Server Platform on Linux Cluster nodes to set up the environment.

Follow the sections given below to complete the IBM Resiliency Orchestration Server installation.

Installation of Linux Enterprise Server OS

• Install the Linux Enterprise Server OS without firewall settings and MySQL database package.



Select “No Firewall” option as IBM Resiliency Orchestration uses ports 8443, 8080, 1099, and 45000 for agent communication with the IBM Resiliency Orchestration Server. So, IBM Resiliency Orchestration expects that there should not be any firewall block related issues for these ports.

Allow the software to install the packages selected by default and choose all packages available under ‘Development’ list, and make sure that "Postgre SQL Database and MySQL Database" are not selected under ‘Server’ list. Do not click “Details” hyperlink to make further selections.

Edit the file /etc/sysconfig/selinux to include the option "SELINUX=permissive".

Check /etc/hosts file to ascertain if localhost alias exists or not. If it doesn’t exist, add the localhost alias, and the IP address of the IBM Resiliency Orchestration Server system.

For Example: 127.0.0.1 localhost localhost <ip-address> <localhost> <hostname>

Installation of Linux Cluster

Install Linux Cluster version 1.9.43 with DLM Mode for GFS shared volume and IP service. To install and configure Linux cluster refer to the following documents:

RED HAT Cluster suite rh-cs-en-4 and rh-gfs-en-6_1 from RED HAT

Additional Settings for Linux Installation

§ Open a terminal, log in as root and issue the following command, whenever the system is rebooted.:

# /sbin/sysctl -w net.ipv4.tcp_retries2=4

§ To avoid this, perform the following steps:

o Open the ‘conf’ file by issuing the following command:

vi /etc/sysctl.conf

o Add the following statement and save it:

edit /etc/sysctl.conf with “net.ipv4.tcp_retries2=4” at the end of the file.

o Reboot the system.

Installation of IBM Resiliency Orchestration Server Platform on Linux Cluster nodes

Perform the following steps to install IBM Resiliency Orchestration Server platform on two cluster nodes. For example, it can be Cluster Node A and Cluster Node B. Use the “clusvcadm” utility, to relocate user services between cluster nodes for installation.

• Create a directory titled ‘mysql’ in <shared cluster volume> by issuing the following command, only if it does not exist:

cd /<shared volume>



mkdir mysql

Create Soft link for ‘Mysql’ Database folder by issuing the following command:

cd /var/lib ln –s <shared Cluster Volume>/mysql /mysql

Create ‘panaces’ folder under the shared volume. To create it, run following command at the shared volume:

mkdir <shared volume> /panaces

Once “panaces” link is created, check for its existence with the following command:

ls panaces (or) ls

Set up environment variable EAMSROOT to /opt/panaces at command line:

export EAMSROOT=/opt/panaces

Installation of MySQL

For installation of MySQL 5.5.34 and upgrade of MySQL 5.5.34, please refer to the MySQL 5.5.34 documentation.

Upgrade of MySQL

When upgrading Mysql after the installation of Resiliency Orchestration suite, manually change the mysql configuration(/etc/my.cnf) and restart the Mysql services. Below is sample configuration according to IBM Resiliency Orchestration specification: cat /etc/my.cnf [mysqld] innodb_log_buffer_size=8M innodb_flush_log_at_trx_commit=1 innodb_print_all_deadlocks = 1 innodb_file_io_threads=4 max_binlog_size=20M max_allowed_packet=16M max_connections=500 #log_bin=panacespri_binlog #binlog-do-db=panaces #binlog-do-db=advancedreporter #binlog-do-db=pfr #server-id=1 #binlog-format=MIXED datadir=/var/lib/mysql socket=/var/lib/mysql/mysql.sock user=mysql log_warnings=1 query_cache_limit=4194304 query_cache_size=33554432 tmp_table_size=268435456



max_heap_table_size=268435456 innodb_buffer_pool_size=1024M thread_cache_size=16 slow_query_log = 1 slow_query_log_file = /drfiler/JR_70_PnS/new_sc1/Mysql_SlowQuery.log #skip-name-resolve # Disabling symbolic-links is recommended to prevent assorted security risks symbolic-links=0 [mysqld_safe] log-error=/var/log/mysqld.log pid-file=/var/run/mysqld/mysqld.pid

Post-Installations of IBM Resiliency Orchestration Server Platform on Linux Cluster

Use the “clusvcadm” utility to relocate cluster to a cluster node, say Cluster Node A, and perform the following steps.

• Start MySQL services whenever the system is rebooted by issuing the following command:

# /etc/init/mysql start &

Check whether you are able to log in to MySQL as root, using the following command:

# mysql -u root

Installation of Resiliency Orchestration Server Software

For the procedure to install IBM Resiliency Orchestration Server software, refer to the section Installation of Resiliency Orchestration Server Software in Chapter 2:




Starting and Stopping Resiliency Orchestration Server

For the procedures to start and stop IBM Resiliency Orchestration server, refer to section Starting and Stopping Resiliency Orchestration Server in Chapter 2:




Configuring Linux Cluster

The following information applies to Red Hat Linux Enterprise Linux 5.0 Server edition.

In Linux Cluster, configure MySQL and IBM Resiliency Orchestration application startup files as script files for application failover. Linux Cluster will start and stop the application from these script files. To configure MySQL and IBM Resiliency Orchestration applications on the cluster, create the following scripts files on /opt/panaces/bin folder.

§ Create Mysqlbat.sh file for MySQL Server and type the following code:

start() { sh /etc/init.d/mysql start } stop() { sh /etc/init.d/mysql stop } status() { mysqladmin status } if [ "#1" = "start" ] ; then start elif [ "#1" = "stop" ] ; then stop elif [ "#1" = "status" ] ; then status fi

Linux Cluster Checking the Application Status by Exit Code

For IBM Resiliency Orchestration Linux cluster integration, add the following exit code value in installation folder/panaces/bin/panaces.sh file. Find the status() function in panaces file. Add exit 9 as given in the code below:

status() { add the following case in Panaces Binary panaces_running if [ #? = 0 ] ; then echo "Panaces server is not running" exit 9 else echo "Panaces server is running" fi tomcat_running if [ #? = 0 ] ; then echo "Tomcat server is not running" exit 9 else



echo "Tomcat server is running" fi }

A sample Cluster Configuration is given below: <resources> <clusterfs device="/dev/sdb1" force_unmount="1" fstype="gfs" mountpoint="/panacs" name="mygfs" options=""/> <ip address="192.168.1.100" monitor_link="1"/> <script file="/opt/panaces/bin/panaces.sh" name="Panaces"/> <script file="/opt/panaces/bin/mysqlbat.sh" name="mysql"/ </resources>

Note After the installation is complete, relocate the cluster and test the application’s function from both the servers.

Linux Cluster Administration

For Linux cluster administration, refer to Red Hat Linux Documentation.



4. Resiliency Orchestration Installation

This chapter outlines the procedures for installing IBM Resiliency Orchestration. IBM Resiliency Orchestration software suite contains the following files. • IBMCC_OVF10.ova: IBM Resiliency Orchestration Virtual Appliance for VMware

Minimum System Requirements The following is the minimum system requirements for IBM Resiliency Orchestration server. • 2 vCPU

• 8 GB Memory

• 100 GB Hard Disk Assumptions It is assumed that the administrator who is installing and configuring IBM Resiliency Orchestration Software is familiar with administering Cisco UCS Director Software including restarting UCS Director services by accessing the UCS Director shell.

Installation of Resiliency Orchestration server virtual appliance for VMWare Prerequisites • You need administrator privileges to connect to VMware VSphere

• If you do not want to use DHCP, you need the following information: IP address, subnet mask, and default gateway. Installation Procedure 1. Login to vCenter using the VMware vSphere Client

2. In the Navigation pane, choose the Data Center for IBM Resiliency Orchestration server deployment.

3. Choose File >Deploy OVF Template.

4. The Deploy OVF Template window appears.

5. In the Source pane, browse to the location where IBMCC_OVF10.ova is located, choose the file, and click Open.



6. In the OVF Template Details pane, verify the details and click Next.

7. In the End User License Agreement pane, read the license agreement, and click Accept.

8. In the Name and Location pane, enter the name for the VM and choose the Data Center where IBM Resiliency Orchestration should be deployed

9. In the Host/Cluster pane, choose the required host, cluster, or resource pool, and click Next.

10. In the Datastore pane, choose the location to store IBM Resiliency Orchestration VM files, and click Next.

11. In the Disk Format pane, choose one of the following radio buttons and click Next to create disks a. Thin Provisioned format—To allocate storage on demand as data is written to disk.

b. Thick Provisioned (Lazy Zeroed) format —To allocate storage immediately in thick format.

c. Thick Provisioned (Eager Zeroed) format —To allocate storage in thick format. It might take longer 12. In the Network Mapping pane, choose your network and click Next.

13. In the IP Address Allocation pane, leave the fields blank for DHCP, or enter the values for static IP

14. Click Next.

15. In the Ready to complete pane, verify the options selected, and click Finish.

16. Power on the VM once the upload is completed Note:

The above steps for Deployment can be used for IBMSiteController.ova which includes IBM Agent Node and Site Controller binaries.

Uploading the license Before using IBM Resiliency Orchestration server, a valid license should be uploaded. To obtain the license key, please contact your IBM sales representative. A valid license can be uploaded anytime and does not require, restarting of IBM Resiliency Orchestration Server or its agents. However, IBM Resiliency Orchestration Server should be running to upload the license. To upload the license to the IBM Resiliency Orchestration server: 1. Copy the license file to the virtual appliance using any secure copy tool - WinSCP (From Windows) or scp (From Unix/Linux) 2. Login into virtual appliance through SSH using the credentials “root” and password “IBM123” 3. cd to /opt/panaces/cli directory and run ./RESILIENCY ORCHESTRATIONLicense.sh 4. Upon running the script, RESILIENCY ORCHESTRATIONLicense prompt will be displayed: RESILIENCY ORCHESTRATIONLicense> Type the following syntax to Upload licensekey: upload licensekey <-l --licensefile> <licensefile name with path> For example, RESILIENCY ORCHESTRATIONLicense>upload licensekey -l /tmp/license.xml Press Enter. 5. License will be uploaded and the message "The license is installed successfully"will be displayed.



5. Installing Agent Node Server on Linux Installation of Agent Node Server This section outlines the procedures to install the Agent Node Server on Linux ( RHEL 5 or 6). Additional steps that you must perform are also included within.

Note

You must have root or root equivalent privileges to install IBM Resiliency Orchestration Agent Node.

To install IBM Resiliency Orchestration agent Node, perform the following steps:

• Download the Agent Node binaries from the given ftp path

Execute the following command: (Use whichever is applicable)

sh IBMAgentNode.bin (or) ./IBMAgentNode.bin at the command prompt to run IBM Resiliency Orchestration Agent Node.

Note Make sure that you have free space of approximately 700 MB in the Resiliency Orchestration Agent Node directory, before executing the above command.

After executing the command IBM Resiliency Orchestration Agent Node installation starts with the following screen.

Note

If the RHEL version is not 5.0 ES/AS and 6.0, then a warning message will be displayed on the screen. However, the user can continue with the installation.



Figure 17: IBM Resiliency Orchestration Agent Node Installer

After displaying the IBM Resiliency Orchestration Agent Node Installer screen, the Introduction window is displayed

Figure 18: IBM Resiliency Orchestration Agent Node Installation on Linux - Introduction

Go through the installation procedure and click Next. The Choose Install Folder window is displayed.



Figure 19: IBM Resiliency Orchestration Agent Node Installation on Linux - Choose Install Folder

Select a path to install the software by clicking Choose. Alternatively, you can click Restore Default Folder to restore the default path. The default path is /opt/panaces. It is recommended that you use the default path displayed

Click Next. The Resiliency Orchestration Agent Node IP Address Configuration window is displayed.

Figure 20: IBM Resiliency Orchestration Agent Node Installation on Linux - IBM Resiliency

Orchestration Agent Node IP Address Configuration



Enter the IP addresses of the primary and secondary IBM Resiliency Orchestration servers, and IBM Resiliency Orchestration Agent Node Address. In a non-NAT environment NAT IP address field should be left blank.

In NAT environment Primary and secondary IBM Resiliency Orchestration server’s public IP should be given. Resiliency Orchestration Agent node address should be the public IP & NAT IP address should be the private IP of the server where you are installing.

Note

To change Nat IP configuration after installation or to trouble shoot, refer Troubleshooting for Nat IP on 257.

Click Next. The Pre-Installation Summary window is displayed.

Figure 21: IBM Resiliency Orchestration Agent Node Installation on Linux - Pre - Installation Summary

Go through the pre-installation summary to verify the inputs provided. If you want to change the inputs, click Previous and modify.

. Click Install. The Installing IBM Resiliency Orchestration Agent Node window is displayed.



Figure 22: IBM Resiliency Orchestration Agent Node Installation on Linux - Installing IBM Resiliency

Orchestration Agent Node

Once the installation is complete, the Starting Resiliency Orchestration Agent Node window is displayed.

Figure 23: IBM Resiliency Orchestration Agent Node Installation on Linux - Starting IBM Resiliency

Orchestration Agent Node

On the Starting Resiliency Orchestration Agents Node window, perform either of the following:

§ Click Yes to start the agent services automatically.



§ Click No to start the agent services manually.

Note

The best practice is not to change the default value displayed on the Starting Resiliency Orchestration Agent Node window.

Restart the IBM Resiliency Orchestration Agent Node machine, if the agents do not start after IBM Resiliency Orchestration Agent Node installation is complete.

Click Next. The Installation Completed window is displayed, indicating successful installation.

Figure 24: IBM Resiliency Orchestration Agent Node Installation on Linux - Installation Completed

Click Done to complete the installation process.

Note

After the agent installation, log off and log in again to your computer to effect IBM Resiliency Orchestration environment variables settings permanently.

When the installation is carried on silent mode or GUI mode, restart with a Putty session for Unix.

16. Update the following parameter for optimal performance

No of groups

File name and Path Parameters Value



500

250 $EAMSROOT/remote/installconfig/panaces.properties


500



500 $EAMSROOT/installconfig/panaces.pro

perties panaces.acp.server.concurrentRequestProcessCount

1000

500 /$EAMSROOT/remote/installconfig/panaces.properties


1000

• The panaces.acp.server.concurrentRequestProcessCount parameter is to set the number of threads

that process the messages from Agents.

Note:

Restart the Agent node and remote agents after updating the parameters in the above table



6. Installing Agents on Windows Server

The agent software is packaged into multiple installation packages on IBM Resiliency Orchestration Distribution FTP. It contains all the binaries and packages to run the IBM Resiliency Orchestration agent software. This software installation involves installing the appropriate agent software.

Note

Windows OS Agent is automatically installed during installation of agents. IBM File Replicator is automatically installed during installation of RESILIENCY FILE REPLICATOR Agent.

Pre-requisites for Installing Resiliency Orchestration Agents

IBM Resiliency Orchestration Agent Software packages are available for each supported application, protection software and operating system. These agents are installed on the servers involved in the Disaster Recovery solution. The installer installs the IBM Resiliency Orchestration Agent Platform package, required for the agent software installation, on the same server. This installation is done automatically during agent installation. Ensure that you have local system administrative privilege during the installation. For the installer to install the IBM Resiliency Orchestration Agent Platform package on Windows successfully, the following prerequisites must be fulfilled.

Note

Restarting Windows server may be required in certain cases and so, plan the downtime of the Windows server where the agents are getting installed.

Windows Server Requirements

The server participating in the DR infrastructure must incorporate the following requirements:

• Hardware / Software Requirements

§ The server must have a minimum of 2 GB RAM.

§ C drive to have additional 10GB disk size for Agent Software



Logs Directory

There must be enough disk space allocated on the server to hold MSSQL transaction logs for up to 5 business days. Take the assistance of the consultant to create the directory size appropriately. This directory can reside on either direct attached storage, or external attached storage. Example: Assume that a log of 2MB is generated every 10 minutes. Then, this will require 2MB/log * 6logs/hour * 24 hr/day * 5 days =� 1.5GB of log device size.

The replication of database dump, from primary server to remote server and vice versa, may be done manually either on tapes, or any other backup device. It is assumed that the server is configured with appropriate backup software to do the same. If the database dump size is small, the replication may be performed on WAN/LAN itself. In this case, backup software is not required.

If required, reboot the server after successfully completing the following operations:

Installation of supported JRE. To know the supported JRE, refer to Prerequisites

Commercial Dependencies The Revival_SwitchXlog.jar file must be downloaded by the customer for Postgress.




Based on the features, download the GPL dependent binaries from this link GPL dependent binaries before starting RESILIENCY FILE REPLICATOR and perform the steps mentioned in the chapter, RESILIENCY FILE REPLICATOR Third Party Installation.Refer to GPL License information for more information on GPL licenses. Tar and Rsync Version Details Platform Tar Version Rsync Version Windows-32/64-Bit tar1.16 rsync3.0.7 Linux-32-Bit RHEL 5.6 tar1.19 rsync3.0.5 Linux-64-Bit RHEL 5.5 rsync3.0.9 Linux-64-Bit RHEL 5.7 rsync3.0.9 Linux-64-Bit RHEL 6.X tar1.23 rsync3.0.9 Linux-64-Bit RHEL 7.X tar1.23 rsync3.0.9 AIX tar1.14 rsync3.0.5 HPUX-64-BIT Itanium tar1.26 rsync3.0.9



HPUX-64-BIT Parisac tar1.26 rsync3.0.9 Solaris_Sparc tar1.18 rsync3.0.5 Solaris_Intel tar1.26 rsync3.0.5

§ Java Tools Prerequisite table in Chapter 1: 1. Installation Overview.

§ Installation of all agents.

Host Machines with Virtual IP Address

If there is a virtual IP address for the host, or if the host is part of an OS Cluster, add the entry PANACES_AGENT_NODE_ADDRESS=<IP Address of the Node> in $EAMSROOT\installconfig\PanacesAgentGeneric.cfg. Using this entry, IBM Resiliency Orchestration Server will always communicate to all agents on this IP address. This could be the Virtual IP or the original IP assigned to the interface.

Specific Prerequisites

The following are the pre-requisites for specific agents; ensure that these pre-requisites are met before starting the agents’ installation.

MSSQL Agent

§ If you have MSSQL 2000 installed, download the following MSSQL 2000 Jar Files from Microsoft site and put them in the %EAMSROOT%\lib folder.

§ Mssqlserver.jar

§ Msutil.jar

§ Msbase.jar

On Windows, after downloading the jar files, update the CLASSPATH in the System variables with the details of the downloaded jar files (An example for the jar file path: C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib). MSSQL Agent can be installed only after the CLASSPATH has been updated with the jar files.

§ If you have the MSSQL 2005 already installed, download the following MSSQL 2005 Jar File from Microsoft site and put them in the %EAMSROOT%\lib folder.

§ sqljdbc.jar

§ On Windows, after downloading the jar files, update the CLASSPATH in the System variables with the details of the downloaded jar files (An example for the jar file path: C:\Program Files\Microsoft SQL Server 2005 Driver for JDBC\lib). MSSQL Agent can be installed only after the CLASSPATH has been updated with the jar files.



Oracle Agent

Download following JDBC jar files for Oracle Agents and place them in the %ORACLE_ HOME%\jdbc\lib directory:

§ nls_charset12.jar

§ ojdbc14.jar

Oracle DG Agent

Download following JDBC jar files for Oracle Agents and place them in the %ORACLE_ HOME%\jdbc\lib directory:

§ nls_charset12.jar

§ ojdbc14.jar

Note If there are some agents already installed and the user tries to install additional agents, the installer will not continue with the installation. Install the additional agents in a different location. Important: As a part of every agent installation, the OS agent will be installed automatically without any user input. During the installation process, there will be an option to start the installed agents automatically. These additional agents should not be started automatically from the installer option, since the installer will start the new OS agent also. After the installation is completed, the additional agent can be started from the services panel

Installation of Agents

This section outlines the steps to install all agents on Windows server. Additional steps that you must perform for specific agents are also included within.

Note You must have administrator, root or equivalent privileges to install IBM Resiliency Orchestration Agents.



To install the agents, perform the following steps:

1. Download the Agent Installer executable files from the given ftp path.

2. Files are available in the zipped format in the Agents folder. Extract Files from WindowsRESILIENCY ORCHESTRATIONAgents.zip for 32-bit Windows Operating Systems and Windows64RESILIENCY ORCHESTRATIONAgents.zip for 64-bit Windows Operating Systems.

3 Goto the extracted folder and double click the install.exe file.

Note

Following are the limitations for installing IBM Resiliency Orchestration Agents on Windows:

§ Services can only be registered and started by users having local administrator permissions on the physical target machine, and not remotely.

§ If Services have to be registered and started from remote machines, such as Terminal Server, then the user must be an Administrator having necessary permissions to the registry and Agents\Windows\System32 directories.

§ Make sure that you have free space of approximately 700 MB in temp directory, before installation.

§ Disable the antivirus (if configured or enabled) before installation.

After executing the file, IBM Resiliency Orchestration Agent installation starts with the following screen.

Figure 25: IBM Resiliency Orchestration Agent Installer



After displaying the IBM Resiliency Orchestration Agent Installer screen, the Introduction window is displayed.

Figure 26: IBM Resiliency Orchestration Agents Installation on Windows Server - Introduction


Figure 27: IBM Resiliency Orchestration Agents Installation on Windows Server - Choose Install Folder



Select a path to install the software by clicking Choose. Alternatively, you can click Restore Default Folder to restore the default path. The default path is C:\Program Files\panaces. It is recommended that you use the default path displayed.

Click Next. The Choose Agents - Windows window is displayed.

Figure 28: IBM Resiliency Orchestration Agents Installation on Windows Server - Choose Agents -

Windows

The list of agents available is displayed on the Choose Agents - Windows window. Select the checkbox next to the specific agent to install that agent. You can choose to install any or all of the agents.

Click Next. The Choose Shortcut Folder window is displayed.



Figure 29: IBM Resiliency Orchestration Agents Installation on Windows Server - Choose Shortcut

Folder

Select an option to create a product icon in the required location. For example, select Other option button to create a product icon in a specific path, or select Don’t create icons button to avoid creating shortcut folders.

Note: During installation, if In a new Program Group option is selected and if no name is given for the program group, the option will be ignored and shortcuts will not be created. Please make sure that the selected path has all the JDBC driver jar file.

Click Next. The Agent Configuration window is displayed.



Figure 30: IBM Resiliency Orchestration Agents Installation on Windows Server - Agent Configuration

Depending on the agent you have selected for installation, perform the steps:

§ MSSQL Agent

Enter MSSQL JDBC driver jar file location. Click Choose button to select the jar file location.

. 14. Enter the IP addresses of the primary and secondary IBM Resiliency Orchestration servers

& IBM Resiliency Orchestration Agent Node Address. In a non-NAT environment NAT IP address field should be left blank. In a NAT environment Primary and secondary Resiliency Orchestration server’s public IP should be given. Resiliency Orchestration Agent node address should be the public IP & NAT IP address should be the private IP of the server where you are installing.



Figure 31: IBM Resiliency Orchestration Agents Installation on Windows Server - IBM Resiliency

Orchestration IP Address Configuration

Click Next. Enter Site Controller IP Address if required.

Figure 32: IBM Resiliency Orchestration Site Controller IP Address Configuration on Windows server




Figure 33: IBM Resiliency Orchestration Agents Installation on Windows Server - Pre-Installation

Summary


Click Install. The Installing IBM Resiliency Orchestration Agents window is displayed.

Figure 34: IBM Resiliency Orchestration Agents Installation on Windows Server - Installing IBM

Resiliency Orchestration Agents

Once the installation is complete, the Starting Agents window is displayed.



Figure 35: IBM Resiliency Orchestration Agents Installation on Windows Server - Starting Agents

On the Starting Agents window, perform either of the following:



Note The best practice is not to change the default value displayed on the Starting Agents window. Restart the agent machine, if the agents do not start after agent installation is complete.

When the installation is carried on silent mode or GUI mode, restart with a Remote Desktop session for Windows.

Click Next. The Install Complete window is displayed, indicating successful installation.



Figure 36: IBM Resiliency Orchestration Agents Installation on Windows Server - Install Complete


Download GPL dependent binaries for Windows OS Agent.

Windows -32 BIT installedlocation/bin/cyggcc_s-1.dllinstalledlocation/bin/cygiconv-2.dll installedlocation/bin/cygintl-8.dll installedlocation/bin/cygwin1.dll Windows-64-BIT installedlocation/bin/cyggcc_s-1.dll installedlocation/bin/cygiconv-2.dll installedlocation/bin/cygintl-8.dll installedlocation/bin/cygwin1.dll

Once the installation is complete, verify the individual agent service installation manually, by clicking the Services icon on the Administrative tools group in Control Panel.

Note For MS Exchange solution, Remote Agent installation is also supported. Perform the following:

Remote agent is supported, however, while agent process runs on Agent Node (Resiliency Orchestration Server), the IBM Resiliency Orchestration MS Exchange Extensions (powershell extensions) needs to be deployed on the client servers. To install the extensions, the user has to install the MS Exchange agent (local agent kit). During installation, do not start any agents or after installation disable the installed agent services (from service list).



1. Note that there will be not separate installer to install extensions as the number of installations is always going to be very few (only one or two). Hence we will reuse the agent installer itself to deploy local agent as well as Extensions for remote agent.

2. The traditional remote agent model where everything is deployed and executed on agent node (or Resiliency Orchestration Server) is not supported due to security restrictions by MS Domain Management and powershell.

3. Have to import replication workflow from $EAMSROOT/workflows/MSExch/MSExchReplicationInfo_Remote.xml

4. When the installation is carried on silent mode or GUI mode, restart with a Remote Desktop session for Windows.

Debugging Agent Installation on Windows Server

To debug the installation on Windows server, and to view or capture the debug output from a Win32 installer, keep the CTRL key pressed immediately after launching the installer, until a console window appears. Before exiting the installer, copy the console output to a text file for later review.

Starting and Stopping of Agent Services on Windows Server

Note Make sure that the clock settings on the IBM Resiliency Orchestration server and the agent server are in sync. Perform the following steps to view the agents installed on the server:

• Go to Control Panel.

Click Administrative tools on the Control Panel.

Click the Services icon on the Administrative Tools window. You can see the agents installed on the server.

The following are the agents supported by IBM Resiliency Orchestration on Windows server. Depending on the installed agents, the services window will show some of the following options:

§ Resiliency Orchestration Agent for MS Windows OS

§ Resiliency Orchestration Agent for IBM File replicator

§ Resiliency Orchestration Agent for MS SQL Server

§ IBM File Replicator

§ Resiliency Orchestration Agent for Oracle



§ Resiliency Orchestration Agent for Oracle DataGuard

§ SRDF Agent

Right-click on the respective service in the Services window and do the following:

§ select Start to start the service.

§ select Stop to stop the service.

§ select Restart to restart the service.



7. Installing Agents on Solaris Server

This software is packaged as an image file on the FTP server at ftp.IBM.com. The agents packaged in the Agents folder are RESILIENCY FILE REPLICATOR, SRS, and Sybase Agents. It contains all the binaries and packages to run IBM Resiliency Orchestration agents software. This software installation involves installing IBM Resiliency Orchestration agents’ binaries, and a few miscellaneous software binaries.

Note Solaris OS Agent is automatically installed during the installation of agents. IBM File Replicator is automatically installed during the installation of RESILIENCY FILE REPLICATOR Agent.


IBM Resiliency Orchestration Agent Software packages are available for each supported application, protection software and operating system. These agents are installed on the servers involved in Disaster Recovery solution. The installer installs IBM Resiliency Orchestration Agent Platform package, required for the installation of agent software, on the same server. This installation happens automatically during agent installation. For the installer to install IBM Resiliency Orchestration Agent Platform package successfully on Solaris, the following prerequisites must be fulfilled.

Solaris Server Requirements

The server participating in the DR infrastructure must incorporate the following requirements.

• Hardware / Software Requirements


§ If the server is running Sybase, then it must have Sybase ASE 12.5 or 15 data center edition.

§ Set the Solaris machine time to a desired time zone. If the desired time zone to which Solaris machine is to be set is not available, then import the time zone from another Solaris machine into /usr/share/lib/zoneinfo directory.

Note Make sure that the time settings on IBM Resiliency Orchestration server and the agent

server are in sync.

Logs Directory

There must be enough disk space allocated on the server to hold Sybase transaction logs, for up to 5 business days. Take the assistance of a consultant to size the directory appropriately. This directory can reside on either direct attached storage, or external attached storage.



Example: Consider that a log of 2MB is generated every 10 minutes. This will require 2MB/log * 6logs/hour * 24 hr/day * 5 days =� 1.5GB of log device size.

The replication of database dump from primary server to secondary server and vice versa must be manually done, either on tapes, or on any other backup devices. It is assumed that the server is configured with appropriate backup software to do the same. If the database dump size is small, and primary and remote servers are connected over LAN, the replication may be performed on LAN itself. In this case, backup software is not required.


If there is a virtual IP address for the host or if the host is part of an OS Cluster, then add the following entry in $EAMSROOT/installconfig/PanacesAgentGeneric.cfg PANACES_AGENT_NODE_ADDRESS=<IP Address of the Node>. Using this entry, IBM Resiliency Orchestration Server always communicates to all agents on this IP address. This could be a Virtual IP or the original IP assigned to the interface.


This section outlines the steps to install all agents on Solaris server. Additional steps that you must perform for specific agents are also included within.

Note

You must have administrator, root or equivalent privileges to install IBM Resiliency Orchestration Agents.


1. Download the Agent Installer executable files from the given ftp path.

2. Files are available in the zipped format in the Agents folder. Extract Files from SolarisIntel_RESILIENCY ORCHESTRATIONAgent_7.1.zip for Intel based architecture and SolarisSparc_RESILIENCY ORCHESTRATIONAgent_7.1.zip.

3. Goto the extracted folder and execute the following command: (Use whichever is applicable)


Note Make sure that you have free space of approximately 700 MB in /tmp directory, before executing the above command.

After executing the command IBM Resiliency Orchestration Agent installation starts with the following screen.




After displaying the IBM Resiliency Orchestration Agent Installer screen, the Introduction window is displayed.

Figure 38: IBM Resiliency Orchestration Agents Installation on Solaris Server - Introduction




Figure 39: IBM Resiliency Orchestration Agents Installation on Solaris Server - Choose Install Folder

Select a path to install the software by clicking Choose. Alternatively, you can click Restore Default Folder to restore the default path. The default path is /opt/panaces. It is recommended that you use the default path displayed.

Click Next. The Choose Agents - Solaris window is displayed.

Figure 40: IBM Resiliency Orchestration Agents Installation on Solaris Server - Choose Agents - Solaris



The list of agents available is displayed on the Choose Agents - Solaris window. Select the checkbox next to the specific agent to install that agent. You can choose to install any or all of the agents.

Click Next. The Choose Link Folder window is displayed.

Figure 41: IBM Resiliency Orchestration Agents Installation on Solaris Server - Choose Link Folder

Choose a path for creating links in the Choose Link Folder window.

§ Select In your home folder for creating a link in the home folder.

§ Select Other to enter a specific path.

§ Select Don’t create links for not creating shortcut folders.

Click Next. The Agent Configuration window is displayed.



Figure 42: IBM Resiliency Orchestration Agents Installation on Solaris Server - Agent Configuration

Enter Sybase JDBC driver jar file location. Click the Choose button to select the jar file location.

Note

Make sure that the selected path has all the JDBC driver jar files.

Click Next. For Sybase agent, enter the Sybase Admin login ID for the Sybase database.

Figure 43: IBM Resiliency Orchestration Agents Installation on Solaris Server - Agent Configuration



15. Enter the IP addresses of the primary and secondary IBM Resiliency Orchestration servers & IBM Resiliency Orchestration Agent Node Address. In a non-NAT environment NAT IP address field should be left blank. In a NAT environment Primary and secondary Resiliency Orchestration server’s public IP should be given. Resiliency Orchestration Agent node address should be the public IP & NAT IP address should be the private IP of the server where you are installing.

Figure 44: IBM Resiliency Orchestration Agents Installation on Solaris Server - IBM Resiliency


Note:

To change Nat IP configuration after installation or to troubleshoot the issue refer to Nat IP in the Troubleshooting section.

Click Next. Enter Site Controller IP Address if required.



Figure 45: IBM Resiliency Orchestration Site Controller IP Address Configuration on Solaris Server


Figure 46: IBM Resiliency Orchestration Agents Installation on Solaris Server - Pre-Installation

Summary


Click Install. The Installing IBM Resiliency Orchestration Agents window is displayed.



Figure 47: IBM Resiliency Orchestration Agents Installation on Solaris Server - Installing IBM

Resiliency Orchestration Agents

Once the installation is complete, the Starting Agents window is displayed.

Figure 48: IBM Resiliency Orchestration Agents Installation on Solaris Server - Starting Agents

On the Starting Agents window, perform either of the following:






Click Next. The Install Complete window is displayed, indicating the successful installation.

Figure 49: IBM Resiliency Orchestration Agents Installation on Solaris Server - Install Complete


Note

After the agent installation, log off and log in again to your computer to effect the IBM Resiliency Orchestration environment variables settings permanently.

When the installation is carried on silent mode or GUI mode, restart with a Putty session for Unix and Remote Desktop session for Windows.

Debugging Agent Installation on Solaris Server

To debug the Agent installation on Solaris server, refer the log entries made in the file PanacesAgentdebug.log. The file is located in /opt directory.

Starting and Stopping Agents on Solaris Server

The script for starting and stopping of the agents resides at the following location on the Solaris server:

/etc/rc3.d



Solaris OS Agent

§ The script S99PanOSAgt starts the service automatically when the server is rebooted.

§ Alternatively, the following steps can be used to start or stop the agent manually -

Go to $EAMSROOT and enter the following command:

# nohup ./SolarisOSAgent.sh start & # nohup . /SolarisOSAgent.sh stop &

Note

Java is not bundled with the installer for Intel Solaris systems. Instead, the system uses Java installed with the Operating System (OS). For Intel Solaris machines, the following steps are performed to use Java installed with the OS:

i. Rename installer bundled java mv /opt/panaces/jre /opt/panaces/orig_jre

ii. Create softlink to the os java : ln -s /usr/bin/java/jre /opt/panaces/jre

§ Note that $EAMSROOT is /opt/panaces as explained in this guide. This is the default location. However, you can install the agents at any other location.

PFR Agent

§ The script S99PanPFRAgt starts the service automatically when the server is rebooted.


Go to $EAMSROOT and enter the following command: # nohup ./PFRAgent.sh start & # nohup ./PFRAgent.sh stop &

Sybase Agent

§ The script S99PanSybAgt starts the service automatically when the server is rebooted.


Go to $EAMSROOT and enter the following command: # nohup ./SybaseAgent.sh start & # nohup ./SybaseAgent.sh stop &

SRS Agent

§ The script S99PanSRSAgt starts the service automatically when the server is rebooted.




Go to $EAMSROOT and enter the following command: # nohup ./SRSAgent.sh start & # nohup ./SRSAgent.sh stop &

Oracle Agent

§ The script S99PanOraAgt starts the service automatically when the server is rebooted.


Go to $EAMSROOT and enter the following command: # nohup ./OracleAgent.sh start & # nohup ./OracleAgent.sh stop &

TrueCopy

§ The script S99PanTrueCopyAgt starts the service automatically when the server is rebooted.


Go to $EAMSROOT and enter the following command: $nohup ./TrueCopyAgent.sh start & $nohup ./TrueCopyAgent.sh stop & Listing the Running Agents

Enter the following command to check whether the agents installed have been started or not: # ps –ef | grep –i LAX

This command will list the names of the agents that have been started.



8. Installing Agents on Linux Server

This software is packaged as an image file on IBM Resiliency Orchestration Distribution is available in the ftp.IBM.com and can be accessed by the customer with the given credentials. This software installation involves installing IBM Resiliency Orchestration agents’ binaries, and a few miscellaneous software binaries.

Note

Linux OS Agent is automatically installed during installation of agents. IBM File Replicator is automatically installed during installation of RESILIENCY FILE REPLICATOR Agent.


This section outlines the steps to install all agents on Linux (RHEL 6.x) server. Additional steps that you must perform for specific agents are also included within.

Note

You must have administrator, root or equivalent privileges to install IBM Resiliency Orchestration Agents.



2 Browse through IBM Resiliency Orchestration software from the downloaded path and go to the folder to the folder Agent/Linux_RESILIENCY ORCHESTRATIONAgent_7.1.zip for 32-bit Linux Operating Systems or Agents/ Linux64_RESILIENCY ORCHESTRATIONAgent_7.1.zip for 64-bit Linux Operating Systems.

3 Execute the following command: (Use whichever is applicable)


Note Make sure that you have free space of approximately 700 MB in /tmp directory, before executing the above command.

4 After executing the command, IBM Resiliency Orchestration Agent installation starts with the following screen.

Note

If the RHEL version is not 6.x, then a warning message will be displayed on the screen. However, the user can continue with the installation.




5 After displaying the IBM Resiliency Orchestration Agent Installer screen, the Introduction window is displayed

Figure 51: IBM Resiliency Orchestration Agents Installation on Linux Server - Introduction

6 Go through the installation procedure and click Next. The Choose Install Folder window is displayed.



Figure 52: IBM Resiliency Orchestration Agents Installation on Linux Server - Choose Install Folder

7 Select a path to install the software by clicking Choose. Alternatively, you can click Restore Default Folder to restore the default path. The default path is /opt/panaces. It is recommended that you use the default path displayed.

8 Click Next. The Choose Agents - Linux window is displayed.

Figure 53: IBM Resiliency Orchestration Agents Installation on Linux Server - Choose Agents - Linux

9 The list of agents available is displayed on the Choose Agents - Linux window. Select the checkbox next to the specific agent to install that agent. The user can choose to install any or all of the agents.



10 Click Next. The Choose Link Folder window is displayed.

Figure 54: IBM Resiliency Orchestration Agents Installation on Linux Server - Choose Link Folder

11 Choose a path for creating links in the Choose Link Folder window.



§ Click Don’t create links for not creating shortcut folders.

12 Click Next. The Agent Configuration window is displayed.



Figure 55: IBM Resiliency Orchestration Agents Installation on Linux Server - Agent Configuration

13 Enter the Oracle home directory location. Click Choose button to select the file location.

14 Click Next. Enter the Oracle JDBC driver jar directory. Click Choose button to select the jar file location.

Note Make sure that the selected path has all the JDBC driver jar files.




15 Click Next. Enter the Oracle Java lib directory location. Click the Choose button to select the file location


16. Enter the IP addresses of the primary and secondary IBM Resiliency Orchestration servers & IBM Resiliency Orchestration Agent Node Address. In a non-NAT environment NAT IP address field should be left blank. In a NAT environment Primary and secondary Resiliency Orchestration server’s public IP should be given. Resiliency Orchestration Agent node address should be the public IP & NAT IP address should be the private IP of the server where you are installing.

Figure 58: IBM Resiliency Orchestration Agents Installation on Linux Server - IBM Resiliency




Note

To change Nat IP configuration after installation or to trouble shoot Nat IP refer Troubleshooting Nat IP on 257.

16 Click Next. Enter Site Controller IP Address if required.

Figure 59: IBM Resiliency Orchestration Site Controller IP Address Configuration on Linux server

17 Click Next. The Pre-Installation Summary window is displayed.

Figure 60: IBM Resiliency Orchestration Agents Installation on Linux Server - Pre - Installation screen



18 Go through the pre-installation summary to verify the inputs provided. If you want to change the inputs, click Previous and modify.

19 Click Install. The Installing IBM Resiliency Orchestration Agents window is displayed.

Figure 61: IBM Resiliency Orchestration Agents Installation on Linux Server - Installing IBM Resiliency

Orchestration Agents

20 Once the installation is complete, the Starting Agents window is displayed.

Figure 62: IBM Resiliency Orchestration Agents Installation on Linux Server - Starting Agents

21 On the Starting Agents window, perform either of the following:






22 Click Next. The Install Complete window is displayed, indicating successful installation.

Figure 63: IBM Resiliency Orchestration Agents Installation on Linux Server - Install Complete

23 Click Done to complete the installation process.

24 Download GPL dependent binaries for RESILIENCY ORCHESTRATION, MySQL Agent.

My SQL EAMSROOT/lib/mysql-connector-java-5.1.20-bin.jar

Note After the agent installation, log off and log in again to your computer to effect IBM Resiliency Orchestration environment variables settings permanently.

When the installation is carried on silent mode or GUI mode, log off and log in with a Putty session for Unix as well as for Windows



Debugging Agent Installation on Linux Server

To debug the Agent installation on Linux server, refer the log entries made in the file PanacesAgentDebug.log. The file is located in the /opt directory.

Starting and Stopping Agents on Linux Server

The script for starting and stopping agents that reside at the following location on the Linux server: /etc/rc3.dLinux OS Agent



Go to $EAMSROOT and enter the following command: # nohup ./LinuxOSAgent.sh start & # nohup ./LinuxOSAgent.sh stop &

Note that $EAMSROOT is /opt/panaces as explained in this guide. This is the default location. However, you can install the agents at any other location.

PFR Agent




Oracle Agent




Oracle Data Guard Agent



Go to $EAMSROOT and enter the following command: # nohup ./dataguardagent.sh start & # nohup ./dataguardagent.sh stop &



PostgreSQL Agent

§ The script S99PanPostgresAgt starts the service automatically when the server is rebooted.


Go to $EAMSROOT and enter the following command: # nohup ./PostgresAgent.sh start & # nohup ./PostgresAgent.sh stop &Listing the Agents that are Running





9. Installing Agents on HPUX Server

This software is packaged as an image file on the FTP server ftp.IBM.com. It contains all the binaries and packages to run IBM Resiliency Orchestration agents software. This software installation involves installing IBM Resiliency Orchestration agents’ binaries, and a few miscellaneous software binaries.

Note

HPUX OS Agent is automatically installed during installation of agents. IBM File Replicator is automatically installed during installation of RESILIENCY FILE REPLICATOR Agent. RESILIENCY FILE REPLICATOR replication may not work on Itanium machines. Install gnu-tar for HPUX for Itanium:

1. Download and manually install the GNU tar files. 2. Create the following soft links, after the installation of gnu tar:

ln -s <agent_install_dir>/tool/usr/local/lib/libiconv.sl /usr/local/lib/libiconv.sl ln -s <agent_install_dir>/tool/usr/local/lib/libintl.sl /usr/local/lib/libintl.sl


This section outlines the steps to install all agents on HPUX server. Additional steps that you must perform for specific agents are also included within.

Note You must have root or root equivalent privileges to install IBM Resiliency Orchestration Agents.



2 Browse through IBM Resiliency Orchestration software from the downloaded path and go to the folder to the folder Agent/HPUX_RESILIENCY ORCHESTRATIONAgent_7.1.zip.

3 Goto the extracted folder and execute the following command: (Use whichever is applicable)


Note

Make sure that you have free space of approximately 700 MB in /tmp directory, before executing the above command.





5 After displaying the IBM Resiliency Orchestration Agent Installer screen, the Introduction window is displayed.

Figure 65: IBM Resiliency Orchestration Agents Installation on HPUX Server - Introduction




Figure 66: IBM Resiliency Orchestration Agents Installation on HPUX Server - Choose Install Folder


8 Click Next. The Choose Agents - HPUX window is displayed.

Figure 67: IBM Resiliency Orchestration Agents Installation on HPUX Server - Choose Agents - HPUX

9 The list of agents available is displayed on the Choose Agents - HPUX window. Select the checkbox next to the specific agent to install that agent. You can choose to install any or all of the agents.




Figure 68: IBM Resiliency Orchestration Agents Installation on HPUX Server - Choose Link Folder

11 Choose a path for creating links in the Choose Link Folder window.







Figure 69: IBM Resiliency Orchestration Agents Installation on HPUX Server - Agent Configuration

13 Enter the Oracle home directory location. Click Choose button to select the file location.

14 Click Next. Enter the Oracle JDBC driver jar directory. Click Choose button to select the jar file location.

Note

Make sure that the selected path has all the JDBC driver jar files.


15 Click Next. Enter the Oracle Java lib directory location. Click the Choose button to select the file location




16 Enter the IP addresses of the primary and secondary IBM Resiliency Orchestration servers & IBM Resiliency Orchestration Agent Node Address. In a non-NAT environment NAT IP address field should be left blank.

In a NAT environment Primary and secondary Resiliency Orchestration server’s public IP should be given. Resiliency Orchestration Agent node address should be the public IP & NAT IP address should be the private IP of the server where you are installing.

Figure 72: IBM Resiliency Orchestration Agents Installation on HPUX Server - IBM Resiliency

Orchestration IP Address configuration



Note

To change Nat IP configuration after installation or to trouble shoot refer Troubleshooting for Nat IP on 257.


Figure 73: IBM Resiliency Orchestration Site Controller IP Address Configuration on HPUX server


Figure 74: IBM Resiliency Orchestration Agents Installation on HPUX Server - Pre-Installation

Summary





Figure 75: IBM Resiliency Orchestration Agents Installation on HPUX Server - Installing IBM Resiliency



Figure 76: IBM Resiliency Orchestration Agents Installation on HPUX Server - Starting Agents







23 Click Next. The Install Complete window is displayed, indicating the successful installation.

Figure 77: IBM Resiliency Orchestration Agents Installation on HPUX Server - Install Complete


Note

After the agent installation, log off and log in again to your computer to effect the IBM Resiliency Orchestration environment variables settings permanently.


Debugging Agent Installation on HPUX Server

To debug the Agent installation on HPUX server, refer to the log entries made in the file PanacesAgentDebug.log. The file is located in the /opt directory.

Starting and Stopping Agents on HPUX Server HPUX OS Agent

§ The following steps can be used to start or stop the agent manually -



Go to $EAMSROOT and enter the following command: # nohup ./HPUXOSAgent.sh start & # nohup ./HPUXOSAgent.sh stop &


PFR Agent



Oracle Agent





Go to $EAMSROOT and enter the following command: # nohup ./DataGuardAgent.sh start & # nohup ./DataGuardAgent.sh stop &

Listing the Agents that are Running





10. Installing Agents on AIX Server

This software is packaged as an image file on the FTP server ftp.IBM.com. It contains all the binaries and packages to run IBM Resiliency Orchestration agents software. This software installation involves installing IBM Resiliency Orchestration agents’ binaries, and a few miscellaneous software binaries.

Note

AIX OS Agent is automatically installed during installation of agents. IBM File Replicator is automatically installed during installation of RESILIENCY FILE REPLICATOR Agent.


IBM Resiliency Orchestration Agent Software packages are available for each supported application, protection software and operating system. These agents are installed on the servers involved in the Disaster Recovery solution. The installer installs the IBM Resiliency Orchestration Agent Platform package, required for agent software to be installed, on the same server. This installation happens automatically during agent installation.

For the installer to install IBM Resiliency Orchestration Agent Platform package successfully on AIX, the following prerequisites must be fulfilled.

AIX Server Requirements

The server participating in the DR infrastructure must incorporate the following requirements:

Hardware / Software Requirements


§ Make sure that the AIX machine is set to a desired time-zone.

Note Make sure that the time settings on the IBM Resiliency Orchestration server and the agent server are in sync.


If there is a virtual IP address for the host or if the host is part of an OS Cluster, add the following entry in $EAMSROOT/installconfig/PanacesAgentGeneric.cfg PANACES_AGENT_NODE_ADDRESS=<IP Address of the Node>. Using this entry, IBM Resiliency Orchestration Server always communicates to all agents on this IP address. This could be a Virtual IP or the original IP assigned to the interface.




This section outlines the steps to install all agents on AIX server. Additional steps that you must perform for specific agents are also included within.

Note You must have administrator, root or equivalent privileges to install IBM Resiliency Orchestration Agents.


1 Download the server binaries from the given ftp path

2 Browse through IBM Resiliency Orchestration software from the downloaded path and go to the folder to the folder Agent/AIX_RESILIENCY ORCHESTRATIONAgent_7.1.zip.

3 Goto the extracted folder and execute the following command: (Use whichever is applicable)


Note






5 After displaying the IBM Resiliency Orchestration Agent Installer screen, the Introduction window is displayed.

Figure 79: IBM Resiliency Orchestration Agents Installation on AIX Server - Introduction


Figure 80: IBM Resiliency Orchestration Agents Installation on AIX Server - Choose Install Folder




8 Click Next. The Choose Agents - AIX window is displayed.

Figure 81: IBM Resiliency Orchestration Agents Installation on AIX Server - Choose Agents - AIX

9 The list of agents available is displayed on the Choose Agents - AIX window. Select the checkbox next to the specific agent to install that agent. You can choose to install any or all of the agents.


Figure 82: IBM Resiliency Orchestration Agents Installation on AIX Server - Choose Link Folder

11 Choose a path for creating links on the Choose Link Folder window.







Figure 83: IBM Resiliency Orchestration Agents Installation on AIX Server - Agent Configuration

13 Enter the DB2 Instance user login ID. Click Next.

Note If PFR agent is select, then installer skips this step and displays IBM Resiliency Orchestration Server IP Address Configuration window as PFR Agent does not require any configuration.



Figure 84: IBM Resiliency Orchestration Agents Installation on AIX Server - Agent Configuration

14 Enter the IP addresses of the primary and secondary IBM Resiliency Orchestration servers & IBM Resiliency Orchestration Agent Node Address. In a non-NAT environment NAT IP address field should be left blank.

In a NAT environment Primary and secondary Resiliency Orchestration server’s public IP should be given. Resiliency Orchestration Agent node address should be the public IP & NAT IP address should be the private IP of the server where you are installing

Note

To change Nat IP configuration after installation or to troubleshoot refer Troubleshooting Nat IP on 257.



Figure 85: IBM Resiliency Orchestration Agents Installation on AIX Server - IBM Resiliency

Orchestration IP Address configuration


Figure 86: IBM Resiliency Orchestration Site Controller IP Address Configuration on AIX server




Figure 87: IBM Resiliency Orchestration Agents Installation on AIX Server - Pre-Installation Summary



Figure 88: IBM Resiliency Orchestration Agents Installation on AIX Server - Installing IBM Resiliency





Figure 89: IBM Resiliency Orchestration Agents Installation on AIX Server - Starting Agents





21 Click Next. The Install Complete window is displayed, indicating successful installation.



Figure 90: IBM Resiliency Orchestration Agents Installation on AIX Server - Install Complete


Note

After the Agent installation, log off and log in again to your computer to effect the IBM Resiliency Orchestration environment variables settings permanently.


Starting and Stopping of Agents on AIX Server

The script for starting and stopping of the agents resides at the following location on AIX server: /etc/rc.d/rc2.dAIX OS Agent



Go to $EAMSROOT and enter the following command: # nohup ./AIXOSAgent.sh start & # nohup ./AIXOSAgent.sh stop &


PFR Agent






Oracle Agent







Go to $EAMSROOT and enter the following command: # nohup ./DataGuardAgent.sh start & # nohup ./DataGuardAgent.sh stop &

Listing the Agents that are Running





11. Installing Resiliency Orchestration

Advanced Reporter

IBM Advanced Reporter is licensed feature. You can install it in GUI mode only. It is supported only in Linux platform, to be installed on Resiliency Orchestration Server.

Pre-requisite

IBM Resiliency Orchestration server has to be already installed in the machine, else installer will display an error and quit.

GUI Mode Installation of Resiliency Orchestration Advanced Reporter

To install the advanced reporter, perform the following steps. The commands specified in the following points must be provided at the command prompt:

1 Download the Advanced Reporter binaries from the given ftp path.

2 IBM Resiliency Orchestration Advanced Reporter can be installed only if you log in as Root user. Go to Advanced Reporter folder and execute the following command.


3 After executing the command IBM Resiliency Orchestration Advanced Reporter installation starts with the following screen.



Figure 91: IBM Resiliency Orchestration Advanced Reporter Installer

4 After displaying the IBM Resiliency Orchestration Advanced Reporter Installer screen, the MySQL root password window is displayed.

Figure 92: IBM Resiliency Orchestration Advanced Reporter Installation - MySQL root password

5 Enter password for MySQL root user or leave it blank if there is no password.

Note Click the Cancel button to quit the installation.

6 Click Next. The Tomcat Home window is displayed.



Figure 93: IBM Resiliency Orchestration Advanced Reporter Installation - Tomcat Home

7 Click Choose… to browse and select the location of Tomcat.

Figure 94: IBM Resiliency Orchestration Advanced Reporter Installation - Tomcat Path

8 When Tomcat is located and then selected, the path appears in the Please Choose a Folder: box in Tomcat Home screen. Click Next, the Introduction window is displayed.



Figure 95: IBM Resiliency Orchestration Advanced Reporter Installation - Introduction

9 Click Next. The Choose IBM Resiliency Orchestration Server Folder window is displayed.

Figure 96: IBM Resiliency Orchestration Advanced Reporter Installation - Choose IBM Resiliency

Orchestration Server Folder

10 Select the path where IBM Resiliency Orchestration Server software is installed. Click Choose… to select the installation path. The default path is /opt/panaces.



Note If the IBM Resiliency Orchestration server is not installed in the given path, an error message is displayed.


Figure 97: IBM Resiliency Orchestration Advanced Reporter Installation - Pre-Installation Summary

Note

Read through the pre-installation summary to verify the inputs provided. If you want to change the inputs, click Previous and modify.

12 Click Install. The Installing IBM Advanced Reporter window is displayed.



Figure 98: IBM Resiliency Orchestration Advanced Reporter Installation - Installing IBM Resiliency

Orchestration Advanced Reporter

13 IBM Resiliency Orchestration Advanced Reporter Installation automatically uploads the IBM Resiliency Orchestration Advanced Reporter schema. If it already exists, a dialog box is displayed as shown below, that confirms if you want to drop the existing IBM Resiliency Orchestration Advanced Reporter schema and replace it through installer.

Figure 99: IBM Resiliency Orchestration Advanced Reporter Installation - Confirmation message

14 Click No to continue the installation with the existing schema. Click Refresh to drop and recreate the IBM Resiliency Orchestration Advanced Reporter schema.



15 After the installation is complete, the Installation Completed window is displayed, indicating successful installation.

Figure 100: IBM Resiliency Orchestration Advanced Reporter Installation - Installation Completed


Perform the following steps to configure Openreports 1 Download openreports3.2.tar.gz $TOMCAT_HOME of RESILIENCY ORCHESTRATION

Server from sourceforge content server https://sourceforge.net/projects/gnu-utils/files/binaries/ The tarball contains openreports.war, mariadb-java-client-1.1.8.jar,jasperreports-4.5.0.jar & jasperreports-javaflow-4.5.0.jar files. 2 Remove existing openreports.war(which is 0kb) file and open reports folder if exists already. 3 Untar openreports3.2.tar.gz using below commands

• cd $TOMCAT_HOME; tar -xvzf openreports3.2.tar.gz After untaring openreports3.2.tar.gz, openreports/WEB-INF/lib structure is created under $TOMCAT_HOME/webapps/ along with the following jar files: mariadb-java-client-1.1.8.jar,jasperreports-4.5.0.jar & jasperreports-javaflow-4.5.0.jar

4 Rename the existing openreports folder as openreports_bak 5 Copy $TOMCAT_HOME/openreports.war to $TOMCAT_HOME/webapps. 6 Unzip the openreports.war at $TOMCAT_HOME/webapps by executing the following

command if the TOMCAT service does not unzip openreports.war • unzip $TOMCAT_HOME/webapps/openreports.war -d openreports

7 Delete the jar files by executing the following command. • rm -f WEB-INF/lib/jasperreports-3.5.1.jar WEB-INF/lib/jasperreports-3.5.1-

javaflow.jar 8 copy mariadb-java-client-1.1.8.jar,jasperreports-4.5.0.jar & jasperreports-javaflow-4.5.0.jar

files from $TOMCAT_HOME/webapps/openreports_bak/WEB-INF/lib to $TOMCAT_HOME/webapps/openreports/WEB-INF/lib



9 Delete the openreports_bak folder. 10 Go to $EAMSROOT/lib. 11 Unzip openreports_dependencies.zip by executing the following command:

• unzip openreports_dependencies.zip -d openreports_dependencies After executing the above command, openreports_dependencies folder will be created under /$EAMSROOT/lib

12 copy classes folder from $EAMSROOT/lib/openreports_dependencies/WEB-INF to $TOMCAT_HOME/webapps/openreports/WEB-INF

13 copy etl.jar from $EAMSROOT/lib/openreports_dependencies/WEB-INF/lib to $TOMCAT_HOME/webapps/openreports/WEB-INF/lib

14 Login to Mysql by executing the following commands at mysql prompt • use advancedreporter; • update REPORT_DATASOURCE set DRIVER='org.mariadb.jdbc.Driver';

Notes: By default, MariaDB connector timeout is set to 8 hours, connection will be timed out if it is idle for 8 hours. To enable the Openreport to validate the connection prior to login, perform the following task:

• Add the validationQuery property in the $TOMCAT_HOME/webapps/openreports/WEB-INF/applicationContext.xml file, as shown in the following snippet.

<bean id="hibernateDataSource" destroy-method="close" class="org.apache.commons.dbcp.BasicDataSource"> <property name="driverClassName" value="${hibernate.jdbc.driver}" /> <property name="url" value="${hibernate.jdbc.url}" /> <property name="username" value="${hibernate.jdbc.username}" /> <property name="password" value="${hibernate.jdbc.password}" /> <property name="maxIdle" value="${hibernate.jdbc.maxIdle}" /> <property name="maxActive" value="${hibernate.jdbc.maxActive}" /> <property name="validationQuery" value="SELECT 1" /> </bean>

15 Restart IBMRESILIENCY ORCHESTRATION services to access open reports.



12. Installation of Resiliency Orchestration Upgrade Assist

IBM Upgrade assist helps in the upgrade of the agents and RESILIENCY FILE REPLICATOR service.

Pre-requisites

The local agent/RESILIENCY FILE REPLICATOR service or both should be installed and running.

Installation

Figure 101: IBM Resiliency Orchestration Upgrade Assist - Introduction

Start the upgrade Installer. Click Next.



Figure 102: IBM Resiliency Orchestration Upgrade Assist – Choose Installer File

Select the path for installation for IBM Upgrade assist. Click Next.

Figure 103: IBM Resiliency Orchestration Upgrade Assist - Choose Link Folder






Select the option Don’t Create Link, Click Next. Note: The following screens shots: 107, 108 and 109 will appear only if the IBM Resiliency Orchestration Agents and RESILIENCY FILE REPLICATOR Agents are not identified by IBM upgrade assist.

Figure 104: IBM Resiliency Orchestration Upgrade Assist – Choose Installed Agents

If both IBM Resiliency Orchestration Agent and RESILIENCY FILE REPLICATOR is installed, and need to upgrade, select RESILIENCY ORCHESTRATIONAgents radio button. If only RESILIENCY FILE REPLICATOR service is installed and need to be upgraded, select RESILIENCY FILE REPLICATOR radio button. Choose the already installed Agents/Services from the options .Click Next.



Figure 105: IBM Resiliency Orchestration Upgrade Assist – Choose IBM Resiliency Orchestration Agents

Installation Provide the EAMSROOT Path, which is the older version’s installation path. Click Next.

Figure 106: IBM Resiliency Orchestration Upgrade Assist – RESILIENCY FILE REPLICATOR Service

Installation Provide the RESILIENCY FILE REPLICATORROOT Path. Click Next to enter the IBM Resiliency Orchestration IP address



Figure 107: IBM Resiliency Orchestration Upgrade Assist – Pre Installation Summary

After verifying all the Pre Installation Summary, click Install to start the Installation process.

Figure 108: IBM Resiliency Orchestration Upgrade Assist – Installing IBM Resiliency Orchestration

Upgrade Assist



Figure 109: IBM Resiliency Orchestration Upgrade Assist – Starting IBM Resiliency Orchestration

Upgrade Assist

§ Select Yes to start the agent services automatically.

§ Select No to start the agent services manually.

Click Next.



Figure 110: IBM Resiliency Orchestration Upgrade Assist – Install Complete

Click Done to complete the installation.

Steps to Upgrade Agent from Resiliency Orchestration.

1. In the Admin page, click the link Go to Agent Upgrade. The Agent Upgrade page will have component name, IP Address, Current version, Upgrade Status and Upgrade options. Once upgrade is completed the latest upgraded version to be displayed. Note: Before Agent upgrade move the dependent Recovery groups and Application groups to maintenance mode.

16 The Upgrade status will display the either of the two status as given below in the figures.



In this scenario, both the agent and RESILIENCY FILE REPLICATOR service needs to be upgraded and binaries need to be uploaded for both.

In this scenario, only the Agent needs to be upgraded as RESILIENCY FILE REPLICATOR is already up to date hence upload binaries required only for Agent.

17 Upload the required binaries in IBM Resiliency Orchestration through jack rabbit repository. Below are the steps to upload.

• Download and keep the required binaries to upload in this path on the Resiliency

Orchestration. $EAMSROOT/upgrade/cli/installer_binaries

• Run the script $EAMSROOT/upgrade/cli/bin/UploadClient.sh

• Type help to see the available options in the Upgrade Assist CLI

• Type the option upload_ installer_ files to upload all the binaries kept at the path $EAMSROOT/upgrade/cli/installer_binaries

• Binaries are uploaded to jack rabbit repository.

18 In the GUI the user can see the binaries are uploaded and upgrade button is shown.



19 After clicking Upgrade button the agent upgrade is successful and displays the latest version for Agent and RESILIENCY FILE REPLICATOR.

Agent/RESILIENCY FILE REPLICATOR Auto-Rollback Functionality

When upgrade button is clicked, and there are issues at the backend (such as no enough space, repository settings are wrong, $EAMSROOT path etc. is wrong) then the upgrade fails. Then by default, due to the auto-rollback functionality agent/RESILIENCY FILE REPLICATOR data gets restored as it was before upgrade keeping the system function as earlier

. Note

Make sure that /tmp folder is empty or has enough space before upgrading Agents or RESILIENCY FILE REPLICATOR otherwise the upgrade may fail. The backup files - PanacesAgentsInstallerUpgrade.properties_<currentversion> and PFRInstallerUpgrade.properties_<currentversion> (example: PanacesAgentsInstallerUpgrade.properties_5.0_FCS_P4_ , PFRInstallerUpgrade.properties_RESILIENCY FILE REPLICATOR_5.0_FCS ) get created under $SASROOT/installconfig path when earlier agent versions till 6.3 Beta are upgraded with IBM Upgrade Assist.



13. Silent Mode Installation of Resiliency Orchestration Advanced Reporter

In Silent mode installation method, the installation program reads the settings of the previous configuration from the .properties file that the user has created prior to installation. The installation program does not display any configuration options during the installation process. The following sections describe how to install IBM Resiliency Orchestration Advanced Reporter, using the installation program in silent mode on Linux platform. It is assumed that the user has acquired the installation program from the FTP server.

Editing Properties File

Before the user can run the installation program for Advanced Reporter in Silent mode, the properties file must be edited as per the following instructions.

To edit PanacesServerInstaller.properties file:

1 Get the Advanced Reporter Installer binary and PanacesServerInstaller.properties file from the FTP server and copy it to /tmp folder.

cp Server/PanacesServerInstaller.properties /tmp/ cp AdvancedReporter/install.bin /tmp

• Open the properties file by using the following command:

vi /tmp/PanacesServerInstaller.properties

Modify the MYSQL_ROOT_PASSWORD to modify MySQL root user password.

Installing Resiliency Orchestration Advanced Reporter on Linux

Perform the following steps to install Advanced Reporter on Linux system.

1. Log on to Linux system.

2. Navigate to the directory that contains the installation file.

3. Launch the installation by entering the following command:

/tmp/install.bin –f /tmp/PanacesServerInstaller.properties

Note: To verify the Advanced Reported installation was successful, go to $EAMSROOT and verify that the reports folder is created and contains the required files.



14. Installing Resiliency Orchestration Using

Silent Mode Installation In Silent mode installation method, the installation program reads the settings for your configuration from the .properties file that you create prior to installation. The installation program does not display any configuration options during the installation process. Silent mode installation is supported on Windows, Linux, Solaris, HPUX and AIX platforms. The following sections describe how to install IBM Resiliency Orchestration, using the installation program in silent mode on Windows, Linux, Solaris, HPUX and AIX platforms. It is assumed that you have acquired the installation program from the FTP server.

Note Make sure that the hardware and software configuration required for IBM Resiliency Orchestration installation is in place. For a complete list of supported configurations, refer to the System Requirements section in Chapter 2:





When you install IBM Resiliency Orchestration in Silent mode, the installation program uses the .properties file for server (PanacesServerInstaller.properties) as well as agents (PanacesAgentsInstaller.properties), to determine which installation options should be implemented. Therefore, before you can run the installation program in Silent mode, you must edit the respective properties file in which you specify the installation options that you want to invoke, while performing the IBM Resiliency Orchestration Server and Agents installation. Perform the following steps to edit the properties files.

1. Get the files from the FTP server and copy properties files by running the following command:

cp Server/PanacesServerInstaller.properties /tmp/ cp Server/install.bin /tmp cp Agents/PanacesAgentsInstaller.properties /tmp

2. Open the properties file by using the following command:

§ Server

vi /tmp/PanacesServerInstaller.properties

§ Agents(UNIX)

vi /tmp/PanacesAgentsInstaller.properties

3. Modify the respective properties file for the key words shown in the following tables, to reflect your configuration.

PanacesServerInstaller.properties file: Key word Description

INSTALLER_UI Displays the mode of installation as “silent”.

MODIFY_SYSTEM_FILES=1 It modifies system files, i.e. /etc/hosts,/etc/sysconfig/selinux, /etc/sysctl.conf

KEYSTORE_FILE_PATH Add the keystore path.

For example: /opt/panaces/installconfig/keystore/IBM.keystore

USER_INSTALL_DIR Enter the default path for the directory to install the

IBM Resiliency Orchestration Server software.(default path is /opt/panaces/ )

REFRESH_EXISTING_SCHEMA

When the Schema Refresh option is chosen, the old schema which is already available in the system will be refreshed.Default is 0, if set to 0 the schema will not be refreshed and when set to 1 schema will be

refreshed/reset.



Key word Description

STOP_IBMRESILIENCY ORCHESTRATION_AND_UNINSTAL

L

If set to 1, it will stop the running services and uninstall.

If set to 0, the services will be running and the uninstaller will quit. The logs will be available in the

\temp directory.

MYSQL_ROOT_PASSWORD

Enter the password to connect to the MYSQL database.

Note: If password is not present, keep the field empty.

USER_MANAGEMENT_MODE Basic

ADVANCED

ADVANCED_SERVER_TYPE NA LDAP or AD Default: AD

ADVANCED_SERVER_URL NA Enter the Advanced Server URL of AD/ LDAP Server

ADVANCED_SERVER_DOMAIN NA

The Server Domain is applicable only to AD.

Note: we should not enter domain for LDAP

DIRECTORY_USERNAME NA Enter the User name for reading the external system for AD/LDAP server.

DIRECTORY_PASSWORD NA Enter the Password for reading the external system for AD/ LDAP server.

SEARCH_BASE_FOR_READING_ROLES NA Enter the searchbase string for AD/

LDAP server.

EULA_ACCEPTED Enter the value “Yes” Otherwise the Installation will display an error message as EULA is not accepted.

SUPPORT_USER_PASSWORD Enter the password for support user(default

=Resiliency Orchestrationsupport123$).

TOMCAT_HOME Enter the Tomcat Installation directory path.

PanacesAgentsInstaller.properties file: Keyword Description

INSTALLER_UI Displays the mode of installation as “silent”. MSSQL_AGENT_WINDOWS_CHK IBM File replicator _AGENT_CHK

SYBASE_AGENT_SOL_CHK SRS_AGENT_CHK

ORACLE_AGENT_CHK ORACLE_DATA_GUARD_AGENT_C

HK TRUE_COPY_AGENT_CHK

SRDF_AGENT_CHK HPXP_AGENT_CHK DB2_AGENT_CHK

POSTGRES_AGENT_CHK

Enter 1 to install the agent. Enter 0 to not install the agent.



Keyword Description

USER_INPUT_RESULT_JAR_MSSQL

Enter the full path of the directory where the MSSQL Jar files have been installed.

For example: On Windows, the location of the Jar files would be C:\Program Files\Microsoft SQL Server 2000 or 2005 Driver for JDBC\lib

USER_INPUT_ORACLE_HOME Enter the full path of the directory where the Oracle is installed.

USER_INPUT_RESULT_JAR_ORA Enter the full path of the directory where the

Oracle Jar files have been installed. Usually it is $ORACLE_HOME/jdbc/lib

USER_INPUT_RESULT_JLIB_ORA Enter the full path of directory where jar libraray

files are located. Usually it is $ORACLE_HOME/jlib

USER_INPUT_RESULT_JAR_SYBASE

Enter the full path of the directory where the Sybase Jar files have been installed. For example: <sybase installation

path>/jConnect-5_5/classes. USER_INPUT_RESULT_SYBASE_LO

GIN Enter the Sybase Admin login ID.

USER_INPUT_RESULT_PRIMARY_PANACES_SERVER_IP Enter the IP address of the primary server.

USER_INPUT_RESULT_SECONDARY_PANACES_SERVER_IP Enter the IP address of the secondary server.

PANACES_AGENT_NODE_ADDRESS Enter the IP address of IBM Resiliency Orchestration Agent.

REG_PANACES_CLASSPATH

Displays the IBM Resiliency Orchestration classpath. By default, the following classpath is

displyed: lax.nl.env.PANACES_CLASSPATH

USER_INPUT_RESULT_DB2DIR Enter DB2 installation path USER_INPUT_RESULT_DB2_INSTAN

CEUSER Enter DB2 instance username

USER_INSTALL_DIR The full pathname for the directory in which you want to install the agent software.

AGENTS_START_YES

Enter 1 if you want to start the agents automatically after the IBM Resiliency

Orchestration installation. Enter 0 if you want to start the agents manually. Refer to the Starting and Stopping of Agents in the respective Installation of Agents chapter in

this guide for more information. USER_INPUT_RESULT_POSTGRES_L

OGIN By default, "postgres" will be pre-filled as the

login ID. USER_INPUT_RESULT_NAT_IP NAT IP Address

USER_INPUT_RESULT_SITE_CONTROLLER_IP Enter Site Controller IP address.

CHOSEN_INSTALL_SET=

Enter Upgrade Note: This is used only during Upgrade

4. Execute the following command to start the installation.

/tmp/install.bin –f /tmp/PanacesServerInstaller.properties



5. Follow the Post Installation Steps.

Note:

Restart the Resiliency Orchestration Server after updating the parameters in the above table

Resiliency Orchestration Agent Server Silent Mode Installation

The following section provides steps to install the software by silent mode on Windows, Linux, Solaris, HPUX and AIX servers.

Note

In silent mode, uninstallation does not check whether services are running or not. The user has to make sure that services are stopped before uninstallation in silent mode.

Starting Silent Mode Installation on Windows System

Perform the following steps to install IBM Resiliency Orchestration on Windows system.

1. Log on to Windows system.

2. Open an MS-DOS command prompt window.

3. Go to the directory that contains the installation file and launch the installation procedure by entering the following command:

install.exe –f <complete path of the .properties file with the properties file name>

For example: install.exe -f c:\\Progra~1\\panaces\\PanacesAgentsInstaller.properties

Note After completing the installation of Agents on Windows Server, no status is displayed. The user does not get information on whether the installation is successful or not.

Starting Silent Mode Installation on Solaris/Linux/HPUX/AIX Servers

1. Log on to Linux/Solaris/HPUX/AIX system.



./install.bin –f <complete path of the .properties file with the properties file name>

For example: For agents ./install.bin –f /Agents/ PanacesAgentsInstaller.properties and for Server, ./install.bin –f /Server/ PanacesServerInstaller.properties

Note



You have to manually start IBM Resiliency Orchestration Server after installing IBM Resiliency Orchestration. Refer to Starting and Stopping Resiliency Orchestration Server for more information.

Vault Configuration:

If you want to use Vault make the following changes before starting Resiliency Orchestration Service. Note: Re-start Resiliency Orchestration if Resiliency Orchestration is already started after the following changes.

1. Set parameter IS_SERIALCALL_ENABLED=TRUE in <EAMSROOT>/installconfig/PanacesAgentGeneric.cfg. By default it is false. Make the changes for both PanacesAgentGeneric.cfg (Agent) and panaces.properties (Panaces services)..

2. Set parameter IBM.vault.agent.onstartup = TRUE in <EAMSROOT>/installconfig/panaces.properties. By default it is false.

For more information on Vault Configuration go to IBM Resiliency Orchestration Online Help and navigate to Home> Configuration> Vault Framework or refer to the admin guide.



15. Upgrading Resiliency Orchestration Server

Resiliency Orchestration Server Upgrade

Prerequisites:

• The IBM Resiliency Orchestration 7.1 release upgrade on Resiliency Orchestration Server can be done on IBM RESILIENCY ORCHESTRATION 6.3 SP4.

• Upgrade should be performed only when all the groups are in "Normal Inactive" or "Normal Reset" state. No operations/workflows should be executing. If NormalCopy/ FailOver/ SwitchOver/ SwitchBack or any Business Process/Test/Policy is in progress, it should be completed, stopped or aborted so that the group can be moved to Normal Inactive state.

• Ports 8081 to 8083 and 80 should be opened between the RESILIENCY ORCHESTRATION Server and the associated agents bidirectionally. Refer to open ports by rootuser On RESILIENCY ORCHESTRATION machine:.

Note 1 Discovered VCenter and AWS management service in 6.3 SP4 cannot be used for the VM protection solution. If required, we need to re-discover after the upgrade to 7.1.

Note 2

Do not use "Change continuity" option to move the group to "Normal Inactive" or Normal Reset".

§ Move all the groups to Normal INACTIVE mode.

§ If Server is configured with Linux OS agent, it has to be stopped.

§ If MySQL replication is also set up, it should also be stopped.

Steps: • Step 1: Stop IBM RESILIENCY ORCHESTRATION Server Services by using the

following command:

$EAMSROOT/bin/panaces stop

• Step 2: Stop all remote agents before upgrade by using the following command: $EAMSROOT/bin/RESILIENCY ORCHESTRATIONAgentsStop.sh ALL

• Step 3: Perform backup of IBM Resiliency Orchestration software and configuration files.



It is highly recommended to take a backup of the existing installation before proceeding with the upgrade. Refer to Backup and Fallback Plan section of this manual for details on files to back up.

Upgrading Resiliency Orchestration Server in GUI mode

Perform the following steps for upgrading IBM Resiliency Orchestration server. The commands specified in the following points must be provided at the command prompt:


2. IBM Resiliency Orchestration Server can be upgraded only if you login as a Root user. Execute the following command: (Use whichever is applicable)


Note


3. After extracting the files from install bin, IBM Resiliency Orchestration Server upgrade starts with the following screen.

Figure 111: IBM Resiliency Orchestration Installer

4. After displaying the IBM Resiliency Orchestration Installer screen, the MySQL root password window is displayed.



Figure 112: IBM Resiliency Orchestration Server Upgrade - MySQL root password

5. Enter MySQL root user password and click Next. The Tomcat Home window is displayed.

Figure 113: IBM Resiliency Orchestration Server Upgrade - Tomcat Home

6. Click Choose… to browse and select the location of Tomcat. When Tomcat is located and then selected, the path appears in the Please Choose a Folder: box in Tomcat Home screen. Click Next, the Introduction window is displayed.



Figure 114: IBM Resiliency Orchestration Server Upgrade - Introduction

7. Click Next. The License Agreement window is displayed

Figure 115: IBM Resiliency Orchestration Server Upgrade - License Agreement

8. Click the appropriate option button after perusal of the License Agreement. The options are:



Option Button Description I accept the terms of the

License Agreement Click this option button for acceptance of the License

Agreement.

I do NOT accept the terms of the License Agreement

Click this option button for rejection of the License Agreement. By default, this is selected.

The Next button is unavailable with this option.

9. Click Next (on acceptance of the License Agreement window) to proceed with the installation. The Choose Install Folder window is displayed.

Figure 116: IBM Resiliency Orchestration Server Upgrade - Choose Install Folder

10. Select a path to install the software by clicking Choose. Choose the path where the Resiliency Orchestration is currently installed.

Note

The 7.1 will be installed in the same path by renaming the existing installation folder by appending the release name. For example, if 7.1 is installed in /opt/panaces then the folder will be renamed to /opt/panaces_6.3_SP4 containing the old installation, while /opt/panaces will be installed with 7.1.

11. Click Next to continue.

12. The Choose Install Set window is displayed. The Choose Install Set screen will be displayed only when the user selects the install location same as the current one. Select Upgrade icon.



Figure 117: IBM Resiliency Orchestration Server Upgrade - Choose Install Set

Note

§ User can upgrade from 6.3 SP4 to 7.1.

§ If Typical is selected and IBM Resiliency Orchestration Server version 6.3 SP4 is present in

the system, then the following error is displayed. Click Quit Installation to cancel the upgrade process.

The IBM Resiliency Orchestration Server version 6.3_FinalBuild10March34218 is already installed in this machine. Installer cannot overwrite the existing installation. Please use upgrade option to upgrade the server to version 7.1 or try installing in different location. The installer will quit now.

13. Click Next. The Pre-Installation Summary window is displayed.



Figure 118: IBM Resiliency Orchestration Server Upgrade - Pre-Installation Summary


15. Click Install. The Installing IBM Resiliency Orchestration Server window is displayed.

Note By now, the older installation folder has been renamed by appending the release name. So if the installation is cancelled then the older installation folder has to be renamed to original folder by the user as part of the fallback plan. For example, if 7.1 is installed in /opt/panaces then the folder will be renamed to /opt/panaces_. If the upgrade is canceled any further, user has to rename /opt/panaces_folder to /opt/panaces to restart upgrade or to use the older version of the product.



Figure 119: IBM Resiliency Orchestration Server Upgrade - Installing IBM Resiliency Orchestration Server

16. Existing metadata will be backed up. If an unexpected error occurs while updating MySQL metadata, sometimes the error message thrown will be too long. The user will not be able to see the complete message since scroll bar is not available. The OK button also will not be visible for the user to click and proceed. In this situation, press the space bar to proceed.

Figure 120: IBM Resiliency Orchestration Server Upgrade - Backing up the Metadata

17. The upgrade process of the metadata scheme to 7.1 is displayed.



Figure 121: IBM Resiliency Orchestration Server Upgrade - Upgrade of the Metadata Scheme

18. Once the installation is complete, the Upgrade Complete window is displayed indicating successful upgrade.

Figure 122: IBM Resiliency Orchestration Server Upgrade - Upgrade Complete

19. Click Done to complete the upgrade process.



License Management

Note:

If there is a change in the Licenses, perform the following steps.

1. Upload the license. [This requires the Resiliency Orchestration Server to be running] 2. Execute $EAMSROOT/bin/licenseUpgrade.sh 3. Errors during the process, if any, will be displayed on the console window.

Post Upgrade tasks

Since the mount TCL scripts are modified, the agents using the TCL scripts (HPXP solution) must also be upgraded when the Resiliency Orchestration Server is upgraded, else the mount operations will fail.

After the successful upgrade of the server, the user should clear the browser cache for the GUI changes to take effect completely.

The comparison between previous roles and new role definitions in Basic User Management are given as follows:

The OPERATOR has READ privileges for all the pages including Admin tab. The ADMINISTRATOR can change their own User Management information and cannot edit or view for other users. SUPER ADMINISTRATOR has all the privileges as in the previous releases.

NOTIFICATION MEMBER wherein it will not be allowed to login into the system. SUPPORT USER will now be able to modify his own password on login. This was not supported in the previous releases. support user will be present and function as in the previous releases. The user will not be listed to other users who are logged into the system. When support logs in, he/she will be able to view the user in the User Listing page and will be able to edit their own password and Home page preference. For customers who are upgrading also the new user name will be reflected. Existing password will not be changed on upgrade. Resiliency Orchestrationadmin user will not be allowed to be deleted by other users with SUPER ADMINISTRATOR role. Only newly created users with SUPER ADMINISTRATOR role can be deleted.

The user name field can accept maximum upto 64 characters. The same will be reflected in the UI in login page and create/edit user page.

If HA is available then

• Uninstall on Slave Resiliency Orchestration Server

• Install on Slave Resiliency Orchestration Server. Do not refresh the schema/DB during installation. Do not start Resiliency Orchestration Services on Slave Server.



• Restart MySQL Replication.

• Restore required custom workflows/scripts from the backup.

• Start up IBM Resiliency Orchestration server services

Server Memory Management

Depending on the expected number of groups that will be supported by IBM Resiliency Orchestration Software, Java maximum heap memory limit parameter needs to be specified. It is defined in the variable named RESILIENCY ORCHESTRATION_SERVER_JVM_MEM which is located at starting lines of the RESILIENCY ORCHESTRATION startup script RESILIENCY ORCHESTRATION Install root/bin/panaces. Default value of this variable is set to –Xmx2048m. Following are the recommended values:

§ Configuration with more than 100 groups: -Xmx4072m is recommended.

Backup and Fallback Plan

Backup Plan

Take the backup of the following files and directories - 1. IBM Server Mysql Metadata

mysqldump -u root --databases panaces pfr advancedreporter -R --triggers > backupfilename.sql

2. IBM Server Installation directory $EAMSROOT 3. The following system files:

i) sysctl.conf ii) any user specific scripts and cron jobentries iii) /etc/hosts

4. User files 5. If Resiliency Orchestration Server is configured with Linux OS agent:

§ Agent Binaries

§ Custom/Field Specific scripts

Fallback Plan

At any time of the upgrade, if there are failures that cannot be corrected within the upgrade window, use the following plan to restore to the old IBM server installation.

1. Drop the existing databases if they already exist a. mysqladmin –u root drop panaces b. mysqladmin –u root drop pfr c. mysqladmin –u root drop advancedreporter

2. Restore the MySQL Metadata from backup. mysql -u root < backupfilename.sql

3. Restore the IBM Server software installation directory (7.1). 4. Startup IBM Server Services.



16. Upgrading Resiliency Orchestration

Advanced Reporter

Upgrading IBM Resiliency Orchestration Advanced Reporter is similar to fresh Installation of Advanced Reporter. Refer to chapter, Installing IBM Advanced Reporter for instructions. However, during the upgrade process user will be prompted whether to refresh the existing advanced reporter metadata as shown below. User should select “No” to retain the metadata and to upgrade only the binaries of advanced reporter.

Figure 123: Upgrade IBM Resiliency Orchestration Advance Reporter - Metadata refresh screen for

Advanced Reporter



17.Upgrading Resiliency Orchestration

Agents

Resiliency Orchestration Agent Upgrade [Optional]

The upgrade of agents on customer servers may be done any time after the IBM Resiliency Orchestration server software is upgraded. Refer the respective agent upgrade chapters for upgrading the agents from the older version to 7.1 version. After the agent upgrade, all new workflows or the new actions that got defined in field or bundled with 7.1 releases will work. Note

Upgrading the agents will retain the existing workflow configuration files in the $EAMSROOT/work directory to maintain backward compatibility. If new workflows from the current version are loaded, it may not work with the existing workflow configuration files. A fresh copy of the configuration file must be copied from $EAMSROOT/scripts/repository/workflow-config directory to the work directory and must be configured to be used by the workflow.

Prerequisites:

• All the agents should be stopped before performing any agent upgrade process.

• Kill rsync.exe processes started by Panaces agents (PFR) if any.

Steps:

• Step 1: For each identified Functional Group, move the Group to maintenance mode.

• Step 2: Upgrade the agent software on all servers using Agent installer 7.1.



18. Upgrading Agents on Windows Server

Pre-requisites before upgrading Agents on Windows Server

§ Stop all the agents.


§ Disable the antivirus if installed or configured before upgrade.

Limitations

§ Agents should be upgraded first and then RESILIENCY FILE REPLICATOR is upgraded, when RESILIENCY FILE REPLICATOR is installed with agents.

§ During upgrade, use old EAMSROOT as installation path.

Upgrading Agents on Windows Server in GUI mode

Perform the following steps for upgrading the Windows server.

To upgrade the agents, perform the following steps:

1. Download the agent binaries from the given ftp path

2. Browse through IBM Resiliency Orchestration software from the downloaded path and go to the folder to the folder Agent/Windows_RESILIENCY ORCHESTRATIONAgent_7.1.zip for 32-bit Linux Operating Systems or Agents/Windows64_RESILIENCY ORCHESTRATIONAgent_7.1.zip for 64-bit Linux Operating Systems.

3. Goto the extracted folder and double click install.exe

Note

Make sure that you have free space of approximately 700 MB in temp directory, before executing the above command.

4. After executing the command, IBM Resiliency Orchestration Agent installation starts with the following screen.




5. After displaying the IBM Resiliency Orchestration Agent Installer screen, the Introduction window is displayed.

Figure 125: Upgrade Agents on Windows Server - Introduction

6. Go through the installation procedure and click Next. The Choose Install Folder window is displayed.



Figure 126: Upgrade Agents on Windows Server - Choose Install Folder

7. Select a path to install the software by clicking Choose. Alternatively, you can click Restore Default Folder to restore the default path. The default path is C:\Program Files\panaces. It is recommended that you use the default path. This needs to be the same as that of the previous agent installation.

8. Click Next. The Choose Install Set window is displayed. Select the Upgrade option and click Next.

Note

User can upgrade from older version to 7.1

The Choose Install Set screen will be displayed only when the user selects the same install location as the current one.



Figure 127: Upgrade Agents on Windows Server - Choose Install Set

Note

An error message is generated as shown in the following figure, if the agents are running during installation.

Figure 128: Upgrade Agents on Windows Server - Agents Running Error Message

9. Click Quit Installation. Stop all the Agents that are running and perform the steps to upgrade the Windows Server.

10. The Choose Agents - Windows window is displayed.



Figure 129: Upgrade Agents on Windows Server - Choose Agents - Windows

11. The list of agents available is displayed on the Choose Agents - Windows window. Select the checkbox next to the specific agent to install that agent. You can choose to install any or all of the agents.

12. Click Next. The Choose Shortcut Folder window is displayed.

Figure 130: Upgrade Agents on Windows Server - Choose Shortcut Folder

Note



During installation, if In a new Program Group option is selected and if no name is given for the program group, the option will be ignored and shortcuts will not be created. Please make sure that the selected path has all the JDBC driver jar files.

13. Select an option to create a product icon in the required location. For example, select Other option button to create a product icon in a specific path, or select Don’t create icons button to avoid creating shortcut folders.

14. Click Next. The Agent Configuration - JDBC window is displayed.

Figure 131: Upgrade Agents on Windows Server - Agent Configuration

15. Depending on the agent you have selected for installation, perform the steps:

§ MSSQL Agent

Enter MSSQL JDBC driver jar file location. Click Choose button to select the jar file location.

16. Click Next. The NAT IP Address Configuration window is displayed.



Figure 132: Upgrade Agents on Windows Server – NAT IP Address Configuration

17. Enter the NAT IP Address if applicable. And click Next. The Site Controller Configuration window is displayed.

Figure 133: Upgrade Agents on Windows Server – Site Controller Configuration

18. Enter the Site Controller IP Address if applicable. And click Next. The Pre-Installation Summary window is displayed



Figure 134: Upgrade Agents on Windows Server - Pre-Installation Summary


20. Click Install. The Installing IBM Resiliency Orchestration Agents window is displayed.

Figure 135: Upgrade Agents on Windows Server - Installing IBM Resiliency Orchestration Agents

20. Once the installation is complete, the Starting Agents window is displayed.



Figure 136: Upgrade Agents on Windows Server - Starting Agents

21. On the Starting Agents window, perform either of the following:



Note The best practice is not to change the default value displayed on the Starting Agents window.

Restart the agent machine, if the agents do not start after agent installation is complete.

22. Click Next. The Upgrade Complete window is displayed, indicating successful upgrade.



Figure 137: Upgrade Agents on Windows Server - Upgrade Complete




19. Upgrading Agents on Solaris Server

Pre-requisites before upgrading agents on Solaris Server



Limitations

• Agents should be upgraded first and then RESILIENCY FILE REPLICATOR is upgraded, when RESILIENCY FILE REPLICATOR is installed with agents.

• During upgrade, use old EAMSROOT as installation path.

Upgrading Agents on Solaris Server in GUI mode

Perform the following steps for upgrading the agents on Solaris server. The commands specified in the following points must be provided at the command prompt:



2. Browse through IBM Resiliency Orchestration software from the downloaded path and go to the folder to the folder Agent/SolarisIntel_RESILIENCY ORCHESTRATIONAgent_7.1.zip for Intel architecture and Agent/SolarisSparc_RESILIENCY ORCHESTRATIONAgent_7.1.zip for Sparc architecture.



Note







Figure 139: Upgrade Agents on Solaris Server - Introduction




Figure 140: Upgrade Agents on Solaris Server - Choose Install Folder

7. Select a path to install the software by clicking Choose. Alternatively, you can click Restore Default Folder to restore the default path. The default path is /opt/panaces. It is recommended that you use the default path. This needs to be the same as that of the previous agent installation.


Note

1. User can upgrade from older version to 7.1 2. The Choose Install Set screen will be displayed only when the user selects the same install

location as the current one.



Figure 141: Upgrade Agents on Solaris Server - Choose Install Set

9. The Choose Agents - Solaris window is displayed.

Figure 142: Upgrade Agents on Solaris Server - Choose Agents - Solaris

10. The list of agents available is displayed on the Choose Agents - Solaris window. Select the checkbox next to the specific agent to install that agent. You can choose to install any or all of the agents.

11. Click Next. The Choose Link Folder window is displayed.



Figure 143: Upgrade Agents on Solaris Server - Choose Link Folder

12. Choose a path for creating links in the Choose Link Folder window.







Figure 144: Upgrade Agents on Solaris Server – NAT IP Address Configuration


Figure 145: Upgrade Agents on Solaris Server – Site Controller Configuration




Figure 146: Upgrade Agents on Solaris Server - Pre-Installation Summary



Figure 147: Upgrade Agents on Solaris Server - Installing IBM Resiliency Orchestration Agents




Figure 148: Upgrade Agents on Solaris Server - Starting Agents









Figure 149: Upgrade Agents on Solaris Server - Upgrade Complete




20. Upgrading Agents on Linux Server

Pre-requisites before upgrading agents on Linux Server



Limitations



Upgrading Agents on Linux Server in GUI mode

Perform the following steps for upgrading the agents on Linux server. The commands specified in the following points must be provided at the command prompt:



2. Browse through IBM Resiliency Orchestration software from the downloaded path and go to the folder to the folder Agent/Linux_RESILIENCY ORCHESTRATIONAgent_7.1.zip for 32-bit Linux Operating Systems or Agents/ Linux64_RESILIENCY ORCHESTRATIONAgent_7.1.zip for 64-bit Linux Operating Systems.



Note







Figure 151: Upgrade Agents on Linux Server - Introduction




Figure 152: Upgrade Agents on Linux Server - Choose Install Folder


8. Click Next. The Choose Install Set window is displayed. Select the Upgrade option and click Next

Note

1. User can upgrade from older version to 7.1

2. The Choose Install Set screen will be displayed only when the user selects the same install location as the current one.



Figure 153: Upgrade Agents on Linux Server - Choose Install Set

9. The Choose Agents - Linux window is displayed.

Figure 154: Upgrade Agents on Linux Server - Choose Agents - Linux

10. The list of agents available is displayed on the Choose Agents - Linux window. Select the checkbox next to the specific agent to install that agent. You can choose to install any or all of the agents.




Figure 155: Upgrade Agents on Linux Server - Choose Link Folder





13. Click Next. The Agent Configuration window is displayed.



Figure 156: Upgrade Agents on Linux Server - Agent Configuration

14. Enter DB2 instance user login ID and click Next.

Figure 157: Upgrade Agents on Linux Server - Agent Configuration

15. Enter the DB2 file location. Click the Choose button to select the jar file location. Click Next. The NAT IP Address Configuration window is displayed.



Figure 158: Upgrade Agents on Linux Server – NAT IP Address Configuration


Figure 159: Upgrade Agents on Linux Server – Site Controller Configuration




Figure 160: Upgrade Agents on Linux Server - Pre-Installation Summary



Figure 161: Upgrade Agents on Linux Server - Installing IBM Resiliency Orchestration Agents




Figure 162: Upgrade Agents on Linux Server - Starting Agents









Figure 163: Upgrade Agents on Linux Server - Upgrade Complete




21. Upgrading Agents on HPUX Server

Pre-requisites before upgrading agents on HPUX Server



Limitations



Upgrading Agents on HPUX Server in GUI mode

Perform the following steps for upgrading the agents on HPUX server. The commands specified in the following points must be provided at the command prompt:



2. Browse through IBM Resiliency Orchestration software from the downloaded path and go to the folder to the folder Agent/HPUX_RESILIENCY ORCHESTRATIONAgent_7.1.zip.



Note







Figure 165: Upgrade Agents on HPUX Server - Introduction




Figure 166: Upgrade Agents on HPUX Server - Choose Install Folder



Note

1. User can upgrade from older version to 7.1




Figure 167: Upgrade Agents on HPUX Server - Choose Install Set

9. The Choose Agents - HPUX window is displayed.

Figure 168: Upgrade Agents on HPUX Server - Choose Agents - HPUX

10. The list of agents available is displayed on the Choose Agents - HPUX window. Select the checkbox next to the specific agent to install that agent. You can choose to install any or all of the agents.




Figure 169: Upgrade Agents on HPUX Server - Choose Link Folder








Figure 170: Upgrade Agents on HPUX Server – NAT IP Address Configuration


Figure 171: Upgrade Agents on HPUX Server – Site Controller Configuration




Figure 172: Upgrade Agents on HPUX Server - Pre-Installation Summary





Figure 173 Upgrade Agents on HPUX Server - Installing IBM Resiliency Orchestration Agents


Figure 174: Upgrade Agents on HPUX Server - Starting Agents









Figure 175: Upgrade Agents on HPUX Server - Upgrade Complete




22. Upgrading Agents on AIX Server

Pre-requisites before upgrading agents on AIX Server



Limitations



Upgrading Agents on AIX Server in GUI mode

Perform the following steps for upgrading the agents on AIX server. The commands specified in the following points must be provided at the command prompt:



2. Browse through IBM Resiliency Orchestration software from the downloaded path and go to the folder to the folder Agent/AIX_RESILIENCY ORCHESTRATIONAgent_7.1.zip.



Note







Figure 177: Upgrade Agents on AIX Server - Introduction




Figure 178: Upgrade Agents on AIX Server - Choose Install Folder



Note

1. User can upgrade from older to 7.1.




Figure 179: Upgrade Agents on AIX Server - Choose Install Set

9. The Choose Agents - AIX window is displayed.

Figure 180: Upgrade Agents on AIX Server - Choose Agents - AIX

10. The list of agents available is displayed on the Choose Agents - AIX window. Select the checkbox next to the specific agent to install that agent. You can choose to install any or all of the agents.




Figure 181: Upgrade Agents on AIX Server - Choose Link Folder





13. Click Next. The Agent Configuration window is displayed.



Figure 182: Upgrade Agents on AIX Server - Agent Configuration

14. Enter Oracle home directory location. Click the Choose button to select the file location.

15. Click Next. Enter Oracle JDBC driver jar file location. Click the Choose button to select the jar file location.

Note Make sure that the selected path has all the JDBC driver jar files.




16. Click Next. Enter the Oracle Java lib directory location. Click the Choose button to select the file location.



Figure 185: Upgrade Agents on Linux Server – NAT IP Address Configuration





Figure 186: Upgrade Agents on Linux Server - Pre-Installation Summary





Figure 187: Upgrade Agents on Linux Server - Installing IBM Resiliency Orchestration Agents


Figure 188: Upgrade Agents on Linux Server - Starting Agents









Figure 189: Upgrade Agents on Linux Server - Upgrade Complete




23. Upgrading Resiliency Orchestration Agents

Using Silent Mode Installation

Pre-requisites before upgrading agents on AIX Server


Limitations




When you upgrade IBM Resiliency Orchestration Agents in Silent mode, the upgrade program uses the .properties file for agents (PanacesAgentsInstaller.properties), to determine which upgrade options should be implemented. Therefore, before you can run the upgrade program in Silent mode, you must edit the respective properties file in which you specify the i upgrade options that you want to invoke, while performing the IBM Resiliency Orchestration Agents upgrade. Perform the following steps to edit the properties files.

1. Get the files from the FTP server and copy properties files by running the following command::

cp Agents/PanacesAgentsInstaller.properties /tmp

2. Open the properties file by using the following command:

§ Agents(UNIX)

vi /tmp/PanacesAgentsInstaller.properties

3. Modify the respective properties file for the key words shown in the following tables, to reflect your configuration.

PanacesAgentsInstaller.properties file: Keyword Description

INSTALLER_UI Displays the mode of installation as “silent”.



Keyword Description MSSQL_AGENT_WINDOWS_CHK IBM File replicator _AGENT_CHK

SYBASE_AGENT_SOL_CHK SRS_AGENT_CHK

ORACLE_AGENT_CHK ORACLE_DATA_GUARD_AGENT_C

HK TRUE_COPY_AGENT_CHK

SRDF_AGENT_CHK HPXP_AGENT_CHK DB2_AGENT_CHK

POSTGRES_AGENT_CHK

Enter 1 to install the agent. Enter 0 to not install the agent.

USER_INPUT_RESULT_JAR_MSSQL

Enter the full path of the directory where the MSSQL Jar files have been installed.

For example: On Windows, the location of the Jar files would be C:\Program Files\Microsoft SQL Server 2000 or 2005 Driver for JDBC\lib

USER_INPUT_ORACLE_HOME Enter the full path of the directory where the Oracle is installed.

USER_INPUT_RESULT_JAR_ORA Enter the full path of the directory where the

Oracle Jar files have been installed. Usually it is $ORACLE_HOME/jdbc/lib

USER_INPUT_RESULT_JLIB_ORA Enter the full path of directory where jar library

files are located. Usually it is $ORACLE_HOME/jlib

USER_INPUT_RESULT_JAR_SYBASE

Enter the full path of the directory where the Sybase Jar files have been installed. For example: <sybase installation

path>/jConnect-5_5/classes. USER_INPUT_RESULT_SYBASE_LO

GIN Enter the Sybase Admin login ID.

USER_INPUT_RESULT_PRIMARY_PANACES_SERVER_IP Enter the IP address of the primary server.

USER_INPUT_RESULT_SECONDARY_PANACES_SERVER_IP Enter the IP address of the secondary server.

PANACES_AGENT_NODE_ADDRESS Enter the IP address of IBM Resiliency Orchestration Agent.

REG_PANACES_CLASSPATH

Displays the IBM Resiliency Orchestration classpath. By default, the following classpath is

displayed: lax.nl.env.PANACES_CLASSPATH

USER_INPUT_RESULT_DB2DIR Enter DB2 installation path USER_INPUT_RESULT_DB2_INSTAN

CEUSER Enter DB2 instance username

USER_INSTALL_DIR The full pathname for the directory in which you want to install the agent software.

AGENTS_START_YES

Enter 1 if you want to start the agents automatically after the IBM Resiliency

Orchestration installation. Enter 0 if you want to start the agents manually. Refer to the Starting and Stopping of Agents in the respective Installation of Agents chapter in

this guide for more information.



Keyword Description USER_INPUT_RESULT_POSTGRES_L

OGIN By default, "postgres" will be pre-filled as the

login ID. USER_INPUT_RESULT_NAT_IP NAT IP Address

USER_INPUT_RESULT_SITE_CONTROLLER_IP Enter Site Controller IP address.

CHOSEN_INSTALL_SET=

Enter Upgrade Note: This is used only during Upgrade

Starting Silent Mode Upgrade on Windows System

Perform the following steps to install IBM Resiliency Orchestration on Windows system.

1. Log on to Windows system.

2. Open an MS-DOS command prompt window.

3. Go to the directory that contains the installation file and launch the installation procedure by entering the following command:

install.exe –f <complete path of the .properties file with the properties file name>

For example: install.exe -f c:\\Progra~1\\panaces\\PanacesAgentsInstaller.properties

Note

After completing the installation of Agents on Windows Server, no status is displayed. The user does not get information on whether the installation is successful or not.

Starting Silent Mode Installation on Solaris/Linux/HPUX/AIX Servers

1. Log on to Linux/Solaris/HPUX/AIX system.



./install.bin –f <complete path of the .properties file with the properties file name>

For example: For agents ./install.bin –f /Agents/ PanacesAgentsInstaller.properties



24. Upgrading Vault to Vault Customers who have already configured Vault need to follow the steps in this section.

Pre-requisites

1. Vault must be configured in 6.3 SP4. i. Step 1 :

Update Resiliency Orchestration configuration by updating the panaces.properties file by setting the following value. This will enable the vault simulator.IBM.vault.simulator = 1

ii. Step 2: In 6.3 SP4 we have to add query parameters in MySQL database for the subsystem in Resiliency Orchestration DB by using following query: Syntax : insert into vault_IBM_db(sysname,accname,password) values(<"sysname">,<" accname">, <"password">); Example: insert into vault_IBM_db(sysname,accname,password) values("sys","acc","IBM543"); Note Ensure that the command syntax, system name, account name and password are correct for the subsystem.

2. Vault queries must be executed on the Resiliency Orchestration Database. The queries will be

in the form of query parameters and passwords. 3. Vault must be configured in Resiliency Orchestration GUI. 4. Subsystems must be updated/ configured with Vault.

Vault to Vault Upgrade Steps

• Stop 6.3 SP4 RESILIENCY ORCHESTRATION server.

• Copy the script 'VaultToVaultUpgradeUtilitySP4.sh' (ftp server) to $EAMSROOT/bin

Copy the jar 'VaultToVaultUpgradeSP4.jar' (ftp server) to $EAMSROOT/lib

Open the script 'VaultToVaultUpgradeUtilitySP4.sh' and modify the variable 'RESILIENCY ORCHESTRATIONDIR' to the appropriate EAMSROOT

cd $EAMSROOT/bin and execute 'VaultToVaultUpgradeUtilitySP4.sh'

Upgrade the server from '6.3 SP4 to 7.1' using the upgrade installer



Copy the scripts 'VaultToVaultUpgrade.sh' , 'VaultToVaultUpgradeUtility.sh' and 'VaultUpgradeUtility.sh'(ftp server) to $EAMSROOT/bin

Copy the jar 'VaultToVaultUpgrade.jar' (ftp server) to $EAMSROOT/lib

cd $EAMSROOT/bin and execute 'VaultToVaultUpgrade.sh'

Modify Vault configuration files at the backend. The backend Vault configuration folder structure will be available by default after 6.3 SP4 to 7.1 upgrade.

11. Start RESILIENCY ORCHESTRATION server.

Steps to Apply patch.

7.1_35095 TO 7.1_GA

• Take a backup of $EAMSROOT and $TOMCAT_HOME/webapps, go to webapps folder and Delete PanacesGUI directory by rm –rf PanacesGUI

Take a backup of mysql db schema, mysqldump -u root --databases panaces pfr advancedreporter –R --triggers > panaces_dump.sql

Download 7.1_P1 patch files from FTP server.

• Server.tar to be downloaded to $EAMSROOT

• Tomcat.tar to be downloaed to $TOMCAT_HOME/webapps/

cd $EAMSROOT and untar Server.tar (tar –xvf Server.tar)

cd $TOMCAT_HOME/webapps/ and untar tomcat.tar (tar –xvf Tomcat.tar)

cd $EAMSROOT/lib and run this command:

mysql -u root panaces< mysql_schema_7.1_7.1P1.sql.


25. Upgrading Non Vault to Vault Customers who do not have Vault configured till IBM Resiliency Orchestration Version 7.1_35095 need to follow the steps in this section.

Steps to Apply patch

7.1_35095 TO 7.1_GA

• Take a backup of $EAMSROOT and $TOMCAT_HOME/webapps, go to webapps folder and Delete PanacesGUI directory by rm –rf PanacesGUI

Take a backup of mysql db schema, mysqldump -u root --databases panaces pfr advancedreporter –R --triggers > panaces_dump.sql

Download 7.1_P1 patch files from FTP server.


• Tomcat.tar to be downloaed to $TOMCAT_HOME/webapps/

cd $EAMSROOT and untar Server.tar (tar –xvf Server.tar)

cd $TOMCAT_HOME/webapps/ and untar tomcat.tar (tar –xvf Tomcat.tar)

cd $EAMSROOT/lib and run this command:

mysql -u root panaces< mysql_schema_7.1_7.1P1.sql.


26. Upgrading RESILIENCY ORCHESTRATION 7.1 GA to RESILIENCY

ORCHESTRATION 7.1 P2 License Patch Upgrade Procedure for RESILIENCY ORCHESTRATION 7.1 GA to RESILIENCY ORCHESTRATION 7.1 P2 License Patch.

Prerequisites




Based on the features, download the GPL dependent binaries from this link GPL dependent binaries before starting RESILIENCY FILE REPLICATOR and perform the steps mentioned in the chapter, RESILIENCY FILE REPLICATOR Third Party Installation.Refer to GPL License information for more information on GPL licenses. Tar and Rsync Version Details. Platform Tar Version Rsync Version Windows-32/64-Bit tar1.16 rsync3.0.7 Linux-32-Bit RHEL 5.6 tar1.19 rsync3.0.5 Linux-64-Bit RHEL 5.5 rsync3.0.9 Linux-64-Bit RHEL 5.7 rsync3.0.9 Linux-64-Bit RHEL 6.X tar1.23 rsync3.0.9 Linux-64-Bit RHEL 7.X tar1.23 rsync3.0.9 AIX tar1.14 rsync3.0.5 HPUX-64-BIT Itanium tar1.26 rsync3.0.9 HPUX-64-BIT Parisac tar1.26 rsync3.0.9 Solaris_Sparc tar1.18 rsync3.0.5 Solaris_Intel tar1.26 rsync3.0.5



1. Stop the Resiliency Orchestration server from <$EAMSROOT>/bin. 2. Stop all agents.

3. Take a backup of $EAMSROOT and $TOMCAT_HOME/webapps, go to webapps folder and Delete PanacesGUI, PFRGUI, UserPortal directory by rm –rf PanacesGUI PFRGUI UserPortal

4. Download 7.1_P2 patch license files from FTP server.


• Tomcat.tar to be downloaded to $TOMCAT_HOME/webapps/

5. cd $EAMSROOT and untar Server.tar (tar –xvf Server.tar)

6. cd $TOMCAT_HOME/webapps/ and untar tomcat.tar (tar –xvf Tomcat.tar)

7. Execute the following commands in $TOMCAT_HOME/webapps/

• unzip PanacesGUI.war -d PanacesGUI,

• unzip PFRGUI.war -d PFRGUI,

• unzip UserPortal.War -d UserPortal

8. cd $EAMSROOT/bin and run this command:

• sh 7_1_P1_cleanup.sh

9. Download GPL dependent binaries for RESILIENCY ORCHESTRATION, RESILIENCY FILE REPLICATOR, Windows OS Agent and MySQL Agent as applicable. Based on the feature update the following files.

UCSD Feature : EAMSROOT/lib/ucsd-oa-annotations.jar EAMSROOT/lib/ucsd-oa-api.jar EAMSROOT/lib/ucsd-rest-api-sdk-v2.ja EAMSROOT/lib/cuic-sdk-v2-0.jar EAMSROOT/lib/inframgr.jar

Vault: EGUARD EAMSROOT/agents/vault/eguard & EAMSROOT/lib/edmz-par-api.jarEAMSROOT/agents/vault/eguard & EAMSROOT/lib/j2ssh-core-0.2.9.jarCYBERARK EAMSROOT/agents/vault/cyberark & EAMSROOT/lib/ javapasswordsdk.jar


Remote Agent My SQL EAMSROOT/tools/mysql/mysql-connector-java-5.1.20-bin.jar

Local Agent

Windows -32 BIT installedlocation/bin/cyggcc_s-1.dllinstalledlocation/bin/cygiconv-2.dll installedlocation/bin/cygintl-8.dll installedlocation/bin/cygwin1.dll Windows-64-BIT installedlocation/bin/cyggcc_s-1.dll installedlocation/bin/cygiconv-2.dll installedlocation/bin/cygintl-8.dll installedlocation/bin/cygwin1.dll My SQL EAMSROOT/lib/mysql-connector-java-5.1.20-bin.jar

10. Refer to RESILIENCY FILE REPLICATOR Third Party Installation and perform the

RESILIENCY FILE REPLICATOR Third Party Installation depending on the Operating System.


27. RESILIENCY FILE REPLICATOR Third Party Installation

During RESILIENCY FILE REPLICATOR installation, the user can configure the $RESILIENCY FILE REPLICATORROOT path. This is the home directory for IBM File Replicator.

Third Party Binary Installation For Windows-32/64-Bit

Perform the following steps after installing RESILIENCY FILE REPLICATOR. Before deploying the dependent binaries, ensure the RESILIENCY FILE REPLICATOR services are stopped. Note: Download the binaries from the link GPL Dependent binaries in Prerequisites.

1. Go to $RESILIENCY FILE REPLICATORROOT/bin folder by executing the following command.

§ cd $RESILIENCY FILE REPLICATORROOT/bin 2. Download the following files to the same location

§ rsync3.0.7-Windows-32bit.zip 3. Extract rsync3.0.7-Windows-32bit.zip 4. Download the following files to the same location

§ tar1.16-Windows-32bit.zip 5. Extract tar1.16-Windows-32bit.zip

Third Party Binary Installation For Linux-32-Bit

Perform the following steps after installing RESILIENCY FILE REPLICATOR. Before deploying the dependent binaries, ensure the RESILIENCY FILE REPLICATOR services are stopped. Note: Download the binaries from the link GPL Dependent binaries in Prerequisites. RHEL 5.6

1. Go to $RESILIENCY FILE REPLICATORROOT folder by executing the following command.

§ cd $RESILIENCY FILE REPLICATORROOT 2. Download and then Unzip the files by executing following command

§ tar -xvzf rsync3.0.5-RHEL5.6-32bit.tar.gz § tar -xvzf tar1.19-RHEL5.6-32bit.tar.gz

Third Party Binary Installation For Linux-64-Bit



RHEL 5.5



§ tar -xvzf rsync3.0.9-RHEL5.5-64bit.tar.gz 3. Create the following soft link.

§ ln -s $RESILIENCY FILE REPLICATORROOT/bin/tar tar

RHEL 5.7



§ tar -xvzf rsync3.0.9-RHEL5.7-64bit.tar.gz 3. Create the following soft link.

§ ln -s $RESILIENCY FILE REPLICATORROOT/bin/tar tar

RHEL 6.X



§ tar -xvzf rsync3.0.9-RHEL6-64bit.tar.gz § tar -xvzf tar1.23-RHEL6-64bit.tar.gz

RHEL 7.X



§ tar -xvzf rsync3.0.9-RHEL7-64bit.tar.gz § tar -xvzf tar1.23-RHEL7-64bit.tar.gz

Third Party Binary Installation For AIX





§ gunzip rsync3.0.5-AIX.tar.gz § tar -xvf rsync3.0.5-AIX.tar.gz

3. Download and then Unzip the files by executing following command § gunzip tar1.14-AIX.tar.gz § tar -xvf tar1.14-AIX.tar.gz

4. Create the following soft links. § ln -s $RESILIENCY FILE REPLICATORROOT/lib/usr/lib/libiconv.a

/usr/lib/libiconv.a

Third Party Binary Installation For HPUX-64-BIT Itanium


1. Go to a $RESILIENCY FILE REPLICATORROOT folder by executing the following command.

§ cd $RESILIENCY FILE REPLICATORROOT 2. Download and then Unzip/Untar the following files by executing following command

§ gunzip rsync3.0.9-HPUX11.31-IA.tar.gz § tar -xvf rsync3.0.9-HPUX11.31-IA.tar § gunzip tar1.26-HPUX11.31-IA.tar.gz § tar -xvf tar1.26-HPUX11.31-IA.tar

3. Create the following soft links. i. ln -s $RESILIENCY FILE REPLICATORROOT/tool/usr/local/lib/libpopt.so

/usr/lib/hpux32/libpopt.so

Third Party Binary Installation For HPUX-64-BIT Parisac



§ cd $RESILIENCY FILE REPLICATORROOT 2. Download and then Unzip/Untar the following files by executing following command

§ gunzip rsync3.0.9-HPUX11i-PARISC.tar.gz § tar -xvf rsync3.0.9-HPUX11i-PARISC.tar § gunzip tar1.26-HPUX11i-PARISC.tar.gz § tar -xvf tar1.26-HPUX11i-PARISC.tar

3. Create the following soft links.


§ ln -s $RESILIENCY FILE REPLICATORROOT/tool/usr/local/lib/libpopt.so /usr/lib/hpux32/libpopt.so

Third Party Binary Installation For Solaris_Sparc



§ cd $RESILIENCY FILE REPLICATORROOT

2. Download and then Unzip/Untar the following files § tar -xvzf rsync3.0.5-SOLARIS10-SPARC.tar.gz

3. Execute the following command to add the library packages Note: (Note that if the package already installed as part of tar, the other packages only

selected ) § pkgadd -d $RESILIENCY FILE REPLICATORROOT/bin/rsync-3.0.5-

sol10-sparc-local -R $RESILIENCY FILE REPLICATORROOT/tool <<EOF 1 EOF

§ pkgadd -d $RESILIENCY FILE REPLICATORROOT/bin/libiconv-1.11-sol10-sparc-local -R $RESILIENCY FILE REPLICATORROOT/tool <<EOF 1 EOF

§ pkgadd -d $RESILIENCY FILE REPLICATORROOT/bin/libintl-3.4.0-sol10-sparc-local -R $RESILIENCY FILE REPLICATORROOT/tool <<EOF 1 EOF

§ pkgadd -d $RESILIENCY FILE REPLICATORROOT/bin/libgcc-3.4.6-sol10-sparc-local -R $RESILIENCY FILE REPLICATORROOT/tool <<EOF 1 EOF

§ pkgadd -d $RESILIENCY FILE REPLICATORROOT/bin/popt-1.14-sol10-sparc-local -R $RESILIENCY FILE REPLICATORROOT/tool <<EOF 1 EOF

4. Download and then Unzip/Untar the following files

§ tar -xvzf tar1.18-SOLARIS10-SPARC.tar.gz 5. Execute the following command to add the library packages


Note: (Note that if the package already installed as part of rsync, the other packages only selected)

§ pkgadd -d $RESILIENCY FILE REPLICATORROOT/bin/tar-1.18-sol10-sparc-local -R $RESILIENCY FILE REPLICATORROOT/tool <<EOF 1 EOF

§ pkgadd -d $RESILIENCY FILE REPLICATORROOT/bin/libiconv-1.11-sol10-sparc-local -R $RESILIENCY FILE REPLICATORROOT/tool <<EOF 1 EOF

§ pkgadd -d $RESILIENCY FILE REPLICATORROOT/bin/libintl-3.4.0-sol10-sparc-local -R $RESILIENCY FILE REPLICATORROOT/tool <<EOF 1 EOF

§ pkgadd -d $RESILIENCY FILE REPLICATORROOT/bin/libgcc-3.4.6-sol10-sparc-local -R $RESILIENCY FILE REPLICATORROOT/tool <<EOF 1 EOF

6. Create the following soft links. § ln –s $RESILIENCY FILE REPLICATORROOT

/tool/usr/local/lib/libiconv.so.2 § ln –s $RESILIENCY FILE REPLICATORROOT

/tool/usr/local/lib/libgcc_s.so.1

Third Party Binary Installation For Solaris_Intel



§ cd $RESILIENCY FILE REPLICATORROOT

2. Download and then Unzip/Untar the following files § tar -xvzf rsync3.0.5-SOLARIS10-x86.tar.gz

3. Execute the following command to add the library packages Note: (Note that if the package already installed as part of tar, the other packages only

selected ) § pkgadd -d $RESILIENCY FILE REPLICATORROOT/bin/rsync-3.0.5-

sol10-x86-local -R $RESILIENCY FILE REPLICATORROOT/tool <<EOF 1 EOF

§ pkgadd -d $RESILIENCY FILE REPLICATORROOT/bin/libiconv-1.14-sol10-x86-local -R $RESILIENCY FILE REPLICATORROOT/tool <<EOF 1


EOF § pkgadd -d $RESILIENCY FILE REPLICATORROOT/bin/libintl-3.4.0-

sol10-x86-local -R $RESILIENCY FILE REPLICATORROOT/tool <<EOF 1 EOF

§ pkgadd -d $RESILIENCY FILE REPLICATORROOT/bin/libgcc-3.4.6-sol10-x86-local -R $RESILIENCY FILE REPLICATORROOT/tool <<EOF 1 EOF

§ pkgadd -d $RESILIENCY FILE REPLICATORROOT/bin/popt-1.16-sol10-x86-local -R $RESILIENCY FILE REPLICATORROOT/tool <<EOF 1 EOF

4. Download and then Unzip/Untar the following files § tar -xvzf tar1.26-SOLARIS10-x86.tar.gz

5. Execute the following command to add the library packages Note: (Note that if the package already installed as part of rsync, the other packages only

selected.) § pkgadd -d $RESILIENCY FILE REPLICATORROOT/bin/tar-1.26-sol10-

x86-local -R $RESILIENCY FILE REPLICATORROOT/tool <<EOF 1 EOF

§ pkgadd -d $RESILIENCY FILE REPLICATORROOT/bin/libiconv-1.14-sol10-x86-local -R $RESILIENCY FILE REPLICATORROOT/tool <<EOF 1 EOF

§ pkgadd -d $RESILIENCY FILE REPLICATORROOT/bin/libintl-3.4.0-sol10-x86-local -R $RESILIENCY FILE REPLICATORROOT/tool <<EOF 1 EOF

§ pkgadd -d $RESILIENCY FILE REPLICATORROOT/bin/libgcc-3.4.6-sol10-x86-local -R $RESILIENCY FILE REPLICATORROOT/tool <<EOF 1 EOF

6. Create the following soft links. § ln –s $RESILIENCY FILE REPLICATORROOT /

tool/usr/local/lib/libintl.so.8 /lib/libintl.so.8 § ln –s $RESILIENCY FILE REPLICATORROOT /

tool/usr/local/lib/libiconv.so.2 /lib/libiconv.so.2 § ln –s $RESILIENCY FILE REPLICATORROOT /

tool/usr/local/lib/libgcc_s.so.1 /lib/libgcc_s.so.1


28. Upgrading RESILIENCY ORCHESTRATION 7.1 P2 to RESILIENCY

ORCHESTRATION 7.1 SP1 License Patch Upgrade Procedure for RESILIENCY ORCHESTRATION 7.1 P2 to RESILIENCY ORCHESTRATION 7.1 SP1 License Patch.

Prerequisites


1. Stop the panaces server from <$EAMSROOT>/bin. 2. Stop all agents.

3. Take a backup of $EAMSROOT and $TOMCAT_HOME/webapps. Go to webapps folder and Delete PanacesGUI directory by rm –rf PanacesGUI

4. Download 7.1_SP1 patch license files from FTP server.


• Tomcat.tar to be downloaded to $TOMCAT_HOME/webapps/

5. cd $EAMSROOT and untar Server.tar (tar –xvf Server.tar)

6. cd $TOMCAT_HOME/webapps/ and untar tomcat.tar (tar –xvf Tomcat.tar)

7. cd $EAMSROOT/lib and execute the command: mysql -u root panaces < mysql_schema_upgrade7.1GA_P2-7.1SP1.sql

8. Start RESILIENCY ORCHESTRATION server.

11. Once the RESILIENCY ORCHESTRATION server and agents are started, cd to < EAMSROOT >/bin.

12. Execute the script 'GroupContinuityStatusUpgradeUtility.sh'. The script should be executed successfully. Log for this utility can be found at <EAMSROOT>/var/log/GroupContinuityStatusUpgradeUtility.log

13. For Vmware to AWS solution, please use the latest RESILIENCY REPLICATION APPLIANCEs from PR RESILIENCY REPLICATION APPLIANCE: FTP server. DR RESILIENCY REPLICATION APPLIANCE: FTP server respectively.

Note: • The default replication is secured replication now. • For Vm protection solution we would need another instance of RESILIENCY

REPLICATION APPLIANCE in AWS called as Proxy RESILIENCY

Comment [s1]: Replace “panaces” by “Resiliency Orchestration”


REPLICATION APPLIANCE wherein only RESILIENCY REPLICATION APPLIANCE Agent should be running. You can find this in the FTP server.

14. Alternatively, local agents can also be downloaded from the FTP server.


29. Upgrading RESILIENCY ORCHESTRATION 7.1 SP1 to

RESILIENCY ORCHESTRATION 7.1 SP2 For upgrading from RESILIENCY ORCHESTRATION 7.1 SP1 to RESILIENCY ORCHESTRATION 7.1 SP2, refer to the ResiliencyOrchestrationInstallationGuide_Upgrade.pdf file at 7.1/Service_Packs/7.1_SP2/Upgrade_7.1SP1-7.1SP2 in the FTP server.


30. Upgrading RESILIENCY ORCHESTRATION 7.1 SP2 to RESILIENCY

ORCHESTRATION 7.1 SP4 This chapter provides the procedure for upgrading from RESILIENCY ORCHESTRATION 7.1 SP2 to RESILIENCY ORCHESTRATION 7.1 SP4. The following are the steps for patch upgrade for upgrading from RESILIENCY ORCHESTRATION 7.1 SP2 to RESILIENCY ORCHESTRATION 7.1 SP4:

1. Stop RESILIENCY ORCHESTRATION services of 7.1SP2. 2. Create a backup of mysql db schema, mysqldump -u root --databases panaces pfr

advancedreporter -R --triggers > panaces_dump.sql 3. Create a backup of $EAMSROOT and $TOMCAT_HOME/webapps. 4. Delete PanacesGUI and cResiliency Orchestration-ws directories by using the rm -rf

PanacesGUI and rm -rf cResiliency Orchestration-ws command. 5. Download 7.1_SP2 patch license files from the FTP server

a. Download the Server.tar file to the $EAMSROOT folder b. Download the Tomcat.tar file in the $TOMCAT_HOME/webapps/ folder

6. Go to cd $EAMSROOT and run the command tar –xvf Server.tar to untar Server.tar

7. Go to cd $TOMCAT_HOME/webapps/ and run the command tar –xvf Tomcat.tar to untar tomcat.tar

8. Kill any VcenterCSA or management service process, if running in the backend. 9. Go to cd $EAMSROOT/lib and run the following command:

mysql -u root < mysql_schema_upgrade_7.1_SP2_SP4.sql 10. Go to cd $EAMSROOT/installconfig and run the following

command: ./importTemplateEvents.sh 11. Go to cd $EAMSROOT/bin and run the following command:

./AddSignature.sh 12. Start RESILIENCY ORCHESTRATION services 13. Stop RESILIENCY ORCHESTRATION services 14. Perform the Post installation steps available in Installation Guide, for third party JS changes. 15. Go to cd $EAMSROOT/lib and run the following command:

mysql -u root < mysql_update_polar_cancellation_srs.sql 16. Start RESILIENCY ORCHESTRATION services



ORCHESTRATION 7.1 SP6 For upgrading from RESILIENCY ORCHESTRATION 7.1 SP4 to RESILIENCY ORCHESTRATION 7.1 SP6, refer to the ResiliencyOrchestrationInstallationGuide_Upgrade.pdf file at 7.1/Service_Packs/7.1_SP6/Upgrade_7.1SP4-7.1SP6 in the FTP server.



ORCHESTRATION 7.1 SP6 For upgrading from RESILIENCY ORCHESTRATION 6.3 SP4 to RESILIENCY ORCHESTRATION 7.1 SP6, refer to the ResiliencyOrchestrationInstallationGuide_Upgrade.pdf file at 7.1/Service_Packs/7.1_SP6/Upgrade_7.1SP4-7.1SP6 in the FTP server.


33. Upgrading RESILIENCY ORCHESTRATION 6.3 SP5, SP6, and SP7 to

RESILIENCY ORCHESTRATION 7.1 SP6 For upgrading from RESILIENCY ORCHESTRATION 6.3 SP5, SP6, and SP7 to RESILIENCY ORCHESTRATION 7.1 SP6, refer to the ResiliencyOrchestrationInstallationGuide_Upgrade.pdf file at 7.1/Service_Packs/7.1_SP6/Upgrade_7.1SP4-7.1SP6 in the FTP server.


34. Uninstalling Resiliency Orchestration Agent Node

Uninstallation of Resiliency Orchestration Agent Node

Perform the following steps to uninstall IBM Resiliency Orchestration Agent Node.

1. Go to <$EAMSROOT>/UninstallerData folder.

2. Click Uninstall IBM Resiliency Orchestration Agent Node folder. The Uninstall IBM Resiliency Orchestration Agent Node window opens.

Figure 190: Uninstall IBM Resiliency Orchestration Agent Node

3. Click Uninstall.

4. The uninstallation process begins and lasts for a few seconds. When the process is complete, the following window is displayed.


Figure 191: Uninstall Complete screen

5. Click Done to close this window.


35. Uninstalling Resiliency Orchestration

Server and Agents This chapter provides detailed information on uninstalling IBM Resiliency Orchestration product on your system.

Note

§ If you have used Silent mode of installation, you can perform only Silent mode of uninstallation. After Silent mode of installation, Graphical mode of uninstallation cannot be performed.

§ If the IBM Resiliency Orchestration Server and/ or Agent is installed through Graphical mode, the uninstallation is possible through both Graphical and Silent mode:

Uninstall_IBM_RESILIENCY ORCHESTRATION__Server -i silent Uninstall_IBM_RESILIENCY ORCHESTRATION_Agents -i silent

Uninstallation of Resiliency Orchestration Server

Uninstallation of IBM Resiliency Orchestration server can be performed from:

§ GUI

§ Command Prompt

GUI

To uninstall IBM Resiliency Orchestration server from GUI, perform the following steps:

1. Go to $EAMSROOT/UninstallerData.

2. Click Uninstall_IBM Resiliency Orchestration_server.

3. The Introduction screen is displayed, as shown in the following figure.


Figure 192: Uninstall IBM Resiliency Orchestration Server – Introduction screen

4. Click the Uninstall button to continue with Uninstallation. The Uninstalling… screen is displayed, as shown in the following figure.


Figure 193: Uninstall IBM Resiliency Orchestration Server – Uninstalling… screen

5. Once the uninstaller removes all the features, the Uninstall Complete screen is displayed, as shown in the following figure.


Figure 194: Uninstall IBM Resiliency Orchestration Server – Uninstall Complete screen

6. Click Done to close the Uninstall IBM Resiliency Orchestration Server window.

Note that uninstallation of IBM Resiliency Orchestration Server does not delete the database. You have to manually delete the databases by providing the following command at the command prompt:

#mysql -u root mysql>drop database panaces; mysql>drop database pfr; mysql>drop database advancedreporter;

Command Prompt

To uninstall IBM Resiliency Orchestration server from the command prompt, perform the following steps:

# cd $EAMSROOT/UninstallerData # ./Uninstall_IBM_RESILIENCY ORCHESTRATION_server

This process will uninstall all binaries that have been installed while installing IBM Resiliency Orchestration server. This process will not uninstall Tomcat binaries.

Uninstallation of Agents

Perform the following steps to uninstall all agents on your system.


Windows

1. Go to C:\Program Files\Panaces\ UninstallerData\ folder.

2. Click Uninstall Agents folder. The Uninstall Agents window opens.

3. Click Uninstall.

4. The uninstallation process begins and lasts for a few seconds. When the process is complete, the following window is displayed.

Figure 195: Uninstall Complete screen

5. Click Done to close this window.

Solaris

Perform the following steps to uninstall all agents from your system. To uninstall Solaris agent(s) from the command prompt, execute the following commands:

# cd $EAMSROOT/UninstallerData # ./Uninstall_IBM_RESILIENCY ORCHESTRATION_Agents

As part of uninstallation, the link names from "/etc/rc3.d" directory should be manually removed.

Linux

Perform the following steps to uninstall all agents from your system.


To uninstall Linux agent(s) from command prompt, do the following steps: # cd $EAMSROOT/UninstallerData # ./Uninstall_IBM_RESILIENCY ORCHESTRATION_Agents

As part of uninstallation, the link names from "/etc/rc.d/rc3.d" directory should be manually removed.

HPUX

Perform the following steps to uninstall all agents from your system. To uninstall HPUX agent(s) from command prompt, do the following steps:

# cd $EAMSROOT/UninstallerData # ./Uninstall_IBM_RESILIENCY ORCHESTRATION_Agents

As part of uninstallation, the link names from "/etc/rc3.d" directory should be manually removed.

AIX

To uninstall AIX agent(s) from command prompt, do the following steps: # cd $EAMSROOT/UninstallerData # ./Uninstall_IBM_RESILIENCY ORCHESTRATION_Agents

As part of uninstallation, the link names from "/etc/rc.d/rc2.d" directory should be manually removed.

During uninstallation, the following directories will not be deleted, as they might be useful. var/log scripts/samples panacesFileReplicator/filesets

If the above directories are not deleted, the uninstallation process will list the name of these directories. After reviewing its contents, the directories can be deleted.


36. Installing Resiliency Orchestration OS Command Processor

Prerequisites

Prior installing the IBM Sz/OS CP (Command Processor), you need to install the following components on your z/OS system:

• z/OS ICSF: ICSF is a software element of z/OS. ICSF works with the hardware cryptographic features and the Security Server (RACF element) to provide secure, high-speed cryptographic services in the z/OS environment. ICSF provides the application programming interfaces, which allow applications to request the cryptographic services. ICSF is also the means for loading the secure cryptographic features with master key values, allowing the hardware features to be used by applications. The cryptographic feature is secure, high-speed hardware that performs the actual cryptographic functions. Your processor hardware determines the cryptographic feature available to your applications. Note: If z/OS ICSF is not installed, refer to the following manual: z/OS

Cryptographic Services Integrated Cryptographic Service Facility System Programmer's Guide.

• z/OS OpenSSH: OpenSSH provides secure encryption for both remote login and file transfer.

Note: If z/OS OpenSSH is not installed, refer to the following manual: z/OS IBM Ported Tools for z/OS: OpenSSH User's

Overview

The IBM Sz/OS CP (Command Processor) enables the IBM Resiliency Orchestration Manager workflows to communicate with z/OS systems. The communication is created by installing several modules in the OMVS subsystem that allow commands to be submitted through SSH communications and through OMVS to execute on your z/OS system. Responses to those commands are then captured and returned to the Resiliency Orchestration Manager server for further workflow processing.

For example, the following figure displays the Resiliency Orchestration Manager workflow, where Step A checks if the job, JOB123 is executing, if it is, Step B submits JOB456 and Step C is ignored, otherwise if Step A is not executing, Step B is ignored and Step C is completed.


Figure 196: Resiliency Orchestration RESILIENCY ORCHESTRATION Workflow

Installing OS Command Processor

The Resiliency Orchestration OS Command Processor can be installed from a tar file. The name of the tar file is IBM-szcpvnnrnn.tar where nn denotes the version and release number of the tar file. Note You need to install OS Command Processor into a directory named /u/IBM.

The following tasks need to be performed to install the Resiliency Orchestration OS Command Processor from a tar file:

1. Extract Installation File 2. Authorize APF for TCMD and ZCMD

3. Define Userid IBM to RACF (or other security program)

Extracting Installation File

The following are the steps to extract the installation file:

1. Specify the IP of your z/OS system, enable the download in binary mode, and FTP the SzCP tar file to your z/OS system. For example:

ftp xxx.xxx.xxx.xxx <- the ip of your z/OS system bin <- set binary mode put /from/IBM-szcpvnnrnn.tar /to/IBM-szcpvnnrnn.tar


2. Create the /u/IBM folder. If you have a previous version installed, copy it to the backup

prior proceeding, for example /u/IBM-prev-version.

3. Extract the IBM-szcpvnnrnn.tar file. Specify -xvf to extract and display the untared files, and then specify the location /xxxx where the tar file is FTP’d in Step 1. The following example displays the snippet for installing v01r00:

tar -xvf /xxxx/IBM-szcpv01r00.tar

Verify that the following files are extracted in the /u/IBM folder:

x /u/IBM/TCMD, 12288 bytes, 24 tape blocks x /u/IBM/ZCMD, 24576 bytes, 48 tape blocks x /u/IBM/tcmd.sh, 64 bytes, 1 tape block x /u/IBM/zcmd.sh, 64 bytes, 1 tape block

Authorizing APF for TCMD and ZCMD

1. After the untar, the contents of the /u/IBM folder is displayed as shown below:

Pathname . : /u/IBM EUID . . . : 0 Command Filename Message Type Permission Audit Ext Fmat --------------------------------------------------------------- . Dir rwxr-xr-x fff--- ---- .. Dir rwxr-xr-x fff--- ---- tcmd.sh File rwxr-xr-x fff--- --s- ---- zcmd.sh File rwxr-xr-x fff--- --s- ---- TCMD File rwxr-xr-x fff--- --s- ---- ZCMD File rwxr-xr-x fff--- --s- ----

Note The contents of /u/IBM folder displayed from ISPF Data Set List Utility or Edit Entry Panel is same.

2. Set the APF Extended Attribute ON for TCMD and ZCMD. You can perform this through ISPF, for example using MX (Modify Extended Attributes):

MX TCMD File rwxr-xr-x fff--- --s- ----


3. Enter “/” next to APF Authorized, as shown below:

Modify z/OS UNIX File Extended Attributes Command ===>

Pathname . : /u/IBM/TCMD Type . . . : File

Enter "/" to select option / Use Shared Address Space / APF Authorized Program Controlled Shared Library

4. After APF authorization is turned on for TCMD and ZCMD, verify that the extended attribute displays, as shown below:

Pathname . : /u/IBM EUID . . . : 0 Command Filename Message Type Permission Audit Ext Fmat --------------------------------------------------------------- . Dir rwxr-xr-x fff--- ---- .. Dir rwxr-xr-x fff--- ---- tcmd.sh File rwxr-xr-x fff--- --s- ---- zcmd.sh File rwxr-xr-x fff--- --s- ---- TCMD File rwxr-xr-x fff--- a-s- ---- ZCMD File rwxr-xr-x fff--- a-s- ----

Defining Userid IBM to RACF/Other Security Program

Define a userid named IBM to RACF or equivalent security program. The IBM userid needs the following OPERPARM attributes set:

OPERPARM INFORMATION -------------------- STORAGE= 00000 AUTH= MASTER DOM= ALL CMDSYS= *

Verifying Sz/OS CP (Command Processor) Install

1. After the install, verify the install by executing the SzCPIVP Workflow from Resiliency Orchestration. The following figure displays the SzCPIVP Workflow.


Figure 197: SzCPIVP

The workflow executes few simple tests to confirm that your install was successful. The following tasks will be performed: TESTDAL: The TESTDAL enters and returns the output from a z/OS command “D A,L”. TESTJESDA: The TESTJESDA enters and returns the output from a JES command “$DA”. TSOLISTCAT: The TSOLISTCAT enters and returns the output from a TSO LISTC command. TSOLU: The TSOLU enters and returns the output from a TSO LU command.

After the workflow has been executed, confirm that each step is successful, for example, successfully executed actions are displayed as shown below:

2. Click on the expand arrow to the left of each Action to verify that the correct output is

returned. For example:


The installation is now complete.


37. Installing Resiliency Orchestration SCLM CL Binaries for Mimix with AS400

Overview

The SclM (IBM cl binaries for Mimix with AS400) enables the IBM Resiliency Orchestration workflows to run Mimix commands using CL programs for AS400. For example, in the following workflow, Step A checks the Mimix Node status. If node Status is “ACTIVE” it executes Step B, otherwise it executes Step C. The following diagram displays an example of the IBM Resiliency Orchestration workflow:

Figure 198: IBM Resiliency Orchestration Workflow Example

Installing IBM cl Binaries for Mimix

The SclM (IBM cl binaries for Mimix with AS400) can be installed using the IBMSAV file, which is a SAVF file. IBMSAV binaries will be available in Resiliency Orchestration server in the following folder: /opt/panaces/scripts/repeatable/MIMIX/SclMbin/IBMSAV

Note The user needs to perform the installation in the library IBM.LIB.

The following are the steps to install the SclM (IBM cl binaries for Mimix with AS400) from a SAVF file. 1. Confirm whether the IBM.LIB library can be created or this library is created in AS400

systems.


2. Create the sav file IBMSAV in IBM.LIB in the AS400 systems.

3. FTP the IBMSAV file to your AS400 systems IBM.LIB, confirm that the download is done in binary mode.

4. Next run the following command to extract the IBMSAV file to IBM.LIB using restobj:

RSTOBJ OBJ(*ALL) SAVLIB(IBM) DEV(*SAVF) SAVF(IBM/IBMSAV) RSTLIB(IBM)

Verifying the IBM Cl Binaries for Mimix Installation

After the install, execute the MimixAS400SclM Workflow from the IBM Resiliency Orchestration to verify the install. The following diagram displays the MimixAS400SclM Workflow:

Figure 199: MimixAS400SclM Workflow

This workflow will execute mimix command on the primary AS400 systems to check for the node status. In action properties of RALs, you need to select the PR Replication Server option and save the workflow. After the workflow has been executed, confirm that each step was successful and if your Mimix manager status is ACTIVE the following figure is displayed, otherwise the figure displays *ATTN:

The installation is now complete.


38. Migrating Resiliency Orchestration Server to new Server with same IP

Assuming /backup has enough disk space for original and new IBM Resiliency Orchestration Server, EAMSROOT as /opt/panaces, and TOMCAT_HOME as /opt/jboss-ews-2.0/tomcat7.0.30, and same OS, with Same MySQL DB version level The below steps need to be followed to migrate IBM Resiliency Orchestration server to new server with same IP

1. Stop all the services in the current IBM Resiliency Orchestration Server. 2. Take the mysql Schema

a. mysqldump -u root –databases panaces pfr advancedreporter –triggers -R > /backup/panaces-pfr-advrpt.sql

3. Take EAMSROOT , and TOMCAT Home folder backup a. cd /opt b. tar –cvzf /backup/EAMSROOT.tar.gz panaces c. cd /opt/ d. tar –cvzf /backup/tomcat7.0.30.tar.gz jboss-ews-2.0

4. Copy /backup/panaces-pfr-advrpt.sql /backup/EAMSROOT.tar.gz /backup/tomcat7.0.30.tar.gz /etc/security/limit.conf /etc/hosts /etc/my.cnf to a common share location

5. Note down hostname of original server , at prompt type hostname 6. Note down the port exceptions in firewall , use system-config-firewall or system-config-

securitylevel 7. Shutdown the current IBM Resiliency Orchestration server using poweroff command 8. Bring the New IBM Resiliency Orchestration Server with Same IP with the help of IT. 9. Login to new IBM Resiliency Orchestration server using putty. 10. Copy from common share folder all files panaces-pfr-advrpt.sql EAMSROOT.tar.gz

tomcat7.0.30.tar.gz limit.conf hosts my.cnf to /backup 11. Extract IBM Resiliency Orchestration binaries

a. cd /opt b. tar –xvzf /backup/ EAMSROOT.tar.gz

12. Extract Tomcat a. cd /opt b. tar –xvzf /backup/tomcat7.0.30.tar.gz

13. Update EAMSROOT a. echo “export EAMSROOT=/opt/panaces” >> /etc/profile

14. refer /backup/limit.conf , /backup/hosts , /backup/my.cnf and update /etc/security/limit.conf /etc/hosts /etc/my.cnf respectively

15. Set hostname same as noted one a. hostname <original_server_hostname> b. update same in /etc/sysconfig/network


16. configure the exception ports as noted earlier using system-config-firewall or system-config-securitylevel

17. Restore the mysql schema a. mysql -u root < /backup/panaces-pfr-advrpt.sql

18. Create required mysql users along with privileges a. Mysql –u root b. use mysql; c. CREATE USER 'pfradmin'@'localhost' IDENTIFIED BY 'pfradmin123'; d. GRANT ALL PRIVILEGES ON *.* TO 'pfradmin'@'localhost' IDENTIFIED BY

'pfradmin123' WITH GRANT OPTION; e. CREATE USER 'panaces'@'localhost' IDENTIFIED BY 'panaces123'; f. GRANT ALL PRIVILEGES ON *.* TO 'panaces'@'localhost' IDENTIFIED BY

'panaces123' WITH GRANT OPTION; g. CREATE USER 'IBMreporter'@'localhost' IDENTIFIED BY 'IBM123'; h. GRANT ALL PRIVILEGES ON *.* TO 'IBMreporter'@'localhost' IDENTIFIED

BY 'IBM123' WITH GRANT OPTION; 19. Verify the panaces, pfr, advancedreporter databases are available after restored in the new

server. 20. Start IBM Resiliency Orchestration Services ;

a. /opt/panaces/bin/panaces start 21. Verify that the console log shows panaces services started successfully

a. tail –f /opt/panaces/var/log/console.log


39. Migrating Resiliency Orchestration Server to new Server with new IP

Assuming /backup has enough disk space for original and new IBM Resiliency Orchestration Server, EAMSROOT as /opt/panaces , and TOMCAT_HOME as /opt/jboss-ews-2.0/tomcat7.0.30, and same OS, with Same MySQL DB version level The below steps need to be followed to migrate IBM Resiliency Orchestration server to new server with new IP

1. Stop all the services in the current IBM Resiliency Orchestration Server. 2. Take the mysql Schema

a. mysqldump -u root –databases panaces pfr advancedreporter –triggers -R > /backup/panaces-pfr-advrpt.sql

3. Take EAMSROOT , and TOMCAT Home folder backup a. cd /opt b. tar –cvzf /backup/EAMSROOT.tar.gz panaces c. cd /opt/ d. tar –cvzf /backup/tomcat7.0.30.tar.gz jboss-ews-2.0

4. Copy /backup/panaces-pfr-advrpt.sql /backup/EAMSROOT.tar.gz /backup/tomcat7.0.30.tar.gz /etc/security/limit.conf /etc/hosts /etc/my.cnf to /backup of new IBM Resiliency Orchestration server using scp.

5. Note down the port exceptions in firewall , use system-config-firewall or system-config-securitylevel

6. Login to new IBM Resiliency Orchestration server using putty 7. Extract IBM Resiliency Orchestration binaries

a. cd /opt b. tar –xvzf /backup/ EAMSROOT.tar.gz

8. Extract Tomcat a. cd /opt b. tar –xvzf /backup/tomcat7.0.30.tar.gz

9. Update EAMSROOT a. echo “export EAMSROOT=/opt/panaces” >> /etc/profile

10. refer /backup/limit.conf , /backup/hosts , /backup/my.cnf and update /etc/security/limit.conf /etc/hosts /etc/my.cnf respectively

11. configure the exception ports as noted earlier using system-config-firewall or system-config-securitylevel

12. Restore the mysql schema a. mysql -u root < /backup/panaces-pfr-advrpt.sql

13. Verify the panaces, pfr, advancedreporter databases are available after restored in the new server.


14. Create required mysql users along with privileges a. Mysql –u root b. use mysql; c. CREATE USER 'pfradmin'@'localhost' IDENTIFIED BY 'pfradmin123'; d. GRANT ALL PRIVILEGES ON *.* TO 'pfradmin'@'localhost' IDENTIFIED BY

'pfradmin123' WITH GRANT OPTION; e. CREATE USER 'panaces'@'localhost' IDENTIFIED BY 'panaces123'; f. GRANT ALL PRIVILEGES ON *.* TO 'panaces'@'localhost' IDENTIFIED BY

'panaces123' WITH GRANT OPTION; g. CREATE USER 'IBMreporter'@'localhost' IDENTIFIED BY 'IBM123'; h. GRANT ALL PRIVILEGES ON *.* TO 'IBMreporter'@'localhost' IDENTIFIED

BY 'IBM123' WITH GRANT OPTION;

15. Update the following tables to be done for Agent Node and Vault Agent, if we use: a. update component set c_ipaddr='New IBMRESILIENCY ORCHESTRATION_IP'

where c_id=5; b. update agent_csa set ac_ipaddress='New IBMRESILIENCY

ORCHESTRATION_IP' where ac_id=168; c. update agent_csa set ac_anode_ip='New IBMRESILIENCY

ORCHESTRATION_IP’ where ac_anode_ip='OLD_RESILIENCY ORCHESTRATION_IP';

d. For Vault Changes 16. update component_OSServer set cos_mgmt_ipaddr='New IBMRESILIENCY

ORCHESTRATION_IP' where cos_mgmt_ipaddr='Old IBMRESILIENCY ORCHESTRATION_IP';

17. Start IBM Resiliency Orchestration Services ; a. /opt/panaces/bin/panaces start

18. Verify that the console log shows panaces services started successfully a. tail –f /opt/panaces/var/log/console.log


40. Troubleshooting

Agent Not Starting on Windows Server

Scripts installed along with the installation starts the Agents, when the system is rebooted. Alternatively, you can start the agents manually, without rebooting the system. However, if the agents do not start by any of these methods, do the following:

Check the respective lax files for the agent’s class path and java path entries. If these entries are incorrect, edit these files and restart the agents once the agent installation is complete.

Perform any of the following procedures depending on the agent selection:

Note

The default value of EAMSROOT is “C:\Program Files\panaces”. If you have installed IBM Resiliency Orchestration at a different location, then the paths in the following lax files would be

appropriately set by the installer program. Following is an example, with the assumption that IBM Resiliency Orchestration has been installed at the default location.

§ IBM File Replicator Service

Open PFRService.lax file that has been installed in the IBM File Replicator Service installation path with a text editor. Check if LAX.CLASS.PATH has the following class path: lax.class.path= C:\Program Files\panaces\lib\commons-lang-1.0.1.jar;C:\Program Files\panaces\lib\PADS.jar;C:\Program Files\panaces\lib\log4j.jar;C:\Program Files\panaces\lib\jacl.jar;C:\Program Files\panaces\lib\tcljava.jar;C:\Program Files\panaces\lib\PFR.jar:lax.jar

Edit the IBM File Replicator installation path in the PFRConfiguration.cfg file by following the steps given below:

Ø Go to $EAMSROOT /installconfig folder.

Ø Open the PFRConfiguration.cfg file. Provide the installation path of IBM File Replicator in the PFR_INSTALL_PATH parameter.

Ø Replace C:\Program Files\panaces with C:\Progra~1\panaces.

§ PFR Agent

Open PFRAgent.lax file that has been installed in PFR agent install path. Check if lax.class.path has the following classpath: lax.class.path= C:\Program Files\panaces\lib\commons-lang-1.0.1.jar;C:\Program Files\panaces\lib\PADS.jar;C:\Program Files\panaces\lib\log4j.jar;C:\Program Files\panaces\lib\tcljava.jar;C:\Program Files\panaces\lib\jacl.jar;C:\Program


Files\panaces\lib\PFR.jar;C:\Program Files\panaces\PFRAgentCSA.jar:lax.jar

§ MSSQL Agent

For MSSQL 2005 Open MSSQLAgent.lax file that has been installed in MSSQL agent installation path with a text editor. Check if “LAX.CLASS.PATH” has the following class path: lax.class.path= C:\Program Files\panaces\lib\commons-lang-1.0.1.jar;C:\Program Files\panaces\lib\PADS.jar;C:\Program Files\panaces\lib\log4j.jar;C:\Program Files\panaces\lib\jacl.jar;C:\Program Files\panaces\lib\tcljava.jar;C:\sqljdbc.jar;C:\Program Files\panaces\MSSQLAgentCSA.jar:lax.jar

§ Windows OS Agent

Open WindowsOSAgent.lax file that has been installed in Windows OS agent installation path with a text editor. Check if “LAX.CLASS.PATH” has the following class path: lax.class.path= C:\Program Files\panaces\lib\commons-lang-1.0.1.jar;C:\Program Files\panaces\lib\PADS.jar;C:\Program Files\panaces\lib\log4j.jar; C:\Program Files\panaces\lib\jacl.jar;C:\Program Files\panaces\lib\tcljava.jar;C:\Program Files\panaces\WindowsOSAgentCSA.jar; C:\Program Files\panaces\lib\commons-dbcp-1.2.1.jar;C:\Program Files\panaces\lib\commons-logging.jar;C:\Program Files\panaces\lib\commons-pool-1.2.jar;C:\Program Files\panaces\lib\quartz-all-1.5.2.jar:lax.jar

Agent Not Stating on Solaris Server

Before starting the agent services, check the respective lax files for the agent’s class path and java path entries. If these entries are incorrect, edit these files and restart the agents once the agent installation is complete.

Perform any of the following procedures depending on the agent selection:

§ Sybase Agent

Open Sybase Agent.lax file that has been installed in the Agent installation path with a text editor. Check if LAX.CLASS.PATH has the following class path: lax.class.path= /opt/panaces/lib/commons-lang-1.0.1.jar:/opt/panaces/lib/PADS.jar:/opt/panaces/lib/log4j.jar:/opt/panaces/lib/jacl.jar:opt/panaces/lib/tcljava.jar:SybaseAgentCSA.jar:opt/panaces/lib/SYBASE/ase_125/jConnect-5_5/classes/jconn2.jar:/SYBASE/ase_125/jConnect-5_5/classes/jTDS2.jar:lax.jar

Also, check for the java installation path displayed under LAX.NL.CURRENT.VM.



Open PFRService.lax file that has been installed in the IBM File Replicator Service installation path with a text editor. Check if LAX.CLASS.PATH has the following class path: lax.class.path= /opt/panaces/lib/commons-lang-1.0.1.jar:/opt/panaces/lib/PADS.jar:/opt/panaces/lib/log4j.jar:/opt/panaces/lib/jacl.jar:opt/panaces/lib/tcljava.jar:/opt/panaces/lib/PFR.jar:lax.jar

§ PFR Agent

Before starting the PFR Agent, open PFRAgent.lax file that has been installed in Agent installation path with a text editor. Check if LAX.CLASS.PATH has the following class path: lax.class.path= /opt/panaces/lib/commons-lang-1.0.1.jar:/opt/panaces/lib/PADS.jar:/opt/panaces/lib/log4j.jar:/opt/panaces/lib/jacl.jar:opt/panaces/lib/tcljava.jar:/opt/panaces/lib/PFRAgentCSA.jar:lax.jar


§ Solaris OS Agent

Open SolarisOSAgent.lax file that has been installed in Solaris OS Agent installation path with a text editor. Check if LAX.CLASS.PATH has the following class path: lax.class.path= /opt/panaces/lib/commons-lang-1.0.1.jar:/opt/panaces/lib/PADS.jar:/opt/panaces/lib/log4j.jar:opt/panaces/lib/jacl.jar:opt/panaces/lib/tcljava.jar:opt/panaces/lib/SolarisOSAgentCSA.jar:/opt/panaces/lib/commons-collections-4.0.jar:/opt/panaces/lib/commons-dbcp-1.2.1.jar:/opt/panaces/lib/commons-logging.jar:/opt/panaces/lib/commons-pool-1.2.jar:/opt/panaces/lib/quartz-all-1.5.2.jar:lax.jar


§ SRS Agent

Open SrsAgent.lax file that has been installed in Solaris OS Agent installation path with a text editor. Check if LAX.CLASS.PATH has the following class path: lax.class.path=/opt/panaces/lib/commons-lang-1.0.1.jar:/opt/panaces/lib/PADS.jar:/opt/panaces/lib/log4j.jar:/opt/panaces/lib/tcljava.jar:/opt/panaces/lib/jacl.jar:.:/opt/panaces/SrsAgentCSA.jar:lax.jar


Agent Not Stating on Linux Server

Before starting the agent services, check the respective lax files for the agent’s class path and java path entries. If these entries are incorrect, edit these files and restart the agents once the agent installation is complete. Perform any of the following procedures depending on the agent selection:



Open PFRService.lax file that has been installed in the IBM File Replicator Service installation path with a text editor. Check if LAX.CLASS.PATH has the following class path: lax.class.path= /opt/panaces/lib/commons-lang-1.0.1.jar;/opt/panaces/l ib/PADS.jar;/opt/panaces/lib/log4j.jar;/opt/panaces/lib/jacl.jar;opt/panaces/lib/tcljava.jar;/opt/panaces/lib/PFR.jar:lax.jar

§ PFR Agent

Before starting the PFR Agent, open PFRAgent.lax file that has been installed in Agent installation path with a text editor. Check if LAX.CLASS.PATH has the following class path: lax.class.path= /opt/panaces/lib/commons-lang-1.0.1.jar;/opt/panaces/l ib/PADS.jar;/opt/panaces/lib/log4j.jar;/opt/panaces/lib/jacl.jar;opt/panaces/lib/tcljava.jar;/opt/panaces/lib/PFRAgentCSA.jar:lax.jar


§ Linux OS Agent

Open LinuxOSAgent.lax file that has been installed in Linux OS Agent installation path with a text editor. Check if LAX.CLASS.PATH has the following class path: lax.class.path= /opt/panaces/lib/commons-lang-1.0.1.jar;/opt/panaces/l ib/PADS.jar;/opt/panaces/lib/log4j.jar;/opt/panaces/lib/jacl.jar;opt/panaces/lib/tcljava.jar;opt/panaces/lib/LinuxOSAgentCSA.jar;/opt/panaces/lib/commons-collections-4.0.jar;/opt/panaces/lib/commons-dbcp-1.2.1.jar;/opt/panaces/lib/commons-logging.jar;/opt/panaces/lib/commons-pool-1.2.jar;/opt/panaces/lib/quartz-all-1.5.2.jar:lax.jar



Agent Not Starting on AIX Server



Open PFRService.lax file that has been installed in the IBM File Replicator Service installation path with a text editor. Check if LAX.CLASS.PATH has the following class path: lax.class.path= /opt/panaces/lib/commons-lang-1.0.1.jar:/opt/panaces/l ib/PADS.jar:/opt/panaces/lib/log4j.jar:/opt/panaces/lib/jacl.jar;opt /panaces/lib/tcljava.jar:/opt/panaces/lib/PFR.jar:lax.jar


§ PFR Agent

Before starting the PFR Agent, open PFRAgent.lax file that has been installed in the Agent installation path with a text editor. Check if LAX.CLASS.PATH has the following class path: lax.class.path=/opt/panaces/lib/commons-lang-1.0.1.jar:/opt/panaces/lib/PADS.jar:/opt/panaces/lib/log4j.jar: /opt/panaces/lib/jacl.jar;opt/panaces/lib/tcljava.jar:/opt/panaces/lib/PFR.jar:/opt/panaces/lib/PFRAgentCSA.jar:lax.jar

Also, check for the java installation path displayed under LAX.NL.CURRENT.VM. In addition to checking class paths for the agents installed as explained in this step, also perform the following step:

§ AIX OS Agent

Before starting the AIX OS Agent, open AIXOSAgent.lax file that has been installed in the Agent installation path with a text editor. Check if LAX.CLASS.PATH has the following class path: lax.class.path=/opt/panaces/lib/commons-lang-1.0.1.jar: /opt/panaces/lib/PADS.jar:/opt/panaces/lib/log4j.jar: /opt/panaces/lib/jacl.jar;/opt/panaces/lib/tcljava.jar:/opt/panaces/lib/commons-collections-4.0.jar:/opt/panaces/lib/commons-dbcp-1.2.1.jar:/opt/panaces/lib/commons-logging.jar:/opt/panaces/lib/quartz-all-1.5.2.jar:/opt/panaces/AIXOSAgentCSA.jar:lax.jar

Check for the java installation path displayed under LAX.NL.CURRENT.VM.


Agent Not Starting on HPUX Server



Open PFRService.lax file that has been installed in the IBM File Replicator Service installation path with a text editor. Check if LAX.CLASS.PATH has the following class path: lax.class.path= /opt/panaces/lib/commons-lang-1.0.1.jar;/opt/panaces/lib/ PADS.jar;/opt/panaces/lib/log4j.jar;/opt/panaces/lib/jacl.jar;opt/panaces/lib/tcljava.jar;/opt/panaces/lib/PFR.jar:lax.jar

§ PFR Agent

Before starting the PFR Agent, open PFRAgent.lax file that has been installed in Agent installation path with a text editor. Check if LAX.CLASS.PATH has the following class path: lax.class.path= /opt/panaces/lib/commons-lang-1.0.1.jar;/opt/panaces/lib /PADS.jar;/opt/panaces/lib/log4j.jar;/opt/panaces/lib/jacl.jar;opt/panaces/lib/tcljava.jar;/opt/panaces/lib/PFRAgentCSA.jar:lax.jar


§ HPUX OS Agent

Open HPUXOSAgent.lax file that has been installed in Linux OS Agent installation path with a text editor. Check if LAX.CLASS.PATH has the following class path: lax.class.path= /opt/panaces/lib/commons-lang-1.0.1.jar;/opt/panaces/lib/PAD S.jar;/opt/panaces/lib/log4j.jar;/opt/panaces/lib/jacl.jar;opt/panaces/lib/tcljava.jar;opt/panaces/lib/LinuxOSAgentCSA.jar;/opt/panaces/lib/commons-collections-4.0.jar;/opt/panaces/lib/commons-dbcp-1.2.1.jar;/opt/panaces/lib/commons-logging.jar;/opt/panaces/lib/commons-pool-1.2.jar;/opt/panaces/lib/quartz-all-1.5.2.jar:lax.jar


Nat IP

The servers that are being managed have a local IP address, but that these servers have Network Attached Translation (NAT) IP and only the NAT ip is used everywhere. Also, the same local IP address might be used by multiple customers and hence the local IP cannot be used to uniquely identify the server and hence only the NAT IP (which is publicly known) can be used.


Enter the IP addresses of the primary and secondary IBM Resiliency Orchestration servers & IBM Resiliency Orchestration Agent Node Address. In a non-NAT environment NAT IP address field should be left blank. In a NAT environment Primary and secondary Resiliency Orchestration server’s public IP should be given. Resiliency Orchestration Agent node address should be the public IP & NAT IP address should be the private IP of the server where you are installing. NoteManualConfigurationifNATIPisnotprovidedduringinstallation.

CFGfileforNATIP

ExampleIBMResiliencyOrchestrationCFGfileforNATIP

PANACES_MASTER_SERVER_ADDRESS=192.168.2.131 //priv IP of RESILIENCY ORCHESTRATION PANACES_SLAVE_SERVER_ADDRESS=192.168.2.131 //priv IP of RESILIENCY ORCHESTRATION PANACES_AGENT_NODE_ADDRESS=192.168.2.131 //priv IP of RESILIENCY ORCHESTRATION PANACES_AGENT_NODE_BIND_ADDRESS= // leave empty

• Discoveragentnodeusing"PANACES_AGENT_NODE_ADDRESS"here192.168.2.131

• DiscoverPR&DRusingtheirpublicIP

ExampleLocalAgentCFGfileforNATIP

PANACES_MASTER_SERVER_ADDRESS=115.119.249.123 //public IP of RESILIENCY ORCHESTRATION PANACES_SLAVE_SERVER_ADDRESS=115.119.249.123 //public IP of RESILIENCY ORCHESTRATION PANACES_AGENT_NODE_ADDRESS=113.22.33.22 //public IP of PR/DR (this server) PANACES_AGENT_NODE_BIND_ADDRESS=192.168.2.4 //private IP of PR/DR (this server)

ExamplePFRConfigurationCFGfileforNATIP

PUBLICIP:115.119.249.125//privateIPofPR/DR

Web Browser displays certificate error

If secure protocol is used to access the IBM Resiliency Orchestration application and you have used the default certificate provided by IBM, the web browser will display the certificate error. If you proceed further with this certificate, the web browser displays the certificate error. Sometimes, you may not be able to access the application. In this case, you need to obtain a certificate from a certifying authority and import the same into the IBM keystore.


Server/Advanced Reporter installation fails with UnsatisfiedLinkError

While Installing the IBM Resiliency Orchestration or Advanced Reporter the user may encounter below UnsatisfiedLinkError The error message looks as IAResourceBundle: create resource bundle: en 'SWING' UI not supported by VM. java.lang.UnsatisfiedLinkError: /tmp/install.dir.30775/Linux/resource/jre/lib/i386/xawt/libmawt.so: libXext.so.6: cannot open shared object file: No such file or directory at java.lang.ClassLoader$NativeLibrary.load(Native Method)

This is due to the 32 bit rpm requirement from the Installer, Required 32 bit rpms (libXext-1.1-3.el6.i686.rpm libX11-1.3-2.el6.i686.rpm libxcb-1.5-1.el6.i686.rpm libXau-1.0.5-1.el6.i686.rpm libXtst-1.0.99.2-3.el6.i686.rpm libXi-1.3-3.el6.i686.rpm ) should be installed to continue installation.


41. License Information

GPL License Information

If you wish to access the source code for any of these packages, it is recommended that you visit the official download site of the package maintainer directly. A link to each download site appears in the table below. These links are provided "as-is" and will take you to sites that are not owned or controlled by IBM. IBM is not accountable for the contents of these sites and is not acting as a distributor of the code on such sites. IBM in no way warrants that the code or other information on these sites is accurate, will function in a particular manner, or is non-infringing of a third party's intellectual property rights. Please contact the maintainers of the code for information on the licenses and documentation that accompany the source code distributed from their site. Open source licenses such as GNU Public License (GPL) require that IBM makes the source available on request by the client. For packages with such licenses, the client must either go to the official site of the source or download the information from this link: https://sourceforge.net/projects/gnu-utils/files/binaries/.

In addition to GPL, each of these packages include its own licensing information. It is essential to understand the terms and conditions pertaining to the licensing information of the individual tools.


Index

A Acronyms used ..................................................................... 11 Agent Installation

on AIX server ................................................................. 91 pre-requisites for ....................................................... 91 procedure of ............................................................... 92

on HPUX server .............................................................. 82 procedure of ............................................................... 82

on Linux server ............................................................... 72 on Linux server

procedure of ......................................................... 44, 72 on Solaris server ............................................................. 61

pre-requisites for ....................................................... 61 procedure of ............................................................... 62

on Windows server ......................................................... 50 pre-requisites for ....................................................... 50 procedure of ............................................................... 52

C Conventions used ................................................................. 10

I Installation ................................................................ 12, 39, 51

components of ................................................................. 12 graphical mode of ........................................................... 16 silent mode of ................................................................. 16 using CDs ....................................................................... 13 using graphical mode ...................................................... 17

L Linux Cluster

administration of ............................................................. 43 configuration of .............................................................. 42

P PFR

starting and stopping of PFR GUI .................................. 38

S IBM Resiliency Orchestration Agent

on AIX server AIX OS agent ............................................................ 98 checking agent service status .................................... 99 PFR agent .................................................................. 99 starting and stopping of ............................................. 98

on HPUX server checking agent service status .................................... 90 HPUX OS agent ........................................................ 89 PFR agent .................................................................. 90 starting and stopping of ............................................. 89

on Linux server checking agent service status .................................... 80

Linux OS agent .......................................................... 79 PFR agent .................................................................. 80 starting and stopping of ............................................. 79

on Solaris server checking agent service status .................................... 71 PFR agent .................................................................. 70 Solaris OS agent ........................................................ 69 SRS agent .................................................................. 70 starting and stopping of ............................................. 69 Sybase agent .............................................................. 70

on Windows server starting and stopping of ............................................. 60

IBM Resiliency Orchestration Server installation of .................................................................. 21 mode of ........................................................................... 37 recovery mode starting of ............................................... 36 restarting ......................................................................... 37 starting of ........................................................................ 36 status of ........................................................................... 37 stopping of ...................................................................... 36

IBM Resiliency Orchestration Server Installation client browser prerequisite .............................................. 15 java tool prerequisite ...................................................... 15 Linux server installation for ........................................... 18 MySQL installation for ................................................... 21 on Linux cluster .............................................................. 39

interoperability matrix for ......................................... 39 Linux server installation ............................................ 40 MySQL installation ................................................... 41 procedure of ............................................................... 39 IBM Resiliency Orchestration server installation ..... 42 IBM Resiliency Orchestration server platform

installation ............................................................ 41 system requirements of .............................................. 39

procedure of .................................................................... 18 IBM Resiliency Orchestration server installation .......... 21 IBM Resiliency Orchestration client agent support ...... 13

IBM Resiliency Orchestration agents supported IBM Resiliency Orchestration agents ............ 10

Silent Mode Installation on Solaris/Linux/HPUX/AIX system ........... 100, 106, 110 on Windows system ...................................................... 110 property file editing .............................................. 106, 107

T Trademark Information .......................................................... 2

U Uninstalling IBM Resiliency Orchestration ....................... 168

agent ...................................................................... 166, 170 AIX .......................................................................... 172 HPUX ...................................................................... 171 Linux ....................................................................... 171 Solaris ...................................................................... 171 Windows .................................................................. 170

server ............................................................................ 168

Resiliency Orchestration Installation Guide 7.1 SP7(English)

Documents

Transcript of Resiliency Orchestration Installation Guide 7.1 SP7(English)