Teamcenter 10.1
Web Application Deployment Guide
Publication Number PLM00015 J Proprietary and restricted rights notice
This software and related documentation are proprietary to Siemens Product Lifecycle Management Software Inc. © 2013 Siemens Product Lifecycle Management Software Inc. All Rights Reserved. Siemens and the Siemens logo are registered trademarks of Siemens AG. Teamcenter is a trademark or registered trademark of Siemens Product Lifecycle Management Software Inc. or its subsidiaries in the United States and in other countries. All other trademarks, registered trademarks, or service marks belong to their respective holders.
2 Web Application Deployment Guide PLM00015 J Contents
Proprietary and restricted rights notice ...... 2
Getting started deploying Web applications ...... 1-1 Deployment considerations ...... 1-1 Before you begin ...... 1-2 Teamcenter Web application deployment interface ...... 1-2 Determining your requirements ...... 1-2 Basic concepts of Teamcenter Web application deployment ...... 1-3
Teamcenter Web application deployment ...... 2-1 Teamcenter Web application deployment ...... 2-1 Basic deployment ...... 2-1 Basic deployment with front-end HTTP (Web) server ...... 2-7 Clustered deployment with front-end HTTP server ...... 2-25 Deploying clustered with front-end load-balanced HTTP servers ...... 2-31
Global Services Web application deployment ...... 3-1 Global Services Web application deployment ...... 3-1
Teamcenter client communication system and proxy server configuration ...... A-1 Teamcenter client communication system and proxy server configuration . . . . A-1 Reverse proxy servers ...... A-4 Enabling File Management System (FMS) URL path extensions ...... A-4 FMS server cache (FSC) SSL client credentials (two-way SSL) ...... A-4 File Management System (FMS), reverse proxy, and two-way SSL configuration details ...... A-5 Configuring Kerberos authentication on the Web tier ...... A-15
Troubleshooting four-tier architecture deployment ...... B-1
Glossary ...... C-1
Index ...... Index-1
Figures
HSE deployment configuration ...... 1-4 H-SE deployment configuration ...... 1-5 H-SE* deployment configuration ...... 1-6 H*-SE* deployment configuration ...... 1-7
PLM00015 J Web Application Deployment Guide 3 Contents
Teamcenter client communication system architecture ...... A-2
4 Web Application Deployment Guide PLM00015 J Chapter 1 Getting started deploying Web applications
Deployment considerations ...... 1-1
Before you begin ...... 1-2
Teamcenter Web application deployment interface ...... 1-2
Determining your requirements ...... 1-2
Basic concepts of Teamcenter Web application deployment ...... 1-3
PLM00015 J Web Application Deployment Guide
Chapter 1 Getting started deploying Web applications
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 application’s 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 Siemens PLM Software certifies third-party software applications with the latest patches available when the certification testing is performed. If you encounter problems deploying a Teamcenter Web application, ensure that you have installed the latest patches for your application server.
Teamcenter and Global Services Web applications support IPv6 for Web tier communications for the following application servers: • JBoss 7.1
• WebSphere 8.5
PLM00015 J Web Application Deployment Guide 1-1 Chapter 1 Getting started deploying Web applications
• 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.
Before you begin
Prerequisites You must have administrator privileges to use the application servers administration tools. You must have performed Web application installation as described in the appropriate Teamcenter server installation guides (for Windows or UNIX/Linux). Enable a Web The Web tier application is enabled by deploying it in the application application server and, depending on your configuration, its associated proxy component in the Web server. Configure a Web Teamcenter Web applications are configured during installation application and in the application server after deployment. Start a Once your Teamcenter Web Application is deployed, it is Teamcenter Web running. If you need to stop, start, or restart the application at application a later time, you must use the application server administration tools to perform these actions.
Teamcenter Web application deployment interface The application server administration tools provide the interface for deploying your Web application.
Determining your requirements How you configure your servers that run your Teamcenter Web tier application depends on your enterprise requirements for scalability (concurrent users and processes) and data availability (server fail over). An HTTP front-end cluster provides better performance for static Web content. Clustering application servers provides better performance for dynamic content and ensures availability because the Teamcenter application has multiple instances that allow a particular application server to fail without causing the Teamcenter data to be inaccessible. To determine the best configuration for your installation you must be familiar with the installation, use, and performance tuning of the servers you choose for deploying the Web tier application. For information about server performance, see the documentation provided with your server and the System Administration Guide. Does your environment require IPv6 support? This requirement determines the application servers that you can choose for your deployment.
1-2 Web Application Deployment Guide PLM00015 J Getting started deploying Web applications
Basic concepts of Teamcenter Web application deployment You should understand the following terms.
Term Definition Basic deployment Basic deployment on an enterprise (J2EE) application (HSE) server. The HTTP Web server (H), servlet container (S), and enterprise Java™ bean (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 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 A stand-alone HTTP Web server is configured with a cluster deployment with of Web application server instances. The HTTP Web server front-end HTTP Web routes requests to a cluster of J2EE application servers. The server (H-SE*) Teamcenter Web tier application (EAR file bundling the WAR file) is deployed in each application server instance in the cluster. Clustered Multiple HTTP Web server instances are configured with deployment a load balancer and a cluster of J2EE application server with front-end, instances. A load balancer in front of the HTTP Web servers load-balanced balances the load for incoming requests and HTTP Web HTTP Web servers servers route that request to the cluster of application (H*-SE*) servers. 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. Enterprise archive An enterprise application that requires a J2EE application (EAR) server. Network load HTTP Web servers are configured to allow each HTTP Web balancing (NLB) server in the load balanced cluster (see Web server farm) 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. Web archive (WAR) A Web application that requires an HTTP Web server and servlet engine.
PLM00015 J Web Application Deployment Guide 1-3 Chapter 1 Getting started deploying Web applications
Term Definition Web server farm Multiple HTTP Web servers are configured as self contained (redundant) servers in a cluster. The Web servers serve a single IP address that allows any of the servers that are available to handle a request the address. This provides improved performance and reliability.
The following figures show each of the deployment configurations for Teamcenter Web tier applications. r r r e e e t t t r r r r n n n l e e e e e e e o v v v v c c c r r r r o e e e e P m m m S S S S a a a
e e e
T T T
s s e c c A s s e c c A