1
Web Application Deployment Guide
Publication Number
PLM00015 J
PLM00015 J
Contents
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1-1
1-2
1-2
1-2
1-3
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-1
2-1
2-7
2-25
2-31
Figures
HSE deployment configuration . .
H-SE deployment configuration .
H-SE* deployment configuration
H*-SE* deployment configuration
PLM00015 J
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1-4
1-5
1-6
1-7
Contents
PLM00015 J
Chapter
PLM00015 J
Chapter
Deployment considerations
Deployment of your Teamcenter Web applications is an important step in setting up
your Teamcenter environment. How you deploy the Web application is determined
by how you intend to use Teamcenter and can affect the applications performance.
1. Consider the high-level requirements of your deployment.
For more information about high-level requirements, see Determining your
requirements.
2. Review the different supported deployment configurations to determine which is
best for your enterprise.
For descriptions of the supported configurations, see Basic concepts of Teamcenter
Web application deployment.
3. Determine your application server. The application server you use may impact
your deployment configuration. Not all configurations are supported for all
application servers.
For information about the supported configurations for Teamcenter Web
applications, see Teamcenter Web application deployment.
Global Services Web applications are supported for basic deployments only.
For the information about the versions of application servers certified for your
platform, see the Siemens PLM Software Certification Database:
http://support.industrysoftware.automation.siemens.com/
certification/teamcenter.shtml
Note
Teamcenter and Global Services Web applications support IPv6 for Web tier
communications for the following application servers:
PLM00015 J
JBoss 7.1
WebSphere 8.5
1-1
Chapter 1
WebLogic 12c
Note
Support for IPv6 requires a dual stack application server host and a dual
stack Teamcenter server host.
For information about supporting IPv6 and dual stack networks on
you application server hose, see your Windows, UNIX, or Linux server
documentation.
Enable a Web
application
1-2
PLM00015 J
Definition
Basic deployment
(HSE)
Basic deployment
A stand-alone HTTP Web server is configured as the
with front-end HTTP front-end to a J2EE application server.
Web server (H-SE)
Clustered
deployment with
front-end HTTP Web
server (H-SE*)
Clustered
deployment
with front-end,
load-balanced
HTTP Web servers
(H*-SE*)
PLM00015 J
Enterprise archive
(EAR)
Network load
balancing (NLB)
1-3
Chapter 1
Term
Definition
Teamcenter
Server
Teamcenter
Server
Server
Pool
Manager
Servlet, JSP/EJB
/Resource Adapter
Instance
Cache Data
Access
Server
Pool
Manager
Client
Client
Client
Server/
HTTP Listener
HSE
Cache Data
Access
Tree Cache
Cache Data
Access
Server
Pool
Teamcenter
Server
The following figures show each of the deployment configurations for Teamcenter
Web tier applications.
1-4
PLM00015 J
PLM00015 J
Client
Client
Client
Firewall
Proxy Plugin
HTTP Server
Server
Pool
Manager
Server
Pool
Manager
Tree Cache
Cache Data
Access
Servlet, JSP/EJB
/Resource Adapter
Instance
SE
Cache Data
Access
Cache Data
Access
DMZ
Teamcenter
Server
Teamcenter
Server
Teamcenter
Server
Server
Pool
1-5
1-6
Client
Client
Client
H*
Firewall
Proxy Plugin
HTTP Server
DMZ
Server
Pool
Manager
Server
Pool
Manager
Tree Cache
Cache Data
Access
Servlet, JSP/EJB
/Resource Adapter
Instance
Servlet, JSP/EJB
/Resource Adapter
Instance
Servlet, JSP/EJB
/Resource Adapter
Instance
[SE]*
Cache Data
Access
Cache Data
Access
Teamcenter
Server
Teamcenter
Server
Teamcenter
Server
Server
Pool
Chapter 1
Getting started deploying Web applications
PLM00015 J
PLM00015 J
Client
Client
Client
Firewall
Load
Balancer
Proxy Plugin
HTTP Server
Proxy Plugin
HTTP Server
Proxy Plugin
HTTP Server
Servlet, JSP/EJB
/Resource Adapter
Instance
Servlet, JSP/EJB
/Resource Adapter
Instance
Servlet, JSP/EJB
/Resource Adapter
Instance
[SE]*
H*
Server
Pool
Manager
Tree Cache
Cache Data
Access
Server
Pool
Manager
Cache Data
Access
Cache Data
Access
DMZ
Teamcenter
Server
Teamcenter
Server
Teamcenter
Server
Server
Pool
1-7
Chapter
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-1
2-2
2-4
2-6
2-6
2-7
2-7
2-7
2-9
PLM00015 J
2-12
2-14
2-15
2-16
2-16
2-19
2-19
2-20
2-20
2-21
2-21
2-21
2-22
2-22
2-23
2-23
. 2-25
. 2-25
. 2-26
. 2-26
. 2-27
. 2-29
. 2-30
Configure Apache HTTP (Web) server as the listener for a cluster . . . . 2-31
Deploy WebSphere application server cluster with HTTP (Web) server . . . . 2-31
Deploying clustered with front-end load-balanced HTTP servers . . . . . . . . . . . 2-31
Configure Microsoft IIS load balancing . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32
PLM00015 J
Chapter
Caution
#
#
#
#
#
#
#
#
#
#
#
#
#
#
Basic deployment
These basic deployments procedures provide instructions for deploying the
Teamcenter Web tier application (EAR file bundling a WAR file) in selected
configurations on selected J2EE application servers.
PLM00015 J
2-1
Chapter 2
Instructions for enabling secure socket layer (SSL) on an application server are
provided in the application server documentation.
For more information, see the vendor documentation for the following application
servers:
JBoss
WebSphere
WebLogic
Note
If you use SSL with your Teamcenter Web tier application, you must set the
WEB_protocol thin client preference in Teamcenter to https://.
For information about using Teamcenter preferences, see the Rich Client
Interface Guide.
Note
This procedure assumes that you downloaded and installed the JBoss 7.1.0
final version and you are using the stand-alone server location for deploying
your Teamcenter Web application.
1. Copy the Teamcenter EAR (by default, tc.ear) file to the following directory:
jboss-as-7.1.0.Final
standalone
deployments
2. Define JMX as a global module.
a. Expand the configurations directory and open the standalone.xml file.
jboss-as-7.1.0.Final
standalone
configuration
b.
2-2
PLM00015 J
<subsystem xmlns="urn:jboss:domain:ee:1.0">
<global-modules>
<module name="org.jboss.as.jmx" slot="main"/>
</global-modules>
</subsystem>
c.
If you require IPv6 support, locate the interface element for the public
interface and modify its contents as follows:
<interface name="public">
<any-address/>
</interface>
3. Define a dependency to allow the JBoss connector module to use JMX MBeans.
a. Expand the main directory and open the module.xml file.
jboss-as-7.1.0.Final
modules
org
jboss
as
connector
main
b.
Locate the dependencies element, and add the following module element:
<module name="org.jboss.as.jmx"/>
Check Command line parameters and Interfaces and ports in the JBoss
documentation.
5. If you require IPv6 support, open the standalone_conf script file in your JBoss
installation bin directory and add the following settings:
-Djava.net.preferIPv4Stack=false
-Djava.net.preferIPv6Addresses=false
PLM00015 J
2-3
Chapter 2
6. Open a command shell and ensure you have defined the JAVA_HOME
environment variable, and set it to the location of your Java installation. The
Teamcenter Web application requires Java 1.7.
7. Start the server by typing standalone (standalone.sh on UNIX) -b host-name
in the command shell.
Note
You must start the application server instance with the bind option
to enable connections from clients running on a host different from
the application server host. The simplest way to do this is to start the
server with the -b host-name option. Substitute the host name or IP
address of the local host for host-name. However, this has some security
implications.
For information about JBoss security, see the JBoss documentation at:
http://www.jboss.org/community/docs/DOC-12188
Note
If the Web tier encounters errors obtaining JCA connections under peak
activity, increase the Max_Pool_Size context parameter value for your
Teamcenter Web application.
For information about changing this context parameter value, see
Troubleshooting four-tier architecture deployment.
2-4
PLM00015 J
6. In the Map modules to servers pane, if you have multiple server instances,
select the check boxes for all modules and map them to the same server instance.
Click Next again.
7. In the summary pane, click Finish. Wait for WebSphere to complete the
application deployment.
8. When WebSphere displays a message indicating the application deployed
successfully, scroll to the bottom of the page and click Manage Applications.
9. In the Enterprise Application pane, click the Teamcenter application name.
10. In the Configuration page, click the Teamcenter application name.
11. Click Manage Modules under Modules.
12. Click JETIResourceAdapter in the Module column.
13. Click Resource Adapter under Additional Properties.
14. Click J2C connection factories under Additional Properties.
15. Click com.teamcenter.jeti.resourceadapter.spi.IJetiConnectionFactory in the
Name column.
16. Type jca/enterprise-app-reg-id/Adapter in the JNDI name box and click Apply.
Note
19. Click Apply, scroll to the top of the page, and click Save.
Your application is now deployed and can be started.
20. In the Enterprise Applications pane, select the Teamcenter Web application
check box and click Start.
PLM00015 J
2-5
Chapter 2
2-6
PLM00015 J
If the Web tier encounters errors obtaining JCA connections during peak
activity, increase the Max_Pool_Size context parameter value for your
Teamcenter Web application.
Note
Deploys the Teamcenter Web tier application (EAR file bundling the WAR file)
on the JBoss Application Server
Note
This procedure assumes that you downloaded and installed the JBoss 7.1.0
final version and you are using the stand-alone server location for deploying
your Teamcenter Web application.
1. Copy the Teamcenter EAR (by default, tc.ear) file to the following directory:
jboss-as-7.1.0.Final
standalone
PLM00015 J
2-7
Chapter 2
deployments
2. Define JMX as a global module.
a. Expand the configurations directory and open the standalone.xml file.
jboss-as-7.1.0.Final
standalone
configuration
b.
c.
If you require IPv6 support, locate the interface element for the public
interface and modify its contents as follows:
<interface name="public">
<any-address/>
</interface>
3. Microsoft IIS uses the AJP 1.3 protocol to forward requests to JBoss. If the
default port for the AJP 1.3 protocol (8009) is not available on your host
running JBoss, update the port number in the following element in the
JBoss-installation/standalone/ /configuration/standalone.xml file:
<socket-binding name="ajp" port="8009" />
Record this value for use when you configure the redirector.
4. Define a dependency to allow the JBoss connector module to use JMX MBeans.
a. Expand the main directory and open the module.xml file.
jboss-as-7.1.0.Final
modules
org
jboss
2-8
PLM00015 J
as
connector
main
b.
Locate the dependencies element, and add the following module element:
<module name="org.jboss.as.jmx"/>
Tip
6. If you require IPv6 support, open the standalone_conf script file in your JBoss
installation bin directory and add the following settings:
-Djava.net.preferIPv4Stack=false
-Djava.net.preferIPv6Addresses=false
7. Open a command shell and ensure you have defined the JAVA_HOME
environment variable, and set it to the location of your Java installation. The
Teamcenter Web application requires Java 1.7.
8. Start the server by typing standalone (standalone.sh on UNIX) -b host-name
in the command shell.
Note
You must start the application server instance with the bind option
to enable connections from clients running on a host different from
the application server host. The simplest way to do this is to start the
server with the -b host-name option. Substitute the host name or IP
address of the local host for host-name. However, this has some security
implications.
For information about JBoss security, see the JBoss documentation at:
http://www.jboss.org/community/docs/DOC-12188
Note
If the Web tier encounters errors obtaining JCA connections under peak
activity, increase the Max_Pool_Size context parameter value for your
Teamcenter Web application.
For information about changing this context parameter value, see
Troubleshooting four-tier architecture deployment.
PLM00015 J
2-9
Chapter 2
For additional information about the settings in these files, see the Tomcat
documentation:
http://tomcat.apache.org/connectors-doc/
1. Create a directory (for example, iis75-jboss7) for the redirector in a location
accessible to Microsoft IIS that contains the following directories:
bin
conf
log
wwwroot
2. Download the ISAPI Redirector from a mirror site for the Apache Tomcat Web
site:
http://www.apache.org/dist/tomcat/tomcat-connectors/jk/binaries/
Note
3. Configure Windows registry settings on the host where IIS and ISAPI Redirector
are installed.
a. In the ISAPI Redirector installation directory, create a file with a .reg
extension. The name of this file is discretionary (isapi_redirector.reg is
recommended).
b.
Siemens PLM Software recommends that you use debug for the log_level
entry when you initially configure the redirector to get all messages. You can
change this after you have tested your installation and determined that it is
working properly. The following table provides a brief description of these
entries:
2-10
Name
Description
extension_uri
log_file
log_level
PLM00015 J
Name
Description
worker_file
worker_mount_file
For more information about these registry settings, see the Apache Tomcat
Connector Reference Guide:
http://tomcat.apache.org/connectors-doc/reference/iis.html
c.
Change the following lines in the .reg file to reflect your directory settings:
A. For log_file, enter the location of the logs directory you created and the
name of the log file.
The log file itself is created later by the ISAPI Redirector.
B. For worker_file, enter a location for the worker definition file. It
is recommended that you create this file in the directory where you
installed the Tomcat ISAPI Redirector. You create this file later.
C. For the worker_mount_file, enter a location for the worker-URI map
file. You create this file later.
D. For the extension_uri, enter tomcat.
The default port is 8009. If you changed this AJP port number in JBoss
configuration when you configured the Tomcat ISAPI Redirector, use that value.
The host-name value is the host where you run JBoss.
5. Save the file as workers.properties in the directory you defined for it in the
registry file.
6. Create a text file with contents similar to the following:
# Send all /tc requests to node1
/tc/*=node1
PLM00015 J
2-11
Chapter 2
Replace tc with the name of your Teamcenter Web application (tc by default).
This configures the redirector to forward all requests with the /tc/* signature to
node1.
7. Save the file as uriworkermap.properties. Save this file in the same directory
as the workers.properties file.
Install and configure the Tomcat ISAPI Redirector on Windows Server 2008
You must install the Tomcat ISAPI Redirector and configure the Windows
registry for the redirector. You must also create the workers.properties and
uriworkermap.properties files for the redirector.
For additional information about the settings in these files, see the Tomcat
documentation:
http://tomcat.apache.org/connectors-doc/
1. Create a directory (for example, iis75-jboss7) for the redirector in a location
accessible to Microsoft IIS that contains the following directories:
bin
conf
log
wwwroot
2. Download the ISAPI Redirector from a mirror site for the Apache Tomcat Web
site:
http://www.apache.org/dist/tomcat/tomcat-connectors/jk/binaries/
Note
Siemens PLM Software recommends that you use debug for the log_level
entry when you initially configure the redirector to get all messages. You can
2-12
PLM00015 J
change this after you have tested your installation and determined that it is
working properly. The following table provides a brief description of these
entries:
Name
Description
extension_uri
log_file
log_level
worker_file
worker_mount_file
uri_select
For more information about these registry settings, see the Apache Tomcat
Connector Reference Guide:
http://tomcat.apache.org/connectors-doc/reference/iis.html
c.
Change the following lines in the .reg file to reflect your directory settings:
A. For log_file, enter the location of the logs directory you created and the
name of the log file.
The log file itself is created later by the ISAPI Redirector.
B. For worker_file, enter a location for the worker definition file. Siemens
PLM Software recommends that you create this file in the directory
where you installed the Tomcat ISAPI Redirector. You create this file
later.
C. For the worker_mount_file, enter a location for the worker-URI map
file. You create this file later.
D. For the extension_uri, enter tomcat.
PLM00015 J
2-13
Chapter 2
The default port is 8009. If you changed this AJP port number in JBoss
configuration when you configured the Tomcat ISAPI Redirector, use that value.
The host-name value is the host where you run JBoss.
5. Save the file as workers.properties in the directory you defined for it in the
registry file.
6. Create a text file with contents similar to the following:
# Send all /tc requests to node1
/tc/*=node1
Replace tc with the name of your Teamcenter Web application (tc by default).
This configures the redirector to forward all requests with the /tc/* signature to
node1.
7. Save the file as uriworkermap.properties. Save this file in the same directory
as the workers.properties file.
Configure Microsoft Internet Information Services
If you are using a Windows Server 2008 host, perform the procedure described in
Configure Microsoft Internet Information Services on Windows Server 2008 instead
of this procedure.
1. Open the IIS Manager and choose StartAdministrative ToolsInternet
Information Services (IIS) Manager.
2. In the Connections pane, expand your computer name until you see Sites.
3. Add a new Web site for your deployment:
a. Right-click Sites and choose Add Web Site.
b.
In the Add Web Site dialog box, type a name for the site in the Site name
box, for example, iis75-jboss75.
c.
In the Physical path box, type or browse to the location of the wwroot
directory you created in Install and configure the Tomcat ISAPI Redirector
on Windows Server 2008.
d. In the Port box, type a value for the binding port, for example, 8028, and
click OK.
4. Add a virtual directory:
a. In the Connections pane, right-click your new site name and choose Add
Virtual Directory.
2-14
PLM00015 J
b.
c.
In the Physical path box, type the path or browse to the bin directory you
created in Install and configure the Tomcat ISAPI Redirector on Windows
Server 2008 and click OK.
c.
c.
d. Click Add.
e.
In the Path to file box, type the path or click Browse to navigate to the
isapi_redirector.dll file, and click OK.
f.
Select the Set extension status to Allowed check box and click OK.
In the Add Web Site dialog box type a name for the site in the Site name
box, for example, iis75-jboss75.
c.
In the Physical path box, type or browse to the location of the wwwroot
directory you created in Install and configure the Tomcat ISAPI Redirector
on Windows Server 2008.
d. In the Port box, type a value for the binding port, for example, 8028 .
e.
Clear the Start Web site immediately check box and click OK.
PLM00015 J
2-15
Chapter 2
a. In the Connections pane, right-click your new site name and choose Add
Virtual Directory.
b.
c.
In the Physical path box, type the path or browse to the bin directory you
created in Install and configure the Tomcat ISAPI Redirector on Windows
Server 2008 and click OK.
c.
d. In the Edit Module Mapping dialog box, type an asterisk (*) character in
the Request path box
e.
Click the browse button next to the Executable box and browse to the
location of the isapi_redirector.dll file.
f.
Click Request Restrictions and clear the Invoke handler only if request is
mapped to check box on the Mapping tab.
g.
Click the Verbs tab and ensure the All verbs option is selected.
h. Click the Access tab, ensure the Execute option is selected, and click OK.
i.
In the Connections pane, select you new site name and click Start in the
Actions pane (on the right side under Manage Web Site).
2-16
PLM00015 J
PAG=C11&SSN=12HFE0003463254433&TRL=TXT&WRD=WebSphere+
Application+Server+v8&PBL=&LST=ALL&RPP=10&submit=Go
1. Install the WebSphere application server on host A. Use the installation wizard
for WebSphere Application Server.
2. Install the IBM HTTP server with the required plug-in on host B. Use the
installation wizard for IBM HTTP Server. If using a different Web server, skip
this wizard and install the Web server per the vendors instructions on host B.
3. If using a previously installed IBM HTTP server or a different Web server,
install the Web server plug-in on host B. Use the installation wizard for Web
Server plug-ins.
4. Copy the configureWeb-server-name script file from the plugins-install-root/bin
directory on host B to the profiles-install-root/profile-name/bin directory on host
A.
5. In a command shell, run the configureWeb-server-name script. This creates a
Web server definition file for the integrated solutions console. You can now use
the console to manage the Web server.
6. Start the WebSphere application server.
7. Start the WebSphere integrated solutions console.
For more information about the console, see the WebSphere documentation.
8. Propagate the Web server plug-in file and configure the Web server to accept all
content.
For an IBM HTTP server:
Note
For most other Web servers, you must manually apply the Web server
plug-in file to the Web server environment, However, It may be possible
to propagate some other Web server plug-in files in this manner.
PLM00015 J
Select AcceptAllContent from the Accept content for all requests list and
click OK.
2-17
Chapter 2
9. In the navigation tree, expand Applications and click Install New Application.
10. In the Preparing for the application installation pane, type the path to, or
browse to, the location of the Teamcenter Web tier EAR file in the Full path box.
Select Prompt me only when additional information is required and click Next.
11. Accept the default Select installed options for enterprise applications and
modules and click Next.
12. In the Map modules to servers pane, if you have multiple server instances,
select the check boxes for all modules and map them to the same server instance.
Click Next again.
13. In the summary pane, click Finish. Wait for WebSphere to complete the
application deployment.
14. When WebSphere displays a message indicating the application deployed
successfully, scroll to the bottom of the page and click Manage Applications.
15. In the Enterprise Application pane, click the Teamcenter application name.
16. In the Configuration page, click the Teamcenter application name.
17. Click Manage Modules under Modules.
18. Click JETIResourceAdapter in the Module column.
19. Click Resource Adapter under Additional Properties.
20. Click J2C connection factories under Additional Properties.
21. Click com.teamcenter.jeti.resourceadapter.spi.IJetiConnectionFactory in the
Name column.
22. Type jca/enterprise-app-reg-id/Adapter in the JNDI name box and click Apply.
Note
2-18
PLM00015 J
25. Click Apply, scroll to the top of the page, and click Save.
Configure the HTTP Web server
1. Open the Teamcenter site_specific.properties file and modify the following
properties:
portalCommunicationTransport=http
HTTP_SERVER_1.URI=http://host-name:port-number/tc-name/webclient
Replace host-name and port-number with the WebSphere application server host
name and HTTP listening port number. Replace tc-name with your Teamcenter
Web application name; by default, this value is tc.
2. In the Integrated Solutions Console navigation tree, expand
EnvironmentVirtual Host and click default_host.
3. Click Host Aliases under Additional Properties and click New.
4. Type the Web server listening port number in the Port box and click OK.
5. In the navigation tree, expand EnvironmentUpdate global web server plug-in
configuration and click OK.
6. Propagate the plug-in configuration file to the Web server. The Web server
plug-in configuration service propagates the plugin-cfg.xml file automatically
for IBM HTTP server. For all other Web servers, propagate the plug-in
configuration file manually. For information about propagating the plug-in
configuration file, see the WebSphere application server documentation.
Note
c.
PLM00015 J
2-19
Chapter 2
2-20
PLM00015 J
Note
If the Web tier encounters errors obtaining JCA connections during peak
activity, increase the Max_Pool_Size context parameter value for your
Teamcenter Web application.
For information about changing this context parameter value, see
Troubleshooting four-tier architecture deployment.
If WebLogic reports an error (BEA-000402) due to more active sockets than
socket readers, add the -Dweblogic.ThreadPoolSize=100 parameter when
starting the application server.
PLM00015 J
2-21
Chapter 2
If the Web tier encounters errors obtaining JCA connections during peak
activity, increase the Max_Pool_Size context parameter value for your
Teamcenter Web application.
For information about changing this context parameter value, see
Troubleshooting four-tier architecture deployment.
If WebLogic reports an error (BEA-000402) due to more active sockets than
socket readers, add the -Dweblogic.ThreadPoolSize=100 parameter when
starting the application server.
Ensure your clients connect to the WebLogic Express host and port,
rather than the Web application server.
2-22
PLM00015 J
If the Web tier encounters errors obtaining JCA connections during peak
activity, increase the Max_Pool_Size context parameter value for your
Teamcenter Web application.
For information about changing this context parameter value, see
Troubleshooting four-tier architecture deployment.
If WebLogic reports an error (BEA-000402) due to more active sockets than
socket readers, add the -Dweblogic.ThreadPoolSize=100 parameter when
starting the application server.
PLM00015 J
2-23
Chapter 2
Note
Ensure that you copy the DLL file from the 32 directory for 32-bit
operating systems or the x64 directory for 64-bit operating systems.
These are not interchangeable and cause errors if you copy the wrong
DLL file.
In the Add Web Site dialog box, type a name for your Web site in the Site
name box, for example, IISWLS, and click the browse button (
the Physical path box.
c.
) next to
In the Browse for Folder dialog box, browse to the directory that contains
the iisproxy.dll and iisforward.dll files and click OK.
d. In the Port box, type a unique port number, for example 8088, and click OK.
5. Add ISAPI Filters:
a. In the Connections pane, select your new Web site and double-click ISAPI
Filters in the Web site Home pane.
Note
You may have to scroll down in the Home pane to access ISAPI
Filters.
b.
c.
In the Add ISAPI Filter dialog box, type a name for the filter in the Filter
name box, for example, iisforward, and click the button next to the
Executable box.
d. In the Open dialog box, browse to the iisforward.dll file location, double-click
the file name, and click OK.
6. Configure a handler mapping:
a. In the Connections pane, select your new Web site and double-click Handler
Mappings in the Web site Home pane.
b.
c.
In the Add a Script Map dialog box, type *.wlforward in the Request path
box and click the button next to the Executable box.
d. Browse to the Web sites home folder and select the iisproxy.dll file.
e.
2-24
Type a name for the script map in the Name box, for example, iisproxy,
and click OK.
PLM00015 J
f.
Click Yes in the Add a Script Map dialog box to allow the ISAPI extension.
7. Create an iisproxy.ini file in the directory that contains the DLLs. This file
must contain the following information:
WebLogicHost=dns-name-or-ip-address
WebLogicPort=listening-port-for-WLS
WlForwardPath=/tc-Web-applicationname
Debug=ALL
DebugConfigInfo=ON
Note
PLM00015 J
2-25
Chapter 2
This change allows the Teamcenter Web Application, when running on multiple
application server instances on the same host, to initialize the TreeCache by
binding to a vacant port within the designated range.
3. Copy the TreeCacheTCP.xml file into the startup class path of your application
servers as follows:
Note
This is required to override this configuration file in the EAR file. You
must restart all servers instances involved after copying this file to the
indicated directories.
For WebLogic, copy the file to the domain root directory. The domain root
is the directory where there can be multiple standalone application servers
or cluster members.
For WebSphere, copy the file to the profile root directory. The profile root is
the directory where there can be multiple standalone application servers
or cluster members.
For JBoss, copy the file to the bin directory of each server instance.
For Oracle Application Server, copy the file to the home directory of each
application server instance, typically the install-root/j2ee/home directory.
Deploys Teamcenter Web tier applications (EAR file bundling the WAR file)
on a Oracle WebLogic Server cluster.
Configures WebLogic Express (WLX) server as the front-end Web tier server
for the cluster. In this configuration, WLX is used as the Web tier providing a
JSP/servlet container in a four-tier architecture supporting the Teamcenter
enterprise application.
Deploys one instance of the Teamcenter proxy application (WAR file) hosted on
the WebLogic Express (WLX) server.
Note
For the list of currently supported Web application servers and HTTP Web
servers for each operating system, see the Siemens PLM Software Global
Technical Access Center (GTAC).
2-26
PLM00015 J
If the Web tier encounters errors obtaining JCA connections during peak
activity, increase the Max_Pool_Size context parameter value for your
Teamcenter Web application.
For information about changing this context parameter value, see
Troubleshooting four-tier architecture deployment.
If WebLogic reports an error (BEA-000402) due to more active sockets than
socket readers, add the -Dweblogic.ThreadPoolSize=100 parameter when
starting the application server.
c.
PLM00015 J
2-27
Chapter 2
d. Click OK.
Note
e.
2-28
PLM00015 J
</servlet>
<servlet-mapping>
<servlet-name>HttpClusterServlet</servlet-name>
<url-pattern>/</url-pattern>
</servlet-mapping>
-->
Replace <WeblogicClusterHost1>:<port1>|<WeblogicClusterHost1>
:<port2> with the host name and port number for each WebLogic server
participating in the cluster.
4. If the context root of the proxy WAR file does not match the context root of the
Teamcenter Web application:
a. Open the weblogic.xml file in this same directory.
b.
Modify the following entry to match the context root Teamcenter Web
application (EAR file) deployed in the application server where the proxy
forwards requests:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-web-app
PUBLIC "-//Oracle Systems, Inc.//DTD Web Application 8.1//EN"
"http://www.Oracle.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
<!--==============================================================================
Copyright (c) 2004 UGS
Unpublished - All rights reserved
==================================================================================
Filename:
weblogic.xml
==================================================================================
Date
Name
Description of Change
11-Apr-2005 vardhan
Proxy weblogic.xml
$HISTORY$
===============================================================================-->
<weblogic-web-app>
<context-root>/tc</context-root>
</weblogic-web-app>
5. In the Web Application Manager, select the solution name and click Modify.
6. Click Generate Deployable File and click OK.
Note
7. Install WebLogic Express and create a domain for deploying the Teamcenter
proxy WAR file.
For information creating domains and deploying WAR files in WebLogic, see
the WebLogic server documentation:
http://www.oracle.com/technetwork/middleware/weblogic/
documentation/weblogic-server-096635.htmll
8. Deploy the Teamcenter Web Tier Proxy file in WebLogic Express.
Note
Ensure your clients connecting to the proxy Web application use the host and
port of the front-end server (WebLogic Express). Clients must not connect to
any of the Web application servers in the cluster.
PLM00015 J
2-29
Chapter 2
Deploys the Teamcenter Web tier application (EAR file bundling the WAR file)
on a Oracle WebLogic Server cluster.
Configures Sun Java System Web Server running as the front-end HTTP listener
for the cluster.
If the Web tier encounters errors obtaining JCA connections during peak
activity, increase the Max_Pool_Size context parameter value for your
Teamcenter Web application.
For information about changing this context parameter value, see
Troubleshooting four-tier architecture deployment.
If WebLogic reports an error (BEA-000402) due to more active sockets than
socket readers, add the -Dweblogic.ThreadPoolSize=100 parameter when
starting the application server.
2-30
PLM00015 J
PLM00015 J
2-31
Chapter 2
instructions for all possible configurations. You can use the Microsoft IIS load
balancing instructions as a guide.
3. In the Network Load Balancing Manager dialog box, right-click the Network
Load Balancing Clusters root node and choose New cluster.
4. Define the cluster parameters:
a. Type the virtual IP address you selected for the cluster in the IP address box.
b.
Type a subnet mask in the Subnet mask box. You must use the same subnet
mask for all servers in the cluster.
Note
c.
2-32
The Full Internet name value is only for reference and is used
primarily for displaying the name of the server. However, if you have
a domain configured for the server you may use that domain name.
If your server has more than one network adapter, click Unicast for the
Cluster operation mode. If you are using a single adapter, Siemens PLM
Software recommends that you select Multicast to allow both the NLB traffic
and the native IP traffic to move through the same network adapter.
PLM00015 J
Note
d. Clear the Allow Remote Control check box and click Next.
Note
If you need this functionality, enable it after you have the cluster
running.
Select the All check box and type 80 in both the From and To boxes.
c.
d. Click Multiple hosts for Filtering mode and None for Affinity.
e.
Click OK.
Select the All check box and type 443 in both the From and To boxes.
c.
d. Click Multiple hosts for Filtering mode and Single for Affinity.
e.
Click OK.
Node 1 is the master, which means that it receives requests and acts
as the routing manager. Although when the load is high on this
node, other machines may take over for the master.
b.
Click Connect.
c.
Click Next.
d. In the Host Parameters dialog box, select 1 from the Priority list.
Note
e.
Priority sets a unique ID for each node in the cluster. The lower the
number the higher the priority.
Click Finish.
The Network Load Balancing Manager configures your network adapter. The
network connection flashes on and off a few times during this configuration
PLM00015 J
2-33
Chapter 2
process on the sever you are configuring as a host. When the configuration is
complete, the Status column displays Converged for the node.
9. In the Network Load Balancing Manager, right-click the cluster domain and
choose Connect.
10. Repeat step 8 until all nodes have been added to the cluster.
2-34
PLM00015 J
Chapter
PLM00015 J
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-1
3-1
3-3
3-4
3-5
3-6
3-9
3-13
3-13
3-15
3-16
3-16
3-17
3-17
3-18
3-19
3-19
. . . . 3-20
. . . . 3-20
. . . . 3-20
. . . . 3-21
Chapter
PLM00015 J
3-1
Chapter 3
Caution
Record the database name and type; you must have this information during the
deployment procedure.
Teamcenter provides the following Global Services database scripts:
Note
The script files contain comments that provide additional information about
their purpose and use.
Create scripts
File name
Purpose
oracle_create_tcgs.sql
sqlserver_create_tcgs.sql
db2_create_tcgs.sql
hsqldb_create_tcgs.sql
oracle_drop_tcgs.sql
sqlserver_drop_tcgs.sql
hsqldb_drop_tcgs.sql
Upgrade scripts
3-2
File name
Purpose
oracle_upgrade_tcgs_v20070.sql
sqlserver_upgrade_tcgs_v20070.sql
oracle_upgrade_tcgs_v20071.sql
sqlserver_upgrade_tcgs_v20071.sql
oracle_upgrade_tcgs_v200711.sql
oracle_upgrade_tcgs_v200712.sql
oracle_upgrade_tcgs_v200713.sql
oracle_upgrade_tcgs_v200714.sql
oracle_upgrade_tcgs_v200715.sql
oracle_upgrade_tcgs_v200716.sql
PLM00015 J
File name
Purpose
oracle_upgrade_tcgs_v200717.sql
oracle_upgrade_tcgs_v200718.sql
oracle_upgrade_tcgs_v20072.sql
sqlserver_upgrade_tcgs_v20072.sql
oracle_upgrade_tcgs_v80000.sql
sqlserver_upgrade_tcgs_v80000.sql
oracle_upgrade_tcgs_v80001.sql
sqlserver_upgrade_tcgs_v80001.sql
oracle_upgrade_tcgs_v80002.sql
sqlserver_upgrade_tcgs_v80002.sql
db2_upgrade_tcgs_v80003.sql
sqlserver_upgrade_tcgs_v80003.sql
oracle_upgrade_tcgs_v80003.sql
db2_upgrade_tcgs_v8000301.sql
Upgrade from Teamcenter 8.3.0.1 to the
sqlserver_upgrade_tcgs_v8000301.sql current release
Deploy on Websphere 8
After you deploy the Web tier application, as a minimum you must perform the
initial configuration, as described in the Global Services Configuration Guide, to
enable Global Services.
http://appserver-host:port-number/GS-app-context-root/controller/index
Replace appserver-host and port-number with the host name and port number the
application server uses. Replace GS-app-context-root with the context root the
application server uses for the Global Services Web tier application; this is usually
the EAR file name without the extension.
PLM00015 J
3-3
Chapter 3
The data store is populated with the initial content the first time that you access
the Global Services Web tier application.
Deploy the Global Services application
The following provides information for deploying the Global Services EAR file. If you
are familiar with deploying applications on your application server, this information
may be sufficient to allow you to perform the installation. For more detailed
instructions, see the appropriate application server topic.
Note
1. Start the application server administration tool if your application server has
one.
Note
2. Create a connection pool and a data source that uses it. Choose an appropriate
driver for your database. The following table provides suggested driver values.
Note
JDBC database
Driver class
Driver type
Default port
DB2
COM.ibm.db2.jdbc.app.DB2Driver
5000
MySQL
org.gjt.mm.mysql.Driver
3306
Oracle
oracle.jdbc.pool.OracleDriver
1521
SQL server
com.microsoft.sqlserver.jdbc.
SQLServerXADataSource
Other
1433
Provide user name and password values to connect to the database for a
database user with read and write access.
The ApplicationInstance context parameter determines the JNDI name for
the data store. This parameter value is defined when you build the Global
Services Web tier application and is used at the beginning of the JNDI name.
The JNDI name is GlobalServicesInstance1/jdbc/GlobalServicesDB if you
accept the default value for the context parameter.
Provide the URL the JDBC connection uses to connect to the database, for
example:
Oracle database:
jdbc:orcle:thin:@host-name:port-number:Oracle-SID
3-4
PLM00015 J
3. Create the following queues if you have included the Teamcenter 10.1 Global
Services - JMS Messaging solution in your Web application:
jms.actionDestination=javax/jms/action
jms.responseDestination=javax/jms/response
4. Deploy the enterprise application you generated as described in the
documentation for your application server.
Caution
Deploy on Websphere 8
Do not enable application server security on the application server where
you deploy the Global Services Web application
Note
1. Before you deploy the Global Services application (EAR) file, complete the
following:
a. Download the binary archive file from the Apache Tomcat site at the
following link:
http://tomcat.apache.org/download-70.cgi
b.
Use an archive management tool, such as 7-Zip file manager, to extract the
servlet-api.jar file in the lib directory of the Tomcat archive file into a
directory accessible to the application server. Note the path to the file for
later use.
c.
Open the Global Services Web application EAR file in 7-Zip file manager and
delete the EAR/lib/asix2-jaxws-1.4.jar file.
7. Type the full path and filename for each of the following files, delimited by
semicolons, into the Classpath box.
Note
The path to the servlet-api.jar file was noted in a previous step. This
must be the last entry in the Classpath property. The other files are
located in the WEB_ROOT/staging-directory/earapp_root/lib directory.
commons-io-1.4.jar
PLM00015 J
3-5
Chapter 3
commons-fileupload-1.2.jar
woden-api-1.0M8.jar
commons-codec-1.3.jar
commons-httpclient-3.1.jar
commons-logging-1.1.1.jar
log4j-1.2.15.jar
servlet-api.jar
8. Click OK, Save , and restart the application server.
9. Deploy the ODE Web applications as described in Configure the application
server for ODE.
10. Configure the deployed ODE Web application:
a. Click the deployed ODE Web application and click Manage Modules under
the Modules section in the Enterprise Applications pane.
b.
c.
Choose Classes loaded with local class loader first (parent last) from
the Class loader order list.
You can start with a low two-digit number if you do not expect
a large number of transfer requests. If you experience time-out
exceptions, increase the value.
You can set properties by manually editing in the
globalservices.properties file in the Global Services datastore or
using the Global Services Web Manager interface.
For information about managing the Global Services datastore, see the
Global Services Configuration Guide.
b.
c.
3-6
PLM00015 J
JNDI Name
Database Type
Database Driver
PLM00015 J
Database Name
Host Name
3-7
Chapter 3
Port
Properties
12. Review the connection parameters and click Test Configuration. If there are
any configuration errors, go back and correct them. If the test is successful,
click Next.
13. Select the servers or clusters on which you want to deploy the data source and
click Finish.
14. If you installed the Teamcenter 10.1 Global Services - JMS Messaging solution,
you must create the required queues.
Note
You can use any JMS provider that you desire. You can also create a
separate JMS server or JMS module to contain your queues.
For more information, see the WebLogic Server Administration Console
Help.
In the JMS Modules page, click the desired module name and click New in
the Summary of Resources table.
c.
e.
Note
3-8
You can provide a queue name if you do not want to use the default
provided.
Repeat this process (step 14) using javax/jms/response for the JNDI Name
value.
Not all changes take effect immediately. For information, see the WebLogic
documentation.
PLM00015 J
The JBoss add-user utility displays prompts for the type of user, realm, user
name, and password. The utility displays default values for user type and
realm in parentheses. Press Enter to accept the default values for user type
and realm (Management User and ManagementRealm).
What type of user do you wish to add?
a) Management User (mgmt-users.properties)
b) Application User (application-users.properties)
(a):
PLM00015 J
3-9
Chapter 3
</subsystem>
For development and testing purposes, you can make the JBoss management
console accessible to remote hosts by editing the inet-address element:
<interface name="management">
<inet-address value="${jboss.bind.address.management:0.0.0.0}"/>
</interface>
Warning
3. If you are deploying the Teamcenter 10.1 Global Services Framework - Ode
BPEL Enterprise Application solution for any reason:
a. Using an archive file management tool, such as 7-Zip File Manager, expand
the ODE archive (tcgs-ode.EAR in the following example) file and remove
the Persistence.xml file from the METAINF locations:
tcgs-ode.EAR
tcgs-ode.WAR
WEB-INF
lib
ode-dao-jpa-1.3.5.jar
META-INF
ode-bpel-store-1.3.5.jar
META-INF
b.
Open the standalone startup batch file or shell script in the following
location:
JBOSS_HOME
bin
standalone
Add the following entry prior to the JBoss bootstrap environment section:
set JAVA_OPTS=-Dorg.apache.ode.rootDir=full path to
ode-working-dir %JAVA_OPTS%
echo =============================================================
echo.
echo
JBoss Bootstrap Environment
3-10
PLM00015 J
foo
myjdbcdriver
main
You can use any valid directory name for the foo and myjdbcdriver
directories.
b.
c.
Create a module.xml file in the main directory that contains the following:
<module xmlns="urn:jboss:module:1.0" name="directory-structure">
<resources>
<resource-root path="driver-file-name"/>
</resources>
<dependencies>
<module name="javax.api"/>
</dependencies>
</module>
For the path attribute (driver-file-name) value, type the database driver file
name. For example, for an Oracle database:
<resource-root path="ojdbc6.jar"/>
d. Open the standalone.xml file that you edited in step 2, locate the drivers
element, and add a driver element as child to the element:
<subsystem xmlns="urn:jboss:domain:datasources:1.0">
<datasources>
<drivers>
.
.
.
<driver name="driver-name" module="directory-structure">
<datasource-class>driver-class-name</datasource-class>
</driver>
</drivers>
Type any unique value for the name (driver-name) attribute value and for
the module (directory-structure) attribute value, type the same value you
used for the name attribute in module.xml file. Type the driver class name
in the data-source-class element, for example:
oracle.jdbc.driver.OracleDriver
e.
PLM00015 J
3-11
Chapter 3
<security>
<user-name>datasource-username</user-name>
<password>datasource-password</password>
</security>
</datasource>
</datasources>
Type the data source JNDI name for the jndi-name (data-source-JNDI-name)
attribute value. This value must have a java:/ prefix.
Type the URL of the JDBC connection for the database for the
connection-url (driver-URL) element value. For example, for an Oracle
database connection:
jdbc:orcle:thin:@host-name:port-number:Oracle-SID
Type the driver class name in the data-source-class element, for example:
oracle.jdbc.driver.OracleDriver
Type the user name used to connect to the database in the user-name
element and the password associated with that user in the password
element.
5. Deploy the EAR file:
a. Open the JBoss console in a browser on the host where JBoss is running:
http://localhost:9990/console
b.
Log on, click Runtime in the top right corner, and click Manage Deployments
in the left pane.
Note
c.
Click Add Content in the Deployments pane and click Browse in the Upload
dialog box.
d. Navigate to the location of the Global Services Web application EAR file
(tcgs.ear by default) and click Open.
e.
After JBoss finishes deploying the application, click the applications Enable
button in the Deployments pane.
You must start the JBoss application server instance with the bind option to enable
connections from clients running on a host different from the application server
host. The simplest way to do this is to start the server with the -b myhost option.
Substitute the host name or IP address of the local host for myhost, for example:
standalone -b 0.0.0.0
3-12
PLM00015 J
1. Create an ODE working directory that is accessible to the application server. For
example, on a UNIX system, create the /mnt/disk1/ode-working-dir directory.
2. Copy the contents of the ode-working-dir directory located in the
WEB_ROOT\staging-directory\earapp_root directory.
3. Deploy the Web application as described in the topic for your application server.
4. Modify the application server Java start options for your application server:
Select Application servers and select the server where you deployed the
Global Services Web application.
c.
Locate the Generic JVM arguments box and add the following argument
at the end of its contents:
-Dorg.apache.ode.rootDir=complete-path-to-ode-working-dir
-Dcom.ibm.websphere.webservices.DisableIBMJAXWSEngine=true
PLM00015 J
3-13
Chapter 3
Note
f.
Property
Value
3-14
PLM00015 J
Caution
1. Check the default settings in the ode-axis2.properties file. For most setups, no
changes are required. The comments in the file provide information about the
settings. Change settings as required.
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
PLM00015 J
3-15
Chapter 3
###hibernate.transaction.manager_lookup_class
## e.g. classname.of.TransactionManagerLookup
## The classname of a TransactionManagerLookup. Examples:
## org.hibernate.transaction.JBossTransactionManagerLookup
## org.hibernate.transaction.WeblogicTransactionManagerLookup
## org.hibernate.transaction.WebSphereTransactionManagerLookup
## org.hibernate.transaction.WebSphereExtendedJTATransactionLookup
JBoss
Weblogic
WebSphere
WebSphere 6
## Default settings
ode-axis2.db.mode=EXTERNAL
ode-axis2.db.ext.dataSource=GlobalServicesInstance1/jdbc/GlobalServicesDB
ode-axis2.dao.factory=org.apache.ode.daohib.bpel.BpelDAOConnectionFactoryImpl
#hibernate.hbm2ddl.auto=update
hibernate.current_session_context_class=jta
#hibernate.transaction.manager_lookup_class=
#hibernate.dialect=
Installing the Global Services signer certificate to the Teamcenter rich client
Installing the Global Services signer certificate to the Teamcenter thin client
3-16
PLM00015 J
Note
For WebSphere application servers, you must enable the States Federal
Information Standard (FIPS) algorithms. The Use the United States Federal
Information Standard (FIPS) algorithms option is located under Security |
SSL certificate and key Management section in the WebSphere integrated
solutions console.
Instructions for enabling secure socket layer (SSL) on an application server are
provided in the application server documentation.
See Deploy the Global Services application for additional information about
application server SSL configuration.
Configuring File Management System for SSL
You must configure File Management System (FMS) to use a purchased vendor
certificate authority that is supported by standard distributions of the Java runtime
environment. The following variables are used in these procedures:
key store-file
key store-password
FSC-myhost
FSC-myhost
-password
FSC-myhost .csr
FSC-myhost .cer
PLM00015 J
3-17
Chapter 3
FSC-myhost-password
3. Verify the key entry by typing the following command and prompt replies:
keytool -list -key store key store-file
Enter key store password: key store-password
key store type: jks
key store provider: SUN
4. Back up the key store file to a secure location. The private key is stored in this
file and is unrecoverable if the file or passwords are lost.
Obtain a signed certificate
You must create a certificate signing request (CSR) and submit it to a certificate
authority (CA) to receive the signed certificate. The process of submitting the CSR
and receiving the signed certificate from the CA varies by signing authority.
1. Generate a CSR from the private key by typing the following command and
prompt replies in your FSC_HOME directory:
keytool -certreq -key store key store-file -alias FSC-myhost -file
FSC-myhost.csr
Enter key store password: key store-password
Enter key password for <FSC-myhost> FSC-myhost-password
2. Open the fsc-myhost.csr file and verify the contents are similar to the following:
-----BEGIN NEW CERTIFICATE REQUEST----MIIBtjCCAR8CAQAwdjELMAkGA1UEBhMCbXkxEDAOBgNVBAgTB215c3RhdGUxDzANBgNVBAcTBm15
Y2l0eTESMBAGA1UEChMJbXljb21wYW55MRIwEAYDVQQLEwlteWNvbXBhbnkxHDAaBgNVBAmTE215
aG9zdC5teWRvbWFpbi5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAJ0h3iF8KBEN2UKw
hw1dw+RlxGwcsptLA3EI+6rAKa32dg/4FY89zBcUG02413X0BxQWcsRznYWFDJHLK4En7I2xeJNs
ORwJfBeF9yW6d4lzaWA6LATFr5T3DHafF6mSRNPl+739mpGuQr44AXBQWqZoOMhecc+n/ErekMlZ
dgWTAgMBAAGgADANBgkqhkiG9w0BAQQFAAOBgQCQJTqujL7GIXz0is0fUoAxtCydMiX1BeVHU+l/
IqcTh4BX8V3vJmm+kHwwKn3yeih+WJzYmDdNh/uaKxO7txyFdPPDd1bdIosFc4XIZwys0jFKwGqf
MUjB9wgaKgHSRQTtCOPBEO/ClLjm8ocFNQBWysYVevAZQAmEMp90BxBt/Q==
-----END NEW CERTIFICATE REQUEST-----
3. Submit the CSR file to the certificate signing authority and receive the signed
certificate using the process defined by the signing authority.
4. Import the signed certificate into the FSC server by typing the following
command and prompt replies in your FSC_HOME directory:
keytool -import -trustcacerts -key store key
storefile -file FSC-myhost.cer -alias FSC-myhost
Enter key store password: key store-password
Enter key password for <FSC-myhost> FSC-myhost-password
3-18
PLM00015 J
2. Configure the FMS master file for SSL through the following as required:
3. Modify any of the following bootstrap configuration values to use the new scheme
(or port) as required:
For an example one-way SSL FSC and FMS configuration, see Configuring Global
Services for HTTPS.
Configure Global Services application as a trusted client
This process depends on the application server you are using for your Global Services
Web application. Similar process to the ones provided for WebSphere and WebLogic
is required for the other supported application servers.
For WebSphere:
1. Log on to the Integrated Solutions Console and navigate to the Key stores and
certificates section (SecuritySSL certificate and key managementKey
stores and certificates).
2. Select the key stores that you create for the Global Services Web application
certificate and for the File Management System (FMS) certificate and click
Exchange Signers.
3. Select the FMS key store and add it as a signer for the Global Services Web
application.
For WebLogic:
1. Open a command shell and navigate to the Java Runtime Environment (JRE) for
your WebLogic domain where you Global Services Web application is deployed.
2. Import the FMS certificate to the Java cacerts key store using the Java keytool
-import utility.
PLM00015 J
3-19
Chapter 3
3. Use the keytool utility to verify the security certificate was added to the portal
key store, for example:
keytool list keystore ..\lib\security\cacerts
The rich client is configured as a trusted client. Try a transfer between sites
using the rich client to verify the configuration.
Install the Global Services signer certificate to Teamcenter thin client
You must import the certificate for the Global Services Web application into the
internet browsers that you use to access your Teamcenter thin client. This process
varies by browser and operating system. The following procedures are for the
currently supported Firefox and Internet Explorer versions on Windows but can be
used as a guide for other browsers and operating systems.
For Firefox:
1. Choose ToolsOptions and click Advanced.
2. Click View Certificates and click the Your Certificates tab.
3. Click Import and navigate to the certificate file and click Open. Type the
certificates pass phase when prompted and click OK.
3-20
PLM00015 J
Note
1. In the Organization application, select the node of the remote site definition
from the Organization List tree.
2. Modify the value in the TcGS URL box to the HTTPS URL for the Global
Services Web application and click Modify.
3. Select the node of the local site definition from the Organization List tree.
4. Modify the value in the TcGS URL box to the HTTPS URL for the Global
Services Web application and click Modify.
5. Choose EditOptions and click Search in the Options dialog box.
6. Search for TC_gms and modify the values for the following preferences as
indicated:
Preference
Value
TC_gms_server
TC_gms_server_ca_file
TC_gms_server_ca_path
TC_gms_sso_enabled
FALSE
Note
PLM00015 J
3-21
Appendix
PLM00015 J
Appendix
PLM00015 J
A-1
Appendix A
A-2
PLM00015 J
the reverse proxy. The cookie patterns for the proxy servers are defined in the
tcsso_rp_cookienamepattern context parameter during the TCCS installation
process as part of the Security Services configuration.
The TcProxyClient component also supports one-way and two-way SSL using
smart card client certificate or soft client-certificate authentication. Client-certificate
authentication is more secure than any of the other supported forms of
authentication. A client certificate can be either of the following:
A smart card containing a certificate that complies with the PKCS#11 standard.
Smart-card authentication is an example of two-factor authentication (2FA).
Two-factor authentication requires the presentation of something the user knows
and something the user has.
Note
PLM00015 J
A-3
Appendix A
IBM WebSEAL
CA SiteMinder
Note
Note
A-4
PLM00015 J
address=https://fscmidzone.yourcompany.com:4544
options=needclientauth>
or
<connection id=another2waySSLconn
protocol=https port=4545
options=needclientauth/>
3. Add trusted certificates to the keystore that can validate the clients that are
allowed to connect.
Note
The trusted certification from the CA, for example the thawte premium
server CA certificate, is required in addition to the client certificate.
Several logical and/or physical zones exist behind the reverse proxy. These are
separated by firewalls.
Reverse proxy sends traffic to an FMS Server Cache (FSC) located within the
same zone (using one-way SSL).
Client zone
All clients are on one side of the reverse proxy server. All communication is
routed through the reverse proxy to the backend servers. The only resource the
clients communicate with is the reverse proxy server.
PLM00015 J
A-5
Appendix A
Middle zone
The location of the reverse proxy, Web tier, first FSC, and LDAP.
Resource zone
The second FSC, volumes, and Oracle.
Definition
fscgroup
A-6
midzone
reszone
PLM00015 J
Element
Definition
FSC
The FSC for each zone is defined within the groups and one FSC
is defined to represent the reverse proxy server, as follows:
clientmap
FSC_fscmidzone_infodba
FSC_fscreszone_infodba
FSC_proxy_infodba
FSC_fscmidzone_infodba
The FSC that is the FMS configuration master.
o
$FSC_HOME/fmsmaster_FSC_fscmidzone_infodba.xml
Master FMS configuration file. For more information, see Configuration
element details, earlier in this appendix.
$FSC_HOME/FSC_fscmidzone_infodba.xml
FSC configuration file that specifies the fscid and master/slave state.
FSC_fscreszone_infodba
o
$FSC_HOME/fmsmaster_FSC_fscreszone_infodba.xml
Local copy of the master FMS configuration file.
$FSC_HOME/FSC_fscreszone_infodba.xml
FSC configuration file that specifies the fscid and master/slave state.
PLM00015 J
A-7
Appendix A
$FMS_HOME/fcc.xml
<parentfsc
address="http://reverseproxy.yourcompany.com:80/tc/fms/471539747"/>
...
...
$FSC_HOME/FSC_fscmidzone_infodba.xml
...
<fscmaster serves="true"/>
...
$FSC_HOME/FSC_fscreszone_infodba.xml
This is the slave fsc.xml file that points to the master FSC. This is on the same
side of the reverse proxy; therefore, a direct reference is used here.
...
<fscmaster serves="false"
address="http://fscmidzone.yourcompany.com:4544/tc/fms/471539747"/>
...
Fms_BootStrap_Urls preference
This value is used to bootstrap other FMS client integrations. The value must
be appropriate for clients outside of the WebSEAL or SiteMinder reverse proxy;
therefore, it points to the reverse proxy.
For example, for a WebSEAL reverse proxy:
http://webseal.yourcompany.com:80/tc/fms/471539747
A-8
PLM00015 J
Definition
FSC
The addresses defined for the FSCs specify https. This causes
the listener to be configured for SSL. The port on the FSC
representing the reverse proxy is changed to use 443 rather than
80.
FSC_fscmidzone_infodba
Specifies the FMS configuration master.
o
$FSC_HOME/fmsmaster_FSC_fscmidzone_infodba.xml
The master FMS configuration file.
$FSC_HOME/FSC_fscmidzone_infodba.xml
FSC configuration file that specifies the fscid and master/slave state.
$FSC_HOME/fsc.FSC_fscmidzone_infodba.properties
Additional properties for this FSC used to configure the keystore.
$FSC_HOME/keystore.FSC_fscmidzone_infodba.jks
Keystore for this FSC.
FSC_fscreszone_infodba
Specifies the FMS configuration slave.
o
$FSC_HOME/fmsmaster_FSC_fscreszone_infodba.xml
Local copy of the master FMS configuration file.
$FSC_HOME/FSC_fscreszone_infodba.xml
FSC configuration file that specifies the fscid and master/slave state.
$FSC_HOME/fsc.FSC_fscreszone_infodba.properties
Additional properties for this FSC used to configure the keystore.
PLM00015 J
A-9
Appendix A
$FSC_HOME/keystore.FSC_fscreszone_infodba.jks
The keystore for this FSC.
Fms_BootStrap_Urls preference
This value is used to bootstrap other FMS client integrations. The value must
be appropriate for clients outside of the WebSEAL or SiteMinder reverse proxy;
therefore, it points to the reverse proxy.
For example, for WebSEAL:
http://webseal.yourcompany.com:443/tc/fms/471539747
$FSC_HOME/fsc.FSC_fscmidzone_infodba.properties
The property file used to configure the keystore.
# fsc.FSC_fscmidzone_infodba.properties
com.teamcenter.fms.servercache.keystore.file=$<FMS_HOME}/keystore.FSC_fscmidzone_infodba.jks
com.teamcenter.fms.servercache.keystore.password=keystore.FSC_fscmidzone_infodba.password
com.teamcenter.fms.servercache.keystore.ssl.certificate.password=keystore.FSC_fscmidzone_infodba.password
# these are not needed for 1-way SSL
# javax.net.ssl.keyStore=$<FMS_HOME}/keystore.FSC_fscmidzone_infodba.jks
# javax.net.ssl.keyStorePassword=keystore.FSC_fscmidzone_infodba.password
# javax.net.ssl.trustStore=$<FMS_HOME}/keystore.FSC_fscmidzone_infodba.jks
# javax.net.ssl.trustStorePassword=keystore.FSC_fscmidzone_infodba.password
$FSC_HOME/keystore.FSC_fscmidzone_infodba
The keystore for this FSC. The keystore must contain the private key and
certificate for the local machine.
fscmidzone> keytool -list -v -keystore keystore.FSC_fscmidzone_infodba.jks
-storepass keystore.FSC_fscmidzone_infodba.password
Keystore type: jks
Keystore provider: SUN
Your keystore contains 1 entries
Alias name: fscmidzone.yourcompany.com
Creation date: Jan 23, 2008
Entry type: keyEntry
Certificate chain length: 2
Certificate[1]:
Owner: CN=fscmidzone.yourcompany.com, OU=QA, O=YOUR Corp, L=Plano, ST=Texas, C=US
Issuer: EMAILADDRESS=premium-server@thawte.com, CN=Thawte Premium Server CA, OU=Certification Services
Division,
O=Thawte Consulting cc, L=Cape Town, ST=Western Cape, C=ZA Serial number: 485099dcc36d1ea9d773ba153022a951
Valid from: Thu Jan 10 16:44:38 CST 2008 until: Thu Mar 27 13:20:25 CDT 2008 Certificate fingerprints:
MD5: 86:7E:16:59:99:E6:6F:B6:27:9B:92:19:E7:65:EB:A2
SHA1: 6A:D1:64:7A:0A:E1:CB:62:D3:EF:91:BF:E9:A0:CE:AF:A3:3D:E4:1E
Certificate[2]:
A-10
PLM00015 J
$FSC_HOME/fsc.FSC_fscreszone_infodba.properties
The property file used to configure the keystore.
# fsc.FSC_fscreszone_infodba.properties
com.teamcenter.fms.servercache.keystore.file=$<FMS_HOME}/keystore.FSC_fscreszone_infodba.jks
com.teamcenter.fms.servercache.keystore.password=keystore.FSC_fscreszone_infodba.password
com.teamcenter.fms.servercache.keystore.ssl.certificate.password=keystore.FSC_fscreszone_infodba.password
# these are not needed for 1-way SSL
# javax.net.ssl.keyStore=$<FMS_HOME}/keystore.FSC_fscreszone_infodba.jks
# javax.net.ssl.keyStorePassword=keystore.FSC_fscreszone_infodba.password
# javax.net.ssl.trustStore=$<FMS_HOME}/keystore.FSC_fscreszone_infodba.jks
# javax.net.ssl.trustStorePassword=keystore.FSC_fscreszone_infodba.password
$FSC_HOME/keystore.FSC_fscreszone_infodba
The keystore for this FSC. The keystore must contain the private key and
certificate for the local machine.
fscreszone> keytool -list -v -keystore keystore.FSC_fscreszone_infodba.jks
-storepass keystore.FSC_fscreszone_infodba.password
Keystore type: jks
Keystore provider: SUN
Your keystore contains 1 entries
Alias name: fscreszone.yourcompany.com
Creation date: Jan 23, 2008
Entry type: keyEntry
Certificate chain length: 2
Certificate[1]:
Owner: CN=fscreszone.yourcompany.com, OU=QA, O=YOUR Corp, L=Plano, ST=Texas, C=US
Issuer: EMAILADDRESS=premium-server@thawte.com, CN=Thawte Premium Server CA, OU=Certification Services
Division,
O=Thawte Consulting cc, L=Cape Town, ST=Western Cape, C=ZA Serial number: 485099dcc36d1ea9d773ba153022a951
Valid from: Thu Jan 10 16:44:38 CST 2008 until: Thu Mar 27 13:20:25 CDT 2008 Certificate fingerprints:
MD5: 86:7E:16:59:99:E6:6F:B6:27:9B:92:19:E7:65:EB:A2
SHA1: 6A:D1:64:7A:0A:E1:CB:62:D3:EF:91:BF:E9:A0:CE:AF:A3:3D:E4:1E
Certificate[2]:
Owner: EMAILADDRESS=premium-server@thawte.com, CN=Thawte Premium Server CA, OU=Certification Services
Division,
O=Thawte Consulting cc, L=Cape Town, ST=Western Cape, C=ZA
Issuer: EMAILADDRESS=premium-server@thawte.com, CN=Thawte Premium Server CA, OU=Certification Services
Division,
O=Thawte Consulting cc, L=Cape Town, ST=Western Cape, C=ZA Serial number: 1
Valid from: Wed Jul 31 19:00:00 CDT 1996 until: Thu Dec 31 17:59:59 CST 2020 Certificate fingerprints:
MD5: 06:9F:69:79:16:66:90:02:1B:8C:8C:A2:C3:07:6F:3A
SHA1: 62:7F:8D:78:27:65:63:99:D2:7D:7F:90:44:C9:FE:B3:F3:3E:FA:9A
*******************************************
*******************************************
PLM00015 J
A-11
Appendix A
address="https://fscmidzone.yourcompany.com:4545"
options="needclientauth">
<!-- the following connection element adds an additional
connection supporting SSL(1-way) to this FSC -->
<connection id="1waysslcon" protocol="https" port="4544"/>
</fsc>
<!-- the following fsc element represents the WebSEAL proxy -->
<fsc id="FSC_webseal_infodba"
address="https://reverse_proxy.yourcompany.com:443"/>
<!-- the following clientmap element is used to map particular
clients (e.g. DAK server, Web Application Server) within the
midzone to the 1-way SSL connection of the midzone FSC -->
<clientmap subnet="146.122.69.94" mask="255.255.255.255">
<assignedfsc fscid="FSC_fscmidzone_infodba"
connectionid="1waysslcon"/>
</clientmap>
<!-- the following clientmap element maps all (remaining)
clients to the WebSEAL proxy -->
<clientmap subnet="127.0.0.1" mask="0.0.0.0">
<assignedfsc fscid="FSC_proxy_infodba"/>
</clientmap>
</fscgroup>
<fscgroup id="reszone">
<!-- the following fsc element is the FSC that hosts the volumes,
the default connection now uses 2-way SSL -->
<fsc id="FSC_fscreszone_infodba"
address="https://fscreszone.yourcompany.com:4545"
options="needclientauth">
<volume id="139747566d871c1b2023"
root="/mnt/disk1/tcapps/tceng2005sr1mp5/TC_VOL/volume1"/>
<transientvolume id="ce8399515feada2dee4c3e79b955d8ba"
root="/tmp/transientVolume_tceng2005sr1mp5_infodba"/>
</fsc>
</fscgroup>
</fmsenterprise>
</fmsworld>
Definition
FSC
connection
clientmap
FSC_fscmidzone_infodba
Specifies the FMS configuration master.
o
$FSC_HOME/fmsmaster_FSC_fscmidzone_infodba.xml
Master FMS configuration file.
A-12
$FSC_HOME/FSC_fscmidzone_infodba.xml
PLM00015 J
FSC configuration file that specifies the fscid and master/slave state.
o
$FSC_HOME/fsc.FSC_fscmidzone_infodba.properties
Additional properties for this FSC used to configure the keystore.
$FSC_HOME/keystore.FSC_fscmidzone_infodba.jks
The keystore for this FSC.
FSC_fscreszone_infodba
Specifies the FMS configuration slave.
o
$FSC_HOME/fmsmaster_FSC_fscreszone_infodba.xml
Local copy of the master FMS configuration file.
$FSC_HOME/FSC_fscreszone_infodba.xml
FSC configuration file that specifies the fscid and master/slave state.
$FSC_HOME/fsc.FSC_fscreszone_infodba.properties
Additional properties for this FSC used to configure the keystore.
$FSC_HOME/keystore.FSC_fscreszone_infodba.jks
The keystore for this FSC.
$FSC_HOME/fsc.FSC_fscmidzone_infodba.properties
Property file used to configure the keystore.
# fsc.FSC_fscmidzone_infodba.properties
com.teamcenter.fms.servercache.keystore.file=${FMS_HOME}/keystore.FSC_fscmidzone_infodba.jks
com.teamcenter.fms.servercache.keystore.password=keystore.FSC_fscmidzone_infodba.password
com.teamcenter.fms.servercache.keystore.ssl.certificate.password=keystore.FSC_fscmidzone_infodba.password
# these are not needed for 1-way SSL
javax.net.ssl.keyStore=${FMS_HOME}/keystore.FSC_fscmidzone_infodba.jks
javax.net.ssl.keyStorePassword=keystore.FSC_fscmidzone_infodba.password
javax.net.ssl.trustStore=${FMS_HOME}/keystore.FSC_fscmidzone_infodba.jks
javax.net.ssl.trustStorePassword=keystore.FSC_fscmidzone_infodba.password
$FSC_HOME/keystore.FSC_fscmidzone_infodba
The keystore for this FSC. The keystore just contain the private key and
certificate for the local machine and it must also contain the trusted (CA)
certificate for any clients you want to accept.
Note
PLM00015 J
You can optionally import individual certificates for each client rather
than importing the signer certificate.
A-13
Appendix A
$FSC_HOME/fsc.FSC_fscreszone_infodba.properties
The property file used to configure the keystore.
# fsc.FSC_fscreszone_infodba.properties
com.teamcenter.fms.servercache.keystore.file=${FMS_HOME}/keystore.FSC_fscreszone_infodba.jks
com.teamcenter.fms.servercache.keystore.password=keystore.FSC_fscreszone_infodba.password
com.teamcenter.fms.servercache.keystore.ssl.certificate.password=keystore.FSC_fscreszone_infodba.password
# these are not needed for 1-way SSL
javax.net.ssl.keyStore=${FMS_HOME}/keystore.FSC_fscreszone_infodba.jks
javax.net.ssl.keyStorePassword=keystore.FSC_fscreszone_infodba.password
javax.net.ssl.trustStore=${FMS_HOME}/keystore.FSC_fscreszone_infodba.jks
javax.net.ssl.trustStorePassword=keystore.FSC_fscreszone_infodba.password
$FSC_HOME/keystore.FSC_fscreszone_infodba
The keystore for this FSC. The keystore must contain the private key and
certificate for the local machine, and it must also contain the trusted (CA)
certificate for any clients you want to accept.
Note
A-14
You can optionally import individual certificates for each client rather
than importing the signer certificate.
PLM00015 J
Ensure that you copy the DLL file from the 32 directory for 32-bit
operating systems or the x64 directory for 64-bit operating systems.
These are not interchangeable and cause errors if you copy the wrong
DLL file.
PLM00015 J
A-15
Appendix A
3. In the navigation tree, expand your host name entry until you see Sites.
4. Create a new Web site with the home folder set to the directory that contains
the DLLs you copied in step 1:
a. Right-click Sites and choose Add a Web Site.
b.
In the Add Web Site dialog box, type a name for your new Web site in the
Site Name box, for example IIS7_WebLogic103, and click the browse button
(
c.
In the Browse for Folder dialog box, browse to the directory that contains
the iisproxy.dll and iisforward.dll files and click OK.
d. In the Port box, type a unique port number (for example, 8088) and click OK.
5. Configure the Web site application pool:
a. In the navigation tree, click Application Pools.
b.
Under Application Pools, right-click your Web site name and choose
Advanced Settings.
c.
In the Advanced Settings dialog box, select True for Enable 32-Bit
Applications.
c.
d. Under Actions in the right pane, click Providers and ensure Negotiate and
NTLM are in the Enabled Providers box. If they are not, select them from
the Available Providers list and click Add.
Note
e.
Under Actions in the right pane, click Advanced Settings and ensure
Enable Kernel-mode authentication is selected.
A-16
PLM00015 J
c.
In the Add ISAPI Filter dialog box, type IISForward in the Filter name box,
browse to the iisforward.dll file in the Executable box, and click OK.
c.
In the Add a Script Map dialog box, type *.wlforward in the Request path
box, browse to the iisproxy.dll file in the Executable box type IISProxy in
the Name box, and click OK.
9. Create an iisproxy.ini file in the directory that contains the DLLs. This file
must contain the following information.
WebLogicHost=<dns-name-or-ip-address>
WebLogicPort=<listening-port-for-WLS>
WlForwardPath=/examplesWebApp
Debug=ALL
DebugConfigInfo=ON
The WebLogicHost value is the host for the Security Services Login Service
application. The WebLogicPort value is the port for the Security Services
Login Service application. The WlForwardPath value is the name of the
Security Services Login Service Web application. The debug values are optional
and are set for debugging purposes. The default log file for debug messages
is C:\TEMP\wlproxy.log.
For more information about the contents of the iisproxy.ini file, see the
WebLogic documentation:
http://docs.oracle.com/cd/E14571_01/web.1111/e14395/isapi.htm
10. In the right pane, click Restart under Manage Web Site.
Configure JBoss 5.10 ISAPI with IIS 7 for Security Services login
service
You must install the Tomcat ISAPI Redirector version 1.2.31 or later and
configure the Windows registry for the redirector. You must also create the
workers.properties and uriworkermap.properties files for the redirector.
For additional information about the settings in these files, see the Tomcat
documentation.
1. Create a directory where you want to install the Tomcat ISAPI Redirector on the
Windows Server 2008, for example:
D:\jboss_iis
2. Create the a directory structure on the Windows Server 2008 host for the new
Web site:
jboss_iis
This is the top level Web site directory. Its name can be anything but it is
recommended that you use an easily identified name such as jboss_iis.
PLM00015 J
A-17
Appendix A
\bin
This is the ISAPI redirector install directory. It contains the redirector
dll file and its registry file.
\conf
Contains the ISAPI redirector configuration files.
\log
Contains the ISAPI redirector log files.
\wwwroot
This is the physical location of the Web site.
3. Download the ISAPI Redirector from the Apache Tomcat Web site and save it in
the ISAPI redirector install (bin) directory.
Note
It is recommended that you use debug for the log_level entry when you
initially configure the redirector to get all messages. You can change this
after you have tested your installation and determined that it is working
properly. The following table provides a brief description of these entries:
A-18
Name
Description
extension_uri
log_file
log_level
PLM00015 J
c.
Name
Description
worker_file
worker_mount_file
uri_select
The default port is 8009. If you could not use the default value and you changed
the AJP port number in JBoss configuration when you configured the Tomcat
ISAPI Redirector, use that value. The port is set (and can be modified) in the
JBoss_home\server\default\deply\jbossweb.sar\server.xml file.
The host-name value is the host where you run JBoss.
6. Add or modify the following Connector element
attributes to the AJP 1.3 connector configuration
(JBoss_home\server\default\deply\jbossweb.sar\server.xml) file:
<!-- A AJP 1.3 Connector on port 8009 -->
<Connector protocol="AJP/1.3" port="8009" address="${jboss.bind.address}"
tomcatAuthentication="false" emptySessionPath="true"
enableLookups="false" redirectPort="8443" />
IIS forwards requests to JBoss using the AJP 1.3 protocol on this port, this must
be set to allow access to the remote user name (getRemoteUser method).
7. Save the file as workers.properties in the conf directory. This must match the
path you defined for it in the registry file.
8. Create a text file with contents similar to the following:
# Send all /tc requests to node1
/tc/*=node1
PLM00015 J
A-19
Appendix A
Replace tc with the name of your Teamcenter Security Services Login Service
Web application. This configures the redirector to forward all requests with
the /tc/* signature to node1.
9. Save the file as uriworkermap.properties. Save this file in the conf directory.
10. To open the IIS Manager, choose StartAdministrative ToolsInternet
Information Services (IIS) Manager.
11. In the navigation tree, expand your host name entry until you see Sites.
12. Create a new Web site with the home folder set to the directory you created
in step 1:
a. Right-click Sites and choose Add a Web Site.
b.
In the Add Web Site dialog box, type a name for you new Web site in the
Site Name box, for example jboss-iis.
c.
d. In the Browse for Folder dialog box, browse to the wwwroot directory you
created in step 1 and click OK.
e.
In the Port box, type a unique port number (for example, 8128) and click OK.
c.
d. Under Actions in the right pane, click Providers and ensure Negotiate and
NTLM are in the Enabled Providers box. If they are not, select them from
the Available Providers list and click Add.
Note
e.
Under Actions in the right pane, click Advanced Settings and ensure
Enable Kernel-mode authentication is selected.
A-20
b.
c.
In the Add ISAPI Filter dialog box, type jkfilter in the Filter name box, browse
to the isapi_redirect.dll file in the Executable box, and click OK.
PLM00015 J
In the Add Virtual Directory dialog box, type jakarta in the Alias box.
Note
c.
The alias value can be anything but it must match the first value in
the extension_uri entry in the isapi_redirect_reg file.
Browse to the d:\jboss_iis\bin directory in the Physical path box and click
OK.
c.
In the Edit Module Mapping dialog box, type * in the Request path box
(remove any existing entry) and browse to the isapi_redirector.dll file in
the Executable box.
d. Click Request Restrictions and click the Verbs tab in the Request
Restriction dialog box and ensure the All verbs option is selected.
e.
Click the Access tab, ensure the Execute option is selected, and click OK.
Select your Web site name and click Advanced Settings under Edit
Application Pool in the right pane.
c.
In the Advanced Settings dialog box, select True for Enable 32-Bit
Applications.
18. In the right pane, click Restart under Manage Web Site.
PLM00015 J
A-21
Appendix
PLM00015 J
Troubleshooting four-tier
architecture deployment
Appendix
Troubleshooting four-tier
architecture deployment
Identify the problem you encountered in your four-tier rich client architecture and
perform the solution described.
Problem
Solution
PLM00015 J
B-1
Appendix B
Problem
Solution
Inspect the Web tier log file for status messages reported
during server manager startup. If the server manager log
contains a message similar to this, set the SERVER_HOST
parameter in the serverPool.properties file to the correct
IP address for the host.
Warnings of discarded messages
B-2
PLM00015 J
Problem
Solution
2. Edit log4j.xml so that more information is logged at run
time. For example, to increase the log4j output for the
JBossCache and jgroup classes to the INFO level, edit
the file:
<logger name="org.jboss.cache" additivity="false">
<level value="INFO"/>
<appender-ref ref="WebTierAppender"/>
<appender-ref ref="ProcessConsoleAppender"/>
</logger>
<logger name="org.jgroups" additivity="false">
<level value="INFO"/>
<appender-ref ref="WebTierAppender"/>
<appender-ref ref="ProcessConsoleAppender"/>
</logger>
The JMX HTTP adaptor allows you to view the status of the
server pool and dynamically change the pool configuration
values (the values are not persistent). Access this functionality
from the following URL:
http://host-name:jmx-port
Replace host-name with the name of the host running the
server manager. Replace jmx-port with the number of the
port running the JMX HTTP adaptor. This port number is
defined on the JMX HTTP Adaptor Port parameter when
you install the server manager.
Configuration is correct, but
run-time errors occur
PLM00015 J
B-3
Appendix B
Problem
Solution
If this is the case, either complete the IPv6 upgrade
configuration as documented in the IBM System Management
Guide or uncomment the following line in the mgrstart script:
#JVM_ARGS="${JVM_ARGS} -Djava.net.preferIPv4Stack=true"
B-4
PLM00015 J
Problem
Solution
A similar problem can occur after the Teamcenter Web tier
application is redeployed on the application server without
stopping and restarting the application server. In this case, an
extra TreeCache instance from the earlier deployment might
still be running in the application server and this can interfere
with proper functioning of the TreeCache. This can usually be
resolved by stopping and restarting the application server.
Due to a Java run-time issue on Linux, these problems are
more likely if the four-tier component is run with the nohup
command on Linux and the process is terminated by sending
it a signal.
The following error messages in the log files indicate that the
TreeCache port is already in use:
FATAL - None - 2007/07/27-16:11:13,244 UTC - host- TreeCache
initialization failed:
com.teamcenter.jeti.serverassigner.ServerAssigner
org.jgroups.ChannelException: failed to start protocol stack
Caused by: java.lang.Exception: exception caused by TCP.start():
java.net.BindException: No available port to bind to
This error indicates that the TreeCache local service port you
have configured is already in use either by another TreeCache
instance or by some other process. To resolve this problem,
choose a different port and restart/redeploy the reconfigured
server manager or Web tier application.
CFI_error displays when running When you run AIE Export in batch mode, Teamcenter displays
AIE export in batch mode
a CFI error. This error occurs because jt.exe (Microsoft Task
Scheduler) file is missing from the %WINDOWS% directory.
To resolve this problem, perform the following steps:
1. Download the jt.zip utility from the following Web site:
ftp://ftp.microsoft.com/reskit/win2000
2. Expand the jt.exe file from the jt.zip file and copy it to
your TC_ROOT\bin directory.
Server manager is not
used/recognized by the Web
tier application when the
manager is restarted without
restarting the Web tier
PLM00015 J
B-5
Appendix B
Problem
Solution
starting and managing the server manager, see the System
Administration Guide.
For information about Web application context parameters,
see the Installation on Windows Servers Guide.
B-6
PLM00015 J
Problem
Solution
PLM00015 J
B-7
Appendix B
Problem
Solution
You publish and item to the default ODS site that is also
the site publishing the item.
To correct this problem, ensure that you have set the Thread
Count and Initial Thread Count to at least the minimum
values required (25 and 15 respectively) and restart the
application server.
Note
B-8
PLM00015 J
Problem
Solution
5. In the Modify Web Application dialog box, click Generate
Deployable File.
6. In the Generate Deployable File dialog box, click OK.
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 OK to close the Modify Web Application dialog box.
PLM00015 J
B-9
Appendix B
Problem
Solution
B-10
PLM00015 J
Problem
Solution
PLM00015 J
B-11
Appendix
PLM00015 J
Glossary
Appendix
Glossary
B
basic deployment (HSE)
Basic deployment on an enterprise (J2EE) application server. The HTTP Web server
(H), servlet container (S), and Enterprise JavaBean (EJB) container (E) are all
provided on the same platform as part of the same process. The Teamcenter Web
tier application (EAR file bundling the WAR file) is deployed on a J2EE application
server that has a built-in HTTP listener, such as JBoss Application Server, Oracle
WebLogic Server, and IBM WebSphere Application Server.
Deploying a separate HTTP Web server to listen to the incoming request is not
required.
basic deployment with front-end HTTP Web server (H-SE)
Stand-alone HTTP Web server is configured as the front-end to a J2EE application
server.
BLOB
Binary large object; attribute type of undefined structure. BLOBs are stored as
binary images within an object.
business object
Logical grouping of data attributes and properties that are manipulated at the
enterprise level.
A Global Services business object allows users to query for and update information
in multiple data sources.
business object definition file
File that contains the XML-based definition of a Global Services business object.
C
clustered deployment (H*-SE)
Multiple HTTP servers configured in a cluster. All requests are sent to the cluster,
which routes the request to a J2EE application server that is available to process the
request. The Teamcenter Web tier application (EAR file bundling the WAR file) is
deployed in each application server instance in the cluster.
clustered deployment with front-end, load-balanced HTTP Web servers (H*-SE*)
Multiple HTTP Web server instances are configured with a load balancer and a
cluster of J2EE application server instances. A load balancer in front of the HTTP
Web servers balances the load for incoming requests and HTTP Web servers route
that request to the cluster of application servers.
PLM00015 J
C-1
Glossary
Appendix C
In this configuration, the Teamcenter Web tier application (EAR file bundling the
WAR file) is deployed in each application server instance in the cluster. Typically,
HTTP Web servers must be configured for this type of distributed environment.
clustered deployment with front-end HTTP Web server (H-SE*)
Stand-alone HTTP Web server is configured with a cluster of Web application server
instances. The HTTP Web server routes requests to a cluster of J2EE application
servers. The Teamcenter Web tier application (EAR file bundling the WAR file) is
deployed in each application server instance in the cluster.
D
data source
System that manages enterprise data and can be accessed by Teamcenter.
Examples are product knowledge management (PKM) systems, product lifecycle
management systems, relational databases, enterprise resource planning (ERP)
systems, component and supplier management (CSM) systems, mechanical design
automation (MDA) systems, purchasing systems, systems engineering GroupWare,
and maintenance, repair, and overhaul (MRO) systems.
datastore
Java Database Connectivity (JDBC) database instance used to store the Global
Services configuration and business object definition (BOD) information. The
majority of the objects in the datastore are stored as serialized objects for improved
performance. The configuration and BOD files are serialized during the process of
uploading them to the datastore. Global Services users with administrator privileges
can access the Configuration Object form in Global Services that allows them to add,
remove, and update objects in the datastore. See also business object definition file.
E
enterprise archive (EAR)
Enterprise application that requires a J2EE application server.
enterprise tier
Teamcenter architectural tier that comprises a configurable pool of Teamcenter
C++ server processes and a server manager. Larger sites can distribute the pool of
server processes across multiple hosts. Smaller sites can run the pool of servers on
the same host as the Web tier.
H
H*-SE
See clustered deployment (H*-SE).
H*-SE*
See clustered deployment with front-end, load-balanced HTTP Web servers (H*-SE*).
HSE
See basic deployment (HSE).
H-SE
See basic deployment with front-end HTTP Web server (H-SE).
C-2
PLM00015 J
Glossary
H-SE*
See clustered deployment with front-end HTTP Web server (H-SE*).
J
JDBC connector
Enterprise JavaBean that connects Global Services to data sources using the Java
Database Connectivity (JDBC) API.
The JDBC connector is provided as part of Global Services.
N
network load balancer (NLB)
HTTP Web servers are configured to allow each HTTP Web server in the load
balanced cluster to respond to a virtual IP address. Requests to this virtual IP are
intercepted and routed to a machine running one of the Web servers in the cluster.
O
Oracle home
Directory in which Oracle software is installed on the Oracle server node.
Oracle system identifier (SID)
Alphanumeric word used to identify a collection of processes and associated memory
structures as belonging to a particular Oracle database instance. The ORACLE_SID
environment variable defines the Teamcenter-Oracle system identifier.
P
preference
Configuration variable stored in a Teamcenter database and read when a Teamcenter
session is initiated. Preferences allow administrators and users to configure many
aspects of a session, such as user logon names and the columns displayed by default
in a properties table.
S
site preference
Teamcenter preference that applies to the entire site.
SQL
See Structured Query Language.
Structured Query Language
ANSI standard command and embedded language for manipulating data in a
relational database.
W
Web Application Manager
Graphical installation utility that generates supporting Web files (WAR and EAR
format) for a named Web application. Web Application Manager also installs the rich
client distribution server and creates distribution server instances.
PLM00015 J
C-3
Appendix C
Glossary
C-4
PLM00015 J
Index
A
Activity status table . . . . . . . . . . . . . . . 3-1
allowuntrustedcertificates property . . . A-4
Apache HTTP server . . . . . . . . . . . . . . 2-20
Apache Web server . . . . . . . . . . . 2-29, 2-31
Application server administration . . . . . 1-2
Application server hangs after publishing an
item . . . . . . . . . . . . . . . . . . . . . . . . . B-8
Application server stops responding . . . B-8
ApplicationInstance context
parameter . . . . . . . . . . . . . . . . . . . 3-4, 3-7
autoReconnect connection pool
property . . . . . . . . . . . . . . . . . . . . . . . 3-8
axis2.max.connections property . . . . . . . 3-6
B
Basic deployment . . . . . . . . . . .
WebSphere Application Server
BEA-000402 error . . . . . . . . . . .
2-212-23, 2-27, 2-30
JBoss . . . . . . . . . . . . . . . . . . . .
. . . . . . 1-3
. . . . . . 2-4
. . . . . 2-7,
. . . . . 3-12
C
Cannot assign requested address . . . . . B-7
Chinese characters in Windows . . . . . . B-10
clientmap element . . . . . . . . . . . . A-7, A-12
Cluster host:port . . . . . . . . . . . . . . . . . 2-29
Clustered with front-end HTTP . . . . . . . 1-3
Clustered with front-end load balanced . . 1-3
COMM_FAILURE error . . . . . . . . . . . . B-7
Commit . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Configuration data . . . . . . . . . . . . . . . . 3-1
Configure a handler mapping . . . . . . . . 2-16
Configuring a JNDI data store
connection . . . . . . . . . . . . . . . . . . . . . 3-4
Configuring FMS . . . . . . . . . . . . . . . . A-5
Configuring Web application . . . . . . . . . 1-2
connection element . . . . . . . . . . . . . . . A-12
Connection factory, JETIAdapter . . 2-5, 2-18
Connection pool database name . . . . . . . 3-7
Connection pool driver . . . . . . . . . . . . . . 3-4
Connection pool properties . . . . . . . 2-5, 2-18
Context parameter
PLM00015 J
ApplicationInstance . . . . . . . .
Context root . . . . . . . . . . . . . . .
CookiePath parameter . . . . . . . .
Cookies overwritten . . . . . . . . .
CORBA error in Web tier . . . . . .
Create a handler mapping . . . . .
Create a new IIS Web site . . . . .
A-16, A-20
Create an IIS handler script map
Create proxy initialization file . .
.
.
.
.
.
. . 3-4, 3-7
. 2-4, 2-18
. . . . B-9
. 2-6, 2-19
. . . . B-7
A-17, A-21
. . . . 2-24,
. . . . . 2-24
. . . . . 2-25
D
Data availability . . . . . . . . . . . . . . . . . . 1-2
Data source . . . . . . . . . . . . . . . . . . 3-4, 3-7
data store
Creating . . . . . . . . . . . . . . . . . . . . . . 3-1
Table . . . . . . . . . . . . . . . . . . . . . . . . 3-1
data store table . . . . . . . . . . . . . . . . . . . 3-1
Database tables
Activity status . . . . . . . . . . . . . . . . . . 3-1
data store . . . . . . . . . . . . . . . . . . . . . 3-1
Message log . . . . . . . . . . . . . . . . . . . . 3-1
Reactor result . . . . . . . . . . . . . . . . . . 3-1
Default Web site . . . . . . . . 2-24, A-16, A-20
Deployment status . . . . . . . . . . . . . . . . 3-7
Deployment with front-end HTTP server
WebSphere Application Server . . . . . 2-16
Deployment, basic . . . . . . . . . . . . . . . . 2-6,
2-202-21, 2-23, 2-26, 2-30
Front-end HTTP Web server
WebSphere application server/IBM
HTTP server . . . . . . . . . . . . . 2-16
Deployment, clustered
Front-end HTTP Web server
WebLogic server/Apache Web
server . . . . . . . . . . . . . . . . . 2-29
WebLogic server/WebLogic
Express . . . . . . . . . . . . . . . . 2-26
Load-balanced HTTP Web server
WebSphere application server/IBM
HTTP (Web) server . . . . . . . . 2-31
WebSphere application server/Sun Web
server . . . . . . . . . . . . . . . . . 2-31
Deployment, distributed . . . . . . . 2-202-21
Index-1
Index
Deployment, H-SE
Front-end HTTP Web server
JBoss application server/Microsoft
IIS . . . . . . . . . . . . . . . . . . . . . 2-7
Distributed deployment
Apache HTTP/WebLogic . . . . . . . . . . 2-20
WebLogic Express/WebLogic . . . . . . . 2-21
Dynamic content . . . . . . . . . . . . . . . . . . 1-2
E
Elements
clientmap . . . . . . . . . . . . . . . . A-7, A-12
connection . . . . . . . . . . . . . . . . . . . . A-12
FSC . . . . . . . . . . . . . . . . . A-7, A-9, A-12
fscgroup . . . . . . . . . . . . . . . . . . . . . A-6
Enable port rollover . . . . . . . . . . . . . . 2-25
Enabling a deployed Web application . . . 1-2
Enabling two-way SSL . . . . . . . . . . . . A-4
Error during JBoss startup . . . . . . . . . B-10
Errors
COMM_FAILURE . . . . . . . . . . . . . . B-7
IPv6 . . . . . . . . . . . . . . . . . . . . . . . . B-7
Java . . . . . . . . . . . . . . . . . . . . . 2-1, B-6
java.net.BindException . . . . . . . . . . . B-7
mcast . . . . . . . . . . . . . . . . . . . . . . . B-7
Pool ID not available . . . . . . . . . . . . B-2
Restarting server manager . . . . . . . . B-6
Server manager . . . . . . . . . . . . . . . . B-6
SERVER_HOST parameter . . . . . . . B-2
TreeCache . . . . . . . . . . . . . . . . . . . . B-5
extension_uri registry entry . . . . . . . . 2-10,
2-13, A-18
F
Fail over . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Failed to start new thread error . . . . . . B-11
Files
Global Services properties . . . . . . . . . 3-6
globalservices.properties . . . . . . . . . . . 3-6
hs_err_* . . . . . . . . . . . . . . . . . . 2-1, B-6
isapi_redirector.reg . . . . . 2-10, 2-12, A-18
JETIServerAccessor.jar . . . . . . . . . . 2-25
Proxy WAR . . . . . . . . . . . . . . . 2-22, 2-27
TreeCacheTCP.xml . . . . . . . . . . . . . . 2-25
uiworkermap.properties . . 2-9, 2-12, A-17
web.xml . . . . . . . . . . . . . . . . . . . . . 2-28
Windows registry . . . . . . . 2-10, 2-12, A-18
workers.properties . . . . . . 2-9, 2-12, A-17
FMS SSL configuration . . . . . . . . . . . . A-4
FMS URL path extensions . . . . . . . . . . A-4
Four-tier architecture
Troubleshooting deployment . . . . . . . B-1
Front-end HTTP . . . . . . . . . . . . . . . . . . 1-3
Index-2
. . . 3-4
. . B-11
. . . 3-6
. . . 3-4
. . . 3-6
3-4, 3-7
H
H*-SE* . . . . . . . . . . . . .
H-SE . . . . . . . . . . . . . . .
H-SE* . . . . . . . . . . . . . .
HP-UX, kernel parameters
hs_err_* . . . . . . . . . . . . .
HSE . . . . . . . . . . . . . . . .
HTTP Web servers . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . . 1-3
. . . 1-3
. . . 1-3
. . B-4
2-1, B-6
. . . . 1-3
. . . . 2-2
I
IBM HTTP server . . . . . .
IBM HTTP server plug-in
IIS
ISAPI filter . . . . . . . . .
Web service extension . .
IIS default Web site . . . . .
IIS virtual directory . . . .
IIS Web site . . . . . . . . . .
Installations
JBoss server . . . . . . . .
WebLogic server . . . . . .
IPv6 mcast mode . . . . . . .
ISAPI filter . . . . . . . . . . .
ISAPI Redirector . . . . . . .
isapi_redirector.reg file . .
. . . . . . 2-16, 2-31
. . . . . . . . . . 2-19
.
.
.
.
.
. . . . . . . . . 2-15
. . . . . . . . . 2-15
2-24, A-16, A-20
. . . . . 2-142-15
. . . . . 2-142-15
.
.
.
.
.
.
.
.
.
.
.
.
. . . . . . . . . 3-9
. . . . . . . . . 3-6
. . . . . . . . B-7
. . . . . . . . 2-15
. . . . . . . . . 2-7
2-10, 2-12, A-18
J
Java error . . . . . . . . . . . . .
Java out of memory error . . .
java.lang.OutOfMemoryError
java.net.BindException . . . .
JBoss
Security . . . . . . . . . . . . .
JBoss 5.1.0 GA . . . . . . . . . .
JBoss application server . . .
JCA connection parameter . .
JETIServerAccessor.jar file .
JNDI data store . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-1, B-6
. . . B-11
. . . B-11
. . . B-7
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-12
B-10
. 2-7
B-9
2-25
. 3-4
PLM00015 J
Index
K
Kernel parameters . . . . . . . . . . . . . . . B-4
L
log_file registry entry . . . . . 2-10, 2-13, A-18
log_level registry entry . . . . 2-10, 2-13, A-18
M
Manager, NLB . . . . . . . .
Max_Pool_Size parameter
Maximum connections . . .
mcast error . . . . . . . . . . .
Message log table . . . . . .
Microsoft IIS . . . . . . . . .
Microsoft IIS 7 . . . . . . . .
Minimum connections . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . . . . . . 2-32
. . . . . . . B-9
. . . . 2-5, 2-18
. . . . . . . B-7
. . . . . . . . 3-1
2-7, 2-142-15
. . . 2-23, A-15
. . . . 2-5, 2-18
N
Network load balancing, see NLB
New IIS Web site . . . . . . . . . . . . 2-142-15
NLB . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Cluster parameters . . . . . . . . . . . . . 2-32
Master host node . . . . . . . . . . . . . . . 2-33
Network load balancing manager . . . 2-32
NLBmgr command . . . . . . . . . . . . . . 2-32
Requirements . . . . . . . . . . . . . . . . . 2-32
Secure port rules . . . . . . . . . . . . . . . 2-33
Standard port rules . . . . . . . . . . . . . 2-33
WebSphere application server/IBM HTTP
(Web) server . . . . . . . . . . . . . . . . 2-31
Not enough storage is available to process this
command error . . . . . . . . . . . . . . . . . B-11
O
One-phase commit . . . . . . . . . .
One-way SSL configuration . . . .
Oracle Manufacturing integration
Override end_port value . . . . . .
...
...
..
...
.
.
.
.
.
.
.
.
. 3-7
A-8
. 3-4
2-25
P
Parameters
ApplicationInstance . . . . . . . . .
CookiePath . . . . . . . . . . . . . . .
Kernel . . . . . . . . . . . . . . . . . .
Max_Pool_Size . . . . . . . . . . . . .
Prerequisites for Web application
deployment . . . . . . . . . . . . . . . .
Preventing cookies from being
overwritten . . . . . . . . . . . . . . . .
Property
PLM00015 J
.
.
.
.
.
.
.
.
3-4, 3-7
. . B-9
. . B-4
. . B-9
. . . . . 1-2
. 2-6, 2-19
axis2.max.connections . . . . . . . . . . . . 3-6
Proxy WAR file . . . . . . . . . . . . . . . . . . 2-22
Publishing to default ODS hangs application
server . . . . . . . . . . . . . . . . . . . . . . . . B-8
R
Reactor result table . . . . . . . . . . . . . . . . 3-1
Redirector directory . . . . . . . 2-10, 2-12, A-17
Redirector logs . . . . . . . . . . . . . . . . . . A-17
S
SAP (T4S) integration . . . . . . . . . . . . . . 3-4
SAP integration . . . . . . . . . . . . . . . . . . 3-4
Security in JBoss . . . . . . . . . . . . . . . . 3-12
Server manager
J2EE based, troubleshooting . . . . . . . B-2
Server manager error . . . . . . . . . . . . . B-6
Server manager restart error . . . . . . . . B-6
SERVER_HOST parameter . . . . . . . . . B-2
serverPool.properties file . . . . . . . . . . . B-2
Session cookies . . . . . . . . . . . . . . . . . . B-9
Session cookies overwritten on the
client . . . . . . . . . . . . . . . . . . . . . . . . B-9
Specifying a specific bind address when a host
has multiple IP addresses . . . . . . . . . B-1
SSL
Application server . . . . . . . . . . . . . . 3-16
SSL configuration
One-way . . . . . . . . . . . . . . . . . . . . . A-8
Two-way . . . . . . . . . . . . . . . . . . . . . A-4
Starting ****OBSOLETE**** . . . . . . . 2-22
Starting a Teamcenter Web
application . . . . . . . . . . . . . . . . . . . . . 1-2
Starting JBoss . . . . . . . . . . . . . . . . . . 3-12
Startup error with JBoss installed on
Solaris . . . . . . . . . . . . . . . . . . . . . . . B-10
Static content . . . . . . . . . . . . . . . . . . . . 1-2
Sun Java System Application Server
hangs . . . . . . . . . . . . . . . . . . . . . . . . B-8
Sun Java System Application Server is
unresponsive . . . . . . . . . . . . . . . . . . . B-8
Supported application servers . . . . . . . . 2-2
Supports global transactions . . . . . . . . . 3-7
T
TCP element . . . . . . . . . . . . . .
TESIS integrations . . . . . . . . .
Tomcat Redirector directory . . .
2-12, A-17
TreeCache initialization fails . .
TreeCache initialization failure
TreeCache local service port . . .
. . . . . . 2-25
. . . . . . . 3-4
. . . . . 2-10,
. . . . . . B-5
. . . . . . B-1
. . . . . . B-5
Index-3
Index
TreeCache peers . . . . . . . .
TreeCacheTCP.xml file . . .
Troubleshooting
Four-tier deployment . . .
Server manager . . . . . . .
Two-way SSL configuration
. . . . . . . . . B-6
. . . . . . . . . 2-25
. . . . . . . . . B-1
. . . . . . . . . B-2
. . . . . . . . . A-4
U
uiworkermap.properties file . . . . . . . . . 2-9,
2-12, A-17
Unexpected error detected by HotSpot . . B-6
uri_select registry entry . . . . . . . . 2-13, A-19
V
Virtual directory . . . . . . . . . . . . . 2-142-15
W
Web server farm . . . . . . . . . . . . . . . . . . 1-4
Web service extension . . . . . . . . . . . . . 2-15
Web tier
Apache HTTP
WebLogic Server . . . . . . . . . . . . 2-20
connection problems . . . . . . . . . . . . . B-2
Deployment, basic
JBoss application server/Microsoft
IIS . . . . . . . . . . . . . . . . . . . . . 2-7
WebLogic Server . . . . . . . . . . . . 2-6,
2-202-21, 2-23, 2-26, 2-30
WebSphere Application Server . . . 2-4
WebSphere application server/IBM
HTTP server . . . . . . . . . . . . . 2-16
Deployment, clustered
WebLogic server/Apache Web
server . . . . . . . . . . . . . . . . . 2-29
WebLogic server/WebLogic
Express . . . . . . . . . . . . . . . . 2-26
WebSphere application server/IBM
HTTP (Web) server . . . . . . . . 2-31
Index-4
PLM00015 J