Download presentation
Presentation is loading. Please wait.
Published byAlexis Gravett Modified over 9 years ago
1
Best Practices for Implementing Unicenter Service Desk r11.x in an HA MSCS Environment -Part 4: HA MDB with eIAM and HA Primary Server Last Revised January 31, 2007
2
© 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 will cover the following topics: -Installing HA MDB with eIAM -Installing HA Primary Server connecting to HA MDB with eIAM
3
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 3 Support Considerations -USD does not currently provide support for High Availability architectures, however, the following best practices demonstrate how a degree of High Availability can be achieved when implemented with assistance from your local CA Technical Services (CATS) team. -The failover process is not entirely automatic. If the MDB fails over to another cluster node, active clients will need to re-login to USD. -Additional questions regarding these guidelines can be directed to ImpCDFeedback@ca.com and every effort will be made to respond as quickly as possible.”ImpCDFeedback@ca.com
4
© 2005 Computer Associates International, Inc. (CA). 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 -“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
5
Introduction
6
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 6 Disclaimer -eIAM has built-in features for failover and replication. This presentation does not cover those features. -The procedures described here require eIAM to be installed with an HA MDB. Although eIAM will not be HA it will provide HA features and will be active on cluster nodes. -The Ingres instance will run on a local drive and will not be controlled as a cluster resource. -As a result if eIAM policies are defined, they need to defined on all cluster nodes
7
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 7 Objectives -The main objective of this presentation is to install and HA MDB with eIAM that can be used by Unicenter Service Desk. -In addition, the HA Primary Server will be installed in the same cluster but allowed to be active in different cluster nodes, thus providing a degree of Cluster Active – Active functionality
8
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 8 Active - Active This shows Primary Server and MDB active on the different cluster nodes MSCS Cluster
9
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 9 Active - Passive This shows Primary Server, eIAM and MDB active on the same cluster node MSCS Cluster
10
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 10 Active - Active This shows Primary Server with eIAM and MDB active on the different cluster node MSCS Cluster
11
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 11 eTrust Services Prior to Install -This shows eTrust services prior to eIAM install
12
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 12 eIAM Services -eTrust Directory Administration Daemon – master -eTrust Directory SSL daemon - iTechPoz-Server -eTrust Directory - iTechPoz- -eTrust Directory - iTechPoz- - Router -Ingres Intelligent Database [ET] -iTechnology iGateway 4.0
13
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 13 Additional Services
14
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 14 Identify Resource Group -Identify the SQL Instance Cluster Group where USD remote components will be installed. -In addition, identify cluster group where the Primary Server will be installed -Should be different from the SQL Cluster Group in order to allow Primary Server and Remote Components to be active on different cluster nodes. Running Primary Server on one cluster node and the MDB on different cluster node provides additional scalability -Cluster group where Primary Server is to be installed must have “Network Name” resource type defined
15
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 15 Verify Shared Disk -Verify the shared disk has adequate free space for USD folder. It requires approximately 2 GB of free space. -Ingres database installed by eIAM will be created on the local disk. This defaults to C: drive
16
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 16 Shared Disk Shared “Disk G:” will be used to create USD Folder
17
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 17 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 -Remote Components will be installed in Group SQL -Primary Server will be installed in Group USD_r11.1
18
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 18 MDB Resource Group eIAM will be installed with MDB server but no specific cluster resources are defined. eIAM will be active all cluster nodes. The Primary Server will connect to the eIAM on the active MDB node
19
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 19 Primary Server Cluster Group
20
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 20 eIAM Architecture and USD Service Desk R11.x Other App eIAM server Ingres global users, roles app 1 user info, policies app 2 user info, policies Web UI Shared Server Global Users either in CA-MDB, or referenced from ADS/eDirectory/ eTrust Admin
21
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 21 eTrust Directory Components
22
Install Overview
23
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 23 USD Components Installed on Two Node Cluster
24
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 24 Install Task Summary -Make Node A active -Define SQL Alias for Node A -Install Remote Components - HA MDB and eIAM. -Install Primary Server using a different cluster group -Run USD Configuration -Stop USD Services -Take a backup of nx.env file -Verify USD Setup -Delete SQL Alias -Move MDB and USD Group to Node B -Define SQL Alias for Node B -Install Remote Components - HA MDB and eIAM -Customize eIAM -Install Primary Server -Stop USD Service -Define USD Cluster Resource -Define MDB Cluster Resource -Configure eIAM -Install non HA Secondary Server -Run pdm_edit to define domsrvs, web engines and directors -Run USD Configuration
25
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 25 Node B Installation Options -Select the same options / features as Node A -This includes destination folder, web host name, eIAM application, etc -Copy eIAM certificates from Node A to Node B -This is required as USD folder is shared
26
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 26 USD r11.2 Install Caveat -USD r11.2 install process includes a check to determine if the pm.xml and wl.xml files already exist in the CATALINA_BASE\webapps folder -If they are not detected, the install copies the epdc.jar file from the CATALINA _BASE\common\lib to the tomcat\4.1.31\common\lib directory in Shared Components. -OK for first node on cluster -On subsequent nodes, because the install detects the files, an upgrade is performed instead -Since the epdc.jar file copy step is not included in an upgrade, the following error will be generated. Cannot load JDBC driver class 'com.ca.common.EncodedPwDriver‘ -To avoid this, manually copy epdc.jar to the Shared Components\tom cat\4.1.31\common\lib before starting the service on subsequent cluster nodes -This only applies to USD r11.2 - it does not affect r11.1.
27
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 27 SQL Alias -To install Remote Components, SQL Alias will have to be defined - After install of remote components, this SQL alias should be deleted. It is only required during the install process
28
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 28 How to Define SQL Alias Real Cluster Node name SQL Instance Name SQL VNode name
29
Walk-Through Installation of HA MDB, eIAM and Primary Server on NodeA
30
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 30 Remote Components Install -Review “Best Practices for Implementing Unicenter Service Desk r11.x in an HA MSCS Environment: Part 1” for additional information -In that presentation, Remote Components are installed on all cluster nodes without eIAM -In this presentation, Remote Components are installed with MDB and eIAM.
31
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 31 Remote Components – MDB and eIAM
32
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 32 Remote Components – MDB and eIAM
33
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 33 Remote Components – Install
34
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 34 Database Configuration SQL Alias must already be defined for this to work.
35
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 35 eIAM Select local drive
36
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 36 Privileged User
37
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 37 Summary
38
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 38 Remote Components - Install
39
Primary Server Install
40
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 40 Primary Server Cluster Group -For this install, Cluster Group USD_r11.1 is selected. This group has two shared drives. Shared Drive G: will be used for the USD folder as it has adequate free space
41
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 41 Primary Server - Install
42
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 42 Destination Location Select shared drive. This shared drive must be part of the cluster group where Primary Server is to be installed
43
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 43 Shared Components - Location Select local drive
44
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 44 Server Features
45
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 45 Setup
46
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 46 Configuration
47
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 47 General Settings Change Primary Server Node to cluster name (default is real node name)
48
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 48 General Settings Change to cluster name
49
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 49 General Settings Select Yes
50
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 50 System Accounts
51
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 51 Database Configuration
52
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 52 MS-SQL Database Configuration HA MDB
53
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 53 Web Interface Web Host set to cluster name
54
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 54 eIAM Specify SQL VNode Name
55
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 55 Configuration Options
56
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 56 Configuration Complete
57
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 57 Verify Setup -To verify Primary Server has been correctly configured, launch Web Client and run some basic tests
58
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 58 Stop Services -Stop Unicenter Service Desk -Make backup copy of \Program Files\CA\Unicenter Service Desk\NX.env. This file will be updated when USD is installed on NodeB. -This copy should not be needed again. It is simply a backup as some of the options, such as @NX_DUMMY,@NX_EIAM_CERT_PASSWORD, @NX_CAWF_PASSWORD, will be updated by the install process on subsequent nodes -Change the Service to Manual (if not already set to Manual)
59
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 59 Move Group -Move Groups so that USD can be installed on the other cluster nodes. Groups that should be moved include: -MDB Cluster group -USD Cluster Group
60
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 60 Move Group MDB Group USD Group
61
Walk-Through Installation of HA MDB, eIAM and HA Primary Server on NodeB
62
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 62 Remote Components - Install -Install Remote Components on NodeB. The install process is similar to the install process on NodeA. -During Database Configuration, it will display a message indicating MDB has been previously configured. This is true, as it has been configured during USD install on Node A. -Click “Yes” to continue
63
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 63 Database Configuration
64
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 64 Remote Components - Install
65
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 65 eIAM Configuration -This lists the basic configuration required. -There should be not any special considerations for configuring eIAM to use External directory for eIAM authentication (this is described later in this presentation)
66
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 66 Edit Router File -This change is required for non-HA install as well -Edit the following file: \Program Files\CA\eTrust Directory\dxserver\config \knowledge \iTechPoz- -Router.dxc -Change -Address = tcp localhost port 1684 to -Address = tcp localhost port 1684, tcp “ ” port 1684 -Where is real cluster node name This change is required for NodeA and NodeB
67
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 67 Edit Router File Updated File Original File Repeat this change for NodeA and NodeB
68
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 68 Copy Certificate files from NodeA -Rename %DXHOME%\config\ssld\personalities\itechpoz- -router.pem to %DXHOME%\config\ssld\personalities\itechpoz- -router.pem_orig -Rename %DXHOME%\config\ssld\personalities\itechpoz- -.pem to %DXHOME%\config\ssld\personalities\itechpoz- -.pem_orig -Copy from NodeA server %DXHOME%\config\ssld\personalities\itechpoz- -router.pem to NodeB Server as %DXHOME%\config\ssld\personalities\itechpoz- -router.pem -Copy from NodeAserver %DXHOME%\config\ssld\personalities\itechpoz-.pem to NodeB as %DXHOME%\config\ssld\personalities\itechpoz-.pem
69
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 69 Rename Files -Save original pem files
70
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 70 Copy pem files from NodeA
71
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 71 Restart eIAM Services -Can be done from Service Control manager or by executing the eIAM_restart.cmd script (included in the USD Cluster resource kit) -It executes the following commands -dxserver stop all -ssld stop -dxserver start all -ssld start
72
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 72 Restart eIAM services
73
Install Primary Server on Node B
74
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 74 Destination Folder Select the same shared disk as NodeA install
75
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 75 Shared Components Folder Select local disk for Shared Components folder
76
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 76 Select Features Select the same features as NodeA
77
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 77 Setup
78
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 78 Status
79
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 79 Configuration
80
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 80 Configuration -USD folder is shared by NodeA and NodeB -Thus nx.env will be shared by NodeA and NodeB -NodeB configuration will display same options as NodeA
81
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 81 General Settings
82
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 82 General Settings
83
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 83 System Accounts
84
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 84 Database Configuration
85
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 85 MS-SQL Database Configuration HA MDB
86
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 86 MS SQL Database Config Database was previously configured by NodeA
87
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 87 eIAM Configuration Same eIAM application label as NodeA. eIAM admin password must be same as NodeA eIAM admin password
88
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 88 Configuration Options
89
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 89 Configuration Complete
90
Secondary Server
91
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 91 Secondary Server -No additional considerations for the Secondary Server if using HA Primary Server and / or HA MDB -During Secondary Server configuration, identify cluster name (i.e., network name for your USD cluster group) as the Primary Server name
92
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 92 Secondary Server Configuration Set to Primary Server Cluster Resource Group Network Name
93
USD MDB Failover Customization
94
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 94 MDB failover -If the MDB fails over to another cluster node, web clients will not be able to reconnect. This is because sqlagent detects a network glitch and will not reconnect to the database. -Active users will simply wait. New users will not be able to connect to the pdmweb. The symptoms are similar to when a non-HA MDB server is being rebooted.
95
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 95 Define Cluster Resource -Extract the contents of the USD Cluster resource kit (usdcluster.zip) to your SQL Shared Drive. The directory name must be as follows: -usdCluster -Cd /usdCluster/bin directory -Update define_resource.cmd file -Execute updated define_resource.cmd to build the cluster resource
96
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 96 Update define_resources.cmd Update the above script with your cluster details
97
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 97 Define Cluster Resource Usdcluster_resource SQL, H:, “SQL Server (SQLINSTA)”
98
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 98 Build Cluster Resource Execute updated define_resources script
99
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 99 Cluster Resource Defined
100
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 100 Startup Script -Update the startup script to restart Unicenter Service Desk on the Primary Server -If Unicenter NSM is installed and Event Agent is running on the Primary Server, you can use cawto command to trigger MRA on the Primary Server -The example shows in-house utility being used to restart the Unicenter Service Desk Service on the Primary Server
101
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 101 Customize Options -If using in-house utility, specify the Primary Server details. Update usdService_restart.dat to specify the primary Server name
102
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 102 Restart USD Service This shows in-house utility being used to restart the USD Service on the Primary Server. Restart status is logged to the Windows Event Log file
103
USD Primary Server Failover Customization
104
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 104 Customization -USD Install on NodeA and NodeB is now complete -Define Cluster Resource for USD Service (pdm_daemon_manager)
105
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 105 Task Summary -NodeB is active node -Launch web client to verify setup -Stop USD service -Define Cluster Resource -Online Cluster Resource -Move Group -Launch web client to verify setup
106
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 106 usdPSCluster Package -Extract USD cluster resource kit usdPSCluster.zip file onto shared disk on which USD folder was created (G: drive in this example) -Directory name “usdPSCluster” will be created on shared G: drive (name cannot be changed)
107
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 107 Define Cluster Resource -Modify \usdPSCluster\bin\define_resource.cmd -Example for this Install -Cd G:\usdPSCluster\bin -Usdpscluster_resource USD_r11.1, G: “Cluster Name” -
108
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 108 Define Cluster Resource Usdpscluster_resource USD_r11.1, G:, “Cluster Name”
109
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 109 Define Resource -Execute define_resources.cmd
110
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 110 USD Resource Defined
111
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 111 Simulate Failover -Online USD Resource “CA_USD Service” -Move Group to simulate failover
112
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 112 Primary Server Failover -If the primary server fails over, the web clients will detect that the Primary Server service restarted and report accordingly -Web client users will be returned to the login screen
113
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 113 Primary Server Failover
114
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 114 Configuration -Any further Primary Server Configuration requires the service to be stopped and restarted. -If special care is not taken, the Primary Server will move from one node to another -Thus, prior to Configuration, change the Cluster Resource to “offline” -In most cases, Configuration should not be required on all cluster nodes – only the active node should suffice. However, there may be some changes, such as passwords, that require configuration to be run on all cluster nodes
115
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 115 Offline Cluster Resource -Take cluster resource offline before configuration is run
116
eIAM Customization
117
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 117 eIAM UI
118
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 118 eIAM Login
119
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 119 Configure
120
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 120 eIAM Configuration
121
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 121 External Directory Reference
122
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 122 Verify eIAM cache Identities
123
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 123 NodeB -Repeat the same changes on all cluster nodes -The Ingres database resides on the local drive and that is why policy is not shared -Ingres database can be relocated on the shared drive if required. This is explained on “MDB Care and Feeding presentation”. However, it requires additional customization, which is outside scope of this document
124
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 124 Reconfigure -Run USD Configuration to set eIAM Authentication option
125
Failover Test for Primary Server
126
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 126 MDB Active NodeA Prior to Failover
127
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 127 Primary Server Active NodeB Prior to Failover
128
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 128 Web Client Prior to Failover: Web Client launched from a different server to Primary Server
129
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 129 Primary Server Failing Over
130
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 130 Failover – Primary Server After Failover: Primary Server active on NodeA
131
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 131 Web Client – After Failover
132
© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 132 Web Client – After Failover Click OK to return to login screen
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.