Custom or Expand Installations › UNIX › Perform a Custom or Expand Installation › Install Only the Web Tier Components › Select a Web Application Server Configuration Option › Configure Your Existing Web Application Server

Configure Your Existing Web Application Server

You must select the Use existing Java application server, deploy web applications option to view the Select a Web Application Server to deploy to screen. Select the server type before configuring your web application server.

To configure your existing web application server

1. Select your existing web application server from one of the following options and press Enter.
   • Tomcat 5.5
   • WebLogic 10
   • WebLogic 9.2
   • WebSphere 6.1
   • Oracle Application Server 10g R3

   If your existing web application server is SAP Application Server 7.0 or JBoss 4.04, select Use existing Java application server, do not deploy web applications.

   Note: If you are using Tomcat 6 as your existing web application server, select Tomcat 5.5 from the drop-down list. If you are using WebSphere 7 as your existing web application server, select WebSphere 6.1 from the drop-down list.

2. Provide the requested configuration details for your web application server and press Enter. The information required for each supported web application server is as follows.

   Apache Tomcat 5.5/6

   • Instance to install to: Name of the current web application server instance (for example, localhost)
   • Application server installation directory: The directory where the web application server is installed (for example, <INSTALLDIR>/wdeploy/appserver/Tomcat5520)

   WebLogic 9.2

   • Admin port: Administration port of the application server - mandatory for WebLogic (for example, 7001)
   • Admin login: User name with administration rights to the application server - mandatory for WebLogic
   • Admin password: Password for account with administration rights to the application server - mandatory for WebLogic
   • Instance to install to: Name of the current web application server instance (for example, mserver1)
   • Application server domain root directory: The WebLogic domain root directory (for example, /bea/user_projects/domains/base_domain)

   WebLogic 10

   • Admin port: Administration port of the application server - mandatory for WebLogic (for example, 7001)
   • Admin login: User name with administration rights to the application server - mandatory for WebLogic
   • Admin password: Password for account with administration rights to the application server - mandatory for WebLogic
   • Instance to install to: Name of the current web application server instance (for example, mserver1)
   • Application server domain root directory: The WebLogic domain root directory (for example, /bea/user_projects/domains/base_domain)

   WebSphere 6.1/7

   • SOAP port: The SOAP Connector Port of the application server (for example, 8880)
   • Admin login: User name with administration rights to the WebSphere application server
   • Admin password: Password for account with administration rights to the application server
   • Instance to install to: Name of the current web application server instance (for example, server1)
   • Virtual host: The virtual host to which the application must be bound
   • Admin is secure?: Select this option to enable security requiring administrative access credentials to the application

     Note: Values for the username and password parameters must be set when Admin is Secure is enabled.

   • Application server installation directory: The directory where the web application server is installed (for example, /IGBM Web Sphere/AppServer)

   Oracle Application Server 10g R3

   • Admin port: Administration port of the application server - mandatory for Oracle 10g R3 (for example, 6003)

     This should be in the Request port of the <notification-server> element in the opmn.xml file.

   • Admin login: User name with administration rights to the application server - mandatory for Oracle 10g R3
   • Admin password: Password for account with administration rights to the application server - mandatory for Oracle 10g R3
   • Admin is secure: Select this option only if you want Secure Sockets Layer (SSL) as part of the deployment

     Note: If Admin is secure is not selected, you still must specify the username and password to access the server.

   • Instance to install to: Name of the current web application server instance (for example, home)
   • Application server installation directory: The directory where the web application server is installed (for example, /product/10.1.3/OracleAS_1)
   • Server Name: Name of the target application server (for example, myserver.domain.com)
   • Group ID: Name of the server group to which the target application belongs (for example, Default_group)