Build additional Web applications
Teamcenter 10.1 Global Services Framework – CPM Connector for
Substance Compliance
Note • Some solutions require other solutions, and some solutions are
incompatible with others. When you select a solution, the Web Application Manager automatically selects prerequisite solutions and disables incompatible solutions.
• If you are installing the Teamcenter Enterprise Connector for Teamcenter Enterprise 2005 SR1 or an earlier release of Teamcenter Enterprise, ensure that you copy the mtiems.jar file to the same location as the mti.jar file. For more information, see Supporting files locations.
9. If you selected a connector that requires supporting files (seeSupporting files locations), click Modify Disk Locations and add the path to any supporting files. 10. Click OK.
The Web Application Manager displays the Modify Required Context
Parameters dialog box.
11. Enter values for required context parameters.
For most context parameters, accept the default values shown. At a minimum, Global Services requires values for the following context parameters:
To set a context parameter, double-click the Value box for the given parameter and enter the new value. To view a description of any context parameter, click the parameter name in the Modify Required Context Parameters dialog box. For more information about Global Services context parameters, seeGlobal Services context parameters.
Note For a description of these parameters, seeGlobal Services context parameters.
ApplicationInstance SSOAppID LogFileLocation TcGSBOSJNDI TcGSJDBCJNDI TcGSMessageServerJNDI TcGSNotifierReactorJNDI TcGSDORJNDI
To set a context parameter, double-click the Value box for the given parameter and enter the new value. To view a description of any context parameter, click the parameter name in the Modify Required Context Parameters dialog box. For more information about Global Services context parameters, seeGlobal Services context parameters.
12. Click OK to begin building the Web application.
The Web Application Manager displays the installation status in the Progress dialog box. When the installation is complete, click OK to close the Progress dialog box.
13. Click Exit to exit the Web Application Manager.
14. Locate the deployable files (by the names you specified in step7) generated during installation. This file is in the deployment directory under the specified staging location.
Deploy the Web application as described in theWeb Application Deployment Guide.6
Build a proxy WAR file for WebLogic
If you use WebLogic Express as a front-end HTTP listener, you must generate a proxy WAR file:
1. Launch the Web Application Manager (insweb.bat). 2. Click Add to begin creating the Web application.
Web Application Manager displays the Add Web Application dialog box. 3. Create the proxy WAR file Web application:
a. In the Name box, type the name of this application, for example, WebLogic
Proxy.
b. Accept the default value for Staging Location or enter a different directory. c. Optionally, type a description of the application in Description box.
d. Click Advanced Web Application Options. Type a name for the deployable file in the Deployable File Name box (alphanumeric characters only). e. Make sure the Disk Locations for Install Images box includes the path to
the Web_tier directory on the Teamcenter software distribution image.
6. The Web Application Deployment Guide provides deployment procedures specific to various supported application servers. Choose the appropriate procedure for the application server you use.
f. Click Solutions. In the Select Solutions dialog box, clear all preselected solutions and select only the Teamcenter – Web Tier Proxy solution.7 Note Do not change the default solution type (Thin Client) in the Solution
Type box.
4. Click OK.
The Web Application Manager displays the Modify Required Context
Parameters dialog box.
5. Enter values for the following required context parameters:
Parameter Description
WebLogicHost Host name of the WebLogic server running the Web tier. The proxy forwards the request to this server.
WebLogicPort Port number of the WebLogic server instance running the Web tier. The proxy forwards the request to this server.
To set a context parameter, double-click the Value box for the given parameter and enter the new value. To view a description of any context parameter, click the parameter name in the Modify Required Context Parameters dialog box. 6. Click OK to begin building the Web application. The Web Application Manager
displays the status of the installation in the Progress dialog box. When the installation is complete, click OK to close the Progress dialog box.
7. Click Exit to exit the Web Application Manager.
8. Locate the deployable file by the name you entered in step3. This file is in the
deployment directory under the specified staging location.
Deploy the Web application as described in theWeb Application Deployment Guide.8
Migrate legacy thin client URLs
If you migrate Web tier applications to Teamcenter 10.1 from Teamcenter engineering process management 2005 or earlier, you must update the link your site uses to access the thin client and the links users saved to objects managed in Teamcenter. Teamcenter 10.1 changes part of the thin client URL from /cgi-bin/iman to
/file-name/webclient. The file-name reference is replaced with the name of the Web
tier EAR file. For example, if the Web tier EAR file is named tc.ear, the value is /tc.
7. If this solution is not included in the solutions list, copy solution ICD files as described inBuild the Teamcenter Web Tier Web application.
8. The Web Application Deployment Guide provides deployment procedures specific to various supported application servers. Choose the appropriate procedure for the application server you use.
To manage this change, install the legacy URL support application (cgi-bin.war) and deploy it on the server where the Teamcenter Enterprise Tier Web application runs.
Note • Install the Teamcenter - Legacy URL (cgi-bin) Support thin client solution in a separate Web application. This solution is not compatible with other Teamcenter thin client solutions.
• Deploy the application so that it intercepts legacy requests and redirects them to the new URL location.
For example, if the original requests are going to port 9090, deploy the
cgi-bin.war application on port 9090. If the original requests are going
to server1, deploy the cgi-bin.war application on server1.
When the cgi-bin.war file is deployed, users who access a legacy /cgi-bin/iman URL are redirected to the /tc/webclient URL with the following message:
You have requested a resource which has moved to a new location. Requested URL: http://host:port/cgi-bin/iman/w8PJDvpRxBRxDD New URL: http://host:port/tc/webclient/w8PJDvpRxBRxDD
You will be redirected to the new URL automatically in nn seconds or you may click the above link manually. If possible, update your links to reflect the new location.
This notification message will be displayed each time an old URL is requested prior to month-day-year. After this time, requested resources that have moved will be automatically redirected to the new URL without notification.
When you create cgi-bin.war using Web Application Manager, you control aspects of the application:
• Whether the application displays the Siemens PLM Software URL message before redirecting users to the new URL. When you choose not to display the Siemens PLM Software URL message, the application redirects users to the new URL but displays no informative message.
• The period of time (in seconds) the application displays the Siemens PLM Software URL message before redirecting users to the new URL.
• The date the Siemens PLM Software URL message expires. After this date, the application redirects the users to the new URL but does not display the informative message.
• The protocol or the port, server, and domain portion of the requested, legacy URL. The application changes the Siemens PLM Software-provided portion of the URL and passes through the site-provided portion of the legacy URL. 1. Launch the Web Application Manager (insweb.bat).
2. Click Add.
Web Application Manager displays the Add Web Application dialog box. 3. Create the legacy URL support application Web application:
a. In the Name box, type the name of this application, for example, Legacy
URL Support.
c. Accept the default value for Staging Location or enter a different directory. d. Make sure the Disk Locations for Install Images box includes the path to
the Web_tier directory on the Teamcenter software distribution image. e. Click Solutions. In the Select Solutions dialog box, deselect all preselected
solutions and select only the Teamcenter – Legacy URL (cgi-bin) Support solution.9
Note Do not change the default solution type (Thin Client) in the Solution
Type box.
4. Click OK.
The Web Application Manager displays the Modify Required Context
Parameters dialog box.
5. Enter values for the following required context parameters:
Parameter Description
TcEngLocale Specifies a locale for messages displayed to the user. This locale must match the locale specified for the Teamcenter Enterprise Tier Web application.
expiryDateOfResource MovedNotification
Specifies the date the URL message expires. This parameter must contain a value. Enter a value in month-day-year format (mm-dd-yyyy), for example, 12-10-2007, or enter one of the following keywords:
NEVER
Specifies that the URL message never expires.
NOW
Specifies that no message or notification regarding the resource move is displayed to the user. The user is immediately redirected to the new URL.
To set a context parameter, double-click the Value box for the given parameter and enter the new value. To view a description of any context parameter, click the parameter name in the Modify Required Context Parameters dialog box. 6. Click OK to begin building the Web application.
The Web Application Manager displays the status of the installation in the
Progress dialog box. When the installation is complete, click OK to close the Progress dialog box.
9. If this solution is not included in the solutions list, copy solution ICD files as described inBuild the Teamcenter Web Tier Web application.
7. Click Exit to exit the Web Application Manager.
8. Locate the deployable file (cgi-bin.war) generated during installation. This file is in the deployment directory under the specified staging location.
Deploy the Web application as described in theWeb Application Deployment Guide.10
Note After installation, you can optionally modify the following context
parameters for legacy URL support:
requestRedirectedTo
replacementFor CGIBIN_IMAN redirectionWaitTime
For information about these context parameters, seeWeb tier context parameters.