ibm...ibm resiliency orchestration - installation guide © ibm corporation 2017 3 contents preface

Installation Guide Version 7.2 SP2

Contents

2

DISCLAIMER

IBM believes that the information in this publication is accurate as of its publication date.

The information is subject to change without notice.

COPYRIGHT

© IBM Corporation 2017. All Rights Reserved.

Printed December 2017.

Use, copy, and distribution of any IBM 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 Corporation and its licensers, if

any.

IBM Resiliency Orchestration - Installation Guide

© IBM Corporation 2017 3

CONTENTS PREFACE .................................................................................................................................................... 11

Purpose ..................................................................................................................................................... 11 Audience ................................................................................................................................................... 11 Conventions .............................................................................................................................................. 12 Acronyms ................................................................................................................................................. 12

1. INSTALLATION OVERVIEW ........................................................................................................ 13

New version on Passport Advantage ........................................................................................................ 13 IBM Resiliency Orchestration Client Agent Support ............................................................................... 13 Client Browser Prerequisite ...................................................................................................................... 14 Prerequisites ............................................................................................................................................. 15

GPL Dependencies for Resiliency Orchestration ................................................................................ 15 Java Version Bundled with Installer ......................................................................................................... 15

2. RESILIENCY ORCHESTRATION SERVER INSTALLATION ON LINUX GRAPHICAL

MODE .......................................................................................................................................................... 16

Physical Dedicated Resource for Two Site Scenario ................................................................................ 16 System Requirements for Resiliency Orchestration (DRM) and Resiliency Orchestration (DRM) HA .. 16 System Requirements for Site Controller with Local Agents ................................................................... 17 System Requirements for Agents Deployed on Endpoint ........................................................................ 18 Installation of Resiliency Orchestration Server ........................................................................................ 19 Installation of Linux Enterprise Server OS ............................................................................................... 19

Installation of MariaDB ....................................................................................................................... 21 Installing Tomcat ................................................................................................................................. 21 Enabling proxy from http daemon service (Apache Http server) for low touch agent upgrade. .......... 22 Installation of Resiliency Orchestration Server Software .................................................................... 24

Post Installation Steps ............................................................................................................................... 35 Configuring Resiliency Orchestration Server For Optimal Performance ................................................. 36

Server Memory Management ............................................................................................................... 36 Recommended Settings ......................................................................................................................... 37 MariaDB connectivity configuration for Resiliency Orchestration Server .......................................... 37 Configuring Resiliency Orchestration with Different MariaDB User ................................................. 38 Configuring Resiliency Orchestration with different MariaDB user password ................................... 38 Configuration Changes in Tomcat ....................................................................................................... 39

Port Forwarding ........................................................................................................................................ 41 Prerequisites for Port Forwarding ...................................................................................................... 41 Configuration ....................................................................................................................................... 41 Steps to Enable Compression in Tomcat Server .................................................................................. 44 Configuring Current Events ................................................................................................................. 45 Fetch Logs............................................................................................................................................ 45

Server (OS) Hardening ............................................................................................................................. 45 Starting and Stopping Resiliency Orchestration Server ............................................................................ 46

Starting Resiliency Orchestration Server ............................................................................................. 46 Starting Resiliency Orchestration Server in Recover Mode ................................................................ 46 Stopping Resiliency Orchestration Server ........................................................................................... 46 Restarting Resiliency Orchestration Server ......................................................................................... 47 Checking Resiliency Orchestration Server Status ................................................................................ 47 Resiliency Orchestration Server Remote Services ............................................................................... 47 Checking Resiliency Orchestration Server Available Modes ............................................................... 47

3. RESILIENCY ORCHESTRATION SERVER INSTALLATION ON LINUX CLUSTER USING

GRAPHICAL MODE ................................................................................................................................. 49

Contents

4

System Requirements ............................................................................................................................... 49 IBM Resiliency Orchestration 7.1 Interoperability Matrix ....................................................................... 50 Installation of Resiliency Orchestration Server ........................................................................................ 51

Installation of Linux Enterprise Server OS .......................................................................................... 51 Installation of Linux Cluster ................................................................................................................ 52 Installation of Resiliency Orchestration Server Software .................................................................... 53

Starting and Stopping Resiliency Orchestration Server ............................................................................ 54 Configuring Linux Cluster ........................................................................................................................ 55

4. RESILIENCY ORCHESTRATION SERVER OVA INSTALLATION ........................................ 57

Minimum System Requirements............................................................................................................... 57 Assumptions ............................................................................................................................................. 57 Installing Resiliency Orchestration Server Virtual Appliance for VMWare ............................................ 57

Prerequisites ........................................................................................................................................ 57 Installation Procedure ............................................................................................................................... 57

Uploading the License ......................................................................................................................... 58

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

Installation of Agent Node Server ............................................................................................................ 60

6. INSTALLING AGENTS ON WINDOWS SERVER ...................................................................... 65

Prerequisites for Installing Resiliency Orchestration Agents ................................................................... 65 Windows Server Requirements ............................................................................................................. 66

Installation of supported JRE For information on the supported JRE, refer to GPL Dependencies for

Resiliency Orchestration under Pre-requisites of Section 1. ..................................................................... 66 Host Machines with Virtual IP Address ............................................................................................... 66 Specific Prerequisites ........................................................................................................................... 67

Installation of Agents ................................................................................................................................ 68 Debugging Agent Installation on Windows Server .................................................................................. 76

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

7. INSTALLING AGENTS ON SOLARIS SERVER ......................................................................... 78

Prerequisites for Installing Resiliency Orchestration Agents ................................................................... 78 Solaris Server Requirements ................................................................................................................ 78

Installation of Agents ................................................................................................................................ 79 Debugging Agent Installation on Solaris Server ....................................................................................... 87

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

8. INSTALLING AGENTS ON LINUX SERVER .............................................................................. 90

Installation of Agents ................................................................................................................................ 90 Debugging Agent Installation on Linux Server ........................................................................................ 98

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

9. INSTALLING AGENTS ON HPUX SERVER .............................................................................. 101

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

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

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

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

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

11. INSTALLING RESILIENCY ORCHESTRATION ADVANCED REPORTER ....................... 122

Prerequisite ............................................................................................................................................. 122



GUI Mode Installation of Resiliency Orchestration Advanced Reporter ............................................... 122 Configuring Openreports ................................................................................................................... 126

12. INSTALLING RESILIENCY ORCHESTRATION SITE DASHBOARD ................................. 127

Prerequisites ........................................................................................................................................... 127 GUI Mode Installation of Resiliency Orchestration Site Dashboard ...................................................... 127

13. SILENT MODE INSTALLATION OF RESILIENCY ORCHESTRATION ADVANCED

REPORTER ............................................................................................................................................... 132

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

14. INSTALLING RESILIENCY ORCHESTRATION USING SILENT MODE INSTALLATION

133

Editing Properties File ............................................................................................................................ 134 Resiliency Orchestration Agent Server Silent Mode Installation ........................................................... 136

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

Vault Configuration ................................................................................................................................ 137

15. UPGRADING RESILIENCY ORCHESTRATION SERVER .................................................... 139

16. RESILIENCY ORCHESTRATION SERVER INSTALLATION ON LINUX GRAPHICAL

MODE ........................................................................................................................................................ 140

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

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

Vault Configuration ................................................................................................................................ 143 License Management .............................................................................................................................. 144 Post Upgrade Tasks ................................................................................................................................ 144 Server Memory Management ................................................................................................................. 145 Backup and Fallback Plan ...................................................................................................................... 145

Backup Plan ....................................................................................................................................... 145 Fallback Plan ..................................................................................................................................... 145

17. UPGRADING RESILIENCY ORCHESTRATION ADVANCED REPORTER ....................... 146

18. UPGRADING RESILIENCY ORCHESTRATION AGENTS .................................................... 147

Prerequisites ........................................................................................................................................... 147 Resiliency Orchestration Agent Upgrade [Optional] .............................................................................. 147 Prerequisites before upgrading agents on Linux Server ......................................................................... 148 Limitations .............................................................................................................................................. 148 Upgrading Agents on Linux Server in GUI mode .................................................................................. 148

19. UPGRADING RESILIENCY ORCHESTRATION AGENTS USING SILENT MODE

INSTALLATION ....................................................................................................................................... 158

Prerequisites before upgrading agents on AIX Server ............................................................................ 158 Limitations .............................................................................................................................................. 158 Editing Properties File ............................................................................................................................ 158

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

20. UPGRADING VAULT TO VAULT ................................................................................................ 161

Prerequisites ........................................................................................................................................... 161 Configuring Vault ................................................................................................................................... 161 Vault to Vault Upgrade Steps ................................................................................................................. 161 Steps to Apply patch ........................................................................................................................... 162

Contents

6

21. UPGRADING NONVAULT TO VAULT ........................................................................................ 163

Steps to Apply patch ............................................................................................................................... 163

22. UPGRADING RESILIENCY ORCHESTRATION 7.1 GA TO RESILIENCY

ORCHESTRATION 7.1 P2 LICENSE PATCH ...................................................................................... 164

Prerequisites ............................................................................................................................................ 164 GPL Dependencies for Resiliency Orchestration ................................................................................... 164 GPL Dependencies for IBM Resiliency IBM Resiliency File Replicator ............................................... 164

Tar and Rsync Version Details........................................................................................................... 164 Steps to Apply patch ............................................................................................................................... 164

23. FILE REPLICATION SERVICE THIRD PARTY INSTALLATION ........................................ 167

Third Party Binary Installation for Windows 32/64-Bit ......................................................................... 167 Third Party Binary Installation for Linux 32-Bit .................................................................................... 167 Third Party Binary Installation for Linux 64-Bit .................................................................................... 167 Third Party Binary Installation for AIX .................................................................................................. 168 Third Party Binary Installation for HPUX 64-Bit Itanium ..................................................................... 169 Third Party Binary Installation for HPUX 64-Bit Parisac ...................................................................... 169 Third Party Binary Installation for Solaris_Sparc ................................................................................... 169 Third Party Binary Installation For Solaris_Intel .................................................................................. 171

24. UPGRADING RESILIENCY ORCHESTRATION 7.1 P2 TO RESILIENCY

ORCHESTRATION 7.1 SP1 LICENSE PATCH .................................................................................... 173

Prerequisites ............................................................................................................................................ 173 Steps to Apply patch ............................................................................................................................... 173

25. UNINSTALLING RESILIENCY ORCHESTRATION AGENT NODE .................................... 174

Uninstallation of Resiliency Orchestration Agent Node ......................................................................... 174

26. UNINSTALLING RESILIENCY ORCHESTRATION SERVER AND AGENTS .................... 176

Uninstallation of Resiliency Orchestration Server .................................................................................. 176 Command Prompt .............................................................................................................................. 178

Uninstallation of Agents ......................................................................................................................... 178 Windows ............................................................................................................................................. 179 Solaris ................................................................................................................................................ 179 Linux .................................................................................................................................................. 179 HPUX ................................................................................................................................................. 180 AIX ..................................................................................................................................................... 180

27. INSTALLING RESILIENCY ORCHESTRATION OS COMMAND PROCESSOR ............... 181

Prerequisites ............................................................................................................................................ 181 Overview ................................................................................................................................................ 181 Installing OS Command Processor ......................................................................................................... 182

Extracting Installation File ................................................................................................................ 182 Authorizing APF for TCMD, ZCMD, GCMD, and XCMD ................................................................ 183 Defining Userid SANOVI to RACF/Other Security Program ............................................................ 184

Verifying Sz/OS CP (Command Processor) Install ................................................................................ 184

28. VIEWING THE HTML DASHBOARD ........................................................................................ 187

29. MIGRATING RESILIENCY ORCHESTRATION SERVER TO NEW SERVER WITH SAME

IP 188

30. MIGRATING RESILIENCY ORCHESTRATION SERVER TO NEW SERVER WITH NEW

IP 190

31. TROUBLESHOOTING .................................................................................................................. 192

Subsystem Discovery Failing for Oracle Solution .................................................................................. 192



Agent Not Starting on Windows Server ................................................................................................. 192 Agent Not Stating on Solaris Server ....................................................................................................... 193 Agent Not Stating on Linux Server ........................................................................................................ 195 Agent Not Starting on AIX Server ......................................................................................................... 196 Agent Not Starting on HPUX Server ...................................................................................................... 197 NAT IP ................................................................................................................................................... 197 Web Browser Displays Certificate Error ................................................................................................ 198 Server/Advanced Reporter Installation Fails with UnsatisfiedLinkError ............................................... 198 Port Forwarding ...................................................................................................................................... 199

Verify Firewall Status ........................................................................................................................ 199 Add Exception to Firewall ................................................................................................................. 199 Open Ports ......................................................................................................................................... 199

Create Server Certificate and Server Private Key Reference.................................................................. 200 Analyse HTTPD Logs ............................................................................................................................ 200 Install httpd, SSL Packages .................................................................................................................... 200

Download/Mount the Operating System ISO ..................................................................................... 200 Install the httpd, SSL Packages .......................................................................................................... 200

32. LICENSE INFORMATION ............................................................................................................ 201

GPL License Information ....................................................................................................................... 201

INDEX ......................................................................................................................................................... 202

List of Figures

8

LIST OF FIGURES

Figure 1: IBM Resiliency Orchestration Installer .............................................................................................. 25 Figure 2: IBM Resiliency Orchestration Server Installation - MySQL root password ...................................... 25 Figure 3: IBM Resiliency Orchestration Server Installation - Tomcat Home ................................................... 26 Figure 4: IBM Resiliency Orchestration Server Installation - Introduction ....................................................... 26 Figure 5: IBM Resiliency Orchestration Server Installation – License Agreement........................................... 27 Figure 6: IBM Resiliency Orchestration Server Installation - Choose Install Folder ........................................ 28 Figure 7: IBM Resiliency Orchestration Server Installation – Sanovi User Account ........................................ 29 Figure 8: IBM Resiliency Orchestration Server Installation – User Management System ................................ 29 Figure 9: IBM Resiliency Orchestration Server Installation - Pre-Installation Summary ................................. 30 Figure 10: IBM Resiliency Orchestration Server Installation - Installing ......................................................... 30 Figure 11: IBM Resiliency Orchestration Server Installation - Confirmation message .................................... 31 Figure 12: IBM Resiliency Orchestration Server Installation - Advanced User Server Details 1 ..................... 32 Figure 13: IBM Resiliency Orchestration Server Installation - Advanced User Server Details 2 ..................... 32 Figure 14: IBM Resiliency Orchestration Server Installation - Support User Account ..................................... 33 Figure 15: IBM Resiliency Orchestration Server Installation - System Configuration ..................................... 34 Figure 16: IBM Resiliency Orchestration Server Installation - Installation Completed .................................... 34 Figure 17: IBM Resiliency Orchestration Agent Node Installer ....................................................................... 61 Figure 18: IBM Resiliency Orchestration Agent Node Installation on Linux - Introduction ............................ 61 Figure 19: IBM Resiliency Orchestration Agent Node Installation on Linux - Choose Install Folder .............. 62 Figure 20: IBM Resiliency Orchestration Agent Node Installation on Linux - IBM Resiliency Orchestration

Agent Node IP Address Configuration .............................................................................................................. 62 Figure 21: IBM Resiliency Orchestration Agent Node Installation on Linux - Pre - Installation Summary ..... 63 Figure 22: IBM Resiliency Orchestration Agent Node Installation on Linux - Installing IBM Resiliency

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

Orchestration Agent Node ................................................................................................................................. 64 Figure 24: IBM Resiliency Orchestration Agent Node Installation on Linux - Installation Completed............ 65 Figure 25: IBM Resiliency Orchestration Agent Installer ................................................................................. 69 Figure 26: IBM Resiliency Orchestration Agents Installation on Windows Server - Introduction ................... 69 Figure 27: IBM Resiliency Orchestration Agents Installation on Windows Server - Choose Install Folder ..... 70 Figure 28: IBM Resiliency Orchestration Agents Installation on Windows Server - Choose Agents -

Windows ............................................................................................................................................................ 70 Figure 29: IBM Resiliency Orchestration Agents Installation on Windows Server - Choose Shortcut Folder . 71 Figure 30: IBM Resiliency Orchestration Agents Installation on Windows Server - Agent Configuration ...... 72 Figure 31: IBM Resiliency Orchestration Agents Installation on Windows Server - IBM Resiliency

Orchestration IP Address Configuration ............................................................................................................ 72 Figure 32: IBM Resiliency Orchestration Site Controller IP Address Configuration on Windows server ........ 73 Figure 33: IBM Resiliency Orchestration Agents Installation on Windows Server - Pre-Installation

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

Resiliency Orchestration Agents ....................................................................................................................... 74 Figure 35: IBM Resiliency Orchestration Agents Installation on Windows Server - Starting Agents .............. 74 Figure 36: IBM Resiliency Orchestration Agents Installation on Windows Server - Install Complete ............ 75 Figure 37: IBM Resiliency Orchestration Agent Installer ................................................................................. 80 Figure 38: IBM Resiliency Orchestration Agents Installation on Solaris Server - Introduction ....................... 80 Figure 39: IBM Resiliency Orchestration Agents Installation on Solaris Server - Choose Install Folder ......... 81 Figure 40: IBM Resiliency Orchestration Agents Installation on Solaris Server - Choose Agents - Solaris..... 81 Figure 41: IBM Resiliency Orchestration Agents Installation on Solaris Server - Choose Link Folder ........... 82 Figure 42: IBM Resiliency Orchestration Agents Installation on Solaris Server - Agent Configuration .......... 83 Figure 43: IBM Resiliency Orchestration Agents Installation on Solaris Server - Agent Configuration .......... 83 Figure 44: IBM Resiliency Orchestration Agents Installation on Solaris Server - IBM Resiliency

Orchestration IP Address Configuration ............................................................................................................ 84 Figure 45: IBM Resiliency Orchestration Site Controller IP Address Configuration on Solaris Server ........... 85 Figure 46: IBM Resiliency Orchestration Agents Installation on Solaris Server - Pre-Installation Summary .. 85 Figure 47: IBM Resiliency Orchestration Agents Installation on Solaris Server - Installing IBM Resiliency

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



Figure 49: IBM Resiliency Orchestration Agents Installation on Solaris Server - Install Complete ................ 87 Figure 50: IBM Resiliency Orchestration Agent Installer ................................................................................. 91 Figure 51: IBM Resiliency Orchestration Agents Installation on Linux Server - Introduction ......................... 91 Figure 52: IBM Resiliency Orchestration Agents Installation on Linux Server - Choose Install Folder .......... 92 Figure 53: IBM Resiliency Orchestration Agents Installation on Linux Server - Choose Agents - Linux ....... 92 Figure 54: IBM Resiliency Orchestration Agents Installation on Linux Server - Choose Link Folder ............. 93 Figure 55: IBM Resiliency Orchestration Agents Installation on Linux Server - Agent Configuration ........... 93 Figure 56: IBM Resiliency Orchestration Agents Installation on Linux Server - Agent Configuration ........... 94 Figure 57: IBM Resiliency Orchestration Agents Installation on Linux Server - Agent Configuration ........... 95 Figure 58: IBM Resiliency Orchestration Agents Installation on Linux Server - IBM Resiliency

Orchestration IP Address Configuration ........................................................................................................... 95 Figure 59: IBM Resiliency Orchestration Site Controller IP Address Configuration on Linux server ............. 96 Figure 60: IBM Resiliency Orchestration Agents Installation on Linux Server - Pre - Installation screen ....... 96 Figure 61: IBM Resiliency Orchestration Agents Installation on Linux Server - Installing IBM Resiliency

Orchestration Agents ......................................................................................................................................... 97 Figure 62: IBM Resiliency Orchestration Agents Installation on Linux Server - Starting Agents .................... 97 Figure 63: IBM Resiliency Orchestration Agents Installation on Linux Server - Install Complete .................. 98 Figure 64: IBM Resiliency Orchestration Agent Installer ............................................................................... 102 Figure 65: IBM Resiliency Orchestration Agents Installation on HPUX Server - Introduction ..................... 102 Figure 66: IBM Resiliency Orchestration Agents Installation on HPUX Server - Choose Install Folder ....... 103 Figure 67: IBM Resiliency Orchestration Agents Installation on HPUX Server - Choose Agents - HPUX ... 103 Figure 68: IBM Resiliency Orchestration Agents Installation on HPUX Server - Choose Link Folder ......... 104 Figure 69: IBM Resiliency Orchestration Agents Installation on HPUX Server - Agent Configuration ........ 105 Figure 70: IBM Resiliency Orchestration Agents Installation on HPUX Server - Agent Configuration ........ 105 Figure 71: IBM Resiliency Orchestration Agents Installation on HPUX Server - Agent Configuration ........ 106 Figure 72: IBM Resiliency Orchestration Agents Installation on HPUX Server - IBM Resiliency

Orchestration IP Address configuration .......................................................................................................... 107 Figure 73: IBM Resiliency Orchestration Site Controller IP Address Configuration on HPUX server .......... 107 Figure 74: IBM Resiliency Orchestration Agents Installation on HPUX Server - Pre-Installation Summary 108 Figure 75: IBM Resiliency Orchestration Agents Installation on HPUX Server - Installing IBM Resiliency

Orchestration Agents ....................................................................................................................................... 108 Figure 76: IBM Resiliency Orchestration Agents Installation on HPUX Server - Starting Agents ................ 109 Figure 77: IBM Resiliency Orchestration Agents Installation on HPUX Server - Install Complete ............... 110 Figure 78: IBM Resiliency Orchestration Agent Installer ............................................................................... 113 Figure 79: IBM Resiliency Orchestration Agents Installation on AIX Server - Introduction ......................... 114 Figure 80: IBM Resiliency Orchestration Agents Installation on AIX Server - Choose Install Folder ........... 114 Figure 81: IBM Resiliency Orchestration Agents Installation on AIX Server - Choose Agents - AIX .......... 115 Figure 82: IBM Resiliency Orchestration Agents Installation on AIX Server - Choose Link Folder ............. 115 Figure 83: IBM Resiliency Orchestration Agents Installation on AIX Server - Agent Configuration ............ 116 Figure 84: IBM Resiliency Orchestration Agents Installation on AIX Server - Agent Configuration ............ 117 Figure 85: IBM Resiliency Orchestration Agents Installation on AIX Server - IBM Resiliency Orchestration

IP Address configuration ................................................................................................................................. 118 Figure 86: IBM Resiliency Orchestration Site Controller IP Address Configuration on AIX server .............. 118 Figure 87: IBM Resiliency Orchestration Agents Installation on AIX Server - Pre-Installation Summary .... 119 Figure 88: IBM Resiliency Orchestration Agents Installation on AIX Server - Installing IBM Resiliency

Orchestration Agents ....................................................................................................................................... 119 Figure 89: IBM Resiliency Orchestration Agents Installation on AIX Server - Starting Agents .................... 120 Figure 90: IBM Resiliency Orchestration Agents Installation on AIX Server - Install Complete .................. 120 Figure 91: IBM Resiliency Orchestration Advanced Reporter Installer .......................................................... 123 Figure 92: IBM Resiliency Orchestration Advanced Reporter Installation - MySQL root password ............. 123 Figure 93: IBM Resiliency Orchestration Advanced Reporter Installation - Tomcat Home ........................... 123 Figure 94: IBM Resiliency Orchestration Advanced Reporter Installation - Tomcat Path ............................. 124 Figure 95: IBM Resiliency Orchestration Advanced Reporter Installation - Introduction .............................. 124 Figure 96: IBM Resiliency Orchestration Advanced Reporter Installation - Choose IBM Resiliency

Orchestration Server Folder............................................................................................................................. 124 Figure 97: IBM Resiliency Orchestration Advanced Reporter Installation - Pre-Installation Summary......... 125 Figure 98: IBM Resiliency Orchestration Advanced Reporter Installation - Installing IBM Resiliency

Orchestration Advanced Reporter ................................................................................................................... 125 Figure 99: IBM Resiliency Orchestration Advanced Reporter Installation - Confirmation message .............. 125 Figure 100: IBM Resiliency Orchestration Advanced Reporter Installation - Installation Completed ........... 126

List of Figures

10

Figure 101: IBM Resiliency Orchestration Site Dashboard Introduction ........................................................ 128 Figure 102: IBM Resiliency Orchestration Site Dashboard - MySQL root password ..................................... 128 Figure 103: IBM Resiliency Orchestration Site Dashboard – Choose Tomcat Home ..................................... 129 Figure 104: IBM Resiliency Orchestration Site Dashboard – IP address ........................................................ 129 Figure 105: IBM Resiliency Orchestration Site Dashboard – Google Apis Key ............................................. 130 Figure 106: IBM Resiliency Orchestration – Pre-Installation Summary ......................................................... 130 Figure 107: IBM Resiliency Orchestration - Installing Site Dashboard .......................................................... 131 Figure 108: IBM Resiliency Orchestration Site Dashboard – Installation Completed .................................... 131 Figure 109: Upgrade IBM Resiliency Orchestration Advance Reporter - Metadata Refresh Screen for

Advanced Reporter .......................................................................................................................................... 146 Figure 110: IBM Resiliency Orchestration Agent Installer ............................................................................. 148 Figure 111: Upgrade Agents on Linux Server - Introduction .......................................................................... 149 Figure 112: Upgrade Agents on Linux Server - Choose Install Folder ........................................................... 149 Figure 113: Upgrade Agents on Linux Server - Choose Install Set ................................................................. 150 Figure 114: Upgrade Agents on Linux Server - Choose Agents - Linux ......................................................... 151 Figure 115: Upgrade Agents on Linux Server - Choose Link Folder .............................................................. 151 Figure 116: Upgrade Agents on Linux Server - Agent Configuration ............................................................. 152 Figure 117: Upgrade Agents on Linux Server - Agent Configuration ............................................................. 153 Figure 118: Upgrade Agents on Linux Server – NAT IP Address Configuration ........................................... 153 Figure 119: Upgrade Agents on Linux Server – Site Controller Configuration .............................................. 154 Figure 120: Upgrade Agents on Linux Server - Pre-Installation Summary ..................................................... 154 Figure 121: Upgrade Agents on Linux Server - Installing IBM Resiliency Orchestration Agents.................. 155 Figure 122: Upgrade Agents on Linux Server - Starting Agents ..................................................................... 156 Figure 123: Upgrade Agents on Linux Server - Upgrade Complete ............................................................... 157 Figure 124: Uninstall IBM Resiliency Orchestration Agent Node .................................................................. 174 Figure 125: Uninstall Complete screen ........................................................................................................... 175 Figure 126: Uninstall IBM Resiliency Orchestration Server – Introduction screen ........................................ 177 Figure 127: Uninstall IBM Resiliency Orchestration Server – Uninstalling… screen .................................... 177 Figure 128: Uninstall IBM Resiliency Orchestration Server – Uninstall Complete screen ............................. 178 Figure 129: Uninstall Complete screen ........................................................................................................... 179 Figure 130: Resiliency Orchestration Workflow ............................................................................................. 182 Figure 131: SzCPIVP ...................................................................................................................................... 184



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 company name IBM and IBM Corporation are used interchangeably. ‘Sanovi Cloud

Continuity’ and ‘Resiliency Orchestration’ terms 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 Linux

o Solaris

o HPUX

o AIX

o Windows

Uninstallation of Resiliency Orchestration Server and agents.

Audience

This manual is for administrators who are responsible for installation, configuration and

uninstallation of Resiliency Orchestration Software and its services.


12

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

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

IBM Resiliency File Replicator service installation

Advanced Reporter

New version on Passport Advantage

The IBM Resiliency Orchestration software is available on IBM Passport Advantage site.

The server part of the IBM Resiliency Orchestration server product is to be installed on a server

hardware. Before starting to install the server, the hardware needs to be prepared with supported

RHEL operating system and mariaDB database softeare, as mentioned in the prerequisite section in

this document.

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/Appli

cation 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,

Windows 2012

Enterprise Edition,

AIX6.*, HP-UX 11i, RHEL

5/6/7

Oracle Dataguard

Intel, AMD,

SUN/Sparc, PA-

RISC

Oracle 10g,

Oracle 11g


Windows 2008 Standard

Edition,

Windows 2008

Enterprise Edition,

Windows 2012 Enterprise

Edition,

AIX 6.*, HP-UX 11i, RHEL

5/6/7


14

Agent Platform Database/Appli

cation Version OS Version/Patch

MS SQL Agent Intel, AMD MSSQL 2008,

MSSQL 2012


Edition,

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


Edition,


Edition,


Edition, Windows 2012

Enterprise Edition, AIX

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

5.x, 6.x, 7.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)


Window 2003

IBM Global Mirror

using OS Agent SUN/Sparc, AIX

IBM DSCLI

Version:

6.6.0.345

Solaris 10, AIX 5

PostgreSQL Agent Intel PostgreSQL 9.2 Linux RHEL 5.6

MySQL Agent Intel MySQL 5.5 Linux RHEL 6.x

MS Exchange Agent Intel Not Applicable

Windows 2008 SP2

Enterprise/Windows 2008 R2

Enterprise

MSSQL Agent Intel/AMD

MSSQL 2005,

MSSQL 2008,

MSSQL 2012


Edition, Windows 2008,


Edition

Client Browser Prerequisite

Browser OS Version/Patch Remarks

Firefox 46.x + and

above and Google

Chrome 52.x + and

above

Windows 7 and Windows 8



Note

• 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.

Prerequisites

GPL Dependencies for Resiliency Orchestration

Based on the features, download the GPL dependent binaries from this link GPL dependent

binaries prior to the 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.

Refer to GPL License information for more information on GPL licenses.

Java Version Bundled with Installer

Java Tools OS Version/Patch Remarks

j2re_1.8.0_131 Windows 2008, Windows 2012

j2re_1.8.0_131 HPUX

j2re_1.8.0_131 Solaris 10

j2re_1.8.0_131 Aix v7

j2re_1.8.0_131 Linux 5.0, 6.0 Enterprise Server Edition Database Agent System

j2re_1.8.0_131 Linux 6.0 Enterprise Server Edition IBM Resiliency Orchestration

Server System

You can perform either of the following methods to install IBM Resiliency Orchestration Software:

• 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.

• Silent Mode: Silent mode installation is a noninteractive 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:Installing Resiliency Orchestration Using

Silent Mode Installation.

https://sourceforge.net/projects/gnu-utils/files/binaries/



16

2. Resiliency Orchestration Server

Installation on Linux 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: Error! Reference source not found..

The following are the Hardware and Software requirements for the IBM Resiliency Orchestration

Software:

Physical Dedicated Resource for Two Site Scenario

The following table shows the physical dedicated resource for two sites.

Description Count OS Software Comments

Resiliency

Orchestration (DRM) 1

RHEL

7.3

MariaDB

10.1.19

Tomcat

7.0.55

Refer to System Requirements for Resiliency

Orchestration (DRM) and Resiliency Orchestration

(DRM) HA section for details.

Resiliency

Orchestration (DRM)

- HA

1 RHEL

7.3

MariaDB

10.1.19

Tomcat

7.0.55

Refer to System Requirements for Resiliency

Orchestration (DRM) and Resiliency Orchestration

(DRM) HA section for details.

Site Controller 2 RHEL

7.3

Not

applicable

One site controller for each site (Primary,

Secondary, and so on) is recommended.

System Requirements for Resiliency Orchestration (DRM) and

Resiliency Orchestration (DRM) HA

The system requirements are defined based on the number of endpoints, which needs to be

managed. An endpoint is the server used for production irrespective of physical / logical sites it

spans. It could be a VM, and / or hypervisor and / or a server running an application / software that

needs to be protected. The following are the system requirements for Resiliency Orchestration and

Resiliency Orchestration HA.

Number of

Endpoints

Managed

Resiliency

Orchestration

Server Memory

Resiliency

Orchestration

Server Cores (CPU

Intel Xeon

2.27GHz)

Resiliency Orchestration Server

Disk Partition Recommendation

100 8 GB 4 The following are Resiliency

Orchestration Server Disk Partition

recommendations to manage 100, 200,

and 500 endpoints:

• /opt: 50 GB (For Resiliency

Orchestration Binaries)

• /opt/$DRM$/var/log: 100 GB

(Debug logs of RO/DRM)

• /var: 100 GB (Maria DB Volume)

200 8 GB 6

500 8 GB 8



• /backup: 100 GB (Maria DB

Backup)

• /boot: 2 GB

• /swap: 2 times the RAM size


Orchestration Server Disk Partition

recommendations to manage 1000, 1500,

and 2000 endpoints:



• /opt/$DRM$/var/log: 200 GB

(Debug logs of RO/DRM)

• /var: 200 GB (Maria DB Volume)

• /backup: 200 GB (Maria DB

Backup)

• /boot: 2 GB


1500 20 GB 12

2000 24 GB 12

As a best practice, you need to confirm that storage and network, for example, RAID protected

storage, dual network interfaces, and so on has no single point of failure.

System Requirements for Site Controller with Remote Agents

The following are system requirements for Site Controller on which only remote agents are

deployed.

Number of

Endpoints

Managed

Resiliency

Orchestration Site

Controller

Memory

Resiliency

Orchestration Site

Controller Cores

(CPU Intel Xeon 2.27

GHz)

Resiliency Orchestration Site

Controller Disk Partition

Recommendation


Orchestration Site Controller disk

partition recommendations:



• /opt/$Agents$/remote: 200

GB

• /var: 50 GB

• /boot: 2 GB


100 16 GB 2

200 32 GB 4

System Requirements for Site Controller with Local Agents

The following are system requirements for Site Controller on which only local agents are deployed

on end point.


18

Number of

Endpoints

Managed

Resiliency

Orchestration

Site Controller

Memory

Resiliency

Orchestration Site

Controller Cores

(CPU Intel Xeon

2.27GHz)

Resiliency Orchestration Site

Controller Disk Partition

Recommendation



partition recommendations to manage

100, 200, and 500 endpoints:



• /opt/$Agents$/remote: 200 GB

(optional but recommended)

• /var: 50 GB

• /boot: 2 GB


200 8 GB 4

500 8 GB 4



partition recommendations to manage

1000 endpoints:



• /opt/$Agents$/remote: 200 GB

(optional but recommended)

• /var: 50 GB

• /boot: 2 GB


As a best practice, you need to confirm that storage and network, for example, RAID protected

storage, dual network interfaces, and so on has no single point of failure. You can add more Site

Controllers for additional end points based on the information shown in this section.

System Requirements for Agents Deployed on Endpoint

• Agents on the endpoint needs upto 256 MB memory and upto 10 GB disk space

• If IBM Resiliency File Replicator (optional software) is also deployed, additional 1.25

GB memory and upto 10 GB disk space is needed.

Site controller augments by acting as a gateway for the set of agents for communicating to

Resiliency Orchestration Server. Site controller can manage its agents, when Site Controller is

installed within LAN, it helps in reducing the bandwidth usage as the communication over WAN to

Resiliency Orchestration Server is greatly reduced.

Site Controller is mandatory for production deployments of Resiliency Orchestration, Site

Controller is a facilitator between agents and RO server, when Site Controller goes down, agents

are not available and hence no monitoring and management of DR is compromised for the

endpoints managed by that Site Controller until it is up.

When to have additional Site Controller will be at the beginning of the implementation, same as

Resiliency Orchestration server. However, unlike Resiliency Orchestration Server, it may be started

with appropriate sizing of site controller during implementation and later keep adding additional

site controllers (if implementation can support the dynamics of increasing resource requirements).

Note that site controller can address scale to an extent but scale needs to be looked holistically. The



recommendation for additional site controller is not really useful as it will be limited by the scale of

Resiliency Orchestration Server.

Installation of Resiliency Orchestration Server

Perform the following steps on dedicated Linux server to install and setup the IBM Resiliency

Orchestration Server:

1. Install either of the following Linux Enterprise Server OS (RHEL 7.1, 7.3):

• Red Hat Enterprise Linux 7.1 with mariaDB 10.1.17

• Red Hat Enterprise Linux 7.3 with mariaDB 10.1.19

2. Install the Tomcat 7.0.55.0

3. Install the IBM Resiliency Orchestration Server Software.

4. Set up the environment.

The following sections describe the procedure 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 MariaDB 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 the following ports with

the IBM Resiliency Orchestration Server:

• 8443: The port 8443 needs to be opened for secure GUI access

• 80: The port 80 needs to be opened for HTTP for IBM upgrade assist

• 45443: The port 45443 needs to be opened for secured agent communication

If agentless method is used, 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. IBM Resiliency IBM Resiliency File Replicator must be enabled on port 46443 (listening

port in agent server) for security purposes.

4. If Agentless method is being used, the following additional prerequisites have to be met on

the managed host:

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


20

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 prerequisites 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, 145, 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 and so

on) uses RPC extensively and hence good range is required. To configure this

custom range, you need to change registry and server reboot is required.

For detailed info, refer to the online help at IBM Resiliency Orchestration.

Additional Settings on File Replication subsystem

Firewall setting: Port 46443 and 46001, where IBM Resiliency File Replicator service is

listening should be open for access from Resiliency Orchestration Server.

Note

• The 46000 port should be opened for nonsecure communication.

• If Firewall settings are “Yes”, 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 to

update the Bash. For example, run the following command to update a Red Hat Enterprise

Linux 6.4 system.

3. Update bash with latest available version (minimum required bash version is bash-4.1.2-

15.el6_5.2).

Installation of MariaDB

For information on installing MariaDB 10.1.19 Server and client software on RHEL 7, refer to the

MariaDB 10.1.19 documentation in the following location:

https://downloads.mariadb.org/mariadb/10.1.19/

Installing Tomcat

For installing Tomcat, refer to the following location:

https://tomcat.apache.org/download-70.cgi


22

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.

The user with root privileges needs to perform the following manual steps if firewall enabling is

required:

1. Perform the following on the Resiliency Orchestration machine:

a) The following ports need to be opened:

22, 80, 45443, 8443

Note: 45443 is the default secure port on the Resiliency Orchestration local

agent.

b) Enable firewall on Resiliency Orchestration Server: The following command

needs to be executed to enable firewall on Resiliency Orchestration Server on

RHEL 7:

systemctl start firewalld.service systemctl status firewalld.service

2. Perform the following on the Local Agent machine:

a) Open the following ports with root user:

22, 80,45443

Note: Open the port 45000 for nonsecure communication

b) Start the firewall

service iptables start

Check the status

service iptables status

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:

1) Check that /etc/sysconfig/ip6tables has the entries for the ports opened

2) Start the firewall

service ip6tables start

3) Check the status service ip6tables status



Note: The output for this is similar to the output of the iptables.

The “/etc/sysconfig/ip6tables” file on local agent machine should have the below contents. [root@oemfitln7 opt]# cat /etc/sysconfig/ip6tables # Firewall configuration written by system-config-firewall # Manual customization of this file is not recommended. *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT -A INPUT -p ipv6-icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT -A INPUT -m state --state NEW -m tcp -p tcp --dport 45443 -j ACCEPT -A INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT -A INPUT -j REJECT --reject-with icmp6-adm-prohibited -A FORWARD -j REJECT --reject-with icmp6-adm-prohibited COMMIT The “/etc/sysconfig/ip6tables” file on the Resiliency Orchestration machine should have the below contents:

B) [root@oemfitln10 bin]# cat /etc/sysconfig/ip6tables

# Firewall configuration written by system-config-firewall # Manual customization of this file is not recommended. *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT -A INPUT -p ipv6-icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT -A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT -A INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT -A INPUT -m state --state NEW -m tcp -p tcp --dport 8083 -j ACCEPT -A INPUT -m state --state NEW -m tcp -p tcp --dport 45443 -j ACCEPT -A INPUT -j REJECT --reject-with icmp6-adm-prohibited -A FORWARD -j REJECT --reject-with icmp6-adm-prohibited COMMIT

C) Below exit codes will be logged in case of failure of the setup for httpd in $EAMSROOT/var/log/httpdconsole.log

#Exit Codes meanings are as follows: #10-/etc/hosts file couldnot be modified with the required mapping [ipaddress localhost hostname] #11-Unable to process the /etc/hosts file to support/check the required [ipaddress localhost hostname] mapping


24

#12-/etc/hosts file couldnot be found #13-setsebool command couldnot run #14-httpd process couldnot be restarted #15-httpd process couldnot be started #16-httpd.conf file couldnot be modified #17-httpd.conf file not found #18-httpd not installed

Installation of Resiliency Orchestration Server Software

This software is packaged into an image file called install.bin on IBM Resiliency Orchestration is

available at IBM Passport Advantage site. 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 MariaDB 10.1.19 (for RHEL 7.3), MariaDB 10.1.16 (for RHEL 7.1) 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 IBM Passport Advantage site.

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

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

or sudo ./install.bin (incase sudo user)

Note

Java will be installed automatically after execution of this command.

Make sure that you have free space of approximately 2 GB in /tmp directory, before

executing the above command.

If server hardening is performed, you need to mention sudo prior to 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 MariaDB 10.1.19

root password window is displayed.

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

5. Enter the password for the MariaDB 10.1.19 root user.

6. Click Next. The Tomcat Home window is displayed (Version 7.0.55)

Note

Click the Cancel button to quit the installation.


26

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.

$TOMCAT_HOME or {TOMCAT_HOME}placeholder will use the specified folder, for

example, /opt/softwares/tomcat7.

8. Click Next, the Introduction window is displayed.

Figure 4: IBM Resiliency Orchestration Server Installation - Introduction

9. Click Next. The License Agreement window will be displayed as shown in the following

figure:



Figure 5: IBM Resiliency Orchestration Server Installation – License Agreement

10. 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 and then click Next. A pop-up is shown

which allows the user to either Accept the License

Agreement or to Quit.

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


28

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

12. Select a path to install the software by clicking Choose. $EAMSROOT or

{EAMSROOT}placeholder that is referred in this document will point to this folder. Click on

Next button.

The Sanovi User Account window is displayed.

Note

A user account with user name “sanovi” will be created for use by IBM Resiliency

Orchestration. This user will be used for starting, stopping IBM Resiliency Orchestration

server, IBM Resiliency Orchestration user interface, IBM Resiliency Orchestration agents.



Figure 7: IBM Resiliency Orchestration Server Installation – Sanovi User Account

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

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

14. Select the appropriate User Management System type. The two options are: Basic User

Management System and Advanced User Management System.


30

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

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

16. Go through the pre-installation summary to verify the inputs provided. If you want to change

the inputs, click Previous and modify.

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

Figure 10: IBM Resiliency Orchestration Server Installation - Installing




18. 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 11: IBM Resiliency Orchestration Server Installation - Confirmation message

19. 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:

# sudo mysqldump –u root –-databases panaces pfr –R –-triggers -p >

backup_file_name.sql

# Drop the existing databases if they already exist

a. sudo mysqladmin –u root drop panaces

b. sudo mysqladmin –u root drop pfr # sudo mysql -u root < $EAMSROOT/lib/mysql_schema_InnoDB.sql

# sudo mysql -u root < $EAMSROOT/lib/pfr.sql

# sudo $EAMSROOT/installconfig/importTemplateEvents.sh

20. 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.


32

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

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

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



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

22. 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. Reenter the password in the

Confirm Password box

Note

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

23. 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.


34

Figure 15: IBM Resiliency Orchestration Server Installation - System Configuration

24. 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.

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

installation.

Figure 16: IBM Resiliency Orchestration Server Installation - Installation Completed

26. 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 the $TOMCAT_HOME/webapps/PanacesGUI/scripts/ folder.

Unzip ThirdPartyJSLib.zip in the $TOMCAT_HOME/webapps/PanacesGUI/scripts/ folder.

Remove ThirdPartyJSLib.zip from the $TOMCAT_HOME/webapps/PanacesGUI/scripts/

folder.

2. If you would like to use the vault integration feature of the product, perform the following

instructions:

a. Confirm 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:

• {TOMCAT_HOME}/webapps/PanacesGUI/WEB-INF/lib

• {TOMCAT_HOME}//webapps/PanacesGUI/pages/classes/lib

• {TOMCAT_HOME}//webapps/userPortal/WEB-INF/lib

• {TOMCAT_HOME}//webapps/userPortal/pages/classes/lib

• {EAMSROOT}/agents/vault/{yourVaultName}/lib

• {EAMSROOT}/lib


36

Note

• You need to set the execute (770) and Tomcat user group permissions for the

vault integration library files in the TOMCAT_HOME locations.

• You need to set the execute (770) and Panaces user group permissions for the

vault integration library files in the EAMSROOT locations.

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:

• {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

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

Resiliency Orchestration Server.

5. Apply product license key by following the steps given below:

a. Copy the license file to $EAMSROOT/cli folder of the Resiliency Orchestration

server. License key file is available under /License folder inside the ‘Docs’

package of the software download. Name of the license file is

RO_7.2_Generic_license.xml

b. Run the ./ License.sh script in the $EAMSROOT/cli folder.

c. When this script runs successfully, the following prompt will be displayed:

License>

d. Execute the following command on the prompt to apply the license key:

SCCLicense>upload licensekey -l RO_7.2_Generic_license.xml

On successful installation of license, the following message will be displayed:

License installed successfully

Configuring Resiliency Orchestration Server For Optimal

Performance

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 DRM_SERVER_JVM_MEM, which is located at starting lines of

the Resiliency Orchestration startup script named panaces available under $EAMSROOT/bin/.

Default value of this variable is set to -Xmx2048m.



Recommended Settings

Update the following parameters for optimal performance depending on the expected number of

recovery groups for your installation:

No. of

Recovery

Groups

File Name and Path Parameters Value

250 $EAMSROOT/installconfig/panaces.

properties

panaces.mysql.maxconnection

500

$EAMSROOT/installconfig/panaces.

properties

panaces.acp.server.concurrentRequestPro

cessCount

500

/etc/my.cnf max_connections

500

500 $EAMSROOT/installconfig/panaces.

properties

panaces.mysql.maxconnection

1000

$EAMSROOT/installconfig/panaces.

properties


cessCount

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.

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. 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 making these changes, restart as mentioned in Starting and Stopping Resiliency Orchestration

Server.

MariaDB connectivity configuration for Resiliency Orchestration Server

IBM Resiliency Orchestration uses MariaDB 10.1.19 for persistence. During installation, default

MariaDB 10.1.19 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 by the IBM Resiliency Orchestration Server.


38

Configuring Resiliency Orchestration with Different MariaDB User

You can configure IBM Resiliency Orchestration software to use different MariaDB user. Refer to

MariaDB 10.1.19 manual on how to create a new user. The MariaDB 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 MariaDB 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 IBM Resiliency IBM Resiliency File Replicator GUI, 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 MariaDB user password

When password(s) for the MariaDB users 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 MariaDB user password for Resiliency Orchestration Server, run the following

command:

# sudo ./changeDBPassword.sh panaces.mysql.password

3. 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

By default, IBM Resiliency Orchestration Server and Agents communication is secure with TLS

using TLSv1.2 protocol.



Resiliency Orchestration also provides support for lower communication protocols: SSL and

NONSECURE for communication between Resiliency Orchestration Server and Agents.

The property panaces.acp.communicationType in

<EAMS_ROOT>/installconfig/panaces.properties is used to set the communication protocol

between Resiliency Orchestration Server and Agents.

You need to configure the Resiliency Orchestration Server and Agents to use the same

communication type.

Resiliency

Orchestration

Server

New Local Agents Old Local Agents

SECURE SECURE SECURE

NONSECURE NONSECURE NONSECURE

SECUREWITHTLS SECUREWITHTLS (TLS1.2) SECUREWITHTLS (TLS1.0)

The Resiliency Orchestration Server supports backward compatibility for old agents. If the

Resiliency Orchestration Server is configured with SECUREWITHTLS, the user needs to

configure old agents also with SECUREWITHTLS and TLS1.0 protocol is used for communication

with old agents. If the configuration change is performed, the user needs to restart the old agents. If

the old agents are upgraded to newer versions, the TLS1.2 protocol is used for communication.

Some properties enables the user to choose a specific protocol and cipher. If no specific protocol is

mentioned, Resiliency Orchestration Server will accept TLSv1.2, TLSv1.1, and TLSv1.0

connections as follows:

panaces.acp.communicationTLSProtocolVersion = TLSv1.2,TLSv1.1,TLSv1

If no specific cipher is mentioned, a default cipher is used to encrypt and decrypt the data over

Resiliency Orchestration Agent communication as follows:

panaces.acp.communicationTLSCipher = default

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 Sanovi KEYSTORE file/Password(Certificate) is shipped with product.

To use a Customer certificate, get the KEYSTORE file and password from customer.

2. Open server.xml using, sudo vi $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"


40

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/sanovi.keystore"

keystorePass="^vMkT%678#4-06Gjue672Kwo95dzg" compression="on"

compressionMinSize="2048" nocompressionUserAgents="gozilla,traviata"



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"


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 the following command: sudo $EAMSROOT/bin/panaces restart

Port number is not required in the URL while accessing Resiliency Orchestration GUI and IBM

Resiliency IBM Resiliency File Replicator GUI through browser.

For Example: If the user enters in weburl as http://192.168.20.15/PanacesGUI, it auto redirects the

web url to https://192.168.20.15/PanacesGUI

Port Forwarding

This section describes port forwarding from secure https(443) to the following ports:

• Resiliency Orchestration server secure tomcat secure port 8443

• Resiliency Orchestration server non-secure tomcat port 8080

• Resiliency Orchestration features using other ports 8082

Prerequisites for Port Forwarding

The following are prerequisites for port forwarding:

• Httpd service. Apache service should be installed

• Server Certificate

• SSLCertificateKeyFile

• http modules: Mod_ssl, mod_proxy, mod_proxy_http

Configuration

The user needs to perform the following steps for port forwarding configuration:

1. HTTP configuration (/etc/httpd/conf/httpd.conf): The user needs to perform the

following http configuration:

a. Run the following command to enable proxy_module, proxy_http_module, and

mod_ssl module in /etc/httpd/conf/httpd.conf folder of Apache web server.

LoadModule proxy_module modules/mod_proxy.so

LoadModule proxy_http_module

modules/mod_proxy_http.so

LoadModule ssl_module modules/mod_ssl.so

b. Run the following command to provide the path to refer to the ssl.conf file.

Include conf.d/ssl.conf

c. In SSL, specify the following details so that Port 443 should be listening.

Listen 443 ssl

http://192.168.20.15/PanacesGUI

https://192.168.20.15/PanacesGUI


42

Listen 80

d. The user needs to provide the following proxy configuration and forward the

configuration.

ProxyRequests Off

# Control Client Access

<Proxy https://localhost:8443/>Order Deny,Allow

Allow from all

</Proxy>

# Set TCP/IP network buffer size for better throughput (bytes)

ProxyReceiveBufferSize 4096

ServerName localhost

ProxyPass /PanacesGUI https://localhost:8443/PanacesGUI

ProxyPassReverse /PanacesGUI https://localhost:8443/PanacesGUI

ProxyPass /rmi http://IP:8081/rmi

ProxyPassReverse /rmi http://IP:8081/rmi

ProxyPass /rmi http://IP:80/rmi

ProxyPassReverse /rmi http://IP:80/rmi

ProxyPass /IBMRODashboard https://localhost:8443/IBMRODashboard

ProxyPassReverse /IBMRODashboard

https://localhost:8443/IBMRODashboard

ProxyPass /cdrm-ws http://localhost:8080/cdrm-ws

ProxyPassReverse /cdrm-ws http://localhost:8080/cdrm-ws

ProxyPass /rest http://localhost:8082/rest

ProxyPassReverse /rest http://localhost:8082/restote

Timeout 2400

ProxyTimeout 2400

ProxyBadHeader Ignore

ServerRoot "/etc/httpd"

Note: The user needs to perform this configuration, if required.

For Example: If the requreiment is Site Dashboard, the user needs to add

IBMRODashboard proxy entries.

2. SSL configuration (/etc/httpd/conf.d/ssl.conf): The user needs to provide the following

configurations for SSL (specified in bold are configured, you need to specify the certificate

and key path as per customer environment):

a. Comment 443 port https port: The user needs to provide the following details to

configure SSL for listening to 443 https port.

#Listen 443 https

3. Server Certificate: The user needs to specify SSLCertificateFile at a PEM encoded

certificate. If the certificate is encrypted, the server prompts for a pass phrase.

Note: A kill-HUP will prompt again. A new certificate can be generated using the

genkey(1) command.

The user needs to provide the following details to configure SSL server certificate.

SSLCertificateFile /etc/pki/tls/certs/localhost.crt

For Example: You need to provide the following details to configure SSL server

certificate in Resiliency Orchestration server.

SSLCertificateFile /opt/tomcat7/conf/ibm.crt



a. Server Private Key: If the key is not combined with the certificate, you need to

specify the key file.

Note: If you have a RSA and a DSA private key, you can configure the

keys in parallel to also allow the use of DSA ciphers, and so on.

The user needs to provide the following details to configure SSL server private key:

SSLCertificateKeyFile /etc/pki/tls/private/localhost.key

For Example: You need to provide the following details to configure SSL server

private key in Resiliency Orchestration server.

SSLCertificateKeyFile /opt/tomcat7/conf/ibm.key

b. Enable/Disable SSL for this virtual host: The user needs to provide the following

details to enable/disable SSL for the virtual host.

SSLEngine on

SSLProxyEngine on

SSLProxyVerify none

SSLProxyCheckPeerCN off

SSLProxyCheckPeerName off

c. SSL Protocol support: The user needs to provide the following details for SSL

protocol support:

• List the enable protocol levels with which clients will be able to connect.

• Disable SSLv2 access by default.

• Uncomment the following command to Disable all, enable requried #SSLProtocol –ALL +TLSv1 +TLSv1.1 +TLSv1.2

• Enable all, disable required as shown in the following command. SSLProtocol all -SSLv2 -SSLv3

d. Inter-Process Session Cache: You need to provide the mechanism to use and then

the expiring timeout (in seconds) to configure the SSL session cache as shown in

the following snippet:

# SSLSessionCache shmcb:/run/httpd/sslcache(512000) SSLSessionCache dbm:/run/httpd/sslcache

SSLSessionCacheTimeout 300

Using IPTables

IPTables Configuration for HTTPS: For forwarding Incoming Port 443 requests to Port 8443 in

Linux, run the following command in shell terminal.

iptables -A INPUT -i eth1 -p tcp --dport 443 -j ACCEPT


iptables -A PREROUTING -t nat -i eth1 -p tcp --dport 443 -j REDIRECT -

-to-port 8443

Note

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 nonroot user.


44

If any other application is using port 443 on the same server, it may not work.

IPTables Configuration for HTTP: For forwarding Incoming Port 80 requests to Port 8080 in

Linux, run the following command in shell terminal.



iptables -A PREROUTING -t nat -i eth1 -p tcp --dport 80 -j REDIRECT --

to-port 8080

Note

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”


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 "sanovi.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 "sanovi.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.

Logs Retention

Server logs and Site Controller logs are written at $EAMSROOT/var/log and for the remote agent

logs in Site Controller are written at $EAMSROOT/remote/var/log

The logs retention will be default set to 7 days, however this can configurable.

For Resiliency Orchestration Server and Site Controller to configure the log retention update the

purge.server.logfiles parameter in $EAMSROOT/installconfig/panaces.properties

For remote agents in Site Controller to configure the log retention update the purge.server.logfiles

parameter in $EAMSROOT/remote/installconfig/panaces.properties

Fetch Logs

When the panaces is running with nonroot, the system logs will not be fetched until read

permission is granted for the nonroot user. The nonroot user, by default, does not have read

permission for the system logs (/var/log/messages and so on).

Server (OS) Hardening

The following are the steps to harden the Resiliency Orchestration server:

Note

$EAMSROOT will point to the Resiliency Orchestration installation directory.

For Example: /opt/panaces/ is the $EAMSROOT.

a. Set the password for IBM user

passwd sanovi

b. Change to bin directory

cd $EAMSROOT/bin

c. Execute the script to secure the server


46

./serverHardening.sh

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

reboot

e. Since the root user is disabled, Login using sanovi user

f. Change directory to $EAMSROOT

cd $EAMSROOT

g. As the server is hardened now, the commands should use sudo as prefix

For Example, to start Resiliency Orchestration services, you can run the following

command:

sudo ./panaces start

Note

If the Server Hardening script has been executed prior to restarting the server, user needs to

perform the following steps:

1. Go to $EAMSROOT/bin/

2. Run the following command:

sudo SecurityUserInjection.sh.

Starting and Stopping Resiliency Orchestration Server

Starting Resiliency Orchestration Server

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

1. Open a terminal using sanovi user

2. 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

The user needs to perform the following steps to start IBM Resiliency Orchestration Server in

recover mode:



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:

• Open a terminal using sanovi user

• Enter the following command at the command prompt:

sudo $EAMSROOT/bin/panaces restart

Checking Resiliency Orchestration Server Status



sudo $EAMSROOT/bin/panaces status

Resiliency Orchestration Server Remote Services

The user needs to confirm that remote services are running with panaces user

If the services are not running with panaces user, run the following script to stop the services:

sudo ./invokeAgentCommand.sh <agent script> stop <IP> LINUXSERVER

The user needs to run the following script to start remote services:

sudo ./invokeAgentCommand.sh <agent script> start <IP> LINUXSERVER

Note: The invokeAgentCommand.sh script is available at EAMSROOT/bin

Checking Resiliency Orchestration Server Available Modes

You need to perform the following steps to check the available modes of IBM Resiliency

Orchestration Server:



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


48

• 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:


50

Resiliency Orchestration Server Installation on Linux Graphical Mode

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:



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 MariaDB 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:

1. Install the Linux Enterprise Server OS (RHEL 7.1 or 7.3).

2. Install Linux Cluster with these configurations: DLM mode, GFS Shared file system with a

minimum of 30 GB, IP service and script service for MariaDB, and IBM Resiliency

Orchestration.

3. Install the MariaDB 10.1.19 (for RHEL 7.3) standard software and MariaDB 10.1.16 (for

RHEL 7.1). The MariaDB 10.1.19 database should be in the shared disk.

4. Install the IBM Resiliency Orchestration Server Software.

5. 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

1. Install the Linux Enterprise Server OS without firewall settings and MariaDB database

package.

IBM Resiliency Orchestration uses ports 8443 for GUI access and 45443 for agent

communication with the IBM Resiliency Orchestration Server, you need to allow the required

ports when configuring Firewall at Operating System level.

2. 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 MariaDB

Database" are not selected under ‘Server’ list. Do not click “Details” hyperlink to make

further selections.

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

4. 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


52

<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

Use the “clusvcadm” utility to relocate user services between cluster nodes for installation, and

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.

1. 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

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

cd /var/lib

ln –s <shared Cluster Volume>/mysql /mysql

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

shared volume:

mkdir <shared volume> /panaces

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

ls panaces (or) ls

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

export EAMSROOT=/opt/panaces



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

Use the “clusvcadm” utility to relocate cluster to a cluster node, for example, Cluster Node A, and

perform the following steps:

1. Start MariaDB services whenever the system is rebooted by issuing the following command:

# /etc/init/mysql start &

2. Check whether you are able to log in to MariaDB 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:


54


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 MariaDB 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 MariaDB and IBM Resiliency Orchestration applications on the cluster, create the

following scripts files on /opt/panaces/bin folder.

Create Mysqlbat.sh file for MariaDB 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"


56

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 Server OVA

Installation

This chapter outlines the procedures for installing IBM Resiliency Orchestration server OVA.

IBM Resiliency Orchestration Server OVA software is delivered as the following file:

• ResiliencyOrchestration_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.

Installing 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 SanoviCC_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 SanoviSiteController.ova which includes Sanovi

Agent Node and Site Controller binaries.

Uploading the License

Prior to using IBM Resiliency Orchestration server, a valid license should be uploaded.

A valid license can be uploaded anytime and does not require restarting IBM Resiliency

Orchestration Server or its agents. However, IBM Resiliency Orchestration Server should be

running to upload the license.

You need to perform the following steps to upload the license to the IBM Resiliency Orchestration

server:

1. Log in to virtual appliance through SSH.

2. Download the file Docs.tar.Z from Fixcentral or PA and untar it.

The License folder displays the RO_generic_license.xml.tar file along with readme file,

extract the RO_generic_license.xml.tar file to /tmp of RO Server

3. Go to /tmp folder and run the following commands to untar the RO_Generic_license.xml.tar

file


cd /tmp

tar –xvf RO_Generic_license.xml.tar

4. Run the following commands for running the DRMLicense.sh script: cd /opt/panaces/cli

./DRMLicense.sh

Note

Upon running the script, DRMLicense prompt will be displayed:

DRMLicense>

5. Type the following syntax to upload the licensekey:

upload licensekey <-l --licensefile> <licensefile name with path>

For example, DRMLicense>upload licensekey -l /tmp/ RO_Generic_license.xml

6. Press Enter. The License will be uploaded and the message "The license is installed

successfully" is 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 7).

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:

1. Download the Agent Node binaries from the IBM Passport Advantage site.

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

sh SanoviAgentNode.bin (or) ./SanoviAgentNode.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 Panaces 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 7, 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

3. 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

4. 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

5. 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

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

and IBM Resiliency Orchestration Agent Node Address.



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

8. Go through the pre-installation summary to verify the inputs provided. If you want to

change the inputs, click Previous and modify.

9. 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

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


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

Orchestration Agent Node

11. On the Starting Resiliency Orchestration Agents Node window, perform either of the

following:

a. Click Yes to start the agent services automatically.

b. 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.

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

installation.


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


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.

14. Update the following parameter for optimal performance.

No of

groups

File name and Path Parameters Value

250 $EAMSROOT/installconfig/panaces.pro

perties


cessCount

500

250 $EAMSROOT/remote/installconfig/pan

aces.properties


cessCount

500

500 $EAMSROOT/installconfig/panaces.pro

perties


cessCount

1000

500 /$EAMSROOT/remote/installconfig/pan

aces.properties


cessCount

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 IBM Passport Advantage site. 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 Resiliency File

Replicator is automatically installed during installation of IBM Resiliency File Replicator Agent.

Prerequisites 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 needs to incorporate the following requirements:

a. Hardware / Software Requirements: The following are the Windows Server Hardware /

Software requirements:

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

• C drive should have additional 10GB disk size for Agent Software

b. 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.

For 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

For information on the supported JRE, refer to GPL Dependencies for Resiliency Orchestration

under Pre-requisites of Section 1.

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 prerequisites for specific agents; ensure that these prerequisites 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 IBM Passport Advantage site.

2. Files are available in the zipped format in the Agents folder. Extract Files from

WindowsDRMAgents.zip for 32-bit Windows Operating Systems and

Windows64DRMAgents.zip for 64-bit Windows Operating Systems.

3. Go to 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


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


displayed.

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

5. 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.

6. 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.

7. Select the checkbox next to the specific agent to install that agent. You can choose to install

any or all of the agents.


8. Click Next. The Choose Shortcut Folder window is displayed.

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

Folder

9. 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.

10. Click Next. The Agent Configuration window is displayed.

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

11. 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.

12. 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.

13. In a NAT environment, enter the primary and secondary Resiliency Orchestration server’s

public IP. Resiliency Orchestration Agent node address should be the public IP and 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

14. 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



17. 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

18. On the Starting Agents 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 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.

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

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


21. Download GPL dependent binaries for Windows OS Agent.

Windows -32 BIT

installedlocation/bin/cyggcc_s-1.dll

installedlocation/bin/cygiconv-2.dll

installedlocation/bin/cygintl-8.dll

installedlocation/bin/cygwin1.dll

Windows-64-BIT





22. 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:

1. Go to Control Panel.

2. Click Administrative tools on the Control Panel.

3. 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:

• Panaces Agent for MS Windows OS

• Panaces Agent for IBM Resiliency File Replicator

• Panaces Agent for MS SQL Server


• IBM Resiliency File Replicator

• Panaces Agent for Oracle

• Panaces Agent for Oracle DataGuard

• SRDF Agent

4. Right-click on the respective service in the Services window and perform the following

steps:

a. Select Start to start the service.

b. Select Stop to stop the service.

c. Select Restart to restart the service.

7. Installing Agents on Solaris Server

This software is available on the IBM Passport Advantage site. The Agents.zip when unzipped will

result in the Agents folder contain IBM Resiliency IBM 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 Resiliency File

Replicator is automatically installed during the installation of IBM Resiliency IBM Resiliency File

Replicator Agent.



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.

a. Hardware / Software Requirements: The following are the Solaris Server Hardware /

Software requirements:


• If the server is running Sybase, 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, import the time zone from another Solaris

machine into /usr/share/lib/zoneinfo directory.

Note

Ensure that the time settings on IBM Resiliency Orchestration server and the agent

server are in sync.

b. Logs Directory: The server should have enough allocated disk space 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.

For 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


Agents.


1. Download the Agent Installer executable files from the IBM Passport Advantage site.

2. Files are available in the zipped format in the Agents folder. Extract Files from

SolarisIntel_DRMAgent_7.1.zip for Intel based architecture and

SolarisSparc_DRMAgent_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.

• If server hardening is performed, you need to mention sudo prior to 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


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


displayed.


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


Default Folder to restore the default path. The default path is /opt/panaces. It is

recommended that you use the default path displayed.

6. 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.

7. Select the checkbox next to the specific agent to install that agent. You can choose to install

any or all of the agents.

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

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

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

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

b. Select Other to enter a specific path.

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



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

11. Enter Sybase JDBC driver jar file location.

12. Click the Choose button to select the jar file location.

Note

Confirm that the selected path has all the JDBC driver jar files.

13. 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

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


15. In a NAT environment, provide the Primary and secondary Resiliency Orchestration server’s

public IP. Resiliency Orchestration Agent node address should be the public IP & NAT IP


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.

16. 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




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


Click Yes to start the agent services automatically.


Click No to start the agent services manually.

Note


window.


21. 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.



# nohup ./PFRAgent.sh start &

# nohup ./PFRAgent.sh stop &

Sybase Agent

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



# nohup ./SybaseAgent.sh start &


# nohup ./SybaseAgent.sh stop &

SRS Agent

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



# nohup ./SRSAgent.sh start &

# nohup ./SRSAgent.sh stop &

Oracle Agent

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



# nohup ./OracleAgent.sh start &

# nohup ./OracleAgent.sh stop &

TrueCopy

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



$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 available on the IBM Passport Advantage site 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 Resiliency File

Replicator is automatically installed during installation of IBM Resiliency IBM Resiliency File

Replicator Agent.


This section outlines the steps to install all agents on Linux (RHEL 7) server. Additional steps that

you must perform for specific agents are also included within.

Note


Agents.



2 Browse through IBM Resiliency Orchestration software from the downloaded path and go to

the folder to the folder Agent/Linux_DRMAgent_7.1.zip for 32-bit Linux Operating Systems

or Agents/ Linux64_DRMAgent_7.1.zip for 64-bit Linux Operating Systems.

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


Note




command.

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

the following screen.

Note

If the RHEL version is not 7, 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



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.



c. 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



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

and IBM Resiliency Orchestration Agent Node Address. In a non-NAT environment NAT IP


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 and

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 troubleshoot Nat IP, refer to

Troubleshooting NAT IP on 197.

17 Click Next. Enter Site Controller IP Address, if required.

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

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

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

19 Go through the pre-installation summary to verify the inputs provided. If you want to change



20 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

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

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

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



Note


window.


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

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

24 Click Done to complete the installation process.

25 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.d

Linux OS Agent




# 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


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

1. Go to $EAMSROOT and enter the following command to start the agent manually:

# nohup ./dataguardagent.sh start &

2. Enter the following command to start the agent manually:

# nohup ./dataguardagent.sh stop &

PostgreSQL Agent

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



# nohup ./PostgresAgent.sh start &

# nohup ./PostgresAgent.sh stop &

Listing the Agents that are Running





9. Installing Agents on HPUX Server

This software is available on the IBM Passport Advantage site. 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 Resiliency File


IBM 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


Note

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




the folder Agent/HPUX_DRMAgent_7.1.zip.

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


Note




command.





Introduction window is displayed.

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


displayed.


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



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 &



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 197.

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

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




Note


window.


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




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 -


# nohup ./HPUXOSAgent.sh start &

# nohup ./HPUXOSAgent.sh stop &



PFR Agent





Oracle Agent









# nohup ./DataGuardAgent.sh start &

# nohup ./DataGuardAgent.sh stop &





10. Installing Agents on AIX Server This software is available on the IBM Passport Advantage site. 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 Resiliency File




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: The following are the AIX Server Hardware / Software

requirements:


• Confirm that the AIX machine is set to a desired time-zone.

AIX 6.1 TL7 (6100-07) or later is required to work with Java 8. For details, refer to

https://www-01.ibm.com/support/docview.wss?uid=isg3T1022644#requirements

Note

Confirm 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.

https://www-01.ibm.com/support/docview.wss?uid=isg3T1022644#requirements



This section outlines the steps to install all agents on AIX server. Additional steps that you must


Note


Agents.


1 Download the server binaries from the IBM Passport Advantage site.


the folder to the folder Agent/AIX_DRMAgent_7.1.zip.

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


Note




command.






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


displayed.

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


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 &



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 197.

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

Orchestration IP Address configuration

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

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




Note


window.


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




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.d

AIX OS Agent




# nohup ./AIXOSAgent.sh start &

# nohup ./AIXOSAgent.sh stop &



PFR Agent







Oracle Agent








Alternatively, the following perform the following steps to start or stop the agent manually:

1. Go to $EAMSROOT and enter the following command to start the agent manually:

# nohup ./DataGuardAgent.sh start &

2. Enter the following command to stop the agent manually:

# nohup ./DataGuardAgent.sh stop &





11. Installing Resiliency Orchestration

Advanced Reporter

IBM Advanced Reporter is the licensed feature. You can install it in GUI mode only. It is

supported only in Linux platform, to be installed on Resiliency Orchestration Server.

Prerequisite

IBM Resiliency Orchestration server should 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 IBM Passport Advantage site.

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.


Note


3 After executing the command IBM Resiliency Orchestration Advanced Reporter installation

starts with the following screen.


Figure 91: IBM Resiliency Orchestration Advanced Reporter Installer

Warning message is shown if Linux version is not RHEL 5 or RHEL 6. User can still Continue.

4 After displaying the IBM Resiliency Orchestration Advanced Reporter Installer screen,

the MariaDB root password window is displayed.

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

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

Warning message is shown if MySQL version is not 5.1.34 or 5.5. User can still Continue.

Note


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 Sanovi 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


Configuring Openreports

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 Confirm that the user of openreports3.2.tar.gz file has Tomcat permissions, if the user does

not have Tomcat permissions, change the Tomcat permissions (Tomcat user and Tomcat user

group) manually.

3 Remove existing openreports.war(which is 0kb) file and open reports folder if exists already.

4 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

5 Rename the existing openreports folder as openreports_bak

6 Prior to copying openreports.war, change the permission of $TOMCAT_HOME

/webapps/openreports/WEB-INF to 757 temporarily.

7 Copy $TOMCAT_HOME/openreports.war to $TOMCAT_HOME/webapps. Revert the

permission of $TOMCAT_HOME /webapps/openreports/WEB-INF when you have copied

openreports.war.

8 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

9 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

10 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

11 Delete the openreports_bak folder.

12 Go to $EAMSROOT/lib.

13 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

14 copy classes folder from $EAMSROOT/lib/openreports_dependencies/WEB-INF to

$TOMCAT_HOME/webapps/openreports/WEB-INF

15 copy etl.jar from $EAMSROOT/lib/openreports_dependencies/WEB-INF/lib to

$TOMCAT_HOME/webapps/openreports/WEB-INF/lib

16 Login to mysql by executing the following commands at mysql prompt

• use advancedreporter;

• update REPORT_DATASOURCE set DRIVER='org.mariadb.jdbc.Driver';

17 Restart IBM Resiliency Orchestration services to access open reports.




Site Dashboard

IBM Resiliency Orchestration Site Dashboard is the licensed feature. You can install it in GUI

mode only. It is supported only in Linux platform, to be installed on Resiliency Orchestration

Server.

Prerequisites

The following are the prerequisites for installing Resiliency Orchestration site dashboard:

• IBM Resiliency Orchestration server should be already installed in the machine, else

installer will display an error and quit.

• The Google map API key has to be generated to use google maps. Refer to

https://developers.google.com/maps/premium/prelaunch-checklist for details.

GUI Mode Installation of Resiliency Orchestration Site Dashboard

You need to perform the following steps to install the site dashboard:

1 Download the Site Dashboard binaries from the IBM Passport Advantage site.

2 IBM Resiliency Orchestration Site Dashboard can be installed only if you log in as Root user.

Run the following command in the Site Dashboard folder.


Note


3 After executing the command, IBM Resiliency Orchestration Site Dashboard installation

starts with the IBM Resiliency Orchestration Site Dashboard Introduction window is

displayed as shown in the following figure:

Figure 101: IBM Resiliency Orchestration Site Dashboard Introduction

4 After displaying the IBM Resiliency Orchestration Site Dashboard Introduction screen,

the IBM Resiliency Orchestration Software License Agreement window is displayed as

shown in the following figure:

Figure 102: IBM Resiliency Orchestration Site Dashboard - MySQL root password

Note


5 Click Next. The Choose Tomcat home Folder window is displayed as shown in the following

figure:


Figure 103: IBM Resiliency Orchestration Site Dashboard – Choose Tomcat Home

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

7 Click Next. The IBM Resiliency Orchestration IP Address window is displayed as shown in

the following figure:

Figure 104: IBM Resiliency Orchestration Site Dashboard – IP address

8 Enter the IP address of the current machine.

9 Click Next. The IBM Resiliency Orchestration Google Apis Key window is displayed as

shown in the following figure:

Figure 105: IBM Resiliency Orchestration Site Dashboard – Google Apis Key

10 Click Next. The IBM Resiliency Orchestration Pre-Installation Summary screen is

displayed as shown in the following figure:

Figure 106: IBM Resiliency Orchestration – Pre-Installation Summary

Note

Read through the preinstallation summary to verify the inputs provided. If you want to

change the inputs, click Previous and modify.

11 Click Install. The IBM Resiliency Orchestration Installing Site Dashboard window is

displayed.


Figure 107: IBM Resiliency Orchestration - Installing Site Dashboard

12 After the installation is complete, the IBM Resiliency Orchestration Installation

Completed window is displayed indicating successful installation.

Figure 108: IBM Resiliency Orchestration Site Dashboard – Installation Completed


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 IBM Passport Advantage site.

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 IBM Passport Advantage site and copy it to /tmp folder.

cp Server/PanacesServerInstaller.properties /tmp/

cp AdvancedReporter/install.bin /tmp

2 Open the properties file by using the following command:

vi /tmp/PanacesServerInstaller.properties

3 Modify the MariaDB_ROOT_PASSWORD to modify MariaDB 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.



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 IBM Passport Advantage site.

Note

Confirm that the hardware and software configuration required for IBM Resiliency Orchestration

installation is in place. For a complete list of supported configurations, refer to 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, prior to when you run the installation program in Silent mode, you need to

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. Download the binaries and properties files from the FTP server to a location on the intended

Resiliency Orchestration server, assuming binary file and property files are available in

/opt/Server and the logged in user has sudo permissions equivalent to root

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

cd /opt/Server

sudo vi PanacesServerInstaller.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/sanovi.keystore

USER_INSTALL_DIR

Enter the default path for the directory to install the


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.

STOP_IBM_RESILIENCY_ORCHESTR

ATION_AND_UNINSTALL

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.

MariaDB_ROOT_PASSWORD

Enter the password to connect to the MariaDB

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_ROL

ES NA

Enter the searchbase string for AD/

LDAP server.

LICENSE_ACCEPTED Enter the value “TRUE”

SUPPORT_USER_PASSWORD

Enter the password for support user(default

=Drmsupport123$).

TOMCAT_HOME Enter the Tomcat Installation directory path.

PanacesAgentsInstaller.properties file:

Keyword Description


MSSQL_AGENT_WINDOWS_CHK

Sanovi 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


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

Keyword Description

USER_INPUT_RESULT_JAR_SYBASE


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_P

ANACES_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_CONTR

OLLER_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. sudo /opt/Server/install.bin –f /opt/Server/PanacesServerInstaller.properties

5. Follow the Post Installation Steps.

Note:

Restart the Panaces 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 Panaces service.

Note: Re-start Panaces if Panaces 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 sanovi.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 Refer to Resiliency Orchestration 7.2 Upgrade Guide to upgrade Sanovi Cloud Continuity 7.1

SP1/SP2/SP4/SP6 to Resiliency Orchestration Server 7.2.

Resiliency Orchestration Server Installation on Linux

Graphical Mode


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. Download the Binaries and properties files from the IBM Passport Advantage site to a

location on the intended Resiliency Orchestration server, Assuming binary file and property

files are available in /opt/Server and the logged in user has sudo permissions equivalent to

root


cd /opt/Server

sudo vi PanacesServerInstaller.properties



PanacesServerInstaller.properties file: The following table describes the keywords in the

PanacesServerInstaller.properties file.



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/sanovi.keystore

USER_INSTALL_DIR

Enter the default path for the directory to install the


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.

STOP_IBM_RESILIENCY_ORCHESTR

ATION_AND_UNINSTALL

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.



MariaDB_ROOT_PASSWORD

Enter the password to connect to the MariaDB

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_ROL

ES NA

Enter the searchbase string for AD/

LDAP server.

LICENSE_ACCEPTED

Enter the value “TRUE” Otherwise, the Installation

will display an error message as EULA is not

accepted.

SUPPORT_USER_PASSWORD

Enter the password for support user(default

=Drmsupport123$).

TOMCAT_HOME Enter the Tomcat Installation directory path.

PanacesAgentsInstaller.properties file: The following table describes the keywords in the

PanacesAgentsInstaller.properties file.

Keyword Description





SRS_AGENT_CHK

ORACLE_AGENT_CHK


HK

TRUE_COPY_AGENT_CHK

SRDF_AGENT_CHK

HPXP_AGENT_CHK

DB2_AGENT_CHK

POSTGRES_AGENT_CHK




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.

Keyword Description


Enter the full path of the directory where the Oracle



USER_INPUT_RESULT_JLIB_ORA Enter the full path of directory where jar libraray

files are located. Usually it is $ORACLE_HOME/jlib


Enter the full path of the directory where the Sybase


For example: <sybase installation path>/jConnect-

5_5/classes.







PANACES_AGENT_NODE_ADDRESS Enter the IP address of IBM Resiliency Orchestration

Agent.


Displays the IBM Resiliency Orchestration classpath.

By default, the following classpath is displyed:







AGENTS_START_YES

Enter 1 if you want to start the agents automatically

after the IBM Resiliency Orchestration installation.


Refer to the Starting and Stopping of Agents in the

respective Installation of Agents chapter in this guide

for more information.


OGIN

By default, "postgres" will be pre-filled as the login

ID.




CHOSEN_INSTALL_SET=

Enter Upgrade


4. Execute the following command to start the installation. sudo /opt/Server/install.bin –f /opt/Server/PanacesServerInstaller.properties

5. Follow the Post Installation Steps.

Note

Restart the Panaces 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

confirm that services are stopped prior to uninstallation in silent mode.

Starting Silent Mode Installation on Windows System








For Example: install.exe -f c:\\Progra~1\\panaces\\PanacesAgentsInstaller.properties

Note








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 prior to starting Panaces service.

Note: Restart Panaces if Panaces 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 sanovi.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.

License Management

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, displays 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.

The 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, the new user name is also reflected. Existing password will not

be changed on upgrade.

The drmadmin 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, perform the following tasks:

• 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 MariaDB 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 DRM_SERVER_JVM_MEM, which is located at starting lines of

the Resiliency Orchestration startup script DRM Install root/bin/panaces. Default value of this

variable is set to –Xmx2048m.

The following are the recommended values:

Configuration with more than 100 groups: -Xmx4072m is recommended.

Backup and Fallback Plan

Backup Plan

A. Take the backup of the following files and directories:

1. IBM Server MariaDB Metadata sudo 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 Panaces Server is configured with Linux OS agent:

B. Agent Binaries

C. 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. Run the following command to drop the existing databases if they already exist: a. sudo mysqladmin –u root drop panaces

b. sudo mysqladmin –u root drop pfr

c. sudo mysqladmin –u root drop advancedreporter

2. Restore the MariaDB Metadata from backup. sudo mysql -u root < backupfilename.sql

3. Restore the IBM Server software installation directory (7.1).

4. Startup IBM Server Services.


Advanced Reporter

Upgrading IBM Resiliency Orchestration Advanced Reporter is similar to fresh Installation of

Advanced Reporter. Refer to the chapter, Installing IBM Advanced Reporter for details.

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 109: Upgrade IBM Resiliency Orchestration Advance Reporter - Metadata Refresh Screen for

Advanced Reporter



Agents

The upgrade of agents on customer servers may be done any time after the IBM Resiliency

Orchestration server software is upgraded.

Prerequisites

The following are prerequisites for upgrading Resiliency Orchestration Agents:

• All the agents need to be stopped before performing any agent upgrade process.

• Kill rsync.exe processes started by Panaces agents (PFR), if any.

• The user needs to add a permanent firewall rule to allow port 8081(jetty) and 8083(RMI)

Note: If the firewall is off, adding a permanent firewall rule is not required.

• The user needs chmod 744 permissions to upload binaries to jackrabbit repository.

Resiliency Orchestration Agent Upgrade [Optional]

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.

The following are the steps to upgrade Resiliency Orchestration agent:

1. For each identified Functional Group, move the Group to maintenance mode.

2. Upgrade the agent software on all servers using Agent installer 7.1.

Upgrading Agents on Linux Server

Prerequisites before upgrading agents on Linux Server

Stop all the agents.

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

the above command.

Limitations

• Agents should be upgraded first and then IBM Resiliency IBM Resiliency File Replicator is

upgraded, when IBM Resiliency IBM Resiliency File Replicator is installed with agents.

• During upgrade, use old EAMSROOT as installation path.

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:

To upgrade the agents, perform the following steps:

1. Download the agent binaries from the IBM Passport Advantage site.

2. Browse through IBM Resiliency Orchestration software from the downloaded path and go to

the folder to the folder Agent/Linux_DRMAgent_7.1.zip for 32-bit Linux Operating Systems

or Agents/ Linux64_DRMAgent_7.1.zip for 64-bit Linux Operating Systems.

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,


▪ If server hardening is performed, you need to mention sudo prior to the above

command.

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



5. After displaying the IBM Resiliency Orchestration Agent Installer screen, the



Figure 111: Upgrade Agents on Linux Server - Introduction


displayed.

Figure 112: Upgrade Agents on Linux Server - Choose Install Folder



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

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 113: Upgrade Agents on Linux Server - Choose Install Set

9. The Choose Agents - Linux window is displayed.


Figure 114: Upgrade Agents on Linux Server - Choose Agents - Linux

10. The list of agents available is displayed on the Choose Agents - Linux window. Select the


of the agents.

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

Figure 115: Upgrade Agents on Linux Server - Choose Link Folder

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



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


Figure 116: Upgrade Agents on Linux Server - Agent Configuration

14. Enter DB2 instance user login ID and click Next.


Figure 117: Upgrade Agents on Linux Server - Agent Configuration

15. Enter the DB2 file location. Click the Choose button to select the jar file location.

16. Click Next. The NAT IP Address Configuration window displays.

Figure 118: Upgrade Agents on Linux Server – NAT IP Address Configuration

17. Enter the NAT IP Address if applicable and click Next.

The Site Controller Configuration window displays.

Figure 119: Upgrade Agents on Linux Server – Site Controller Configuration

18. Enter the Site Controller IP Address if applicable and click Next.

The Pre-Installation Summary window displays.

Figure 120: Upgrade Agents on Linux Server - Pre-Installation Summary





Figure 121: Upgrade Agents on Linux Server - Installing IBM Resiliency Orchestration Agents

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

Figure 122: Upgrade Agents on Linux Server - Starting Agents




Note

The best practice is not to change the default value displayed on the Starting Agents window.


23. Click Next. The Upgrade Complete window is displayed, indicating successful upgrade.


Figure 123: Upgrade Agents on Linux Server - Upgrade Complete

24. Click Done to complete the upgrade process.


Agents Using Silent Mode Installation

Prerequisites before upgrading agents on AIX Server

Stop all the agents.

Limitations

• Agents should be upgraded first and then IBM Resiliency IBM Resiliency File Replicator is

upgraded, when IBM Resiliency IBM Resiliency File Replicator is installed with agents.

• During upgrade, use old EAMSROOT as installation path.


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 IBM Passport Advantage site and copy properties files by running the

following command:

cp Agents/PanacesAgentsInstaller.properties /tmp


▪ Agents(UNIX)

vi /tmp/PanacesAgentsInstaller.properties



PanacesAgentsInstaller.properties file:

Keyword Description



Keyword Description




SRS_AGENT_CHK

ORACLE_AGENT_CHK


HK

TRUE_COPY_AGENT_CHK

SRDF_AGENT_CHK

HPXP_AGENT_CHK

DB2_AGENT_CHK

POSTGRES_AGENT_CHK





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.



Oracle Jar files have been installed.


USER_INPUT_RESULT_JLIB_ORA

Enter the full path of directory where jar library

files are located. Usually it is

$ORACLE_HOME/jlib



Sybase Jar files have been installed.

For example: <sybase installation

path>/jConnect-5_5/classes.







PANACES_AGENT_NODE_ADDRESS Enter the IP address of IBM Resiliency

Orchestration Agent.


Displays the IBM Resiliency Orchestration

classpath. By default, the following classpath is

displayed:







AGENTS_START_YES

Enter 1 if you want to start the agents

automatically after the IBM Resiliency

Orchestration installation.


Refer to the Starting and Stopping of Agents in

the respective Installation of Agents chapter in

this guide for more information.


OGIN

By default, "postgres" will be pre-filled as the

login ID.


Keyword Description



CHOSEN_INSTALL_SET=

Enter Upgrade


Starting Silent Mode Upgrade on Windows System








For Example: install.exe -f c:\\Progra~1\\panaces\\PanacesAgentsInstaller.properties

Note








For Example: For agents ./install.bin –f /Agents/ PanacesAgentsInstaller.properties


20. Upgrading Vault to Vault

Customers who have already configured Vault need to follow the steps in this section.

Prerequisites

1. Vault must be configured in 6.3 SP4.

2. Vault queries must be executed on the Panaces Database. The queries will be in the form of

query parameters and passwords.

3. Vault must be configured in Panaces GUI.

4. Subsystems must be updated/ configured with Vault.

Configuring Vault

The following are the steps to configure vault in 6.3 SP4:

1. Update Panaces configuration by updating the panaces.properties file by setting the

following value. This will enable the vault simulator.sanovi.vault.simulator = 1

2. In 6.3 SP4 we have to add query parameters in MariaDB database for the subsystem in

panaces DB by using following query:

Syntax:

insert into vault_sanovi_db(sysname,accname,password) values(<"sysname">,<"

accname">, <"password">);

For Example:

insert into vault_sanovi_db(sysname,accname,password)

values("sys","acc","Sanovi543");

Note

Ensure that the command syntax, system name, account name and password are correct for

the subsystem.

Vault to Vault Upgrade Steps

1. Stop 6.3 SP4 Resiliency Orchestration server.

2. Copy the script 'VaultToVaultUpgradeUtilitySP4.sh' (IBM Passport Advantage site) to

$EAMSROOT/bin

3. Copy the jar 'VaultToVaultUpgradeSP4.jar' (IBM Passport Advantage site) to

$EAMSROOT/lib

4. Open the script 'VaultToVaultUpgradeUtilitySP4.sh' and modify the variable 'DRMDIR' to

the appropriate EAMSROOT. Run the following codes:

cd $EAMSROOT/bin and execute 'VaultToVaultUpgradeUtilitySP4.sh'

5. Upgrade the server from '6.3 SP4 to 7.1' using the upgrade installer

6. Copy the scripts 'VaultToVaultUpgrade.sh' , 'VaultToVaultUpgradeUtility.sh' and

'VaultUpgradeUtility.sh'(IBM Passport Advantage site) to $EAMSROOT/bin

7. Copy the jar 'VaultToVaultUpgrade.jar' (IBM Passport Advantage site) to $EAMSROOT/lib.

Run the following codes:

cd $EAMSROOT/bin and execute 'VaultToVaultUpgrade.sh'

8. 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.

9. Start Resiliency Orchestration server.

Steps to Apply patch

7.1_35095 TO 7.1_GA

1. Take a backup of $EAMSROOT and $TOMCAT_HOME/webapps, go to webapps folder

and Delete PanacesGUI directory by rm –rf PanacesGUI

2. Take a backup of mysql db schema, mysqldump -u root --databases panaces pfr

advancedreporter –R --triggers > panaces_dump.sql

3. Download 7.1_P1 patch files from IBM Passport Advantage site.

• Server.tar to be downloaded to $EAMSROOT

• Tomcat.tar to be downloaed to $TOMCAT_HOME/webapps/

4. Run the command cd $EAMSROOT and untar Server.tar (tar –xvf Server.tar)

5. Run the command cd $TOMCAT_HOME/webapps/ and untar tomcat.tar (tar –xvf

Tomcat.tar)

6. Run the command cd $EAMSROOT/lib and then run the following command.

mysql -u root panaces< mysql_schema_7.1_7.1P1.sql.


21. Upgrading NonVault 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.


The following are the steps to apply patch 7.1_35095 TO 7.1_GA:



2. Take a backup of mysql db schema, mysqldump -u root --databases panaces pfr

advancedreporter –R --triggers > panaces_dump.sql

3. Download 7.1_P1 patch files from IBM Passport Advantage site.


• Tomcat.tar to be downloaed to $TOMCAT_HOME/webapps/

4. Run the command cd $EAMSROOT and untar Server.tar (tar –xvf Server.tar)

5. Run the command cd $TOMCAT_HOME/webapps/ and untar tomcat.tar (tar –xvf

Tomcat.tar)

6. Run the command cd $EAMSROOT/lib and then run the following command:

mysql -u root panaces< mysql_schema_7.1_7.1P1.sql.


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

GPL Dependencies for Resiliency Orchestration


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 IBM Resiliency IBM Resiliency File Replicator


binaries before starting IBM Resiliency IBM Resiliency File Replicator and perform the steps

mentioned in the chapter, IBM Resiliency IBM 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 panaces server from <$EAMSROOT>/bin.

2. Stop all agents.







and Delete PanacesGUI, PFRGUI, UserPortal directory by rm –rf PanacesGUI PFRGUI

UserPortal

4. Download 7.1_P2 patch license files from IBM Passport Advantage site.


• 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, IBM Resiliency IBM

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.jar

EAMSROOT/agents/vault/eguard & EAMSROOT/lib/j2ssh-

core-0.2.9.jar

CYBERARK

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





Windows-64-BIT





My SQL

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

10. Refer to IBM Resiliency IBM Resiliency File Replicator Third Party Installation and

perform the IBM Resiliency IBM Resiliency File Replicator Third Party Installation

depending on the Operating System.


23. File Replication Service Third Party

Installation

During IBM Resiliency IBM Resiliency File Replicator installation, the user can configure the

$SFRROOT path. This is the home directory for IBM Resiliency IBM Resiliency File Replicator.

Third Party Binary Installation for Windows 32/64-Bit

Perform the following steps after installing IBM Resiliency IBM Resiliency File Replicator. Before

deploying the dependent binaries, ensure the IBM Resiliency IBM Resiliency File Replicator

services are stopped.

Note: Download the binaries from the link GPL Dependent binaries in Prerequisites.

1. Go to $SFRROOT/bin folder by executing the following command.

▪ cd $SFRROOT/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





RHEL 5.6

1. Go to the $SFRROOT folder by executing the following command.

▪ cd $SFRROOT

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

Perform the following steps after installing IBM Resiliency IBM Resiliency IBM Resiliency File

Replicator. Before deploying the dependent binaries, ensure the IBM Resiliency IBM Resiliency

IBM Resiliency File Replicator services are stopped.


RHEL 5.5


▪ cd $SFRROOT

2. Download and then unzip the files by executing following command.


3. Create the following soft link.

▪ ln -s $SFRROOT/bin/tar tar

RHEL 5.7


▪ cd $SFRROOT

2. Download and then unzip the files by executing following command.


3. Create the following soft link.

▪ ln -s $SFRROOT/bin/tar tar

RHEL 6.X


▪ cd $SFRROOT

2. Download and then unzip the files by executing following command

▪ tar -xvzf rsync3.0.9-RHEL6-64bit.tar.gz

▪ tar -xvzf tar1.23-RHEL6-64bit.tar.gz

RHEL 7.X


▪ cd $SFRROOT


▪ tar -xvzf rsync3.0.9-RHEL7-64bit.tar.gz

▪ tar -xvzf tar1.23-RHEL7-64bit.tar.gz

Third Party Binary Installation for AIX






▪ cd $SFRROOT


▪ gunzip rsync3.0.5-AIX.tar.gz

▪ tar -xvf rsync3.0.5-AIX.tar.gz


▪ gunzip tar1.14-AIX.tar.gz

▪ tar -xvf tar1.14-AIX.tar.gz


4. Create the following soft links.

▪ ln -s $SFRROOT/lib/usr/lib/libiconv.a /usr/lib/libiconv.a

Third Party Binary Installation for HPUX 64-Bit Itanium






▪ cd $SFRROOT

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


▪ ln -s $SFRROOT/tool/usr/local/lib/libpopt.so /usr/lib/hpux32/libpopt.so

Third Party Binary Installation for HPUX 64-Bit Parisac






▪ cd $SFRROOT

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


▪ ln -s $SFRROOT/tool/usr/local/lib/libpopt.so /usr/lib/hpux32/libpopt.so

Third Party Binary Installation for Solaris_Sparc

Perform the following steps after installing IBM Resiliency File Replicator. Before deploying the

dependent binaries, ensure the IBM Resiliency File Replicator services are stopped.


1. Go to $SFRROOT folder by executing the following command.

▪ cd $SFRROOT

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 is installed as part of tar, the other packages only selected)

▪ pkgadd -d $SFRROOT/bin/rsync-3.0.5-sol10-sparc-local -R

$SFRROOT/tool <<EOF

1

EOF

▪ pkgadd -d $SFRROOT/bin/libiconv-1.11-sol10-sparc-local -R

$SFRROOT/tool <<EOF

1

EOF

▪ pkgadd -d $SFRROOT/bin/libintl-3.4.0-sol10-sparc-local -R

$SFRROOT/tool <<EOF

1

EOF

▪ pkgadd -d $SFRROOT/bin/libgcc-3.4.6-sol10-sparc-local -R

$SFRROOT/tool <<EOF

1

EOF

▪ pkgadd -d $SFRROOT/bin/popt-1.14-sol10-sparc-local -R $SFRROOT/tool

<<EOF

1

EOF


▪ tar -xvzf tar1.18-SOLARIS10-SPARC.tar.gz


Note: (Note that if the package already installed as part of rsync, the other packages

only selected)

▪ pkgadd -d $SFRROOT/bin/tar-1.18-sol10-sparc-local -R $SFRROOT/tool

<<EOF

1

EOF

▪ pkgadd -d $SFRROOT/bin/libiconv-1.11-sol10-sparc-local -R

$SFRROOT/tool <<EOF

1

EOF

▪ pkgadd -d $SFRROOT/bin/libintl-3.4.0-sol10-sparc-local -R

$SFRROOT/tool <<EOF

1

EOF

▪ pkgadd -d $SFRROOT/bin/libgcc-3.4.6-sol10-sparc-local -R

$SFRROOT/tool <<EOF

1

EOF


▪ ln –s $SFRROOT /tool/usr/local/lib/libiconv.so.2

▪ ln –s $SFRROOT /tool/usr/local/lib/libgcc_s.so.1


Third Party Binary Installation For Solaris_Intel





1. Go to $SFRROOT folder by executing the following command.

▪ cd $SFRROOT


▪ tar -xvzf rsync3.0.5-SOLARIS10-x86.tar.gz


Note: (Note that if the package already installed as part of tar, the other packages only

selected )

▪ pkgadd -d $SFRROOT/bin/rsync-3.0.5-sol10-x86-local -R $SFRROOT/tool

<<EOF

1

EOF

▪ pkgadd -d $SFRROOT/bin/libiconv-1.14-sol10-x86-local -R

$SFRROOT/tool <<EOF

1

EOF

▪ pkgadd -d $SFRROOT/bin/libintl-3.4.0-sol10-x86-local -R

$SFRROOT/tool <<EOF

1

EOF

▪ pkgadd -d $SFRROOT/bin/libgcc-3.4.6-sol10-x86-local -R

$SFRROOT/tool <<EOF

1

EOF

▪ pkgadd -d $SFRROOT/bin/popt-1.16-sol10-x86-local -R $SFRROOT/tool

<<EOF

1

EOF


▪ tar -xvzf tar1.26-SOLARIS10-x86.tar.gz


Note: (Note that if the package already installed as part of rsync, the other packages only

selected.)

▪ pkgadd -d $SFRROOT/bin/tar-1.26-sol10-x86-local -R $SFRROOT/tool

<<EOF

1

EOF

▪ pkgadd -d $SFRROOT/bin/libiconv-1.14-sol10-x86-local -R

$SFRROOT/tool <<EOF

1

EOF

▪ pkgadd -d $SFRROOT/bin/libintl-3.4.0-sol10-x86-local -R

$SFRROOT/tool <<EOF

1

EOF

▪ pkgadd -d $SFRROOT/bin/libgcc-3.4.6-sol10-x86-local -R

$SFRROOT/tool <<EOF

1

EOF


▪ ln –s $SFRROOT / tool/usr/local/lib/libintl.so.8 /lib/libintl.so.8

▪ ln –s $SFRROOT / tool/usr/local/lib/libiconv.so.2 /lib/libiconv.so.2

▪ ln –s $SFRROOT / tool/usr/local/lib/libgcc_s.so.1 /lib/libgcc_s.so.1



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


4. Download 7.1_SP1 patch license files from IBM Passport Advantage site.


• 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.

9. Once the Resiliency Orchestration server and agents are started, cd to < EAMSROOT >/bin.

10. Execute the script 'GroupContinuityStatusUpgradeUtility.sh'. The script should be executed

successfully. Log for this utility can be found at

<EAMSROOT>/var/log/GroupContinuityStatusUpgradeUtility.log

11. For Vmware to AWS solution, please use the latest SRAs from OVA SRA: IBM Passport

Advantage site. AMI SRA and AMI Proxy available on the AWS Management Console.

Note:

• The default replication is secured replication now.

• For Vm protection solution we would need another instance of SRA in AWS called

as Proxy SRA wherein only SRA Agent should be running. You can find this in the

IBM Passport Advantage site.

12. Alternatively, local agents can also be downloaded from the IBM Passport Advantage site.

25. 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 124: 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 125: Uninstall Complete screen

5. Click Done to close this window.

26. 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 -i silent

Uninstall_IBM_Resiliency_Orchestration -i silent

Uninstallation of Resiliency Orchestration Server

Uninstallation of IBM Resiliency Orchestration server can be performed from:

• GUI

• Command Prompt

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 126: 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 127: 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 128: 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

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 129: 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:


# ./Uninstall_IBM_Resiliency_Orchestration_Agents

As part of uninstallation, the link names from "/etc/rc3.d" directory should be manually removed.

Linux


To uninstall Linux agent(s) from command prompt, do the following steps:



As part of uninstallation, the link names from "/etc/rc.d/rc3.d" directory should be manually

removed.

HPUX


To uninstall HPUX agent(s) from command prompt, do the following steps:



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:



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.


27. 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 130: 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 sanovi-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/sanovi.

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, ZCMD, GCMD, and XCMD

3. Define Userid SANOVI 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/sanovi-szcpvnnrnn.tar /to/sanovi-szcpvnnrnn.tar


2. Create the /u/sanovi folder. If you have a previous version installed, copy it to the

backup prior proceeding, for example /u/sanovi-prev-version.

3. Extract the sanovi-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/sanovi-szcpv01r00.tar

Verify that the following files are extracted in the /u/sanovi folder:

x /u/sanovi/TCMD, 12288 bytes, 24 tape blocks

x /u/sanovi/ZCMD, 24576 bytes, 48 tape blocks

x /u/sanovi/tcmd.sh, 64 bytes, 1 tape block

x /u/sanovi/zcmd.sh, 64 bytes, 1 tape block

Authorizing APF for TCMD, ZCMD, GCMD, and XCMD

1. After the untar, the contents of the /u/sanovi folder is displayed as shown below:

gcmd.sh File rwxrwxrwx fff--- --s- ----

tcmd.sh File rwxr-xr-x fff--- --s- ----

xcmd.sh File rwxr-xr-x fff--- --s- ----

zcmd.sh File rwxr-xr-x fff--- --s- ----

GCMD File rwxrwxrwx fff--- --s- ----

TCMD File rwxr-xr-x fff--- --s- ----

XCMD File rwxr-xr-x fff--- --s- ----

ZCMD File rwxr-xr-x fff--- --s- ----

Note

The contents of /u/sanovi 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/sanovi/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/sanovi

EUID . . . : 0

Command Filename Message Type Permission Audit Ext Fmat

-----------------------------------------------------------------------------

. Dir rwxr-xr-x fff--- ----

.. Dir rwxr-xr-x fff--- ----

gcmd.sh File rwxrwxrwx fff--- --s- ----

tcmd.sh File rwxr-xr-x fff--- --s- ----

xcmd.sh File rwxr-xr-x fff--- --s- ----

zcmd.sh File rwxr-xr-x fff--- --s- ----

GCMD File rwxrwxrwx fff--- a-s- ----

TCMD File rwxr-xr-x fff--- a-s- ----

XCMD File rwxr-xr-x fff--- a-s- ----

ZCMD File rwxr-xr-x fff--- a-s- ----

Defining Userid SANOVI to RACF/Other Security Program

Define a userid named SANOVI to RACF or equivalent security program. The SANOVI 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 131: 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 is 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:

Your install is now complete. If you encounter any problem, contact support for assistance.


28. Viewing the HTML Dashboard

You can access or switch between the Flex Dashboard (that is enabled by default) and the

HTML Dashboard by using the following URLs for the Manager Dashboard and the

Operational Dashboard:

Manager Dashboard:

http://192.168.20.72:8080/PanacesGUI/flex/SanoviDashboard.jsp [Flex]

http://192.168.20.72:8080/PanacesGUI/flex/SanoviDashboardPlain.jsp [HTML]

Operational Dashboard:

http://192.168.20.72:8080/PanacesGUI/flex/OperationalDashboard.jsp [Flex]

http://192.168.20.72:8080/PanacesGUI/flex/OperationalDashboardPlain.jsp [HTML]

http://192.168.20.72:8080/PanacesGUI/flex/SanoviDashboard.jsp

http://192.168.20.72:8080/PanacesGUI/flex/SanoviDashboardPlain.jsp

http://192.168.20.72:8080/PanacesGUI/flex/OperationalDashboard.jsp

http://192.168.20.72:8080/PanacesGUI/flex/OperationalDashboardPlain.jsp

29. 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, and

same OS, with Same MariaDB 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.tar.gz jboss-ews-2.0

4. Copy /backup/panaces-pfr-advrpt.sql /backup/EAMSROOT.tar.gz /backup/tomcat7.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.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.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 'sanovireporter'@'localhost' IDENTIFIED BY 'sanovi123';

h. GRANT ALL PRIVILEGES ON *.* TO 'sanovireporter'@'localhost' IDENTIFIED

BY 'sanovi123' 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

30. 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, and

same OS, with Same MariaDB 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.tar.gz jboss-ews-2.0

4. Copy /backup/panaces-pfr-advrpt.sql /backup/EAMSROOT.tar.gz /backup/tomcat7.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.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 'sanovireporter'@'localhost' IDENTIFIED BY 'sanovi123';

h. GRANT ALL PRIVILEGES ON *.* TO 'sanovireporter'@'localhost' IDENTIFIED

BY 'sanovi123' 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_IBM_Resiliency_Orchestration_IP where

c_id=5;

b. update agent_csa set ac_ipaddress='New_IBM_Resiliency_Orchestration_IP where

ac_id=168;

c. update agent_csa set ac_anode_ip='New_IBM_Resiliency_Orchestration_IP where

ac_anode_ip='OLD_IBM_Resiliency_Orchestration_IP';

d. For Vault Changes

16. update component_OSServer set

cos_mgmt_ipaddr='New_IBM_Resiliency_Orchestration_IP where cos_mgmt_ipaddr='Old

IBM_Resiliency_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

31. Troubleshooting

Subsystem Discovery Failing for Oracle Solution

The product by default supports discovery and management for Oracle 12c. Discovery may fail for

Oracle 11g.

For managing Oracle 11g or lower versions, replace ‘ojdbc8.jar’ with ‘ojdbc6.jar’ in the

AGENT_CLASSPATH in the following files:

$EAMSROOT/bin/OracleAgent.sh

$EAMSROOT/bin/DataGuardAgent.sh

Example:

AGENT_CLASSPATH=$ORA_CLIENT_HOME/ojdbc6.jar:$EAMSROOT/lib/DGAgentCSA.jar:

$EAMSROOT/lib/jcifs-1.3.18.jar:$EAMSROOT/lib/j-interopdeps.jar:$EAMSROOT/lib/j-

interop.jar:$EAMSROOT/lib/maverick-legacy-client-1.6.16-all.jar

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 Resiliency File Replicator Service

Open PFRService.lax file that has been installed in the IBM Resiliency 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 Resiliency File Replicator installation path in the PFRConfiguration.cfg

file by following the steps given below:

1. Enter in the $EAMSROOT /installconfig folder.

2. Open the PFRConfiguration.cfg file. Provide the installation path of IBM Resiliency

File Replicator in the PFR_INSTALL_PATH parameter.


3. 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:






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:





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:



Files\panaces\lib\log4j.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.


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/pa

naces/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.







naces/lib/jacl.jar:opt/panaces/lib/tcljava.jar:/opt/panaces/lib/PFR.ja

r: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:



naces/lib/jacl.jar:opt/panaces/lib/tcljava.jar:/opt/panaces/lib/PFRAge

ntCSA.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:


1.0.1.jar:/opt/panaces/lib/PADS.jar:/opt/panaces/lib/log4j.jar:opt/pan

aces/lib/jacl.jar:opt/panaces/lib/tcljava.jar:opt/panaces/lib/SolarisO

SAgentCSA.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-


naces/lib/tcljava.jar:/opt/panaces/lib/jacl.jar:.:/opt/panaces/SrsAgen

tCSA.jar:lax.jar



Agent Not Stating on Linux Server





Sanovi IBM Resiliency File Replicator Service




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/p

anaces/lib/tcljava.jar;/opt/panaces/lib/PFR.jar:lax.jar

PFR Agent



class path:



anaces/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




anaces/lib/tcljava.jar;opt/panaces/lib/LinuxOSAgentCSA.jar;/opt/panace

s/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









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


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


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


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/li

b/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










1.0.1.jar;/opt/panaces/lib/

PADS.jar;/opt/panaces/lib/log4j.jar;/opt/panaces/lib/jacl.jar;opt/pana

ces/lib/tcljava.jar;/opt/panaces/lib/PFR.jar:lax.jar

PFR Agent



class path:


1.0.1.jar;/opt/panaces/lib

/PADS.jar;/opt/panaces/lib/log4j.jar;/opt/panaces/lib/jacl.jar;opt/pan

aces/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



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 and

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 provided. Resiliency Orchestration Agent node address should be the public IP, and NAT IP


Note Manual Configuration if NAT IP is not provided during installation.

CFG file for NAT IP

Example IBM Resiliency Orchestration CFG file for NAT IP

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

• Discover agent node using "PANACES_AGENT_NODE_ADDRESS" here 192.168.2.131

• Discover PR & DR using their public IP

Example Local Agent CFG file for NAT IP

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)

Example PFR Configuration CFG file for NAT IP

PUBLIC IP: 115.119.249.125 //private IP of PR/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 Sanovi keystore.

Server/Advanced Reporter Installation Fails with

UnsatisfiedLinkError

While Installing the IBM Resiliency Orchestration or Advanced Reporter, the user may encounter

the following UnsatisfiedLinkError:


The error message is as follows:

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.

Port Forwarding

Verify Firewall Status

The following are details to verify the Firewall status.

[sanovi@sbrphln02 lic]$ sudo systemctl status firewalld.service

â firewalld.service - firewalld - dynamic firewall daemon

Loaded: loaded (/usr/lib/systemd/system/firewalld.service; disabled;

vendor preset: enabled)

Active: active (running) since Wed 2017-09-06 23:47:29 IST; 1 day 14h

ago

Docs: man:firewalld(1)

Main PID: 29752 (firewalld)

CGroup: /system.slice/firewalld.service

ââ29752 /usr/bin/python -Es /usr/sbin/firewalld --nofork --nopid

Sep 06 23:47:28 sbrphln02 systemd[1]: Starting firewalld - dynamic

firewall daemon...

Sep 06 23:47:29 sbrphln02 systemd[1]: Started firewalld - dynamic

firewall daemon.

[sanovi@sbrphln02 lic]$

Add Exception to Firewall

The following are details to add exception to firewall.

sudo firewall-cmd --zone=public --add-port=443/tcp –permanent

sudo firewall-cmd --zone=public --add-port=22/tcp --permanent



sudo firewall-cmd --zone=public --add-port=8081/tcp --permanent

Open Ports

The following are details to list the ports, which are open to access.

[root@sbrphln02 httpd]# firewall-cmd --list-all

public (active)

target: default

icmp-block-inversion: no

interfaces: enp3s0f0

sources:

services: dhcpv6-client ssh

ports: 45443/tcp 443/tcp 22/tcp 8081/tcp 8083/tcp

protocols:

masquerade: no

forward-ports:

sourceports:

icmp-blocks:

rich rules:

[root@sbrphln02 httpd]#

Create Server Certificate and Server Private Key Reference

The following snippet shows the details for creating server certificate and server private key

reference:

openssl req -new -x509 -days 365 -sha1 -newkey rsa:2048 -nodes -keyout

/opt/tomcat7/conf/ibm.key -out /opt/tomcat7/conf/ibm.crt -subj "/O=IBM

Corporation/OU=PS/CN=sbrphln02.in.ibm.com" -config "/etc/pki/tls/openssl.cnf"

Analyse HTTPD Logs

The following are details to see httpd logs: journalctl -xe

/bin/systemctl status httpd.service ( for checking the

status of httpd service )

Ref:

-- Unit user-0.slice has begun shutting down.

Sep 10 00:51:42 sbrphln02 sudo[10839]: sanovi : TTY=pts/0 ;

PWD=/etc/httpd/conf.d ; USER=root ; COMMAND=/bin/bash

Sep 10 00:51:43 sbrphln02 dbus-daemon[840]: dbus[840]: [system]

Activating service name='org.freedesktop.problems' (using

servicehelper)

Sep 10 00:51:43 sbrphln02 dbus[840]: [system] Activating service

name='org.freedesktop.problems' (using servicehelper)

Sep 10 00:51:43 sbrphln02 dbus-daemon[840]: dbus[840]: [system]

Successfully activated service 'org.freedesktop.problems'

Sep 10 00:51:43 sbrphln02 dbus[840]: [system] Successfully activated

service 'org.freedesktop.problems'

[root@sbrphln02 ~]#

Install httpd, SSL Packages

Download/Mount the Operating System ISO

mailcap-2.1.41-2.el7.noarch.rpm

httpd-tools-2.4.6-31.el7.x86_64.rpm

httpd-2.4.6-31.el7.x86_64.rpm

mod_ssl-2.4.6-45.el7.centos.x86_64.rpm

Install the httpd, SSL Packages

rpm -ivh mailcap-2.1.41-2.el7.noarch.rpm httpd-2.4.6-31.el7.x86_64.rpm

httpd-tools-2.4.6-31.el7.x86_64.rpm

rpm -ivh mod_ssl-2.4.6-45.el7.centos.x86_64.rpm


32. 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

prerequisites 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


procedure of .............................................................. 62

on Windows server ........................................................ 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


HPUX OS agent ....................................................... 89

PFR agent ................................................................. 90


on Linux server


Linux OS agent ......................................................... 79

PFR agent ................................................................. 80


on Solaris server


PFR agent ................................................................. 70

Solaris OS agent ....................................................... 69

SRS agent ................................................................. 70


Sybase agent ............................................................. 70

on Windows 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

ibm...ibm resiliency orchestration - installation guide © ibm corporation 2017 3 contents preface

Documents