Deploy on a WebLogic application server/Apache HTTP server (H-S)
This procedure deploys one instance of the Teamcenter web tier application (WAR file) hosted on Oracle WebLogic (application) Server and configures an Apache HTTP server that is used as the web tier server.
1. Deploy one instance of an Oracle WebLogic Server hosting the Teamcenter web tier application (WAR file).
2. Configure the Apache HTTP server.
You must install the Apache HTTP server and configure it so that it can communicate with the your Teamcenter application on the WebLogic application server.
a. Install the Apache HTTP server on a separate host from the WebLogic server host.
For information for installing Apache HTTP server on a specific type of host, see the Apache web server documentation:
http://httpd.apache.org/docs/2.4/platform/
b. Install and configure the Apache HTTP server plug-in as described in the Oracle WebLogic documentation:
http://docs.oracle.com/cd/E21764_01/web.1111/e14395/apache.htm#CDEGCBAC
Deploy on a WebLogic application server/WebLogic Express server (H-S)
This procedure deploys one instance of the Teamcenter web tier application (WAR file) hosted on Oracle WebLogic (application) Server and one instance of the Teamcenter proxy application (WAR file) hosted on a WebLogic Express (WLX) server. 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.
1. Deploy one instance of an Oracle WebLogic Server hosting the Teamcenter web tier application (WAR file).
2. Deploy the Teamcenter proxy application.
a. Generate the Teamcenter WebLogic proxy WAR file.
For information, see the Teamcenter server installation manual (forWindowsorUNIX/Linux).
b. Install WebLogic Express and create a domain for deploying the WebLogic proxy WAR file.
c. Deploy the WebLogic proxy WAR file in WebLogic Express.
For information, see Deploying New Applications and Modules in theWebLogic Express documentation.
Note
Ensure your clients connect to the WebLogic Express host and port, rather than the web application server.
Deploy on a WebLogic server/Internet Information Server (IIS)
You can use IIS as your HTTP server on Windows 2008 servers in an H-S configuration. You must configure the WebLogic server proxy (WLS proxy) DLLs in this configuration. You can choose to use either 32-bit DLLs or 64-bit DLLs. This procedures uses the 32-bit DLLs.
For information about installing IIS7 on Windows 2008 servers, see the following URL:
http://learn.iis.net/page.aspx/29/installing-iis7-on-windows-server-2008/
1. Deploy one instance of an Oracle WebLogic Server hosting the Teamcenter web tier application (WAR file).
2. Copy the iisproxy.dll and iisforward.dll files available in the WLSHOME\Server\plugin\win\32 or WLSHOME\Server\plugin\win\x64 directory to the directory that you want as your home folder for your IIS web site. Change the directory security properties to allow execute permission to its contents.
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.
3. Open the IIS Manager and choose Start→Administrative Tools→Internet Information Services (IIS) Manager.
4. In the Connections pane, expand your computer name entry until you see Sites.
5. 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 web site in the Site name box, for example, IISWLS, and click the browse button ( ) next to the Physical path box.
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.
6. 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. Click Add in the Actions pane (on the right).
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.
7. 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. In the right pane, click Add Script Map.
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 site's home folder and select the iisproxy.dll file.
e. Type a name for the script map in the Name box, for example, iisproxy, and click OK.
f. Click Yes in the Add a Script Map dialog box to allow the ISAPI extension.
8. 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-application—name Debug=ALL
DebugConfigInfo=ON
The WebLogicPort value is 7001 by default. The WlForwardPath value points to the web application that the proxy forwards to (tc is the default for the Teamcenter web application). If you want to forward to all web applications, set this value to /.
The debug values are optional and are set for debugging purposes. The default log file for debug messages is C:\TEMP\wlproxy.log.
9. Restart IIS.
To access the web site, enter a URL in the following format:
http://host-name:port-number/console/login/LoginForm.jsp