Configuring a Split Configuration
This procedure refers to the following variable elements:
<webapp> - The web application context root for Windchill that you entered when installing Info*Engine, for example "Windchill".
<Windchill_hostname> - Fully qualified host name of the Windchill host
<remote_Apache_hostname> - Fully qualified host name of the machine HTTP Server will run on.
<taskdispatcher_minport> - value of the wt.adapter.simpleTaskDispatcher.minPort property in Windchill
1. Following the instructions in this guide, install and configure Windchill together on a machine with its HTTP Server. Verify that you can access the Windchill server using a web browser through HTTP Server (see Using a URL to Access Windchill).
2. Install HTTP Server on the remote machine using a different hostname than the Windchill server, updating its configuration to enable it to recognize the Windchill installation.
3. Restart HTTP Server on the remote machine.
4. Update wt.properties on the Windchill server.
 |
When updating the wt.properties file, use the xconfmanager utility from within a windchill shell.
|
Set the following properties and propagate to wt.properties:
wt.rmi.clientSocketFactory=wt.boot.WTRMIMasterSocketFactory
wt.rmi.serverSocketFactory=wt.util.WrappedRMISocketFactory
wt.rmi.javarmicgi=servlet/JavaRMIServlet
wt.server.codebase=http://<remote_Apache_hostname>:<webserver port>/<webapp>
wt.rmi.serverSocketFactory=wt.util.WrappedRMISocketFactory
wt.rmi.javarmicgi=servlet/JavaRMIServlet
wt.server.codebase=http://<remote_Apache_hostname>:<webserver port>/<webapp>
For more information, see Reverse Proxies and Configuring RMI for Tunneling over HTTP.
5. Restart the Method Server.
6. Access the Windchill server using http://<remote_Apache_hostname>/<webapp>