C Configuring IIS as a Proxy Server for Agile PLM

C.1 Configuring IIS as a Proxy Server for Agile PLM

To set up an Agile Web proxy on IIS for WebLogic:

1. Download ofm_wlsplugins_generic_11.1.1.7.0_disk1_1of1 from the web site: http://www.oracle.com/technetwork/middleware/ias/downloads/wls-plugins-096117.html

2. Extract the WLSPlugin11g-IIS6-IIS7-IIS75-win64-x64.zip file to the <WLS_Home>\weblogic-plugins-1.1 directory

3. Create the iisproxy.ini file in the %WLS_PLUGIN_HOME%\lib directory with the following details:

   For Standalone environment

   WebLogicHost=wls-host

   WebLogicPort=wls-port

   Debug=ALL

   WLLogFile=C:\Temp\wl-proxy.log

   For Cluster environment

   WebLogicCluster=ManagedServer1:ManagedServer1 Listen port, ManagedServer2: ManagedServer2 Listen port

   Debug=ALL

   WLLogFile=C:\Temp\wl-proxy.log

4. Verify that the %WLS_PLUGIN_HOME%\lib is included in the PATH environment variable properties.

5. On the Web server computer, choose Start > Administrative Tools > Internet Information Services (IIS) Manager.

   The Internet Information Services Manager window appears.

6. Expand the tree view under the Connections pane.

7. Click the + next to the server name and select Sites.

8. Click the Default Web Site.

   
   

   Note: Due to security vulnerabilities, we recommend that you do not use the Default Web Site installed with Internet Information Server and create a new Web site named Agile PLM Web Site instead.

   
   

9. Open Handler Mappings.

10. Add a script map. Set Extension like *, set Executable to %WLS_PLUGIN_HOME%\lib\iisproxy.dll, and enter a Name.

11. Start IIS.

    
    

    Note: To start IIS, stop all of the IIS services through the Control Panel and then restart them, or restart the computer. This ensures that the .dll is reloaded. Do not use IIS Manager to restart IIS.

    
    

C.2 Logging In to the Agile Web Client

To test the Agile Web client setup:

1. Start the Agile Server:

   a. Windows: Choose Start > All Programs > Agile >Agile PLM > Start Agile Server to start the Agile server, if it is not installed as a Windows service.

   UNIX: Run the StartAgile.sh script located in the AGILE_HOME/agileDomain/bin directory.

   b. A command window appears. This window must remain open, but can be minimized, for users to access the Agile Web client.

   Wait until the following message appears in the command window: "Agile PLM Server Starting Up".

2. Open your browser and go to the following URL to test the Agile Web client setup:

   http://webserver_hostname:port/virtual_path/PLMServlet

   
   

   Note: The URL is case-sensitive.

   
   

   The login window for the Agile Web client appears in the browser.

   If you need to stop the application server, close the command window or choose Start > All Programs > Agile > Agile PLM > Stop Agile Server.

C.3 Troubleshooting the Agile Web Client

This section provides the basics for troubleshooting the Agile Web client and Web server issues.

C.3.1 Confirming Accessibility

Confirm that the following connections are valid:

• Ping the Agile Application Server computer to make sure it is accessible from the Agile Web proxy computer and that the specified port is available.

• Make sure the web server is up and running on the specified ports, and that the specified DNS hostname is valid and registered for external accessibility by the Agile Web client browsers.

C.3.2 URL Error Messages

If you specify the web client URL in the browser and receive the message "Page not found", check the following:

• Make sure that the IIS Web server is accessible.

• Open the iisproxy.ini file and make sure the client virtual path name is the same as the login URL for the Agile Web client.

• Make sure the Agile Viewer has started on the host computer.

If the following error message appears:

"Servlet tunneling to AgileViewServerHost:5099 (IP=x.x.x.x) Connection state: ERROR"

• Check to see if the Agile Viewer hostname specified during the installation is correct and the port number is available. The information on the Agile Viewer hostname and port number is specified in the web.xml file.

• Make sure the Agile Viewer-specific ports are open from the DMZ firewall to the internal firewall.

C.3.3 Connection Refused or Server is Busy Error Message

TCP connections can be buffered in a wait queue, which has a default value of 50. To increase this value, open AGILE_HOME\agileDomain\config\config.xml and increase the wait queue attribute value by 25 percent until the messages no longer appear.

C.3.4 Changing the Password for the Agile Domain

Changing the password from the console only changes the WebLogic password. The Agile Web client uses a password that is specified during installation. This password cannot be changed in WebLogic.