Best Practices for Implementing Unicenter Asset Portfolio Management r11.2 in an HA MSCS Environment - Part 2 – Unicenter Asset Management Portfolio Draft – Revised August 7th 2006
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 2 Agenda - This presentation details the installation of Unicenter Asset Portfolio Management (UAPM) in a Microsoft Cluster Server (MSCS) environment. - Installation of the UAPM HA Optional Components is covered in Part 1 of this presentation series.
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 3 Disclaimer - UAPM does NOT support High Availability (HA) out-of-box (but it is targeted for future release). - However, if implemented correctly, these Best Practices demonstrate that it can be cluster aware. - These Best Practices only apply to Microsoft Cluster. It is not intended to be used with other vendor clusters.
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 4 Glossary The following terms and abbreviations are used in this presentation: - “HA” = Highly Available - “UAPM” – Unicenter Asset Management Portfolio - “USD” = Unicenter Service Desk - “eIAM” = CA eTrust Embedded Identity and Access Management - “MSCS” = Microsoft Cluster Server - “Cluster Name” = Network name associated with the cluster group
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 5 References - The following presentations are referenced and should be consulted for additional information: - Best Practices for Implementing Unicenter Asset Portfolio Management r11.2 in an HA MSCS Environment - Part I – Installing UAPM Optional Components. - This describes how to install UAMP Optional Components including creating an HA MDB in a Microsoft Cluster environment - Best Practices for Implementing Unicenter Service Desk r11.1 in an HA MSCS Environment – Parts 1 through 4
Introduction
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 7 Setup - HA SQL MDB exists on same cluster - UAPM will be installed on same cluster but in a different Cluster Resource Group - This procedure can also be adapted to install HA Optional Components and HA UAPM on 2 different clusters or to intermix with a non-HA setup.
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 8 Reconciliation Considerations - Unicenter Desktop Server Management (DSM) is not HA and should not be installed with HA UAPM. - DSM can share an HA MDB if installed correctly, however, there are some limitations when a failover occurs. - For detailed information on how to install HA MDB from DSM media review - Desktop Server Management HA MDB Desktop Server Management HA MDB
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 9 HA - UAPM and MDB MSCS Cluster UAPM Manager components and MDB on different cluster nodes
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 10 HA - UAPM and MDB MSCS Cluster UAPM Manager components and MDB on same cluster nodes
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 11 HA - UAPM and MDB MSCS Cluster UAPM Manager components and MDB on different cluster nodes. MDB is now running on Cluster A. Previously it was running on Cluster B.
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 12 Identify Resource Group - Identify cluster group where the UAPM will be installed. - Should be different from the SQL Cluster Group in order to allow UAPM and MDB to be active on different cluster nodes. - If required, however, they can both share the same SQL Cluster Group. - If SQL Cluster Group is used for UAPM manager components and MDB, then manager components and MDB will always be active on the same node. - If other products are also installed on the same cluster, it is recommended to use different cluster groups - Cluster group where UAPM is to be installed must have “Network Name” resource type defined
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 13 Cluster Setup - The following example shows two cluster groups: - 1 with SQL instance “SQLINSTA” installed - 1 with “Network Name” cluster resource type - So, for this setup - MDB will be installed in Group SQL - UAPM will be installed in Group USD_r11.1
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 14 MDB Resource Group
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 15 UAPM Cluster Group
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 16 Install Task Summary 1.Install UAPM Optional Components on NodeA 2.Repeat UAPM Optional Components install on NodeB - For steps 1 and 2 consult part 1 of this presentation series 3.Install UAPM Manager components and utilities on NodeA 4.Define UAPM Cluster Resources 5.Move Group 6.Repeat install UAPM Manager components and utilities on NodeB 7. Verify Setup
Walk-Through Installation of HA UAPM on NodeA
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 18 Optional Components - If the UAPM Optional Components have not been installed, then please install them prior to installing UAPM components
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 19 Install
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 20 Install Products
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 21 UAPM - Prerequisites
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 22 UAPM - Prerequisites
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 23 UAPM - Prerequisites
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 24 Setup Type
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 25 Components
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 26 Destination Folder Local Drive selected for the destination folder. This requires care to ensure consistent configuration on all cluster nodes
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 27 Web Console Location Local Drive selected for the destination folder. This requires cluster VNode to be used for web clients
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 28 Database Type This document only applies to SQL MDBs. Steps for other database engines are outside the scope of this document
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 29 SQL JDBC Driver JDBC driver must be available on all cluster nodes
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 30 SQL Server Info Specify the SQL VNode and the instance name. If using default instance, just specify the SQL VNode
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 31 SQL JDBC Drivers Local drive is selected since JDBC driver is installed on both cluster nodes
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 32 SQL User Account Password
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 33 Install Summary
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 34 Install
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 35 Database Utility
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 36 Database Utility
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 37 Reboot Prior to reboot, define cluster resources
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 38 UAPM Services This shows UAPM services after install
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 39 Define Cluster Resources - Install UAPM Cluster Resource Kit (uAPMCluster.zip) to define cluster resources to manage 3 UAPM Services: - Cache Service - Notification Service - Tomcat Service - The following service is not managed by the cluster resource - ASP.NET State Service - This kit is available from Implementation Best Practices pages on SupportConnect.
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 40 uAPMCluster Resource Kit - Extract uAPMCluster.zip resource kit to a shared disk. This shared disk should be part of the cluster group where UAPM Cluster resources will be defined. - Directory name “uAPMCluster” will be created on shared drive (G: in the following example)
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 41 Resource Kit Install Shared Drive: G: Resource Kit Directory Name: uAPMCluster
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 42 Define Cluster Resource - Modify \uapmCluster\bin\define_Resource.cmd - Example for this Install - Cd G:\uapmCluster\bin - uapmcluster_resource USD_r11.1, “Cluster Name”
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 43 Define Cluster Resource uapmcluster_resource USD_r11.1, “Cluster Name”
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 44 Cluster Group Cluster Group State prior to defining UAPM resources
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 45 Define Resource - To define UAPM cluster resources execute - cd g:\uapmCluster\bin - define_resources.cmd
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 46 Cluster Resources Defined Cluster Group State after defining UAPM resources
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 47 Online / Offline - Online the 3 cluster resources defined. This will then change the Windows service status to “manual” - Launch the UAPM configurator to customize UAPM options - Once the configuration is completed, offline the 3 cluster resources prior to moving the cluster group to NodeB
UAPM Configurator
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 49 Configuration
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 50 APM Configuration
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 51 Configurations - There should not be any special considerations for other components
Walk-Through Installation of HA UAPM on NodeB
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 53 NodeB - Install - Move Group to NodeB. - UAPM install insists on a reboot. - Prior to reboot of NodeA, verify the 3 UAPM cluster resources defined are in offline state. - After install of NodeA, during reboot it will automatically move the group to NodeB - Repeat the install on NodeB. - Select the same options as NodeA
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 54 Database Utility No need to run the database utility again
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 55 Reboot Prior to reboot, online UAPM cluster resources
Verification
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 57 UAPM Web Clients - When launching UAPM web client, use the cluster virtual name instead of real node name. - This will eliminate the need to know the active cluster node
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 58 Remote Web Client Launched from a remote system using Cluster Name
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 59 Notification - Following sample generated by the database failover
Copyright ©2006 CA. All rights reserved. All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 60 Web Services Timeout - By default, UAPM Web Services timeout is 60 minutes. Thus if the failover occurs, this session will still be active.