Best Practices for Implementing Unicenter Asset Portfolio Management r11.2 in an HA MSCS Environment -Part I: Installing UAPM Optional Components Draft – Last Revised August 7 th 2006

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 2 Agenda -This presentation focuses on the procedures for installing Unicenter Asset Management Portfolio (UAPM) r11.2 Optional Components in a Microsoft Cluster Server (MSCS) environment

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 3 Disclaimer -Although this presentation focuses on 2 node clusters, MSCS supports clusters with more than 2 server nodes. The concepts that apply to 2 node clusters, however, also apply to multiple server node clusters. -These procedures are specific to MS-SQL The procedures for MS-SQL 2005 should be similar to SQL 2000 but are not covered in this document -Although UAPM r11.2 also supports Oracle and Ingres MDBs, the procedures in this document only pertain to SQL-based MDBs and should not be used for Oracle or Ingres MDBs!

Preparing UAPM Optional Components for MSCS

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 5 UAPM – SQL MDB -UAPM release 11.2 supports -SQL MDB -Ingres MDB -Oracle MDB -The procedure documented here only applies to SQL MDB and should not be used to install HA Ingres or Oracle MDB.

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 6 SQL Server Requirements -To install an HA SQL MDB, you must have an HA SQL Server which has its own cluster resource group. -If you do not want to install an HA MDB you should refer to the UAPM documentation as there should not be any additional considerations for installing a non-HA MDB in MSCS environment.

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 7 SQL Cluster Group The SQL Cluster Group has only one shared drive (H:) – and this is where the MDB will be created. SQL Instance name is SQLINSTA SQL VNode is I14YCLUSTSQL

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 8 Application Cluster Group

Installing UAPM Optional Components on NodeA

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 10 Install

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 11 Install UAPM Products

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 12 SQL MDB

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 13 SQL Server Info Provide SQL Virtual Node name and SQL instance name

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 14 Required SQL Server Information -The install process does not need to know the SQL Cluster Group name. -MDB is created on the default MSSQL shared drive associated with SQL Instance (the “H:” drive in this example) -If default SQL instance is created instead of named SQL instance you should only specify the SQL VNode name

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 15 UAPM SQL Users There are 3 SQL users created by the install process

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 16 Install Summary

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 17 Creating MDB

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 18 Install Log

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 19 UAPM - SQL Users This shows UAPM SQL users and MDB created

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 20 MDB This shows MDB created on the shared drive

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 21 Reboot

Installing UAPM Optional Components on NodeB

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 23 Move SQL Group -Move SQL Group to NodeB -Repeat the install process as described for NodeA. -Install process will not create MDB as it was already created by NodeA -The UAPM SQL user’s password must be same as specified during install on NodeA -The main reason for installing on NodeB is to create the required registry entries.

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 24 HA MDB -Installation is now setup to connect to an HA MDB -Test configuration by moving group and verify that your UAPM web clients function correctly when a failover occurs