Deploy the rich client distribution instance on a supported Web application server.
Note If your Teamcenter network contains 32-bit and 64-bit systems, you must deploy 32-bit and 64-bit rich client distribution instances.
Users with 32-bit Web browsers must use the 32-bit Over-the-Web Installer, and users with 64-bit Web browsers must use the 64-bit Over-the-Web Installer.
Before you start
Install a supported third-party Web server.
A rich client distribution instance requires a Web server, such as Apache HTTP Server. You can also use an application server, such as IBM WebSphere, but it is not required. For information about supported Web servers and application servers, see the Siemens PLM Software Certification Database:
http://support.industrysoftware.automation.siemens.com/ certification/teamcenter.shtml Deploy the distribution server instance
Web Application Manager installs the following files in the webapp_root/otwweb directory under the distribution server instance staging location.
• otw_installer.jar file
Contains the Over-the-Web Installer.
• images directory
Contains all images used by the Web pages.
• installed.html file
Contains the English version of the HTML page displayed with installation completes successfully.
• installfailed.html file
Contains the English version of the HTML page displayed when installation fails.
• installing.html file
Contains the English version of the HTML page for launching the Over-the-Web Installer.
• launcherror.html file
Contains the English version of the HTML page displayed to the user when the Over-the-Web Installer cannot install the rich client due to one of the following problems:
o The connection to the Web is not available or the user has not provided permissions to install.
o The required Java Plug-in is not available and cannot be installed automatically.
o Java and or JavaScript are disabled in the Web browser.
• otw.html file
Contains the logic for detecting the Web browser and Java Plug-in required for installing the rich client over the Web.
• localized directory
Contains subdirectories for each supported locale other than English (French, German, Italian, Japanese, Korean, Russian, S_Chinese, Spanish, and
T_Chinese). The subdirectories contain localized versions of the installing.html and error.html files. To use a localized version of the installation, deploy the localized installing.html and error.html files rather than the English versions.
Note Before deploying a localized installing.html file, you must edit it as follows:
1. Using a text editor, find the following two lines and in each replace change_me_instance with the name of the instance:
<param name="instance" value="change_me_instance>
instance="change_me_instance"
2. Find the following two lines and in each replace change_me_server with the name of the server host:
<param name="server_name" value="change_me_server>
server_name="change_me_server"
When editing the preceding information, do not delete the quotation marks.
For each distribution server instance you create, deploy these files in a Web server.
If you are creating multiple rich client distribution instances, consider creating a unique directory in the Web server documentation root for each instance and copy all the files in the webapp_root/otwweb directory there. For detailed deployment information, see the documentation for the Web server. The following examples use the name of the instance for the Web component directory name:
Web server Deployment Apache HTTP
Server
1. In the conf configuration file, find the HTTP document root directory:
DocumentRoot “document-root-path”
2. Create the instance-name directory under the HTTP document root directory.
3. Copy the rich client Web file to the instance-name directory.
4. Publish the following URL:
http://host-name/instance-name/otw.html Apache Tomcat 1. In the server.xml configuration file, find the HTTP
document base directory. For example:
<!-- Tomcat Root Context -->
<!--<Context path="" docBase="ROOT" debug="0"/>
-->
2. Create the instance-name directory under the HTTP document base directory.
3. Copy the rich client Web components to the instance-name directory.
Web server Deployment
4. Publish the following URL:
http://host-name:8080/instance-name/otw.html Sun Java System 1. In the config configuration file, find the HTTP document
root directory. For example:
<VARS docroot="document-root-path">
2. Create the instance-name directory under the HTTP document base directory.
3. Copy the rich client Web components to the instance-name directory.
4. Publish the following URL:
http://host-name/instance-name/otw.html IBM WebSphere 1. Find the document root directory (HTTP server core
settings in the administration server console).
2. Create the instance-name directory under the HTTP document root directory.
3. Copy the Web components to the instance-name directory.
4. Publish the following URL:
http://host-name/instance-name/otw.html
Publish information for users
To enable users to install the rich client over the Web, publish the following information:
• URL where the Web components are located.
• The location in which the rich client will be installed on user workstations. Users must have write permissions for this location.
• For rich client instances that include support for Teamcenter lifecycle visualization or NX, the locations in which users must install Teamcenter lifecycle visualization and NX.
Note If your Teamcenter network contains 32-bit and 64-bit systems, you must provide 32-bit and 64-bit rich client distribution instances.
Users with 32-bit Web browsers must use the 32-bit Over-the-Web Installer, and users with 64-bit Web browsers must use the 64-bit Over-the-Web Installer.
Start and stop the rich client distribution server
You can start and stop the rich client distribution server as described in the following sections.
Start the rich client distribution server
1. Go to the staging location directory you created for the distribution server.
This is the directory containing the distribution server application and administration utilities.
2. In the webapp_root subdirectory find and run the start_rmi program file.
The start_rmi program file starts the Java remote method invocation (RMI) registry.
3. In the webapp_root subdirectory, find and run the start_server program file.
The start_server program file starts the distribution server.
When this distribution server is successfully started, it displays the following message:
Distribution Server Started
When the distribution server is running, rich client can be installed over the Web.
Stop the rich client distribution server
Stop a rich client distribution server from a local computer by using the control-C keys on the distribution server console. The distribution server stops, and cleanup progress is reported.
To stop a rich client distribution server from a remote computer, or if you changed the port number the RMI registry is running on, you must have file access to the stop_server program file and the dist_server.jar file in the webapp_root subdirectory of the distribution server staging location. To stop the distribution server, enter the following command:
stop_server host-name:port-number
Replace host-name with the name of the computer where the distribution server is running. Replace port-number with the port number.
The stop_server program prints the results of the remote shutdown. If the results include Java exceptions, errors occurred. Usually exceptions occur when no distribution server is running on the specified host.
To stop the RMI registry, use the operating system facilities.
The operating system facilities stop the RMI registry server.