Kbase 20141: How to Connect a Multi-homed AdminServer from 2 Subnetworks
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/16/2008 |
|
Status: Unverified
GOAL:
How to Connect a Multi-homed AdminServer from 2 Subnetworks
GOAL:
How to Connect a Multi-homed AdminServer from 2 non-routing (separate) Subnetworks
FACT(s) (Environment):
Progress 9.x
FIX:
In addition to changes in the code, some manual editing of the JVM arguments (java system properties) is required.
The Progress patch for Version 9.1A (September 6, 2000) addresses the problem.
A permanent fix is written into Version 9.1B.
The problem was discovered by a Progress customer who tried to access the AdminServer with the Progress Explorer from each of two separate subnets (blind to each other). The Progress AdminServer was installed between these subnets with two possible network connections, two Network Interface Cards (NIC), and two IP addresses, one for each of the subnets/NICs.
The following clarifies the setup:
Server
|---------------|
|----Central----|
[IP#1]->|WebSpeed &/or |<-[IP#2]
[Network A]-------------|Progress server|-------------[Network B]
Progress | (AdminServer) | Progress
Explorer A |_______________| Explorer B
In the above configuration, the RMI layer in the AdminServer chooses a name that maps to only one of the IP Addresses. The name used by the RMI layer must be set to a name that can be resolved from both subnets.
This can be done by starting the AdminServer using the java system property:
java.rmi.server.hostname.
The java system properties for the AdminServer can be modified by using a proset.env file on UNIX. This optional file may need to be created. The file - proset.env - is a plain file with parameter/value pairs and it should be located in your PROPATH.
After you install the patch or upgrade Version 9.1B:
- On UNIX
a proset.env file should be created and the following line added:
JVMARGS="$JVMARGS -Djava.rmi.server.hostname=<hostname>"
- On Windows NT
change the value of the following Registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\PSC\AdminService\<version>\StartupCmd\Chimera
by adding:
-Djava.rmi.server.hostname=<hostname>
just before,
com.progress.chimera.adminserver.AdminServer.
The host server and the machines running the Progress Explorer clients need modifications made to their /etc/hosts files.
The following example reflects the above diagram (bigserver is the name given to the example server). The example:
Server:(servername = bigserver)
IP#1 - 10.1.1.1 (bigserver-a)
IP#2 - 10.1.2.1 (bigserver-b)
hosts file entry:
127.0.0.1 localhost loopback bigserver
Clients on 10.1.1.x [IP#1]subnet:
hosts file entry:
10.1.1.1 bigserver-a bigserver
Clients on 10.1.2.x [IP#2]subnet:
hosts file entry:
10.1.2.1 bigserver-b bigserver
These settings allow the clients to see the host and connect to the appropriate IP address on the server from their individual subnets. Please make sure that the IP address comes first in each line of the /etc/hosts file.