CA Oblicore Guarantee 7.0 Service Pack 1 High Availability Upgrade Guide

Transcription

1 CA Oblicore Guarantee 7.0 Service Pack 1 High Availability Upgrade Guide

2

3 CA Inc. All rights reserved. CA Oblicore Guarantee 7.0 Service Pack 1. This document is subject to the following conditions and restrictions: It contains CA Inc., proprietary information. This information is supplied solely for the purpose of assisting explicitly and properly authorized users of CA Oblicore Guarantee. No part of its contents may be used for any other purpose, disclosed to any person or firm or reproduced by any means, electronic or mechanical, without the express prior written permission of CA Inc. The text and graphics are for the purpose of illustration and reference only. The specifications on which they are based are subject to change without notice. The software described in this document is furnished under a license. The software may be used or copied only in accordance with the terms of that agreement. Information in this document is subject to change without notice. Corporate and individual names and data used in examples herein are fictitious unless otherwise noted. CA Oblicore Guarantee is a trademark of CA Inc. Other company and brand products and service names are trademarks or registered trademarks of their respective holders. Release Information Software Version: 7.0 Service Pack 1 Release Date: 20 October, 2010 Last Updated Date: 20 October, 2010

4

5 Contents Introduction... 3 Upgrading Instructions... 5 Upgrading Process...5 Post-Installation Activities...7 ACE2 Installation Index... 15

6

7 Chapter 1 Introduction This guide describes the instructions for upgrading CA Oblicore Guarantee on high availability environments. This guide is intended for personnel who are required to upgrade CA Oblicore Guarantee on high availability environments.

8

9 Chapter 2 Upgrading Instructions Upgrading from a previous version of CA Oblicore Guarantee is performed on each server. The process is performed in the following sequence: Application servers then Web servers and lastly Adapter servers. Important Notes: For proper failover of the Application server, make sure that enough processes and sessions are defined in the database server. CA recommends doubling the processes and sessions in relation to a non-high availability environment. As stated, the upgrading process is performed in a sequence. Therefore, make sure NOT to perform it in parallel, but rather one machine at a time. Upgrading Process To upgrade the Application servers: 1. Perform all prerequisite steps as described in the CA Oblicore Guarantee 7.0 Service Pack 1 Installation Guide document. 2. Connect to the first Application cluster node machine. 3. Open the Cluster Administrator program. 4. In Action, select Open connection to cluster. 5. In Cluster or Server name, select the Application cluster name. 6. Click OK. 7. Check that the first Application cluster node is the owner of all Oblicore services, on Cluster Group and on Shared Folders. 8. On each Oblicore service clustered group, right click and select Take Offline. 9. Right-click on Shared Folders and select Take Offline. 10. Make sure that Cluster Group is Online and the first Application cluster node is the owner. 11. Run the CA Oblicore Guarantee 7.0 Service Pack 1 installation. 12. Restart the first Application cluster node machine. 13. Repeat steps 2 to 12 on each Application cluster node machine making sure that it is the owner. To upgrade the Web servers: 1. Perform all prerequisite steps as described in the CA Oblicore Guarantee 7.0 Service Pack 1 Installation Guide document. 2. Connect to the first Web node machine. 3. Run the CA Oblicore Guarantee 7.0 Service Pack 1 installation. 4. Restart the first Web node machine. 5. Repeat steps 2 to 4 on each Web node machine.

10 6 CA Oblicore Guarantee 7.0 Service Pack 1 High Availability Upgrade Guide To upgrade the Adapter servers: 1. Connect to the first Adapter cluster node machine. 2. Open the Cluster Administrator program. 3. In Action, select Open connection to cluster. 4. In Cluster or Server name, select the Adapter cluster name. 5. Click OK. 6. Check that the first Adapter cluster node is the owner of all Oblicore services, on Cluster Group and on Shared Folders. 7. Check that Cluster Group and Shared Folders are Online. 8. Take all adapter services Offline. 9. Run the CA Oblicore Guarantee 7.0 Service Pack 1 installation. Note: If a message stating that the Distributed Transaction Coordinator service is not started appears, click Ignore. 10. Restart the first Adapter cluster node machine. 11. Repeat steps 2 to 9 on each Adapter cluster node machine.

11 Upgrading Instructions 7 Post-Installation Activities After upgrading, the following activities must be performed: On the Application servers: 1. On each Application node machine, delete any queues if they are found in the Private Queues storage folder. 2. Configure MSMQ to work in a cluster as follows (for more information, see the Microsoft website): a. Verify that the MSTDC resource is clustered. b. Create and configure an MSMQ resource and group (virtual server) as follows: i. Open the Cluster Administrator program. ii. In Action, select Open connection to cluster. iii. In Cluster or Server name, select the Application cluster name iv. In the console tree, click Cluster Group. v. Go to File->New->Resource. vi. In the New Resource Wizard, in Name, type Clustered MSMQ. vii. In the Resource type list box, select Message Queuing and click Next. viii. On the Possible Owners page, click Next. ix. On the Dependencies page, under Available resources, select the resource whose type is Network Name and click Add. x. Select Disk S (the resource of type Physical Disk) and click Add. xi. Click Finish. c. Bring the Clustered MSMQ resource online. d. In the console tree, click Cluster Group. e. Go to File->New->Resource. f. In the New Resource Wizard, in Name, type Clustered Computer Management. g. In the Resource type list box, select Generic Application and click Next. h. On the Possible Owners page, click Next. i. On the Dependencies page, under Available resources, select the resource whose type is Network Name and click Add. j. Select the Clustered MSMQ resource and click Add. k. Click Next. l. In Command Line, type: mmc compmgmt.msc m. In Current Directory, type: %windir%\system32 n. Select the Use Network Name for the computer name, and Allow application to interact with desktop check boxes. o. Click Next, and then click Finish. p. Bring the Clustered Computer Management resource online. A Computer Management console is displayed. You must be logged into the Console Session (Session 0) to view Computer Management. The MMCV.exe can also be used to manage the MSMQ queues in a Clustered environment. For more information, see the Microsoft website.

12 8 CA Oblicore Guarantee 7.0 Service Pack 1 High Availability Upgrade Guide 3. From the Computer Management console that was opened, go to Services and Applications- >Message Queuing->Private Queues and create the following four private queues as shown in the figure below. OG Alerts OG Adapter Listener OG Dashboard OG Current Status. 4. Update the queues address in the database to the MSMQ clustered network address. This can be done from the CA Oblicore Guarantee UI by going to Administration- >Preferences->Advanced->Queues (see the figure below).

13 Upgrading Instructions 9 5. Add the Scripthost service into the cluster (see the figure below). 6. On each Oblicore service clustered group, right click and select Bring Online. On the Web servers: Go to \Program Files\Oblicore and copy the Booklet Templates, Export Templates and Packages folders to the Web shared folder (see the figure below).

14 10 CA Oblicore Guarantee 7.0 Service Pack 1 High Availability Upgrade Guide On the Adapter servers: 1. Connect to the first Adapter cluster node machine. 2. Open the Cluster Administrator program. 3. Change the Oblicore AdapterDeployment service name in the Parameters tab to AdapterDeployment. 4. Go to \Program Files\Oblicore\Adapters and copy the SqlAdapter.exe and TextFileAdapter.exe files to the Adapters folder on Disk S (the clustered shared folder). 5. Open the Registry Editor and go to HKEY_LOCAL_MACHINE->SOFTWARE->Oblicore- >Adapters. Verify that the AdaptersDir string has the value S:\Adapters. If not, change it. 6. Bring all adapter services Online.

15 Appendix A ACE2 Installation ACE2 is an enhanced operational mode of the Calculation Engine. ACE2 is architectured for improved scalability and higher performance. This appendix describes the installation instructions for ACE2 on high availability environments. To install ACE2 on high availability environments: 1. Install ACE2 manager and workers on each machine as described in the CA Oblicore Guarantee 7.0 Service Pack 1 Administration Guide. Make sure that the same number of worker instances are installed on each machine. 2. On the ACE2 Manager (JBOSS Side) machine, create a new cluster group called Oblicore - ACE2 Manager (see the figure below) 3. Assign this group with cluster IP and network name resources.

16 12 CA Oblicore Guarantee 7.0 Service Pack 1 High Availability Upgrade Guide 4. Add a new cluster resource service to the group using the ACE2 manager service name (JBOSSServiceForACE2) 5. Update the value of the new group network name in the database (see the figure below)

17 ACE2 Installation On each PslWorker node machine, change the parameters for each worker, to an assigned number as follows (see the figure below): a. Change Key name b. Change Display name c. Change the value of the image path (set.appn=<the worker number>) 7. Restart the node.

18 14 CA Oblicore Guarantee 7.0 Service Pack 1 High Availability Upgrade Guide 8. Add a new cluster group for the PslWorker called Oblicore PslWorker as follows: a. Add to the group cluster service resource for each modified PslWorker service (see the figure below) b. The value of the service name should be the new service key in the registry (see the figure below)

19 Index A ACE 2 Installation 11 I Introduction 3 P Post-Installation Activities 7 U Upgrading Instructions 5 Upgrading Process 5