Each RMI stub contains a server host name.

The value serialized into stub objects is controlled by the java.rmi.server.hostname property of the RMI server. This property identifies the fully qualified host name of the server where the properties in wt.properties are executed and is set in the code by default. You normally do not need to set the value of this property. This value is used for direct communication between the nodes in a cluster, JMX communication, and other internal communication.

The host name used to connect to the Windchill instance is stored in the wt.rmi.server.hostname property (which is initially set during installation as the value provided for the web server DNS host name). This host name is used by all clients that are not JMX clients. For a monolithic system, the web server DNS host name specified during installation provides the correct logical host name (also known as the symbolic name) in the wt.rmi.server.hostname property. For cluster configurations, you may need to update the value that was set during installation. For a simple cluster, ensure that this value is set to the cluster alias. If you are using a reverse proxy in front of the cluster, ensure that the property value is set to the reverse proxy host name. In a split-web-server configuration, set the property value to the web server host name. For more information about cluster environments, see Installing and Configuring a Cluster Environment.

You can use the xconfmanager utility to set wt.rmi.server.hostname to a symbolic name that all clients are able to resolve to a server address. Because Java applets can connect only to their codebase hosts, it should be the same symbolic name used in the wt.server.codebase property, which is used as the document base for Windchill HTML pages. If a Windchill server host name alias is used and it does not resolve to the local server (such as an alias for an IP load balancing server cluster), the name must be forced to resolve locally to the loopback address, 127.0.0.1. This is because the RMI stubs can contain only one host name, which will be used by all clients, both local and remote. However, to remain local, some local communication between the server manager and method servers must be guaranteed. If you give the system its own host name alias, as recommended above (rather than using actual host names), then you can safely override the local name resolution (in the /etc/hosts file) for this alias.

If required, you can set both the java.rmi.server.hostname and wt.rmi.server.hostname properties in the Windchill wt.properties file since the values in that file are used as Java system properties by the Windchill servers.