|
Problem(Abstract) |
When gathering metrics across different domains,
explicitly set the java.rmi.server.hostname in the server script
(dsserver, ssserver, etc) to the fully-qualified domain name of the
machine that is requesting the metrics. |
|
|
|
Resolving the
problem |
When gathering metrics across different domains, you must
explicitly set the java.rmi.server.hostname in the server script
(lbserver, ssserver, etc) to the fully-qualified domain name (FQDN) of the
machine that is requesting the metrics. This is necessary because,
depending on your setup and operating system,
InetAddress.getLocalHost.getHostName() might not return the FQDN.
Example: Site Selector on a Windows platform, with a back-end server in a
different DNS domain.
Site Selector machine host name = foo.bar.com
Back-end server machine = metric.server.com
(Note: metric.server.com must be able to resolve foo.bar.com either
through /etc/hosts or through client DNS resolver.)
Set the java system property java.rmi.server.hostname to foo.bar.com in
ssserver.cmd file as follows:
javaw %LB_ENCODING% -Xrs -Xms64M -cp %LB_CLASSPATH% %LB_INSTALL_PATH%
%LB_CLIENT_KEYS% %LB_SERVER_KEYS% -Djava.rmi.server.hostname=foo.bar.com
-Djava.protocol.handler.pkgs=com.ibm.net.ssl.internal.www.protocol
com.ibm.internet.nd.server.SRV_SSRConfigServer %LB_RMIPORT% %LB_LOGDIR%
%LB_SAVEDIR% %LB_BINDIR% %LB_CONFIGFILE% %LB_RMISERVERPORT%
Stop and restart ssserver on foo.bar.com
Stop and restart the metricserver on metric.server.com
Note: For AIX, Solaris, HP-UX, and Linux, set java.rmi.server.hostname in
the appropriate server scripts.
|
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
WebSphere Edge Server |
Load Balancer |
AIX, Linux, Solaris, Windows 2000, Windows NT |
Edge Server 2.0 GA, Edge Server 2.0 NLV, Edge Server 2.0 PTF1, Edge
Server 2.0 PTF2 |
|
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|