CONTROL-M V8 INSTALLATION ON WINDOWS 2008 CLUSTER. Guide to install Control-M Enterprise Manager and Control-M Server V8 on Windows 2008 Cluster

Transcription

1 CONTROL-M V8 INSTALLATION ON WINDOWS 2008 CLUSTER Guide to install Control-M Enterprise Manager and Control-M Server V8 on Windows 2008 Cluster

2 Content Page 1. Pre-Installation Checklist Creating Disk, IP Address and Network Name for Control-M Installation Control-M EM Installation on Primary Clustered Node Setting up failover nodes for Control-M EM Control-M Server Installation on Primary Clustered Node Setting up failover nodes for Control-M Server Setting up Control-M GTW on Control-M Configuration Manager (CCM) and Failover Cluster Management GUI 38 Page 1

3 1. Pre-Installation Checklist Note: - One Install is not supported on Windows Cluster Environment: - Install Microsoft.NET Framework 4 on both Windows 2008 Cluster Node. If not, proceed to install using the binary provided. Page 2

4 Page 3

5 2. Creating Disk, IP Address and Network Name for Control-M Installation - Log on as Domain Administrator to start installation - Ensure that the Current Host Server is the node that the installation is being performed. Page 4

6 - Verification that the Disk, IP Address and Network Name are online and available. - Create a New Service or Application for Control-M Right-click on Services and Applications > More Actions > Create Empty Service or Application Page 5

7 - When the new application is created, right click on the New service or Application Select Rename and give the Application a new name. (CTMV8) - Add a New Resource Right click on CTMV8 > Add a resource > 1 Client Access Point - Give the Client Access Point, CTMV8, a new IP Address ( ) Page 6

8 - Click Next to complete the creation of the Client Access Point. - Add a storage Right Click on CTMV8 > Add Storage Page 7

9 - Check the disk to be added to this Application. Page 8

10 - Bring the Server Name, Disk Drives and Network IP Address online. Right click on CTMV8 > Bring this service or application online Page 9

11 3. Control-M EM Installation on Primary Clustered Node - Start the Control-M EM Installation on the Primary Clustered Node as followed: Page 10

12 Page 11

13 Note: If the Cluster Group, Disk Resource and Network are configured correctly and online, these information will appear as above automatically. If not, please repeat STEP (2) again. Page 12

14 Page 13

15 PostgreSQL service password: Pa55word Page 14

16 Database Owner Username: emuser Database Owner Password: empass Database Administrator Password: password Page 15

17 Page 16

18 - Installation completed successfully and the Control-M Workload Automation GUI should be started as below. Page 17

19 - Install the Control-M Batch Impact Manager Page 18

20 - Install the Control-M Forecast Page 19

21 - Control-M Enterprise Manager / Control-M Batch Impact Manager / Control-M Forecast should be able to be start and made ONLINE using the Windows Cluster Management. Page 20

22 4. Setting up failover nodes for Control-M EM - Verify that the owner of the Control-M/EM cluster group is the primary node on which you installed the full Control-M/EM installation. On each failover node, perform the following - Bring the primary Disk, IP address, and Network Name cluster resources online. - Ensure that the Control-M CORBA Naming service remains online. - Perform a failover of the Control-M/EM group from the primary node to the secondary node. Page 21

23 - Ensure that the Disk, IP address, and Network Name resources are online on the failover node. All resources except Control-M Naming Service for EM will be OFFLINE. - Open a command prompt and run Setup_files\3RD\setup_em.bat from the installation DVD. Note: If you are using Windows 2008, you must run the command prompt as an administrator. Page 22

24 - The following step applies only for a PostgreSQL installation. On a PostgreSQL installation, give Log On as a Services permissions to the local NT user that was created for PostgreSQL by performing the following steps: - From the command line (Start > Run), run Services.msc - Locate PostgreSQL for Control-M/EM version xxx and locate.\<name of user>and save this name for later. Page 23

25 - Exit Service.msc - From the command line (Start > Run), run secpol.msc - Browse to Security Setting > Local Policies > User Rights Assignments - Select Log On as Service policy - Click Add user or group - Click Location - Select the current node name Page 24

26 - Enter the object name to select, enter a name for the this account service. This name is the <name of user> you saved in above. - Bring up the Control-M EM Application online - Right click on the Control-M Application then select Bring this service or application online. Page 25

27 - Control-M EM Application can be move to another node as well. Page 26

28 5. Control-M Server Installation on Primary Clustered Node - Start the installation for Control-M Server - Select Control-M Server under the Advanced Installations Page 27

29 Page 28

30 Page 29

31 - Select the Database Server Installation (In this guide, Control-M Server will be using the existing BMC-supplied PostgreSQL Database Server) - Perform a Test to ensure that the Host is available. Page 30

32 Control-M Server Database Owner: ctmuser Control-M Server Database Owner Password: ctmpass Database Administrator Password: password Page 31

33 Page 32

34 Page 33

35 6. Setting up failover nodes for Control-M Server - Verify that the owner of the Control-M cluster group is the primary node on which you installed the full Control-M installation. On each failover node, perform the following - Bring the primary Disk, IP address, and Network Name cluster resources online. - Ensure that the Control-M Server and Control-M Server Configuration service remains online. - Perform a failover of the Control-M group from the primary node to the secondary node. Page 34

36 - Ensure that the Disk, IP address, Network Name and Control-M Application resources are online on the failover node. - Open a command prompt and run Setup_files\3RD\setup_ctm.bat from the installation DVD. Note: If you are using Windows 2008, you must run the command prompt as an administrator. Page 35

37 - If setup_ctm.bat did not start executing and display the following error, please do check that the Control-M Server and Control-M Server Configuration Agent application services is online on the secondary nodes. - Right click on the Control-M Application then select Bring this service or application online. - Also ensure that the Control-M Application cab be move to the Primary node. Page 36

38 Page 37

39 7. Setting up Control-M GTW on Control-M Configuration Manager (CCM) and Failover Cluster Management GUI - Discover Control-M Server and the its Gateway. Page 38

40 Page 39

41 - Set the Gateway Desired Status to Ignore - Launch the Failover Cluster Management GUI - Create a resource (Generic Application) for Control-M Server Gateway Add a resource > Generic Application Page 40

42 - Supply the information as followed: Page 41

43 - Add the Control-M Naming Service for EM as a Dependency Page 42

44 Page 43

45 - Update the Pending timeout to 10 minutes. - Control-M Server installation on Windows 2008 Cluster completed. Page 44