Академический Документы
Профессиональный Документы
Культура Документы
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:
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
1 INTRODUCTION
1.1 Overview.................................................................................................................6
1.2 Configuration.........................................................................................................6
2 INSTALLATION
P50010-A0153-M002-2-7699
2 of 32
3 UPGRADE
30
3.1 Versant..................................................................................................................30
3.1.1 Precondition....................................................................................................................... 30
3.1.2 Upgrade procedure............................................................................................................ 30
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
01
09.09.2002
02
19.09.2002
IUS
03
27.02.2003
04
27.03.2003
05
27.03.2003
06
11.04.2003
07
12.06.2003
Table 1: History
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
Server Process
Server Process
SharedRAID System
Switch over
Database Files
ACI Logs
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
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
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).
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)
P50010-A0153-M002-2-7699
9 of 32
TABLE OF CONTENTS
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]:
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]:
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
ATTENTION: Make sure, that the chosen directory is located on the shared disk!
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]:
Type the name, which is defined in the Cluster resource ACI Hostname (see 2.2)
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):
Type the name, which is defined in the Cluster resource ACI Hostname (see 2.2)
What port should the Locator use [3075]:
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]:
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
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
Corba Configuration Repository for ACI_CORBA_DOMAIN
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 Configuration Repository for ACI_CORBA_DOMAIN
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
P50010-A0153-M002-2-7699
16 of 32
TABLE OF CONTENTS
P50010-A0153-M002-2-7699
17 of 32
TABLE OF CONTENTS
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
P:\Program Files\Siemens AG\AccessIntegrator V8.2 Domain
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
P:\Program Files\Siemens AG\AccessIntegrator V8.2 Domain
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
P:\Program Files\Siemens AG\AccessIntegrator V8.2 Domain
ACI Traffic
Listing properties for 'ACI Traffic':
Name
ACI Traffic
Type
File Share
Description
ACI Traffic directory
ShareName
TRAFFIC
Path
P:\Program Files\Siemens AG\AccessIntegrator V8.2 Domain
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
P:\Program Files\Siemens AG\AccessIntegrator V8.2 Domain
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
P:\Program Files\Siemens AG\
AccessIntegrator V8.2 Domain\bin
InteractWithDesktop
1 (0x1)
UseNetworkName
1 (0x1)
Listing resource dependencies for 'Stop ACI DB':
Versant
P50010-A0153-M002-2-7699
19 of 32
TABLE OF CONTENTS
Services file
Check the services file on both nodes, which is located in
<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
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)
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
P:\Program Files\Siemens AG\AccessIntegrator V8.2 EM XL\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
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
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
P:\Program Files\Siemens AG\
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
P50010-A0153-M002-2-7699
23 of 32
TABLE OF CONTENTS
P50010-A0153-M002-2-7699
24 of 32
TABLE OF CONTENTS
ACI Background
ACI CONF
ACI DB Backup
Registry Replication:
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
Listing resource dependencies for 'ACI DB Backup':
Shared Disk
ACI CONF
Listing properties for 'ACI CONF':
Name
ACI DB Backup
Type
File Share
Description
ACI configuration files
ShareName
CONF
Path
the position of this shared folder
Listing resource dependencies for 'ACI DB Backup':
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
the position of this shared folder
Listing resource dependencies for 'ACI DB Backup':
Shared Disk
P50010-A0153-M002-2-7699
25 of 32
TABLE OF CONTENTS
acis-nmtdm
50195/tcp
P50010-A0153-M002-2-7699
26 of 32
TABLE OF CONTENTS
P50010-A0153-M002-2-7699
27 of 32
TABLE OF CONTENTS
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'
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
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
Bring the Versant resource online and check if it is working on both nodes. (For Trouble
Shooting see chapter 2.3.4)
'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.
3.3.2 Upgrade procedure
Start the Upgrade-CD on the active node and follow the Install Shield procedure
Change the settings for the Domain Manager V8.2 services (see chapter 2.5.2 Manual
configurations after SW-Installation) on the first node
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!)
Start the Upgrade-CD on the second, now active, node and follow the Install Shield
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
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)
'ACI Hostname'
'ACI IP Address'
'Shared Disk'
'Versant'
for an Element Manager XL3.0-Upgrade online. All other resources should be offline.
3.4.2 Upgrade procedure
Start the Upgrade-CD on the active node and follow the Install Shield procedure
Change the settings for the Element Manager XL3.0 services (see chapter 2.6.2 Manual
configurations after SW-Installation) on the first node
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!)
Start the Upgrade-CD on the second, now active, node and follow the Install Shield
procedure
Change the settings for the Element Manager XL3.0 services (see chapter 2.6.2 Manual
configurations after SW-Installation) on the second node
Bring the Element Manager XL3.0 resources online and check if it is working on both nodes.
'ACI Hostname'
'ACI IP Address'
'Shared Disk'
'Versant'
'corba'
for an Network Manager TDM V2.0-Upgrade online. All other resources should be offline.
3.5.2 Upgrade procedure
Start the Upgrade-CD on the active node and follow the Install Shield procedure
Change the settings for the Network Manager TDM 2.0 services (see chapter 2.6.2 Manual
configurations after SW-Installation) on the first node
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!)
Start the Upgrade-CD on the second, now active, node and follow the Install Shield
procedure
Change the settings for the NM TDM V2.0 services (see chapter 2.6.2 Manual
configurations after SW-Installation) on the second node
Bring the Network Manager TDM V2.0 resources online and check if it is working on both
nodes.
P50010-A0153-M002-2-7699
32 of 32