You are on page 1of 45

CONTROL-M V8

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

Control-M V8 installation on WIndows 2008 cluster


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

Page 1

Control-M V8 installation on WIndows 2008 cluster

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

Control-M V8 installation on WIndows 2008 cluster

Page 3

Control-M V8 installation on WIndows 2008 cluster

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

Control-M V8 installation on WIndows 2008 cluster


-

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

Control-M V8 installation on WIndows 2008 cluster


-

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 (192.168.134.90)

Page 6

Control-M V8 installation on WIndows 2008 cluster

Click Next to complete the creation of the Client Access Point.

Add a storage
Right Click on CTMV8 > Add Storage

Page 7

Control-M V8 installation on WIndows 2008 cluster

Check the disk to be added to this Application.

Page 8

Control-M V8 installation on WIndows 2008 cluster


-

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

Page 9

Control-M V8 installation on WIndows 2008 cluster

3. Control-M EM Installation on Primary Clustered Node


-

Start the Control-M EM Installation on the Primary Clustered Node as followed:

Page 10

Control-M V8 installation on WIndows 2008 cluster

Page 11

Control-M V8 installation on WIndows 2008 cluster

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

Control-M V8 installation on WIndows 2008 cluster

Page 13

Control-M V8 installation on WIndows 2008 cluster

PostgreSQL service password: Pa55word

Page 14

Control-M V8 installation on WIndows 2008 cluster

Database Owner Username: emuser


Database Owner Password: empass
Database Administrator Password: password

Page 15

Control-M V8 installation on WIndows 2008 cluster

Page 16

Control-M V8 installation on WIndows 2008 cluster

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

Page 17

Control-M V8 installation on WIndows 2008 cluster

Install the Control-M Batch Impact Manager

Page 18

Control-M V8 installation on WIndows 2008 cluster


-

Install the Control-M Forecast

Page 19

Control-M V8 installation on WIndows 2008 cluster


-

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

Control-M V8 installation on WIndows 2008 cluster

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

Control-M V8 installation on WIndows 2008 cluster


-

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

Control-M V8 installation on WIndows 2008 cluster

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

Control-M V8 installation on WIndows 2008 cluster


-

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

Control-M V8 installation on WIndows 2008 cluster


-

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

Control-M V8 installation on WIndows 2008 cluster

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

Page 26

Control-M V8 installation on WIndows 2008 cluster

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

Control-M V8 installation on WIndows 2008 cluster

Page 28

Control-M V8 installation on WIndows 2008 cluster

Page 29

Control-M V8 installation on WIndows 2008 cluster


-

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

Control-M V8 installation on WIndows 2008 cluster

Control-M Server Database Owner: ctmuser


Control-M Server Database Owner Password: ctmpass
Database Administrator Password: password

Page 31

Control-M V8 installation on WIndows 2008 cluster

Page 32

Control-M V8 installation on WIndows 2008 cluster

Page 33

Control-M V8 installation on WIndows 2008 cluster

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

Control-M V8 installation on WIndows 2008 cluster

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

Control-M V8 installation on WIndows 2008 cluster

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

Control-M V8 installation on WIndows 2008 cluster

Page 37

Control-M V8 installation on WIndows 2008 cluster

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

Control-M V8 installation on WIndows 2008 cluster

Page 39

Control-M V8 installation on WIndows 2008 cluster


-

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

Control-M V8 installation on WIndows 2008 cluster


-

Supply the information as followed:

Page 41

Control-M V8 installation on WIndows 2008 cluster

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

Page 42

Control-M V8 installation on WIndows 2008 cluster

Page 43

Control-M V8 installation on WIndows 2008 cluster


-

Update the Pending timeout to 10 minutes.

Control-M Server installation on Windows 2008 Cluster completed.

Page 44

You might also like