installing and configuring siemens plm solutions...

Installing and configuring Siemens PLM Solutions Teamcenter

Unified 8.0.1 Server For PDM applications on AIX servers

.

Gary Hornyak Terry Wang

Sachin Bhandare

ISV Business Strategy and Enablement December 2009

© Copyright IBM Corporation, 2009. All Rights Reserved. All trademarks or registered trademarks mentioned herein are the property of their respective holders

Table of contents Abstract........................................................................................................................................1 Introduction .................................................................................................................................1 Resource planning......................................................................................................................1

Teamcenter two-tier architecture ........................................................................................................... 2 Teamcenter four-tier architecture........................................................................................................... 2 Client-server database environment ...................................................................................................... 3

Teamcenter 8.0.1 installation environment ..............................................................................4 Assumptions ...............................................................................................................................4 Creating Oracle Database for Teamcenter................................................................................4

Copying UGS templates......................................................................................................................... 4 Creating Teamcenter Oracle Database instance with DBCA ................................................................ 4

Creating DB2 Database for Teamcenter ...................................................................................7 Installing Teamcenter 8.0.1 ........................................................................................................8

Installation images.................................................................................................................................. 8 Preinstallation setup ...............................................................................................................................8 Starting Teamcenter Engineering Manager ........................................................................................... 8 Starting Teamcenter Environment Manager (phase one installation).................................................... 9 Starting Teamcenter Environment Manager – phase two installation ................................................. 19 Installation checkpoint .......................................................................................................................... 31

Generating the Web-tier application .......................................................................................31 Installing Web Application Manager..................................................................................................... 31 Before starting Web Application Manager............................................................................................ 32 Start Web Application Manager ........................................................................................................... 32

Deploying WebSphere Application Server .............................................................................38 Deploying Teamcenter Web applications using utility programs ......................................................... 38 Starting WebSphere Application Server and IBM HTTP Server processes ............................................. 39 Installing and configuring UNI801 EAR in WebSphere 6.1.................................................................. 39

Installing the new application .................................................................................................. 39 Manually configuring the JETI resource adapter..................................................................... 43

Accessing the thin client....................................................................................................................... 47 Installing and configuring the distribution server .................................................................47

Preparing to install the distribution server for the four-tier rich client................................................... 47 Creating the distribution server ............................................................................................................ 49 Creating the distribution-server instance.............................................................................................. 50

Creating more business-application servers .........................................................................55 Making new copies of the pool_manager directory................................................................. 55 Adding a system with name mewe as an additional application server .................................. 56

Summary....................................................................................................................................57 Appendix A: setvars.sh ............................................................................................................58 Appendix B: Resources............................................................................................................59 About the authors .....................................................................................................................60 Trademarks and special notices..............................................................................................61

Teamcenter Unified 8.0.1 Installation Guide for PDM Apllications


1

Abstract This paper provides detailed installation and configuration instructions for Teamcenter Unified Server for IBM Power Systems servers. Also included in this paper are explicit instructions on how to create Oracle and DB2 9.5 databases for Teamcenter 8.0.1 and the deployment of the Web application on IBM WebSphere Application Server, as well as creating the distribution server used to automate the installation of the rich client for a four-tier environment. This paper is intended as a mechanism to educate Advanced Technical Support (ATSS) and Field Technical Support Specialist (FTSS) personnel on the installation and configuration of Teamcenter 8.0.1 Server on IBM Power Systems servers, in support of sales engagements.

Introduction This paper supplements the Teamcenter 8.0.1 installation documentation, it does not replace it. The focus

here is on the installation and configuration of Teamcenter 8.0.1 on the IBM® AIX operating system.

Siemens Teamcenter 8.0.1 has increased the support for IBM Blue Stack. Together with IBM Blue Stack, Teamcenter provides a platform for product lifecycle management (PLM) integration and extensibility

throughout the broader enterprise. You can find more information about the customer benefits at www.plm.automation.siemens.com/en_us/products/teamcenter/teamcenter_ibm.shtml where you can find information about the added support for IBM DB2® and readiness for enterprise integration using the IBM

Product Development Integration Framework.

Resource planning Teamcenter 8.0.1 supports two types of clients (rich and thin client) and two architecture models (two-tier and four-tier). The basic architecture of Teamcenter Unified 8.0.1 is similar to Teamcenter Engineering 2007 and supports the same multitier deployment options.

The two types of clients are:

A thin, browser-based client. The thin client provides access to the most common features and functions needed by users who reference or consume Teamcenter information, and requires only

a commercial browser to be installed on the server. A rich, Java™-based client. The rich client provides access to all Teamcenter Engineering

features and functions, requiring a Java Runtime Environment (JRE) and a local (or mapped)

installation on the user’s desktop machine. The rich client can either be deployed in two- or four-tier architecture.

2

Teamcenter two-tier architecture

In the two-tier deployment, the Java based rich client, the enterprise-tier server, and the supporting software run on the users’ workstations. Database, volumes and other resource-tier components run on

separate systems.

Two-tier rich

client

Teamcenter server

implementation repository

Database

1

2

database server

Figure 1. Rich client two-tier architecture

Where:

Tier one is the Teamcenter two-tier rich client

Tier two is the database server (Oracle or DB2 on AIX, along with SQL server on the Microsoft® Windows® platform)

Teamcenter four-tier architecture

In the four-tier deployment, only the Java based rich client runs on the users’ workstations. The enterprise

tier, database, volumes and other resource-tier components can run on separate systems.


3

Third-party applications server (WebSphere) EAR file generated using Web Application Manager (insweb)

Deployed in third-party application server software Port number used by clients

Teamcenter serversand server manager installed using

Teamcenter Manager (tem.sh)

Resource tier

Teamcenter server nExe - tcserver

Teamcenter server n+1 Exe - tcserver

Teamcenter server n+1 Exe - tcserver

Server manager Exe – mgrstart Uses – tc_root tc_data

Database

4

Starts server processes for multiple users

FMS and volume server

Four-tier rich client Installed on client host over the Web

Thin client Installed as part of the Web tier

2

1

3

Rich client four-tier architecture

Where:

Tier 1 is the resource tier (database, file management system and volume servers). Tier 2 is the Teamcenter server tier. Tier 3 is the Java 2 Platform, Enterprise Edition (J2EE) Web applications server tier.

Tier 4 is the Teamcenter client tier.

Client-server database environment

If the Oracle database server is on a separate system than the Teamcenter server’s processes (configured with Oracle client) you are required to configure the Teamcenter server with Oracle netca to

create the configuration files necessary for remote-database access.

DB2 database-server communication requires that you configure the DB2 database server to support TCP/IP communication, because Teamcenter uses Java™ database communication (JDBC)

communication to talk to with the database server.


4

Teamcenter 8.0.1 installation environment Teamcenter 8.0.1 was successfully installed on the Power Systems server. A four-tier architecture was implemented using three logical partitions (LPARs) on various Power Systems servers.

IBM Power™ 520 server model 8203-E4A and IBM BladeCenter® JS22 blade servers running AIX 5.3 TL7 with SP1 and AIX 6.1 TL3

XL C/ C++ for AIX runtime (xlC.aix50.rte and xlC.aix60.rte) at 9.0.0.3 and 10.0.0.2

IBM Java5 SDK (32-bit Java, delivered with AIX media), service refresh SR8 or later is suggested Both Oracle 10.2.0.3 and DB2 9.5 databases along with WebSphere Application Server 6.1.0.25

WebSphere Application Server LPAR ran AIX 6.1

Teamcenter 8.0.1 Server manager (configured for multicast) Teamcenter 8.0.1 server LPAR ran AIX 5.3 TL7/SP1 FlexLM V10.8 license server – delivered with Teamcenter

Assumptions This paper assumes Oracle 10g Release3 (server and client code) or DB2 9.5 database software and WebSphere Application Server 6.1.0.13, are installed and configured. If not, refer to the following document: WebSphere Application Server V6..1.FP25 Install Guide for PDM Applications

(http://www.ibm.com/partnerworld/wps/servlet/ContentHandler/whitepaper/aix/websphere_v6r1/guide).

Creating Oracle Database for Teamcenter

If using Oracle with Teamcenter 8.0.1, create a database instance by using templates provided by Siemens PLM Solutions with Oracle DBCA. The templates populate the database with the required

Oracle user accounts and table spaces.

1. The templates create a single database user (infodba) per Oracle system identifier (SID). 2. After completing the Oracle DCBA steps, a TC801 database is created to use for the installation

of Teamcenter 8.0.1, which includes a user infodba with Oracle password of infodba.

Copying UGS templates

Copy the UGS-supplied Oracle 10g template files by using the following steps:

1. Access the Teamcenter CD-ROM or CD-ROM images.

2. Copy all files in the /dbscripts/oracle directory on the Teamcenter Engineering CD-ROM to the templates directory of the Oracle installation. For example: cp /cdrom/aix/tc/db_scripts/oracle/* to $ORACLE_HOME/assistants/dbca/templates

Creating Teamcenter Oracle Database instance with DBCA

To create the Teamcenter Oracle Database instance by using DBCA, follow these steps:

1. Start Oracle Database Configuration Assistant by issuing the #/home/oracle/ora10/bin/dbca

command.


5

2. Oracle Database Configuration Assistant shows the Welcome page (screen not shown here). Click Next.

3. On the Operations window, select Create a Database, then click Next (see Figure 2).

Figure 2. Create a database

4. On the Database Templates window (screen not shown here), select Teamcenter Oracle 10g, then click Next.

5. On the Database Identification window (see Figure 3), enter the Global Database Name (tc801),

then click Next.

Figure 3. Database Identification window


6

6. On the Management Options window (screen not shown here), click Next. 7. On the Database Credentials window (see Figure 4), select Use the Same Password for All

Accounts, type ibm123 as the password (and to confirm the password), then click Next.

Figure 4. Database Credentials window

8. On the Storage Options window (screen not shown here), click Next. 9. On the Database File Location window (screen not shown here), select Use Database File

Locations from Templates, click Next.

10. On the Recovery Configuration window (screen not shown here), accept the defaults and click Next. 11. On the Database Content window (screen not shown here), click Next. 12. On the Initialization Parameters window (see Figure 5), select Typical with a percentage of 40.

Then, click Next.

Figure 5. Initialization Parameters window


7

13. On the Database Storage window (screen not shown here), click Next. 14. On the Create Options window (screen not shown here), select Create Database and click Finish.

15. On the General Purpose window (screen not shown here), click Next. 16. On the Confirmation window (screen not shown here), review the information, then click OK.

(Note: Database creation starts and takes several minutes.)

17. On the Database Credentials window (screen not shown here), select Use the Same Password for All Account, then click Next.

18. On the Database Creation Complete window (screen not shown here), click Exit.

Creating DB2 Database for Teamcenter

If using DB2 9.5 with Teamcenter 8.0.1, (support for DB2 on the AIX operating system is new with the 8.0.1 release) create a database instance using scripts and templates provided by Siemens PLM Solutions. The templates populate the database with the required user accounts and table spaces. Under

tc/db_scripts/db2/9.5, a dbcrt.sh shell script will prompt for key information (such as the DB2 instance owner [db2adm9], the AIX user that performs the Teamcenter installation (infodba), and the location where the tablespaces are created [such as /home/TC801]).

Prior to running the dbcrt.sh script, ensure that the DB_PASSWORD environment variable is set correctly in the script. The following is an example of the questions and responses for the dbcrt.sh script:

Follow these instructions to create a DB2 Database

-n Enter the DB2 Admin user:

db2adm9

-n Enter OS User to be used for installation:

infodba

-n Enter the Path where you want to create the Database:

/home/TC801

-n Enter the DB2 Instance on Linux:

-n Enter the path for DB2 Bind:

/opt/IBM/db2/V9.5/bin/

Hint: The location specified for the DB2 Bind is the directory where the db2clipk.bnd file is located.

After running the dbcrt.sh, a database named tc is created.

Hint: Ensure that the db2set parameters described in the Teamcenter installation guide are set,

especially the DB2_SNAPSHOT_NOAUTH=on parameter — not having these db2set parameters set for the database instance causes problems during the installation of Teamcenter.


8

Installing Teamcenter 8.0.1 This section explains how to install Teamcenter 8.0.1.

Installation images

Before beginning the installation, mount the CD-ROMs or hard-disk devices on the network node that will

run Teamcenter Environment Manager. You can either locally mount or use the network file system (NFS) to remotely mount the CD-ROM or hard-disk devices.

In the following instructions, the entire contents of the Teamcenter Engineering CD-ROMs are copied to

the hard disk. The installation directories are then NFS-mounted from a remote NFS server. You must run Teamcenter Environment Manager on the local server node.

The installation image directory (/MNT/tcunified801) is then NFS-mounted from a remote NFS server.

Preinstallation setup

Before installing the code, do the following:

1. Create the user and group infodba and infodba. 2. Create /home/infodba (3 GB, owned by infodba).

3. Increase /tmp so that it has500 MB free. 4. In the graphical window running the installer: export the following:

LDR_CNTRL=NAMEDSHLIB=TCINST,doubletext32@MAXDATA=0x80000000@DSA

5. if using virtual network computing (VNC) to perform the installation, run ulimit –d unlimited, and then run ulimit –s 132768. If using AIX 6.1 to perform the installation, run ulimit –r unlimited in the aixterm before starting the tem.sh script as the infodba user.

Note: Appendix A has an example shell script (setvars.sh) that you can use to set the values

Starting Teamcenter Engineering Manager Before installing Teamcenter, you need to do the following steps:

1. As root, run: ifconfig lo0 inet6 ::1/0 delete. Running this AIX command deletes the ipv6 configuration for localhost, which causes

problems with the multicast pool manager. Run this command on the Teamcenter server system, as well as on the WebSphere Application server system.

2. Start the database and listener.

Use the procedures in the Oracle Installation Guide to start the UNI801 database and listener.

if using DB2, run db2start as the DB2 instance owner (db2adm9).

3. Verify that infodba is able to communicate with the database-server system If the Oracle database client has been installed on the server that you intend to install the

Teamcenter corporate server software, set the Oracle database environment variables, then

run tnsping UNI801 to verify that infodba is able to communicate with the Oracle database instance. Set the database environment variables as described in the Oracle Installation


9

document, then run tnsping UNI801 to verify that infodba is able to communicate with the Oracle database instance.

4. Start the WebSphere Application Server and IBM HTTP Server processes. Use the procedure in the WebSphere Installation Guide (refer the "Appendix B: Resources"

section which has the URL) to start these processes.

Starting Teamcenter Environment Manager (phase one installation)

Log in as user infodba for installing and maintaining the Teamcenter 8.0.1 installation. In phase one, the corporate server is installed, selecting the Teamcenter File Services and Teamcenter Foundation.

To start Teamcenter Environment Manager, complete the following steps:

1. Access the directory (/MNT/tcunified801) for the Teamcenter Engineering NFS-mounted file system.

2. Run the tem.sh script.

3. On the Choose Install Language screen (see Figure 6), select a language for the installation program and click OK. (Note: The language you select is used only for the installation program.)

Figure 6. Choose Install Language dialog window

4. On the Getting Started panel (see Figure 7), select Create a new installation of the product, then click Next.


10

Figure 7. Getting Started window

5. On the Copyright Notice panel (no image is shown here), click Next. 6. On the New Configuration panel (see Figure 8), enter a unique ID for the description and ID, then

click Next. (Note: Record the description and ID you enter for this configuration. When

uninstalling this configuration or performing other maintenance tasks, you must select this configuration from a list. In addition, installation log files use the ID you enter in their names.)


11

Figure 8. New configuration window

7. On the Solutions panel (see Figure 9), select Corporate Server. (Note: Because of minor problems with the installer, which will be corrected in a future product release, additional software is installed using Add Features and is documented in a later section.) Click Next.

Figure 9. Solutions window

8. On the Select Features page (see Figure 10), unselect NX UG Integration and FMS Server Cache.

Note: In phase one, the most basic components needed for a Teamcenter 8.0.1 environment

are installed. In phase two, additional commonly installed components are installed.


12

9. If this corporate server is also a Teamcenter (FlexLM/FlexNet) license server, select Flex License Server. If you do not select this option, you must provide information about the license

server later in this installation. 10. In the Installation Directory field, enter the absolute path to the directory where you want to install

Teamcenter 8.0.1, such as /home/infodba/Teamcenter8. (Note: You must install Teamcenter

8.0.1 in a new directory. To upgrade an existing installation, return to the Getting Started panel and select an upgrade installation.) Click Next.

Figure 10. Select Features page

11. On the TCFS Service page (see Figure 11), change the port to 11528, then click Next.

Figure 11. TCFS Service page

12. On the Operating System User page (see Figure 12), enter the AIX password in the Password and Confirm fields, then click Next.


13

Figure 12. Operating System User page

13. On the Configure TC_DATA screen (see Figure 13), enter the directory for the Data Directory Location, then click Next.

Figure 13. Configure TC.DATA page


14

14. If using Oracle, then on the Database Engine Selection page (see Figure 14), select Oracle. Then, enter the values For Database Server, Service, Port, Database User (infodba) and

Database Password (infodba), then click Next.

Figure 14. Database Engine Selection page

15. If using DB2 9.5, on the Database Engine Selection page (see Figure 15), select IBM DB2. Then, enter the values For Database Server, Name, Port, Database User (infodba) and Database

Password (infodba), then click Next.

Figure 15. Database Engine Selection page


15

16. On the Volume Specification page (see Figure 16), verify the values shown, then click Next.

Figure 16. Volume Specification page

17. On the Transient Volume Settings page (see Figure 17), verify the values, then click Next.

Figure 17. Transient Volume Settings page


16

18. On the Default Site Web Server page (see Figure 18), click Next.

Figure 18. Default Site Web Server page

19. On the Flex License Client page (see Figure 19), enter in the Port and Server of your FlexLM

license server, then click Next.

Figure 19. Flex License Client page


17

20. On the Teamcenter Administrative User page (see Figure 20), click Next.

Figure 20. Teamcenter Administrative User page

21. On the Database Template Summary page (see Figure 21), click Next.

Figure 21. Database Template Summary page


18

22. On the Confirm Selections page (see Figure 22), click Next. The installation will begin and status information will display in the Install Features status window (image not provided).

Figure 22. Confirm Selections page

23. On the Install Features window (see Figure 23), click Close.

24. As root, run the Post_task shell script, using the name displayed in the Install Features Successful area of the window.

Figure 23. Install Features window


19

Starting Teamcenter Environment Manager – phase two installation As user infodba, you install and maintain the Teamcenter 8.0.1.

1. Prior to running the tem.sh script, as root, run slibclean. 2. To start Teamcenter Environment Manager, enter the following:

cd /home/infodba/Teamcenter8/install/ ./tem.sh

3. On the Maintenance panel (see Figure 24), click Next.

Figure 24. Maintenance panel

4. On the Configuration Maintenance panel (see Figure 25), select option Perform maintenance on existing configuration then click Next.

Figure 25. Configuration Maintenance panel


20

5. On the Configuration Selection panel (see Figure 26), click Next.

Figure 26. Configuration Selection panel

6. On the Feature Maintenance panel (see Figure 27), select Add/Remove Features, click Next.

Figure 27. Feature Maintenance panel


21

7. On the Select Features panel (see Figure 28), select the following: a. FMS Server Cache

b. J2EE-based Server Manager c. Under Rich Client (double-click to expand), select Teamcenter Rich Client 2-tier. d. Click Next.

Figure 28. Select Features panel

8. On the File System Control (FSC) Service panel (FMS - File Management System), verify its

values, then click Next.


22

Figure 29. FSC Service panel

9. On the FSC Service: Connections panel (see Figure 30), review its values, then click Next.

Figure 30. FSC Service: Connections panel

10. On the FSC Service: FCC Defaults panel (see Figure 31), review the values, then click Next.


23

Figure 31. FSC Service: FCC Defaults panel

11. On the FSC Service Additional Sites panel (see Figure 32), click Next.

Figure 32. FSC Service Additional Sites panel

12. On the FSC Additional Group Sites panel (see Figure 33), click Next.


24

Figure 33. FSC Additional Group Sites panel

13. On the FSC Deployment Model panel (see Figure 34), click Next.

Figure 34. FSC Deployment Model panel

14. On the Operating System User panel (see Figure 35), enter the password twice, then click Next.


25

Figure 35. Operating System User panel

15. On the Teamcenter Administrative User panel (see Figure 36), enter the password, then click Next.

Figure 36. Teamcenter Administrative User panel


26

16. On the TcServer Character Encoding Settings panel (see Figure 37), click Next.

Figure 37. TcServer Character Encoding Settings panel

17. On the Server Manager for J2EE panel (see Figure 38), select Multicast Mode, then click Next.

Figure 38. Server Manager for J2EE panel


27

18. On the Server Manager for J2EE Performance Tuning panel (see Figure 39), click Next.

Figure 39. Server Manager for J2EE Performance Tuning panel

19. On the FCC Settings panel (see Figure 40), select Proposed Value For FMS_HOME. Click Next.

Figure 40. FCC Settings panel


28

20. On the FCC Parents panel (see Figure 41), click Next.

Figure 41. FCC Parents panel

21. On the IIOP Server Settings panel (see Figure 42), click Next.

Figure 42. IIOP Server Settings panel


29

22. On the Rich Client Settings panel (see Figure 43). a. Ensure that the Web Browser is correct for the browser that has been

installed on AIX, then select Next.

Figure 43. Rich Client Settings panel

23. On the Confirm Selections panel (see Figure 44), click Next.


30

Figure 44. Confirm Selections panel

24. The installation begins and status information is displayed in the Install Features panel (image not

provided). 25. On the Install Features panel (see Figure 45), click Close. As root, run the Post_task shell script,

using the name displayed in the Install Features Successful area.


31

Figure 45. Install Features panel

Installation checkpoint

Complete the following steps at this installation checkpoint.

1. Start the rich client to confirm a successful installation, by entering the following command: /home/infodba/Teamcenter8/portal/start_portal

2. Exit the rich client. 3. Start Pool Manager.

Reminder: If you use multicast and receive an error when attempting to start the processes, make sure to run the ifconfig lo0 inet6 ::1/0 delete command as root: /home/infodba//Teamcenter8/pool_manager/mgrstartMYDB

Generating the Web-tier application This section explains how to generate the Web-tier application.

Installing Web Application Manager

To install Web Application Manager, as infodba user, do the following steps:


32

1. Create a directory on your system named Web_tier under the Teamcenter 8.0.1 installation location (for example: /home/infodba/Teamcenter8).

2. Locate the INSTALL_TCWEB.TZ file in the installation directory (/MNT/tcunified801/Web_tier). 3. Copy the directory (using the AIX cd command) to the Web_tier directory on your system (such

as /home/infodba/Teamcente8/Web_tier).

4. Untar the Web_tier/INSTALL_TCWEB.TZ file to the Web_tier directory you just created:

cat ~image_path/Web_tier/INSTALL_TCWEB.TZ | uncompress –c | tar -xvf – (where image_path would be similar (/MNT/tcunified801/)

Before starting Web Application Manager

Prior to starting Web Application Manager, follow these steps:

1. Install the Teamcenter server and server manager using Teamcenter Environment. Manager (done as part of the phase one and two installations discussed earlier in this paper).

2. Install Web Application Manager (see the previous step Installing Web Application Manager). 3. Install a supported J2EE application server (WebSphere). 4. Obtain the information required to install the Web-tier application.

Start Web Application Manager

As user infodba, start Web Application Manager by performing these steps:

1. Copy the directory (with the CD command) to the local Web_tier directory. ( java must be in the PATH.) 2. Run the java –version command, which must return a version level of 1.5.0 or above.

3. Enter ./insweb. Then, on the Welcome Teamcenter panel (see Figure 46), click Copy ICDs.

Figure 46. Welcome Teamcenter panel

4. Browse to the Web_tier/icd sub-directory in the Teamcenter Engineering NFS-mounted file system.

Select this directory, ensure that ICD Sources is displayed in the Files of Type field. Click Open 5. Web Application Manager displays the path you chose in the Source field of the Copy ICD Files

dialog panel (see Figure 47). Click OK.


33

Figure 47. Copy ICD Files dialog panel

6. Web Application Manager copies the ICD files and shows a Progress dialog window (see Figure 48). When copying is complete, click OK.

Figure 48. Progress dialog window

7. The Teamcenter Web Application Manager dialog panel is shown. Click Add.

Figure 49. Teamcenter Web Application Manager dialog window

8. On the Add Web Application panel (see Figure 50), enter these fields: a. In the Name field, enter the name of this application (for example, UNI801).


34

b. In the Staging Location field, enter the path to the location where the application files will reside. (Note: Typically, the Web tier application is installed in a directory under the Web_tier

directory. Web Application Manager creates the directory you specify if it does not exist.) c. Optionally, in the Description field, enter a brief description of this application. d. Click Add.

Web Application Manager shows the Add Disk Location dialog

9. In the Disk Locations for Install Images field, enter the path to the Web_tier directory (/MNT/tcunified801/Web_tier) on the Teamcenter 8.0.1 NFS-mounted file system. (Note: This

location contains required source images required for generating the Web-tier application.) 10. Web Application Manager shows the Add Web Application dialog and shows the path you

entered in the Disk Locations for Install Images field. Select the list icon adjacent to the Solution

Type field and choose Thin Client from the list. 11. Web Application Manager shows Thin Client in the Solution Type field. Select Solutions

(adjacent to the Selected Solutions field).

Figure 50. Add Web Application panel

12. On the Select Solutions panel (see Figure 51), choose the following solutions, then click OK:

Teamcenter - Server Adapter Teamcenter – Web Tier Infrastructure Teamcenter - Web Tier Core Applications

Teamcenter Services WSDL/SOAP Support


35

Figure 51. Select Solutions dialog panel

13. On the Add Web Application panel, ensure that the solutions you select are displayed in the

Selected Solutions field, then click OK.

Figure 52. Add Web Application panel


36

14. For most parameters on the Modify Required Context Parameters panel, you can accept the default values. You must supply values for the following parameters, then click OK.

TreeCache Cluster Name => Cluster TreeCache Mode => Mcast TreeCache Cluster Port (when using multicast communication protocol) => 45566

Figure 53.

15. Web Application Manager begins installing files and displays the Progress panel (see Figure 54). Click OK (to close the Progress dialog window)

Figure 54. Progress panel


37

16. Web Application Manager shows the Modify Web Application dialog (see Figure 55). Click Modify.

Figure 55. Teamcenter Web Application Manager panel

17. On the Modify Web Application panel (see Figure 56), select Generate Deployable File….

Figure 56. Modify Web Application panel

18. In the Generate Deployable File dialog window (see Figure 57), enter a name for the Web-tier EAR file in the Deployable File Name field. Click OK. (Note: Web Application Manager adds the

file extension. In this example, UNI801 becomes a file named UNI801.ear. )

Figure 57. Generate Deployable File dialog window


38

Web Application Manager begins building the EAR file, and the WAR file within it, and displays the Progress dialog window (see Figure 57).

19. When Web Application Manager indicates that file generation is complete, do the following:

a. Click OK to close the Progress window. b. Click OK to close the Modify Web Application dialog window. c. Click Exit to exit Web Application Manager.

Web Application Manager creates the UNI801.ear file in the deployment directory under the staging locations (/home/infodba/Teamcenter8/Web_tter/staging1/deployment).

Figure 58. Progress panel

Deploying WebSphere Application Server This section explains Web application deployment as well as the required server-manager processes that need to be started. This example deploys one instance of WebSphere Application Server 6.1.0.25 hosting

the Teamcenter Engineering Web-tier application (EAR file).

For a list of currently supported Web-application servers for each operating system, see the Teamcenter 8.0.1 Release Bulletin and the Siemens PLM Solutions Global Technical Access Center.

Two methods to deploy a Web application are described in this paper. The first uses a set of utility programs to deploy the Web application into WebShpere. The second method uses the Integrated Solutions Console to deploy and configure a Web application.

Deploying Teamcenter Web applications using utility programs

The task of installing and configuring the Siemens PLM – Teamcenter Unified 8.0.1 Web application into WebSphere is automated and uses wsadmin scripts. Also, a few steps are required after installing a Web application; these steps are also automated, using shell (ksh) scripts. The tools to deploy a Web

application are contained in TC801-was-scripts.tar The following section gives a brief usage of the scripts.


39

tc801_variables.ksh – This shell (ksh) script sets the environment variables that are used to install and uninstall the Teamcenter Unified 8.0.1 Web application. You need to update the relevant

environment variable from this file. tc801_was_install.ksh – This script installs, configures and starts the Teamcenter Unified 8.0.1 Web

application by using the wsadmin script (files: install_uni801.py, RAconf_uni801.py, start_uni801.py).

tc801_was_uninstall.ksh – This script stops and uninstalls the Teamcenter Unified 8.0.1 Web application by using the wsadmin script (file: stop_uni801.py, uninstall_uni801.py).

The following wsadmin (Jython interface) scripts achieve the install and uninstall procedures.

install_uni801.py RAconf_uni801.py uninstall_uni801.py

start_uni801.py stop_uni801.py

After the tc801_was_install.ksh shell script successfully completes, proceed to the section of this paper

entitled Accessing the thin client.

Starting WebSphere Application Server and IBM HTTP Server processes

You can use the following steps to start WebSphere Application Server and the WebSphere Administration console:

1. As root, run the following command: ifconfig lo0 inet6 ::1/0 delete 2. Start WebSphere Application Server by running the following scripts:

/usr/IBM/WebSphere/AppServer/bin/startServer.sh server1

/usr/IBMHTTPserver/bin/apachectl start 3. Open the WebSphere Application Server Integrated Solution Console in a browser by entering

the following URL: http://was_server_name:9060/ibm/console

Installing and configuring UNI801 EAR in WebSphere 6.1

This section explains the steps for installing, configuring and starting the UN801 application.

Installing the new application

First, you need to install the UNI801 application.

1. After logging in, from the left panel of the welcome screen on the administration console, select Install New Application (see Figure 59).

2. Provide the path (again, see Figure 59) to the location of the Teamcenter 8.0.1 Web-tier EAR file

(UNI801.ear) that was copied from the system where Teamcenter 8.0.1 was installed onto the WebSphere Application Server system. (Note: If the Web tier EAR file is named UNI801.ear, specify the context root as UNI801. After the context root and location for the UNI801.ear file

have been provided.) 3. Click Next.


40

Figure 59. Installing and configuring UNI801 EAR

4. On the screen shown in Figure 60, select Generate Default Bindings and Use the default virtual host name for Web and SIP Modules, then click Next.

Figure 60. Installing and configuring UNI801 EAR (continued)

5. Next, you will see an Application Security Warnings screen, which is informational and requires no action on your part (no screen capture is provided here). Click Continue.

6. Click Next. after verifying that the application name provided by the script is your expected value (see Figure 60).


41


7. Click both lines in Clusters and servers(see Figure 61), ensure that the box adjacent to UNI801 is selected, then click Apply, and then click Next. (Note: UNI801 should have both server1 and wbeserver1 selected; the other two are only serviced by server1.)


8. Continue to click Next on the following screens, accepting the default values (no screen captures are provided).


42

9. When you receive an Application Resource Warnings screen (no screen capture is shown here), click Continue.

10. Place a check mark in Select, adjacent to UNI801 (no screen capture is provided here). This maps the application to default_host.

11. Click Next, then click Finish.


12. After the Installation completes (see Figure 64), click Manage Applications to proceed to

additional changes.



43

Manually configuring the JETI resource adapter

After installing the Teamcenter 8.0.1 Web-tier application EAR file, you need to manually configure

the JETI resource adapter.

1. From the administrative console, click UNI801 to manage the application (see Figure 65).

Figure 65. Configuring the JETI resource adapter

2. Click Manage Modules (see Figure 66).

Figure 66. Configuring the JETI resource adapter (continued)


44

3. Select the connector module named JETIResourceAdapter by clicking the text JETIResourceAdapter under the Module column (see Figure 67).


4. Under Additional Properties, click Resource Adapter (see Figure 68).


5. Click J2C connection factories (no screen shot is provided here). 6. Click New (no screen shot is provided here).


45

7. On the screen shown in Figure 69, name the connection factory JETIResourceAdapter.


8. On the screen shown in Figure 70, set the JNDI name to jca/JETI/Adapter, then click Apply.

9. Again, on the screen shown in Figure 70, select Connection pool properties.


10. On the following screen (not shown here), enter the following values, then save the application-

server configuration changes: 1000 for Maximum connections 0 for Minimum connections

11. Click OK 12. Click Save to apply the changes to the master configuration as shown in Figure 72.


46

Figure 71. Configuring the JETI resource adapter and saving the changes (continued)

13. If the UNI801 application is not running, click the check box adjacent to the application (see Figure 72), then click Start (near the top of the screen panel).



47

14. Regenerate and propagate the plug-in by clicking Generate Plug-in, then by clicking Propagate Plug-in. This step is required to access the UNI801 application through IBM HTTP Server.


Accessing the thin client

This section explains how to start the UN801 application.

1. Verify the connection by accessing http://thetah.austin.ibm.com:9080/UNI801/webclient. 2. Verify that the application is accessible through the default Web server, using IBM HTTP Server

as the front end, with port 80 and using this URL: http://thetah.austin.ibm.com/UNI801/webclient.

Note: Substitute the name of your WebSphere server system for thetah.austin.ibm.com.

Installing and configuring the distribution server There is Siemens PLM Solutions documentation for installing and configuring the distribution server and distribution-server instance used to install the client application over the Web. Refer to Installation on

UNIX and Linux Servers, in the section entitled Part V: Web tier Installation. Installation documents may

be accessed from either the Product Media for Teamcenter or online for registered Siemens customers at http://support.ugs.com/docs.

After completion of this step, you can install the tier-four rich client on a client workstation by simply invoking the otwweb/otw.html page from a Web browser.

The distribution-server installation process provides the utility programs that are used to listen for

requests to install the software. The distribution-server instance installation process defines the files that are installed on the rich client, as well as the files that need to be added to the IBM HTTP Server to allow a client workstation to request the initial installation.

Preparing to install the distribution server for the four-tier rich client

Prepare to install the distribution server in a four-tier rich-client environment with these steps:

1. As user infodba, enter the following AIX commands: cd /home/infodba/Teamcenter8 mkdir Webclient_tier cd Webclient_tier


48

2. Untar the Web_tier/INSTALL_TCWEB.TZ file to the Web_tier directory you just created: cat ~image_path/Web_tier/INSTALL_TCWEB.TZ | uncompress –c | tar -xvf (where image_path would be similar to /MNT/tcunified801)

3. Ensure that java is in the PATH. 4. Run the following command: java –version (needs to return version 1.5.0 or above) 5. Enter the command: insweb.

6. Click Copy ICDs (see Figure 74), then browse to where the otw/icd directory is and click OK,

Figure 74. Preparing to install the distribution server for the four-tier rich client

7. Click Exit (see Figure 75).


49

Figure 75. Preparing to install the distribution server for the four-tier rich client (continued)

Creating the distribution server

To create the distribution server, follow these steps:

8. Click Add (see Figure 76).


9. Add the disk location where the files that are needed to install the distribution server are found by

following these steps: a. In the Add Disk Location pop-up panel, browse to the correct location then click OK. b. For the name, enter a unique value such as UNI801DistServer.

c. In the Add Web Application pop-up window, click OK,


50


10. Leave the values in the Modify Required Context Parameters as the defaults, and click OK


11. In the Progress window (not shown here) click OK, after creating the distribution server.

Creating the distribution-server instance

This section explains how to create the distribution-server instance.

1. Click Add (see Figure 79).


51

Figure 79. Creating the distribution server instance

2. Change Name to something unique, such as UNI801DistServerInstance, 3. Change Disk Location to /MNT/tcunified801.

4. Change Solution Type to Distribution Server Instance. 5. In Selected Solutions, verify that the list includes at least the two shown in the screen capture

shown in Figure 80. Click OK.


52

Figure 80. Creating the distribution server instance (continued)

6. Modify the Context Parameters if necessary, then click OK.


7. Enter the Host where the FSC runs, then click OK


53


8. In the URI field, enter http:/thetah.austin.ibm.com/UNI801, then click OK. (Substitute the name

of the WebSphere server system that hosts the Web Application, along with the name of the EAR file you generated when deploying the Web application.)


9. In the Progress Window, click OK.


54

10. In the Web Application Manager window click Exit (no screen captures are shown for these step). 11. There are files to be placed in HTTPServer, so, as user infodba on the Teamcenter 8.0.1 Server,

enter the following: cd /home/infodba/Teamcenter8/Webclient_tier/staging2/webapp_root tar –cvf /tmp/OTWWEB.tar otwweb

12. As root, copy the OTWWEB.tar file to your IBM HTTP Server system: cd /usr/IBM/HTTPServer/htdocs/en_US tar –xvf /tmp/OTWWEB.tar

13. To start the processes and verify the installation, on the Teamcenter Engineering Server system, run the following commands as user infodba, ensuring that the java command is in the $PATH:

cd /home/infodba/Teamcenter8/Webclient_tier/staging1/webapp_root ./start_rmi ./start_server

14. From a Windows system, connect to the following URL through a browser, substituting the name of the system where IBM HTTP Server runs:

http:/thetah.austin.ibm.com/otwweb/otw.html

This runs an application that downloads the files for the four-tier rich client environment to the desktop (see Figure 84) and can take several minutes, depending on network traffic and latency.

This also installs the files and adds an icon to the desktop to start Teamcenter 8.0.1.


15. Double-click the Teamcenter 8.0.1 Rich Client 4-Tier icon on the Windows desktop to start the

rich client (see Figure 85).


55

Figure 85. Teamcenter desktop icon

16. Enter the user and password (infodba and infodba for this basic installation), as shown in this screen capture of the Teamcenter Login panel in the Rich Client GUI (see Figure 86).


Congratulations, you have successfully verified the over-the-Web installer and the execution of the four-tier Rich Client for Teamcenter 8.0.1, accessing your IBM Power System Server running AIX.

Creating more business-application servers An advanced deployment method includes creating more business-application servers. That is, Teamcenter 8.0.1 supports horizontal scalability by adding more application-server systems.

1. Create a unique pool_manager directory for each system that will become an additional server.

2. NFS-mount the /home/infodba file system onto each additional application server. 3. Start the pool_manager process on each node.

Making new copies of the pool_manager directory

Here are the steps to make new copies of the pool_directory:

1. Create a copy of the pool_manager directory (under tc_root which is /home/infodba/Teamcenter8).

a. Name it something like pool_manager_tcserver2, where tcserver2 is the hostname (uname –n) of the AIX server you desire to add as an application server.


56

b. Inside this directory, edit the serverPool*.properties file. (The exact name of this file varies, depending on the configuration name given during the initial installation with Teamcenter

Environment Manager (TEM). In our example installation, this unique name was MYDB). c. In this file, change the value assigned to POOL_ID; the value must be unique. (In this

example, the uname –n was appended to the existing value.)

2. In the same properties file, check the SERVER_HOST property. If this property is set, change it to the hostname of the server you are adding. Alternatively, you can unset this property (no text to the right of SERVER_HOST=).

Note: Typically, SERVER_HOST is set when a system has more than one network interface.

3. Edit the mgrstartMYDB file (not the template, but the actual script). Replace all occurrences of pool_manager with pool_manager_tcserver2 (using the same value that was used for the new

pool_manager directory). 4. Start the server-pool manager process on the new host (start it from the new

pool_manager_tcserver2 directory).

Adding a system with name mewe as an additional application server

The following steps let you add a system with the name mewe as an additional application server.

1. On the additional systems that are to be application servers, ensure that the infodba user and

group are defined and match the user ID and group ID that are assigned on the system where TC 8.0.1 is installed.

2. NFS-export the /home/infodba file system from the server where Teamcenter 8.0.1 is installed

and NFS-mount the /home/infodba file system onto the servers that are to become additional application-server nodes.

3. As user infodba, create new copies of the pool_manager directory and modify the contents to be

unique for each server node. 4. If using multicast, delete the ipv6 definition for lo0, as defined earlier in the paper:

cd /home/infodba/Teamcenter8

mkdir pool_manager_mewe (cd pool_manager && tar –cvf- ./) | (cd pool_mamanger_mewe && tar –xvf-) cd pool_manager_newe

5. Use the AIX vi editor to modify serverPoolMYDB.properties by changing line POOL_ID=PoolA to Pool_ID=PoolAmewe.

6. Use vi to modify mgrstartMYDB, changing all occurrences of pool_manager to

pool_manager_mewe. 7. On the mewe system, enter the following:

cd /home/infodba/Teamcenter8/pool_manager_mewe

./mgrstartMYDB

Upon completing these steps, the additional pool manager is available for the Web application that runs in WebSphere Application Server to route requests for server connections to Teamcenter 8.0.1.


57

Summary This paper has provided detailed installation and configuration instructions for Teamcenter Unified 8.0.1 on an IBM Power Systems servers on AIX 53 TL7 and also using AIX 6.1 for the Oracle and DB2

database servers and WebSphere Application Server. Steps to configure the over-the-Web installer to automatically install the four-tier rich client were included. It also provided information on how to create an Oracle or DB2 database instance for Teamcenter. In all, this paper provides easy to follow instructions for

ATSS and FTSS personnel, who want to install and configure Teamcenter Engineering on IBM Power System servers for their PDM applications.

For more information about Teamcenter products or other information not covered in this paper, see the

list of resources provided in the following appendices.


58

Appendix A: setvars.sh The following script can be executed before starting the installation; which does the required environment setup in a given VNC Session.

# setvars.sh

# Purpose set values in aixterm to prepare for install of Teamcenter 8.0.1

# Author: Gary Hornyak

# Genesis: 10/02/2009

# Provided As-is

#

export LDR_CNTRL=NAMEDSHLIB=TCINST,doubletext32@MAXDATA=0x80000000@DSA

export EXTSHM=ON

ulimit -d unlimited

ulimit -s 132768

if [[ $(uname -v) -eq 6 ]]

then

ulimit -r unlimited

fi


59

Appendix B: Resources These Web sites provide useful references to supplement the information contained in this paper:

IBM System p Information Center

http://publib.boulder.ibm.com/infocenter/pseries/index.jsp

System p on IBM PartnerWorld®

ibm.com/partnerworld/systems/p

AIX on IBM PartnerWorld ibm.com/partnerworld/aix

IBM Systems on IBM PartnerWorld ibm.com/partnerworld/systems/IBM Publications Center

IBM Publications Center

www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi?CTY=US

IBM Redbooks® ibm.com/redbooks

IBM developerWorks® ibm.com/developerworks

WebSphere Application Server V6.1 Install Guide for PDM Applications

http://www.ibm.com/partnerworld/wps/servlet/ContentHandler/whitepaper/aix/websphere_v6r1/guide

Siemens PLM Solutions Global Technical Access Center http://support.ugs.com

Oracle www.oracle.com/index.html


60

About the authors Gary Hornyak is an IBM Senior Software Engineer Technical Consultant for PLM Solutions, specializing in PDM application architecture within Systems and Technology Group in the ISV Global Enablement

organization. Gary has more than 20 years of experience with various PLM software solutions.

Terry Wang is a Senior Technical Consultant with IBM System and Technology Group. Terry joined IBM

in 1988 to work on AIX development. He is currently with the IBM STG ISV Solution Enablement team. His most recent interest is in the area of applying advanced AIX technology to PLM applications. Terry earned M.S. degree of Computer Science from the University of Wisconsin, Madison in 1986.

Sachin Bhandare is an IBM Software Engineer Technical Consultant for PLM Solutions. Sachin has more than eight years of experience in software development and maintenance in various projects on the

UNIX® platform.



61

Trademarks and special notices © Copyright IBM Corporation 2009. All rights Reserved.

References in this document to IBM products or services do not imply that IBM intends to make them

available in every country.

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked

terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A

current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other

countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Other company, product, or service names may be trademarks or service marks of others.

Information is provided "AS IS" without warranty of any kind.

Information concerning non-IBM products was obtained from a supplier of these products, published announcement material, or other publicly available sources and does not constitute an endorsement of

such products by IBM. Sources for non-IBM list prices and performance numbers are taken from publicly available information, including vendor announcements and vendor worldwide homepages. IBM has not tested these products and cannot confirm the accuracy of performance, capability, or any other claims

related to non-IBM products. Questions on the capability of non-IBM products should be addressed to the supplier of those products.

All statements regarding IBM future direction and intent are subject to change or withdrawal without

notice, and represent goals and objectives only. Contact your local IBM office or IBM authorized reseller for the full text of the specific Statement of Direction.

Some information addresses anticipated future capabilities. Such information is not intended as a

definitive statement of a commitment to specific levels of performance, function or delivery schedules with respect to any future products. Such commitments are only made in IBM product announcements. The information is presented here to communicate IBM's current investment and development activities as a

good faith effort to help with our customers' future planning.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part

of the materials for this IBM product and use of those Web sites is at your own risk.

installing and configuring siemens plm solutions...

Documents