Cluster Installation

Access Integrator
Cluster Installation and Upgrade

P50010-A0153-M002-2-7699
Status: IUS
Date: 11.04.2003
Issued by
ICN, Information and Communication Networks
Hofmannstrasse 51, D-81359 Munich
Copyright
Siemens AG 2016
SIEMENS AKTIENGESELLSCHAFT
Author:
Translator:
Notification:
Barbara Wenzl - ICN CP D NM F2
All Rights Reserved.
In addition to the authors named on the cover page the following persons have
collaborated on this document:
Luis Ortega - ICN CP D NM 3
0 GENERAL INFORMATION
0.1 Issue Control..........................................................................................................5

0.2 History....................................................................................................................5
0.3 List of Figures and Tables....................................................................................5
1 INTRODUCTION
1.1 Overview.................................................................................................................6
1.2 Configuration.........................................................................................................6
2 INSTALLATION
2.1 Precondition for installation on a Cluster...........................................................7

2.2 Basic cluster configuration for ACI.....................................................................7
2.3 Versant....................................................................................................................9
2.3.1 SW-Installation..................................................................................................................... 9
2.3.1.1 Location............................................................................................................................. 9
2.3.1.2 Parameter.......................................................................................................................... 9
2.3.2 Manual configurations after SW-Installation.....................................................................9
2.3.3 Cluster configuration.......................................................................................................... 9
2.3.4 Trouble Shooting............................................................................................................... 10
2.4 Corba (ORBIX)......................................................................................................11

2.4.1 SW-Installation................................................................................................................... 11
2.4.1.1 Location........................................................................................................................... 11
2.4.1.2 Parameter........................................................................................................................ 11
2.4.2 Corba configuration........................................................................................................... 11
2.4.2.1 Corba Server................................................................................................................... 11
2.4.2.2 Corba Client.................................................................................................................... 15
2.5 Domain Manager V8.2.........................................................................................18

2.5.1 SW-Installation................................................................................................................... 18
2.5.1.1 Location........................................................................................................................... 18
2.5.1.2 Parameter........................................................................................................................ 18
The document comprises 32 pages, all pages have issue no 05.

This issue was created on 13.06.2003 12:13.
This document was edited with MS WinWord version 7.0.
.
P50010-A0153-M002-2-7699
2 of 32
2.5.2 Manual configurations after SW-Installation...................................................................18

2.5.3 Cluster configuration........................................................................................................ 18
2.6 Element Manager XL3.0......................................................................................22

2.6.1 SW-Installation................................................................................................................... 22
2.6.1.1 Location........................................................................................................................... 22
2.6.1.2 Parameter........................................................................................................................ 22
2.7 Network Manager TDM V8.2...............................................................................25

2.7.1 SW-Installation................................................................................................................... 25
2.7.1.1 Location........................................................................................................................... 25
2.7.1.2 Parameter........................................................................................................................ 25
2.8 How to change the configuration of a Service.................................................28
3 UPGRADE
30
3.1 Versant..................................................................................................................30
3.1.1 Precondition....................................................................................................................... 30
3.1.2 Upgrade procedure............................................................................................................ 30
3.2 Corba (ORBIX).....................................................................................................30

3.3 Domain Manager V8.2.........................................................................................30
3.3.1 Precondition....................................................................................................................... 30
3.4 Element Manager XL3.0......................................................................................31

3.4.1 Precondition....................................................................................................................... 31
3.5 Network Manager TDM V8.2...............................................................................32

3.5.1 Precondition....................................................................................................................... 32
P50010-A0153-M002-2-7699
3 of 32
TABLE OF CONTENTS
0 GENERAL INFORMATION
0.1 Issue Control
The document comprises 32 pages, all pages have issue no 03.
0.2 History
Issue
Date
Reason for Changes
01
09.09.2002
new issue / AFI
02
19.09.2002
IUS
03
27.02.2003
Unnecessary EM share for Background directory removed

Handling of EMXL ProcessMonitor added
Corrections regarding Stop ACI DB
04
27.03.2003
DM share corrected: not os-conf but conf must be shared
05
27.03.2003
Upgrade procedure added

Corrections regarding Stop ACI DB (dependency order between
Versant and Stop ACI DB changes, Stop ACI DB should be
configured as Do not restart
06
11.04.2003
Remove dependency to background share for ACI SNMP Server

Next step for Corba server configuration corrected
07
12.06.2003
Upgrade for ACI NM Server
Table 1: History
0.3 List of Figures and Tables

Figure 1 ACI in a Cluster with shared RAID System....................................................................6
Figure 2 Service properties, General, (local Computer).............................................................28
Figure 3 Service properties, LogOn, (local Computer)...............................................................29
Table 1: History............................................................................................................................ 5
P50010-A0153-M002-2-7699
4 of 32
TABLE OF CONTENTS
1 Introduction
1.1 Overview
Server clusters are configurations of two or more machines that share some disks. A failure in
one machine causes the data services to automatically relocate to the backup machine. If the
shared disk is itself a RAID, then the configuration admits no single point of failure.
1.2 Configuration
There are a number of configurations for server clusters. Here the two nodes share a disk array.
The secondary node monitors the primary to determine if it has failed. When it detects a failure,
it immediately starts a script that restarts all the failed services on the secondary node and
changes the IP address of the backup node to that of the failed node.
Client
GUI
GUI
Application
Logic
Application
Logic
API
API
ACI Group
Active
node
NM, DM, EM, SNMP,

Brass, Orbix, Versant
NM, DM, EM, SNMP,

Redundant node Brass, Orbix, Versant
Server Process
Server Process
SharedRAID System
Switch over
Database Files
ACI Logs
Figure 1 ACI in a Cluster with shared RAID System

Normally each cluster consists out of two nodes.
Each node has a local disk C: and each cluster a shared disk drive P: which is located on the
Raid-Array.
Each cluster uses at least 5 different IP-Addresses:
- external IP-Address for Node1 and Node 2
these addresses could be used to access the nodes itself from any PC in the network.
- internal IP-Address for Node1 and Node 2
these addresses are used for the communication between the two nodes of a cluster.
- common IP-Address for the Cluster group
this address is used to access the two nodes as one cluster. The cluster itself decides which
of the two nodes is the active.
P50010-A0153-M002-2-7699
5 of 32
TABLE OF CONTENTS
2 Installation
2.1 Precondition for installation on a Cluster
As basic precondition for an Access Integrator installation (including Versant and Orbix) the
basic cluster group must be configured.
This means that at least the Cluster Group with the following resources must be available
Quorum Disk
Listing properties for 'Quorum Disk':
Name
Disk Q:
Type
Physical Disk
Description
Listing resource dependencies for 'Quorum Disk':
None
Cluster IP Address
Listing properties for 'Cluster IP Address':
Name
Cluster IP Address
Type
IP Address
Description
Network
PUBLIC LAN
Address
192.168.237.100
SubnetMask
255.255.255.0
EnableNetBIOS
1 (0x1)
Listing resource dependencies for 'Cluster IP Address':
None
Cluster Name
Listing properties for 'Cluster Name':
Name
Cluster Name
Type
Network Name
Description
Name
ACIDOM1
Listing resource dependencies for 'Cluster Name':
Cluster IP Address
2.2 Basic cluster configuration for ACI

As first step a new ACI Cluster Group, e.g. ACI Group must be created. Both nodes of the
cluster must be configured to be Preferred Owners of this group.
For this ACI Cluster Group the following resources must be defined, before the installation of
AccessIntegrator software can be started.
Shared Disk
Listing properties for 'Shared Disk':
Name
Shared Disk
Type
Physical Disk
Description
Disk P
Listing resource dependencies for 'Shared Disk':
None
ACI IP Address
P50010-A0153-M002-2-7699
6 of 32
TABLE OF CONTENTS
Listing properties for 'ACI IP Address':

Name
ACI IP Address
Type
IP Address
Description
ACI IP Address
Network
PUBLIC LAN
Address
192.168.237.103
SubnetMask
255.255.255.0
EnableNetBIOS
1 (0x1)
Listing resource dependencies for 'ACI IP Address':
None
ACI Hostname
Listing properties for 'ACI Hostname':
Name
ACI Hostname
Type
Network Name
Description
ACI Hostname
Name
ACIDOM1R
RemapPipeNames
0 (0x0)
Listing resource dependencies for 'ACI Hostname':
ACI IP Address
P50010-A0153-M002-2-7699
7 of 32
TABLE OF CONTENTS
2.3 Versant
2.3.1 SW-Installation
For a Cluster configuration Versant must be installed twice, on each node of a cluster
separately. This is necessary because the machine configuration (e.g. Registry, Environment
variable) must be the same on both machines.
The normal Versant installation, which is part of the AccessIntegrator installation CD, can be
used. But both nodes must be installed using the same options and parameters during
installation!
Installation can only be done on the node, which is currently the Owner of the basic resources
of the ACI Group (see 2.2).
Before you start the installation of Versant switch off the second node (Power off) completely.
Reason for this is that it is necessary to reboot the machine after installation and the same
machine must be the active one after the reboot to finalize the installation in a proper way.
2.3.1.1 Location
Install the complete Versant environment on the shared disk, but at least the database
directory must be located on the shared disk!
2.3.1.2 Parameter
During Versant installation the Hostname and the IP-Address of the ACI cluster group (e.g. ACI
Hostname and ACI IP-Address) must be used (see 2.2).
2.3.2 Manual configurations after SW-Installation
After installation the Startup type of the Versantd service is Automatic and the service is
configured to use the local System account.
To allow the Microsoft Cluster Service to control this service the Startup type must be changed
to Manual and the option Allow the service to interact with desktop must be activated (see
2.8).
2.3.3 Cluster configuration

Within the ACI Cluster Group (see 2.2) two new resources must be defined:
Versant
Listing properties for 'Versant':
Name
Versant
Type
Generic Service
Description
ACI Database Application
ServiceName
versantd
StartupParameters
VERSANT_HOST_NAME=ACIDOM1R
VERSANT_IP=192.168.237.103
P50010-A0153-M002-2-7699
8 of 32
TABLE OF CONTENTS
UseNetworkName
HOMEDRIVE=P:
HOMEPATH=\Versant\db\
VERSANT_DB=P:\Versant\db
VERSANT_DBID=P:\Versant\db
VERSANT_DBID_NODE=ACIDOM1R
1 (0x1)
Listing resource dependencies for 'Versant':

ACI Hostname
Shared Disk
Now it is be possible to bring the Versant resources to online.

2.3.4 Trouble Shooting
Hosts file
Check the host file on both nodes, which is located in
<Windows installation directory>\system32\drivers\etc.
Here you should find a line for the ACI IP-Address and ACI Hostname e.g.
192.168.237.103 ACIDOM1R
Services file
Check the services file on both nodes, which is located in
<Windows installation directory>\system32\drivers\etc. Here you should find the following line
for Versant:
oscssd
5019/tcp
# VERSANT connect service
Environment settings
Check the variable VERSANT_DBID_NODE in the following files (on both nodes):
- <Versant installation directory>\6_0_1\NT\lib\sysinfo
- <Windows installation directory>\vr060001.ini
Check the environment variable VERSANT_HOST_NAME on both nodes.
VERSANT_HOST_NAME=<ACI Hostname>
OSC-DBID file
Check if the osc-dbid file in the Versant DB directory is created. If not, open command shell and
type dbid N (on the active node).
P50010-A0153-M002-2-7699
9 of 32
TABLE OF CONTENTS
2.4 Corba (ORBIX)

For a Cluster configuration Corba must be installed twice, on each node of a cluster separately.
This is necessary because the machine configuration (e.g. Registry, Environment variable) must
be the same on both machines.
The normal Corba installation, which is part of the AccessIntegrator installation CD, can be
used. But both nodes must be installed using the same options and parameters during
installation!
Installation can only be done on the node, which is currently the Owner of the basic resources
of the ACI Group (see 2.2).
2.4.1.1 Location
Install the complete Corba environment on the shared disk, but at least the domain
information must be located on the shared disk!
2.4.1.2 Parameter
At the beginning of the installation it must be decided if the cluster should act as Corba Client
or Corba Server. If the configuration only consists out of one cluster, the Corba Server should
be located on the Cluster.
If the configuration consists out of more than one cluster, the Corba Server should be located on
the Domain Manager cluster and the Element Manager clusters should act as Corba client.
2.4.2 Corba configuration
After SW-installation the Corba Domain must be configured (on both nodes of a cluster) using
the <Orbix-Installation-Directory>\orbix_art\1.2\bin\configure.exe.
Before starting the configuration make sure, that the file licenses.txt file is stored in <OrbixInstallation-Directory>\etc.
The following steps depend on if the cluster is a Corba Client or Corba Server.
2.4.2.1 Corba Server
Follow the question of the configure.exe tool.
Orbix 2000 Configuration
----------------------------------------------(c) Copyright 1993-2000 IONA Technologies PLC. All rights reserved.
Welcome to the Orbix 2000 Configuration application. This application
will walk you through the process of configuring the following
Orbix 2000 components:
Configuration Domain
Locator Daemon
Activator Daemon
Orbix 2000 Services
P50010-A0153-M002-2-7699
10 of 32
TABLE OF CONTENTS
Configuration Scripts
You can enter input interactively or from a pre-configured file.
Execute 'configure -?' for more details.
Press any key to begin. [continue]:
After confirmation, check the Orbix installation path

Is your IONA product directory P:\Program Files\IONA [yes]:
This will show a selection menu:

Configuration Activities
----------------------------------------------Orbix 2000 organizes configuration information into domains that can be
shared across multiple machines. This utility allows you to create a
new domain or build a link to an existing domain running on another
machine. Do you want to:
[1] Create a new Orbix 2000 domain
[2] Create a link to an existing Orbix 2000 domain
Enter [1]:
Choose to create a new domain,

What should this domain be called [orbix2000]:
For example choose ACI_CORBA_DOMAIN for the domain name

Where should configuration files for this domain be placed [P:\Program
Files\IONA\etc\domains]:
ATTENTION: Make sure, that the chosen directory is located on the shared disk!
Choose Domain Type
----------------------------------------------Orbix 2000 currently supports two types of configuration domain:
[1] Configuration Repository Based.
This type of domain stores
configuration
information
in
a
centralized
Configuration
Repository, which can be easily accessed from multiple machines.
Select this type of domain if you expect to share configuration
information across multiple systems.
[2] File Based. This type of domain stores configuration information
in a file on the local machine. It can be useful for smaller
systems that cannot afford the overhead of additional services.
Enter [1]:
Choose Configuration Repository Based for the domain type

Do you want to install the selected services as NT services? [yes]:
Confirm the question to install the selected services as NT services

Configuration Repository Settings
----------------------------------------------The Configuration Repository is accessed through a CORBA service,
which makes it available to multiple machines.
This service must
listen on a fixed port so that applications can access it at a
well-known location. You may also want to specify the hostname used
to advertise the Configuration Repository.
If you do not specify a
hostname, the Configuration Repository will use the system's current
hostname.
What hostname should the Configuration Repository advertise (leave
blank for default):
Type the name, which is defined in the Cluster resource ACI Hostname (see 2.2)
P50010-A0153-M002-2-7699
11 of 32
TABLE OF CONTENTS
What port should the Configuration Repository use [3076]:
Confirm the proposed port number

Where do you want to place databases and logfiles for this domain [P:\Program
Files\IONA\var\ACI_CORBA_DOMAIN]:
Use as Default Domain
----------------------------------------------Orbix 2000 can designate one domain as being the default domain for
this machine. This domain will be used for applications that are
started without an explicit domain.
Do you wish to designate this domain as the default domain [yes]:
Choose yes to designate this domain as the default. Take care, during configuration of the
second node the default for this question will be [no].
Deploy Locator
----------------------------------------------The Orbix 2000 Locator service manages persistent servers.
You must
deploy this service if you intend to develop servers using PERSISTENT
POAs, or if you intend to use other Orbix 2000 services such as the
Naming Service or Interface Repository.
Do you want to deploy a Locator into this domain [yes]:
Choose yes to deploy a Locator. Take care, during configuration of the second node the default
for this question will be [no].
To insure interoperability among services of the same type across domains,
a unique name must be provided for the locator.
Locator name:
[rts120]:
The Orbix 2000 Locator must listen on a fixed port so that applications
can access it at a well-known location. You may also want to specify
the hostname used to advertise the Locator. If you do not specify a
hostname, the Locator will use the system's current hostname.
What hostname should the Locator advertise (leave blank for default):
What port should the Locator use [3075]:
Accept the default port number

Deploy Activator
----------------------------------------------The Orbix 2000 Activator service starts applications on a
particular machine. You must deploy an Activator service on every
machine on which you intend to use Orbix 2000's automatic server
activation feature.
Do you want to deploy an Activator into this domain [yes]:
Choose yes to deploy an Activator

Orbix 2000 Services
----------------------------------------------Orbix 2000 offers the following standard CORBA services. Using a commaseparated list, please select the set of services you wish to deploy
in this domain. (For example: 1,3):
[1] Naming Service
[2] Interface Repository
[3] Event Service
[4] All additional services
[5] No additional services
Services [4]:
P50010-A0153-M002-2-7699
12 of 32
TABLE OF CONTENTS
Choose 4
Client Preparation File
----------------------------------------------Orbix 2000 can generate a preparation file that allows you to easily
configure other machines with access to this domain.
Would you like to generate client and service preparation files [yes]:
Accept the preparation files generation

Please enter the name of the client preparation file [P:\Program Files\IONA\var\
CORBA_DOMAIN_NAME\client.prep]:
Use the default path

creating configuration files........................................done.
building Configuration Domain...........done.
deploying Locator daemon.......done.
deploying Activator daemon.....done.
deploying Naming Service.........done.
done
To use this domain, setup your environment as follows:
Run "P:\Program Files\IONA\bin\CORBA_DOMAIN_NAME_env.bat"
to setup your environment for this domain
Run "P:\Program Files\IONA\bin\CORBA_DOMAIN_NAME_java_env.bat"
to setup your java environment for this domain
Run "P:\Program Files\IONA\bin\start_CORBA_DOMAIN_NAME_services.bat"
to start the services associated with the domain
Run "P:\Program Files\IONA\bin\stop_CORBA_DOMAIN_NAME_services.bat"
to stop the services associated with the domain
Instead of using the above batches (they would have to be used every time the system is
restarted) open the Control Panel | System Properties dialog and set the following system
variables:
IT_CONFIG_DOMAINS_DIR=P:\Program Files\IONA\etc\domains
IT_DOMAIN_NAME=<CORBA_DOMAIN_NAME>
The creation of Orbix configuration domain ACI_CORBA_DOMAIN is now done. The computer
must be restarted to allow changes to take effects. If all the ACI servers are intended to run on
this machine (hosting the configuration repository at the same time) this is the only step needed,
otherwise continue with step 3 for other machines
----------------The installed Corba services are:
1. IT config_rep cfr- ACI_CORBA_DOMAIN (ACI_CORBA_DOMAIN is the Corba Domain
Name, chosen during configure.exe !!!!)
2. IT locator default-domain
3. IT naming default-domain
4. IT activator default-domain
5. IT ifr default-domain
6. IT event default-domain
Next Step:
To allow the Microsoft Cluster Service to control these services the Startup type must be
changed to Manual and the option Allow the service to interact with desktop must be
activated (see 2.8).
P50010-A0153-M002-2-7699
13 of 32
TABLE OF CONTENTS
2.4.2.2 Corba Client

This step is intended to repeat on all the machines where the ACI servers are to be run. If the
given ACI server is not intended to be run on the same host as the Orbix server (where the
configuration domain has been created in the previous step), this step must be done.
Precondition: The machine hosting the configuration repository (Corba Server) must be
running and reachable while configuring a Corba Client
1. Copy the client preparation file from the Orbix server machine [P:\Program
Files\IONA\var\ACI_CORBA_DOMAIN\client.prep] to the machine on that the ACI server shall
run.
2. Open the command prompt window
3. Change directory to the following location
%Orbix-installed-dir%\orbix_art\1.2\bin\
Run the configure.exe utility with the useprep parameter

%Orbix-installed-dir%\orbix_art\1.2\bin\configure useprep <client.prep>
<client.prep> is the absolute path and name of the client.prep file, e.g. C:\temp\client.prep
The following information appears:
Is your IONA product directory P:\Program Files\IONA [yes]:
Use the default path provided
Where should configuration files for this domain be placed [P:\Program
Files\IONA\etc\domains]:
Where do you want to place databases and logfiles for this domain [P:\Program
Files\IONA\var\ACI_CORBA_DOMAIN]:
Use as Default Domain
----------------------------------------------Orbix 2000 can designate one domain as being the default domain for this machine. This
domain will be used for applications that are started without an explicit domain.
Do you wish to designate this domain as the default domain [yes]:
Select this domain as the default domain
This will produce the following output
creating configuration files........done.
creating link to Configuration Domain....done.
To use this domain, setup your environment as follows:
Run "P:\Program Files\IONA\bin\ACI_CORBA_DOMAIN_env.bat"
to setup your environment for this domain
Run "P:\Program Files\IONA\bin\ACI_CORBA_DOMAIN_java_env.bat"
to setup your java environment for this domain
Set / check the system variables
Ignore the part To use this domain.
P50010-A0153-M002-2-7699
14 of 32
TABLE OF CONTENTS
Instead of using the above batches (they would have to be used every time the system is
restarted) open the Control Panel | System Properties dialog and set the following system
variables in the Environment tab:
IT_PRODUCT_DIR=P:\Program Files\IONA
IT_CONFIG_DOMAINS_DIR=P:\Program Files\IONA\etc\domains
IT_DOMAIN_NAME=<CORBA_DOMAIN_NAME>
Restart the computer
The configuration of this machine to use ACI_CORBA_DOMAIN configuration domain is now
completed. The computer must be restarted to allow changes to take effects.
Cluster configuration
It is not necessary to define any cluster resources for a Corba client.
For a Corba Server it is necessary to define following Cluster resources in the ACI Cluster
Group (see 2.2):
Corba Configuration Repository for ACI_CORBA_DOMAIN
Listing properties for 'Corba Configuration Repository for ACI_CORBA_DOMAIN':
Name
Type
Generic Service
Description
ORBIX - Corba Configuration Repository for Domain "ACI_CORBA_DOMAIN"
ServiceName
IT config_rep cfr-ACI_CORBA_DOMAIN
StartupParameters
UseNetworkName
1 (0x1)
Listing resource dependencies for 'Corba Configuration Repository for ACI_CORBA_DOMAIN':
ACI Hostname
Shared Disk
Versant
Corba Locator Daemon
Listing properties for 'Corba Locator Daemon':
Name
Corba Locator Daemon
Type
Generic Service
Description
ORBIX - Corba Locator Daemon
ServiceName
IT locator default-domain
StartupParameters
UseNetworkName
1 (0x1)
Listing resource dependencies for 'Corba Locator Daemon':
Corba Naming Service
Listing properties for 'Corba Naming Service':
Name
Corba Naming Service
Type
Generic Service
Description
ORBIX - Corba Naming Service
ServiceName
IT naming default-domain
StartupParameters
UseNetworkName
1 (0x1)
Listing resource dependencies for 'Corba Naming Service':
Corba Locator Daemon ACI-DM
P50010-A0153-M002-2-7699
15 of 32
TABLE OF CONTENTS
Corba Activator daemon

Listing properties for 'Corba Activator daemon':
Name
Corba Activator daemon
Type
Generic Service
Description
ORBIX - Corba Activator Daemon
ServiceName
IT activator default-domain
StartupParameters
UseNetworkName
1 (0x1)
Listing resource dependencies for 'Corba Activator daemon':
Corba Naming Service ACI-DM
Corba Interface Repository
Listing properties for 'Corba Interface Repository':
Name
Corba Interface Repository
Type
Generic Service
Description
ORBIX - Corba Interface Repository
ServiceName
IT ifr default-domain
StartupParameters
UseNetworkName
1 (0x1)
Listing resource dependencies for 'Corba Interface Repository':
Corba Activator daemon ACI-DM
Corba Event Service
Listing properties for 'Corba Event Service':
Name
Corba Event Service
Type
Generic Service
Description
ORBIX - Corba Event Service
ServiceName
IT event default-domain
StartupParameters
UseNetworkName
1 (0x1)
Listing resource dependencies for 'Corba Event Service':
Corba Interface Repository ACI-DM
Now it is be possible to bring the ORBIX resources to online.
Trouble Shooting
Environment settings
IT_PRODUCT_DIR=<Corba Installation directory>
IT_CONFIG_DOMAINS_DIR = <Corba Installation directory>\etc\domains
IT_DOMAIN_NAME = ACI_CORBA_DOMAIN (Your corba domain name)
P50010-A0153-M002-2-7699
16 of 32
TABLE OF CONTENTS
2.5 Domain Manager V8.2

For a Cluster configuration the Domain Manager must be installed twice, on each node of a
cluster separately. This is necessary because the machine configuration (e.g. Registry,
Environment variable) must be the same on both machines.
Use the common AccessIntegrator installation CD and install on both nodes using the same
options and parameters during installation!
Installation can only be done on the node, which is currently the active one. The basic resources
of the ACI Group (see 2.2), Versant and Orbix must be active on this node.
2.5.1.1 Location
Use the shared disk as target for the Domain Manager installation.
2.5.1.2 Parameter
During installation the Hostname and the IP-Address of the ACI cluster group (e.g. ACI
Depending on the selected components during installation of the Domain Manager the
installation has inserted at least two services into the system.
- Access Integrator Process Monitor
- ACI DM TDM Server (8.2.x.y)
The following services are installed if the Qd2 DCN Server and/or the SNMP DCN Server have
been chosen during installation.
- ACI Qd2 DCN Server (8.2.x.y)
- ACI SNMP DCN Server (8.2.x.y)
- SNMP BRASS Management Multiplexer
The configurations of these services are not discussed in the following.
After installation the Startup type of all these services is Automatic. Only the SNMP BRASS
Management Multiplexer would be configured to use the local System account all other
services are installed to use the Log on, which was requested during installation procedure.
To allow the MSCS to control these service, the Startup type of the Process Monitor service
must be changed to disabled. All other Domain Manager services must be changed from
Automatic to Manual.
Within the ACI Cluster Group (see 2.2) only a resource for ACI DM TDM Server (8.2.x.y) must
be defined. The Process Monitor is not used in a Cluster environment.
P50010-A0153-M002-2-7699
17 of 32
TABLE OF CONTENTS
ACI DM TDM Server (8.2.x.y)

Listing properties for 'ACI DM 8.2 Server':
Name
Value
---------------------------------------------------Name
ACI DM 8.2 Server
Type
Generic Service
Description
ACI DomainManager 8.2 Server
ServiceName
ACICLASSICServer
StartupParameters
UseNetworkName
1 (0x1)
Listing resource dependencies for 'ACI DM 8.2 Server':
Corba Event Service
Versant
ACI Background
ACI DB Backup
ACI CONF
ACI Root
ACI Params
ACI Traffic
Registry replication:
HKEY_LOCAL_MACHINE\SOFTWARE\Siemens AG\Access Integrator V8.2 Classic Server
ACI Background
Listing properties for 'ACI Background':
Name
ACI Background
Type
File Share
Description
ACI Background directory
ShareName
BACKGROUND
Path
P:\Program Files\Siemens AG\AccessIntegrator V8.2 Domain
Manager\background
Listing resource dependencies for 'ACI Background':
Shared Disk
ACI DB Backup
Listing properties for 'ACI DB Backup':
Name
ACI DB Backup
Type
File Share
Description
ACI Database Backup directory
ShareName
OS_BACKUP
Path
Manager\os_backup
Listing resource dependencies for 'ACI DB Backup':
Shared Disk
ACI Root
Listing properties for 'ACI Root':
Name
ACI Root
Type
File Share
Description
ACI Root directory
ShareName
MLOSROOT
Path
Manager
Listing resource dependencies for 'ACI Root':
Shared Disk
ACI Conf
Listing properties for 'ACI CONF':
P50010-A0153-M002-2-7699
18 of 32
TABLE OF CONTENTS
Name
Type
Description
ShareName
Path
Manager\conf
ACI Conf
File Share
ACI Configuration directory
CONF
Listing resource dependencies for 'ACI CONF':

Shared Disk
ACI Traffic
Listing properties for 'ACI Traffic':
Name
ACI Traffic
Type
File Share
Description
ACI Traffic directory
ShareName
TRAFFIC
Path
Manager\traffic
Listing resource dependencies for 'ACI Traffic':
Shared Disk
ACI Params
Listing properties for 'ACI Params':
Name
ACI Params
Type
File Share
Description
ACI Parameter directory
ShareName
PARAMS
Path
Manager\params
Listing resource dependencies for 'ACI Params':
Shared Disk
Stop ACI DB
Listing properties for 'Stop ACI DB':
Name
Stop ACI DB
Type
Generic Application
Description
cleanup Versant processes
RestartAction
0 (0x0) (= Do not restart)
CommandLine
P:\Program Files\Siemens AG\
AccessIntegrator V8.2 Domain\bin\killprocess.bat
CurrentDirectory
AccessIntegrator V8.2 Domain\bin
InteractWithDesktop
1 (0x1)
UseNetworkName
1 (0x1)
Listing resource dependencies for 'Stop ACI DB':
Versant
Now it is possible to bring the Domain Manager resources to online.

Hosts file
192.168.237.13 ACIEM1R
P50010-A0153-M002-2-7699
19 of 32
TABLE OF CONTENTS
Services file
<Windows installation dir>\system32\drivers\etc.
Here you should find the following line for the Domain Manager:
acis-dm
50190/tcp
# ACI DM server
P50010-A0153-M002-2-7699
20 of 32
TABLE OF CONTENTS
2.6 Element Manager XL3.0

For a Cluster configuration the Element Manager XL 3.0 must be installed twice, on each node
of a cluster separately. This is necessary because the machine configuration (e.g. Registry,
Environment variable) must be the same on both machines.
2.6.1.1 Location
Use the shared disk as target for the Element Manager XL 3.0 installation.
2.6.1.2 Parameter
The installation installs four services on the system
- SNMP BRASS Management Multiplexer
- ACI Server EMXL (8.2.x.y)
- ACI SNMP DCNServer EMXL (8.2.x.y)
- Access Integrator Process Monitor EMXL
After installation the Startup type of all these services is Automatic. Only the SNMP BRASS
Management Multiplexer is configured to use the local System account all other services are
installed to use the Log on, which was requested during installation procedure.
To allow the Microsoft Cluster service to control these service, the Startup type of the Process
Monitor service must be changed to disabled. All other Element Manager services must be
changed from Automatic to Manual. Additionally, the option Allow the service to interact with
desktop must be set (see 2.8).
Within the ACI Cluster Group (see 2.2) the following Cluster resources are necessary for an
Element Manager:
ACI Brass
Listing properties for 'ACI Brass':
Name
ACI Brass
Type
Generic Service
Description
ACI Brass
P50010-A0153-M002-2-7699
21 of 32
TABLE OF CONTENTS
ServiceName
StartupParameters
UseNetworkName
BRASSD
1 (0x1)
Listing resource dependencies for 'ACI Brass':

ACI Hostname
Shared Disk
ACI SNMP Server

Listing properties for 'ACI SNMP Server':
Name
ACI SNMP Server
Type
Generic Service
Description
ACI SNMP Server
ServiceName
ACI SNMP DCNServer EMXL
StartupParameters
UseNetworkName
1 (0x1)
Listing resource dependencies for 'ACI SNMP Server':
ACI Brass
Versant
ACI DB Backup
ACI Root
Registry Replication:
HKEY_LOCAL_MACHINE\SOFTWARE\Siemens AG\Access Integrator V8.2 SNMP Server EMXL
ACI EM XL 3.0 Server

Listing properties for 'ACI EM XL 3.0 Server':
Name
ACI EM XL 3.0 Server
Type
Generic Service
Description
ACI ElementManager XL 3.0 Server
ServiceName
ACI Server EMXL
StartupParameters
UseNetworkName
1 (0x1)
Listing resource dependencies for 'ACI EM XL 3.0 Server':
ACI SNMP Server
HKEY_LOCAL_MACHINE\SOFTWARE\Siemens AG\Access Integrator V8.2 EM XL Server
ACI DB Backup
Name
ACI DB Backup
Type
File Share
Description
ShareName
OS_BACKUP
Path
P:\Program Files\Siemens AG\AccessIntegrator V8.2 EM XL\OS_backup
Shared Disk
ACI Root
Listing properties for 'ACI Root':
Name
ACI Root
Type
File Share
Description
ACI Root directory
ShareName
ACI_EMXL_ROOT
Path
P:\Program Files\Siemens AG\AccessIntegrator V8.2 EM XL
P50010-A0153-M002-2-7699
22 of 32
TABLE OF CONTENTS
Listing resource dependencies for 'ACI Root':

Shared Disk
Stop ACI DB
This resource is only necessary if the Element Manager is the only ACI process on the
machine. If there is also a Domain Manager installed, this resource is not necessary.
Listing properties for 'Stop ACI DB':
Name
Stop ACI DB
Type
Generic Application
Description
cleanup Versant processes
RestartAction
0 (0x0) (= Do not restart)
CommandLine
AccessIntegrator V8.2 EM XL\bin\killProcess.bat
CurrentDirectory
P:\Program Files\Siemens AG\AccessIntegrator V8.2 EM XL\bin
InteractWithDesktop
1 (0x1)
UseNetworkName
1 (0x1)
Listing resource dependencies for 'Stop ACI DB':
Versant
Now it is possible to bring the EM XL resources to online.

Hosts file
192.168.237.13 ACIEM1R
Services file
Here you should find the following lines for the Element Manager:
acid-snmp-emxl
50201/tcp
# ACI EMXL snmp server
acis-emxl
50200/tcp
# ACI EMXL server
P50010-A0153-M002-2-7699
23 of 32
TABLE OF CONTENTS
2.7 Network Manager TDM V8.2

For a Cluster configuration the Network Manager TDM V8.2 must be installed twice, on each
node of a cluster separately. This is necessary because the machine configuration (e.g.
Registry, Environment variable) must be the same on both machines.
2.7.1.1 Location
Use the shared disk as target for the Network Manager TDM V8.2 installation.
2.7.1.2 Parameter
The installation installs four services on the system
- ACI Server Network Manager TDM (8.2.x.y)
After installation the Startup type of this service is Automatic. The service is installed to use
the Log on, which was requested during installation procedure.
This service must be changed from Automatic to Manual. Additionally, the option Allow the
service to interact with desktop must be set (see 2.8).
Within the ACI Cluster Group (see 2.2) the following Cluster resources are necessary for an
Element Manager:
NM TDM 2.0 Server

Listing properties for 'ACI NM V8.2':
Name
ACI NM V8.2
Type
Generic Service
Description
Network Manager
ServiceName
ACIPSMServer
UseNetworkName
1 (0x1)
Listing resource dependencies for 'ACI NM V8.2':
Corba Event Service
Versant
P50010-A0153-M002-2-7699
24 of 32
TABLE OF CONTENTS
ACI Background
ACI CONF
ACI DB Backup
HKEY_LOCAL_MACHINE\ SOFTWARE\Siemens AG\Access Integrator V8.2 PSM Server
ACI Background
Listing properties for 'ACI Background':
Name
ACI DB Backup
Type
File Share
Description
ACI data files
ShareName
BACKGROUND
Path
the position of this shared folder
Shared Disk
ACI CONF
Listing properties for 'ACI CONF':
Name
ACI DB Backup
Type
File Share
Description
ACI configuration files
ShareName
CONF
Path
Shared Disk
ACI DB Backup
Name
ACI DB Backup
Type
File Share
Description
ShareName
OS_BACKUP
Path
Shared Disk
Corba and Versant Dependencies as to be handle in the same way as by DM or EM.

Now it is possible to bring the NM TDM XL resources to online.
Hosts file
192.168.237.13 ACIEM1R
Services file
Here you should find the following lines for the Element Manager:
P50010-A0153-M002-2-7699
25 of 32
TABLE OF CONTENTS
acis-nmtdm
50195/tcp
P50010-A0153-M002-2-7699
# ACI NM TDM server
26 of 32
TABLE OF CONTENTS
2.8 How to change the configuration of a Service

After installing a product and before rebooting the machines, the Startup Type for the installed
services needs to be changed from Automatic to Manual. To change this setting bring up the
services dialog box from the Control Panel and double click on servicename and change the
setting as shown below (e.g. VERSANTD).
Figure 2 Service properties, General, (local Computer)
P50010-A0153-M002-2-7699
27 of 32
TABLE OF CONTENTS
Figure 3 Service properties, LogOn, (local Computer)

The Service works as the "local System account" and the MSCS should be able to interact with
this Service. Now the new generic Service of the MSCS will start and stop this local service (e.g.
VERSANT).
P50010-A0153-M002-2-7699
28 of 32
TABLE OF CONTENTS
3 Upgrade
3.1 Versant
The following steps must only be done if an upgrade of Versant is necessary. If not please
proceed with chapter 3.3 or 3.5.
3.1.1 Precondition
Take ACI Cluster Group 'ACI Group' offline and bring only the necessary resources
'ACI Hostname'
'ACI IP Address'
'Shared Disk'
for a Versant-Upgrade online. All other resources should be offline.

3.1.2 Upgrade procedure
Pause the inactive node
Start the Upgrade-CD on the active node and follow the Install Shield procedure
Change the settings for the Versant service (see chapter 2.3.2 Manual configurations after
SW-Installation) on the first node
Reboot both nodes
Resume the inactive node
Move the cluster group to the second node (the Versant resource must be offline!)
Start the Upgrade-CD on the second, now active, node and follow the Install Shield
procedure
Change the settings for the Versant service (see chapter 2.3.2 Manual configurations after
SW-Installation) on the second node
Reboot both nodes
Bring the Versant resource online and check if it is working on both nodes. (For Trouble
Shooting see chapter 2.3.4)
3.2 Corba (ORBIX)

Until know there is no necessary Corba upgrade
3.3 Domain Manager V8.2

3.3.1 Precondition
'ACI Hostname'
P50010-A0153-M002-2-7699
29 of 32
TABLE OF CONTENTS
'ACI IP Address'
'Shared Disk'
'Versant'
for a Domain Manager V8.2-Upgrade online. All other resources should be offline.
Change the settings for the Domain Manager V8.2 services (see chapter 2.5.2 Manual
configurations after SW-Installation) on the first node
Reboot both nodes
Move the cluster group to the second node (the 'ACI DM 8.2 Server', 'ACI Background',
'ACI DB Backup', 'ACI Root', 'ACI CONF', 'ACI Traffic' and 'ACI Params' resources
must be offline!)
procedure
Change the settings for the Domain Manager V8.2 services (see chapter 2.5.2 Manual
configurations after SW-Installation) on the second node
Reboot both nodes
Bring the Domain Manager V8.2 resources online and check if it is working on both nodes.
(For Trouble Shooting see chapter 2.5.4)
3.4 Element Manager XL3.0

3.4.1 Precondition
'ACI Hostname'
'ACI IP Address'
'Shared Disk'
'Versant'
for an Element Manager XL3.0-Upgrade online. All other resources should be offline.
Change the settings for the Element Manager XL3.0 services (see chapter 2.6.2 Manual
Reboot both nodes
P50010-A0153-M002-2-7699
30 of 32
TABLE OF CONTENTS
Move the cluster group to the second node (the ACI Brass, ACI SNMP Server', 'ACI EM XL
3.0 Server', 'ACI DB Backup' and 'ACI Root' resources must be offline!)
procedure
Change the settings for the Element Manager XL3.0 services (see chapter 2.6.2 Manual
Reboot both nodes
Bring the Element Manager XL3.0 resources online and check if it is working on both nodes.

For Trouble Shooting, please see also chapter 2.6.4.
Additionally to this chapter please check in the registry HKEY_LOCAL_MACHINE\SOFTWARE\Siemens
AG\Access Integrator V8.2 EM XL Server if the string SNMPServerVersion shows the new
version. If this is not true, please change the following registry entries on BOTH nodes to the
actual version
HKLM\SOFTWARE\Siemens AG\Access Integrator V8.2 EM XL Server\SNMPServerVersion
HKLM\SOFTWARE\Siemens AG\Access Integrator V8.2 EM XL Server\Installation\Version
HKLM\SOFTWARE\Siemens AG\Access Integrator V8.2 SNMP Server EMXL\Installation\Version
3.5 Network Manager TDM V8.2

3.5.1 Precondition
'ACI Hostname'
'ACI IP Address'
'Shared Disk'
'Versant'
'corba'
for an Network Manager TDM V2.0-Upgrade online. All other resources should be offline.
Change the settings for the Network Manager TDM 2.0 services (see chapter 2.6.2 Manual
Reboot both nodes
P50010-A0153-M002-2-7699
31 of 32
TABLE OF CONTENTS
Move the cluster group to the second node ('NM TDM V2.0 Server', 'ACI DB Backup' and
'ACI Root' resources must be offline!)
procedure
Change the settings for the NM TDM V2.0 services (see chapter 2.6.2 Manual
Reboot both nodes
Bring the Network Manager TDM V2.0 resources online and check if it is working on both
nodes.

For Trouble Shooting, please see also chapter 2.6.4.
P50010-A0153-M002-2-7699
32 of 32

Cluster Installation

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Cluster Installation

Uploaded by

Copyright:

Available Formats

Access Integrator

Cluster Installation and Upgrade

Barbara Wenzl - ICN CP D NM F2

All Rights Reserved.

0.1 Issue Control..........................................................................................................5

2.1 Precondition for installation on a Cluster...........................................................7

2.4 Corba (ORBIX)......................................................................................................11

2.5 Domain Manager V8.2.........................................................................................18

The document comprises 32 pages, all pages have issue no 05.

2.5.2 Manual configurations after SW-Installation...................................................................18

2.6 Element Manager XL3.0......................................................................................22

2.7 Network Manager TDM V8.2...............................................................................25

2.8 How to change the configuration of a Service.................................................28

3.2 Corba (ORBIX).....................................................................................................30

3.4 Element Manager XL3.0......................................................................................31

3.5 Network Manager TDM V8.2...............................................................................32

Reason for Changes

new issue / AFI

Unnecessary EM share for Background directory removed

DM share corrected: not os-conf but conf must be shared

Upgrade procedure added

Remove dependency to background share for ACI SNMP Server

Upgrade for ACI NM Server

0.3 List of Figures and Tables

NM, DM, EM, SNMP,

NM, DM, EM, SNMP,

Figure 1 ACI in a Cluster with shared RAID System

2.2 Basic cluster configuration for ACI

Listing properties for 'ACI IP Address':

2.3.3 Cluster configuration

Listing resource dependencies for 'Versant':

Now it is be possible to bring the Versant resources to online.

2.4 Corba (ORBIX)

After confirmation, check the Orbix installation path

This will show a selection menu:

Choose to create a new domain,

For example choose ACI_CORBA_DOMAIN for the domain name

Choose Configuration Repository Based for the domain type

Confirm the question to install the selected services as NT services

What port should the Configuration Repository use [3076]:

Confirm the proposed port number

Accept the default port number

Choose yes to deploy an Activator

Accept the preparation files generation

Use the default path

2.4.2.2 Corba Client

Run the configure.exe utility with the useprep parameter

Corba Activator daemon

2.5 Domain Manager V8.2

ACI DM TDM Server (8.2.x.y)

Listing resource dependencies for 'ACI CONF':

Now it is possible to bring the Domain Manager resources to online.

2.6 Element Manager XL3.0

Listing resource dependencies for 'ACI Brass':

ACI SNMP Server

ACI EM XL 3.0 Server

Listing resource dependencies for 'ACI Root':

Now it is possible to bring the EM XL resources to online.

2.7 Network Manager TDM V8.2

NM TDM 2.0 Server

Corba and Versant Dependencies as to be handle in the same way as by DM or EM.

# ACI NM TDM server

2.8 How to change the configuration of a Service