7 Reconfiguring Application Server Instances

7.2.1.1 Things to Know Before You Start

During installation, port numbers were reserved for OracleAS Web Cache services. You can find the port numbers in the following file:

(UNIX) ORACLE_HOME/install/portlist.ini
(Windows) ORACLE_HOME\install\portlist.ini

The port numbers are listed as:

Web Cache HTTP Listen port = port_number
Web Cache HTTP Listen (SSL) port = port_number
Web Cache Administration port = port_number
Web Cache Invalidation port = port_number
Web Cache Statistics port = port_number

These port numbers will be used when you configure OracleAS Web Cache. If you want to use different port numbers, you can change them after you configure OracleAS Web Cache.

7.2.1.2 Configuring OracleAS Web Cache

To configure OracleAS Web Cache, take the following steps:

1. Using the Application Server Control Console, navigate to the Application Server Home page for the instance in which you want to configure OracleAS Web Cache.

2. On the Application Server Home page, in the System Components section, click Configure Component.

3. On the Select Component page, select Web Cache from the menu. Click Continue.

4. On the Login page, in the Administration Password field, enter the ias_admin password. Click Finish.

7.2.1.3 Post-Configuration Tasks

When the configuration is finished, take the following steps:

1. In the Application Server Control Console Confirmation page, click OK. The Application Server Home page appears.

2. Verify that Web Cache is listed in the System Components section. It will have a status of Down. Select the check box next to Web Cache and click Start.

3. When the operation completes, verify that Web Cache shows a status of Up. Then, click Web Cache and verify that the Web Cache Home page is displayed.

4. On the Web Cache Home page, click Administration to set up OracleAS Web Cache.

   
   

   See Also: Oracle Application Server Web Cache Administrator's Guide for basic setup and configuration tasks

   
   

7.2.2.1 Things to Know Before You Start

Before you configure OracleAS Portal, make sure that the sqlnet.ora file contains the following line, and that LDAP is listed in the line:

NAMES.DIRECTORY_PATH= (TNSNAMES, LDAP, ONAMES, HOSTNAME)

The sqlnet.ora file is located in the following directory:

(UNIX) Oracle_Home/network/admin
(Windows) Oracle_Home\network\admin

7.2.2.2 Configuring OracleAS Portal

To configure OracleAS Portal, take the following steps:

1. Using the Application Server Control Console, navigate to the Application Server Home page for the instance in which you want to configure OracleAS Portal.

2. On the Application Server Home page, in the System Components section, click Configure Component.

3. On the Select Component page, select Portal from the menu. Click Continue.

4. On the Login page, in the Administration Password field, enter the ias_admin password. Click Finish.

7.2.2.3 Post-Configuration Tasks

When the configuration is finished, take the following steps:

1. In the Application Server Control Console Confirmation page, click OK. The Application Server Home page appears.

2. Verify that OC4J_Portal and Portal:portal are listed in the System Components section.

3. Restart Oracle HTTP Server and start OC4J_Portal:

   1. In the System Components table, select HTTP_Server, and click Restart.

   2. Select OC4J_Portal, and then click Start.

      The home OC4J instance will be Down after configuring OracleAS Portal through Application Server Control Console. If you wish to start this service, click the home component in the System Components section, then click Start.

4. Verify that OC4J_Portal and Portal:portal both have a status of Up:

   1. Click OC4J_Portal and verify that the OC4J_Portal page is displayed.

   2. Click Portal:portal and verify that the Portal page is displayed.

      Initially, the Portal:portal status may be displayed as Down. This is normal. The status should be updated approximately five minutes after configuration.

5. If this is the first instance of OracleAS Portal to use this OracleAS Metadata Repository, run the following command in the middle-tier Oracle home (make sure the ORACLE_HOME environment variable is set before you run this command):

   • On UNIX:

     ORACLE_HOME/portal/conf/ptlconfig -dad portal [-pw PORTAL_schema_password]
     
     

   • On Windows:

     ORACLE_HOME\portal\conf\ptlconfig -dad portal [-pw PORTAL_schema_password]
     
     

   This script writes OracleAS Portal configuration entries into the OracleAS Metadata Repository. Do not run this script if there are other OracleAS Portal instances using the OracleAS Metadata Repository, because this script will overwrite any existing OracleAS Portal configuration entries in the OracleAS Metadata Repository.

   
   

   Note: The PORTAL schema password is stored in the Oracle Internet Directory and the entry may be viewed by an administrator using the oidadmin utility with the following path under Entry Management: OrclResourceName=PORTAL,orclReferenceName=iasdb.myhost.mycompany.com, cn=IAS Infrastructure Databases,cn=IAS,cn=Products,cn=OracleContext

   
   

6. Verify that you can access OracleAS Portal at the following URL:

   http://hostname.domain:port/pls/portal
   
   

   In the URL, hostname.domain is the OracleAS Portal host and port is the OracleAS Web Cache HTTP Listen port for the OracleAS Portal instance. For example:

   http://myhost.mycompany:7777/pls/portal
   
   

   You can log in to OracleAS Portal as the user portal.

   • If this is the first OracleAS Portal instance to use the OracleAS Metadata Repository, the password is the original ias_admin password you supplied for this middle tier during installation. The original ias_admin password is required, even if you changed the ias_admin password after installation.

   • If this is not the first OracleAS Portal instance to use the OracleAS Metadata Repository, the password is either:

     • The original ias_admin password for the first middle tier associated with the OracleAS Metadata Repository

     • The current portal password, if the administrator changed the portal user password after the first OracleAS Portal instance was installed

   
   

   See Also: Oracle Application Server Portal Configuration Guide for more information on configuring OracleAS Portal

   
   

7.2.2.4 Steps Needed If OracleAS Portal Configured Before OracleAS Web Cache

If you expanded the instance before you configured OracleAS Web Cache, you must take the following steps to correct the situation:

1. Configure OracleAS Web Cache, as described in Section 7.2.1.

2. Edit iasconfig.xml and change the port that OracleAS Portal is listening on to match that of OracleAS Web Cache. The file is located in:

   (UNIX) ORACLE_HOME/portal/conf]
   (Windows) ORACLE_HOME\portal\conf
   ]
   

3. Run the following command to make Oracle Application Server aware of the change:

   • On UNIX:

     ORACLE_HOME/portal/conf/ptlconfig update ptlconfig -dad portal [-pw PORTAL_schema_password]
     
     

   • On Windows:

     ORACLE_HOME\portal\conf\ptlconfig update ptlconfig -dad portal [-pw PORTAL_schema_password]
     

7.2.3.1 Configuring OracleAS Wireless

To configure OracleAS Wireless, take the following steps:

1. Using the Application Server Control Console, navigate to the Application Server Home page for the instance in which you want to configure OracleAS Wireless.

2. On the Application Server Home page, in the System Components section, click Configure Component.

3. On the Select Component page, select Wireless. Click Continue.

4. On the Login page:

   • User Name: Enter cn=orcladmin, or the distinguished name of a user in the iASAdmins group.

   • Password: Enter the password for the user.

   The SSL Only check box is grayed out because you cannot change this feature in this operation.

5. Click Finish.

7.2.3.2 Post-Configuration Tasks

When the configuration is finished, take the following steps:

1. In the Application Server Control Console Confirmation page, click OK. The Application Server Home page appears.

2. Verify that OC4J_Wireless and Wireless are listed in the System Components section. OC4J_Wireless and Wireless will have a status of Down. Select the check boxes next to OC4J_Wireless and Wireless, and click Start.

3. When the operation completes, verify that OC4J_Wireless and Wireless have a status of Up. Click OC4J_Wireless and verify that the OC4J_Wireless page is displayed. Click Wireless and verify that the Wireless page is displayed.

4. Select the check boxes next to HTTP_Server and Web Cache, and click Restart.

5. Verify that you can access OracleAS Wireless at the following URL:

   http://hostname.domain:port/webtool/login.uix
   
   

   In the URL, hostname.domain is the OracleAS Wireless host and port is the OracleAS Web Cache HTTP listen port number for the instance.

   You can log in as the user orcladmin with the orcladmin password.

   
   

   See Also: Oracle Application Server Wireless Administrator's Guide for more information on configuring OracleAS Wireless

   
   

7.2.4.1 Configuring OracleBI Discoverer

To configure OracleBI Discoverer, take the following steps:

1. Using the Application Server Control Console, navigate to the Application Server Home page for the instance in which you want to configure OracleBI Discoverer.

2. On the Application Server Home page, in the System Components section, click Configure Component.

3. On the Select Component page, select Discoverer. Click Continue.

4. On the Login page, in the Administration Password field, enter the ias_admin password. Click Finish.

7.2.4.2 Post-Configuration Tasks

When the configuration is finished, take the following steps:

1. In the Application Server Control Console Confirmation page, click OK. The Application Server Home page appears.

2. If you did not have an OC4J_BI_Forms instance before, you will have one now. The OC4J_BI_Forms instance will have a status of Down. You will also have a Discoverer instance with a status of Down. Select the check boxes next to OC4J_BI_Forms and Discoverer, and click Start.

3. When the operation completes, verify that OC4J_BI_Forms and Discoverer have a status of Up. Click OC4J_BI_Forms and verify that the OC4J_BI_Forms page is displayed. Click Discoverer and verify that the Discoverer page is displayed.

4. Select the check box next to HTTP_Server, and click Restart.

5. Check that OracleBI Discoverer services are started.

   For all of these URLs, hostname.domain is the host on which Discoverer is installed and port is the Web Cache HTTP listen port number.

   • Discoverer Viewer:

     http://hostname.domain:port/discoverer/viewer
     
     

   • Discoverer Plus:

     http://hostname.domain:port/discoverer/plus
     
     

   • Discoverer Portlet Provider:

     http://hostname.domain:port/discoverer/portletprovider
     

     
     

     See Also: Oracle Business Intelligence Discoverer Configuration Guide for additional steps for configuring OracleBI Discoverer, including installing OracleBI Discoverer workbooks and End User Layer (EUL) into each database that contains data to be analyzed

     
     

7.2.5.1 Configuring OracleAS Forms Services

To configure OracleAS Forms Services, take the following steps:

1. Using the Application Server Control Console, navigate to the Application Server Home page for the instance in which you want to configure OracleAS Forms Services.

2. On the Application Server Home page, in the System Components section, click Configure Component.

3. On the Select Component page, select Forms. Click Continue.

4. On the Login page:

   • User Name: Enter cn=orcladmin, or the distinguished name of a user in the iASAdmins group.

   • Password: Enter the password for the user.

   The SSL Only check box is grayed out because you cannot change this feature in this operation.

5. Click Finish.

7.2.5.2 Post-Configuration Tasks

When the configuration is finished, take the following steps:

1. In the Application Server Control Console Confirmation page, click OK. The Application Server Home page appears.

2. If you did not have an OC4J_BI_Forms instance before, you will have one now. The OC4J_BI_Forms instance will have a status of Down. You will also have a Forms instance with a status of Down. Select the check box next to OC4J_BI_Forms and click Start.

3. When the operation completes, verify that OC4J_BI_Forms and Forms have a status of Up. Click OC4J_BI_Forms and verify that the OC4J_BI_Forms page is displayed. Click Forms and verify that the Forms page is displayed.

4. Verify that you can access OracleAS Forms Services at the following URL:

   http://hostname.domain:port/forms/frmservlet
   
   

   In the URL, hostname.domain is the OracleAS Forms Services host and port is the OracleAS Web Cache HTTP listen port number.

   If you do not have Oracle JInitiator installed on your system, you are prompted to install and run it. Click Yes, then follow the directions in the wizard.

   When the page is displayed, try to access the links on this page to verify that the Forms servlet is available.

5. Refer to the OracleAS Forms Services online help for more information on configuring OracleAS Forms Services. Specifically, note that if you want to manage OracleAS Forms Services runtime processes through the Application Server Control Console, the entry em_mode in the default section of the Forms Web Configuration must be set to the value 1 (the default is 0). Also, to view OracleAS Forms Services trace output, the entry for allow_debug in that section should be set to true.

   
   

   See Also: Oracle Application Server Forms Services Deployment Guide

   
   

7.2.6.1 Things to Know Before You Start

During installation, port numbers were reserved for OracleAS Reports Services. You can find the port numbers in the following file:

(UNIX) ORACLE_HOME/install/portlist.ini
(Windows) ORACLE_HOME\install\portlist.ini

The port numbers are listed as:

Reports Services bridge port = 14011
Reports Services discoveryService port = 14021

These port numbers will be used when you configure OracleAS Reports Services. If you want to use different port numbers, you can change them after you configure OracleAS Reports Services.

7.2.6.2 Configuring OracleAS Reports Services

To configure OracleAS Reports Services, take the following steps:

1. Using the Application Server Control Console, navigate to the Application Server Home page for the instance in which you want to configure OracleAS Reports Services.

2. On the Application Server Home page, in the System Components section, click Configure Component.

3. On the Select Component page, select Reports Server. Click Continue.

4. On the Login page:

   • User Name: Enter cn=orcladmin, or the distinguished name of a user in the iASAdmins group.

   • Password: Enter the password for the user.

   The SSL Only check box is grayed out because you cannot change this feature in this operation.

5. Click Finish.

7.2.6.3 Post-Configuration Tasks

When the configuration is finished, take the following steps:

1. In the Application Server Control Console Confirmation page, click OK. The Application Server Home page appears.

2. If you did not have an OC4J_BI_Forms instance before, you will have one now and it will have a status of Down. You will also have a Reports Server:rep_server instance with a status of Down. Select the check boxes next to OC4J_BI_Forms and Reports Server: rep_server and click Start.

3. When the operation completes, verify that OC4J_BI_Forms and Reports Server: rep_server have a status of Up. Click OC4J_BI_Forms and verify that the OC4J_BI_Forms page is displayed. Click Reports Server: rep_server and verify that the Reports page is displayed.

4. Specify your outgoing mail server.

   1. Edit the following file:

      • On UNIX systems:

        ORACLE_HOME/reports/conf/rep_server_name.conf
        
        

      • On Windows systems:

        ORACLE_HOME\reports\conf\rep_server_name.conf
        
        

   2. Uncomment the pluginParam name="mailServer" element and update it with the outgoing mail server name. For example, change the following line:

      <!--pluginParam name="mailServer">%MAILSERVER_NAME%</pluginParam-->
      
      

      To:

      <pluginParam name="mailServer">smtpserver.myco.com</pluginParam>
      
      

   3. Save and close the file.

5. Verify that OracleAS Reports Services is started, by using the following URL:

   http://hostname.domain:port/reports/rwservlet/getserverinfo
   
   

   In the URL, hostname.domain is the OracleAS Reports Services host and port is the OracleAS Web Cache HTTP listen port number.

   You can log in as orcladmin with the orcladmin password.

   
   

   See Also: Oracle Application Server Reports Services Publishing Reports to the Web for more information on configuring and using Reports

   
   

7.2.8.1 Configuring OracleAS Single Sign-On

To configure OracleAS Single Sign-On, take the following steps:

1. Using the Application Server Control Console, navigate to the Application Server Home page for the Infrastructure instance in which you want to configure OracleAS Single Sign-On.

2. On the Application Server Home page, in the System Components section, click Configure Component.

3. On the Select Component page, select Single Sign-On Server. Click Continue.

4. On the Login page:

   • User Name: Enter cn=orcladmin, or the distinguished name of a user in the iASAdmins group.

   • Password: Enter the password for the user.

   The SSL Only check box is grayed out because you cannot change this feature in this operation.

5. Click Finish.

7.2.8.2 Post-Configuration Tasks

When the configuration is finished, take the following steps:

1. In the Application Server Control Console Confirmation page, click OK. The Application Server Home page appears.

2. If you did not have an OC4J_SECURITY instance before, you will have one now. The OC4J_SECURITY instance will have a status of Down. You will also have a Single Sign-On:orasso instance with a status of Down. Select the check box next to OC4J_SECURITY and click Start.

   Note: You cannot start the Single Sign-On:orasso instance. This feature is started and stopped when you start and stop HTTP_Server and OC4J_SECURITY.

3. When the operation completes, verify that OC4J_SECURITY has a status of Up.

   Note: The Single Sign-On:orasso status may be displayed as Down. This is normal. The status should be updated approximately five minutes after configuration.

4. Select HTTP_Server and click Restart.

5. Verify that you can access OracleAS Single Sign-On at the following URL:

   http://hostname.domain:port/pls/orasso
   
   

   In the URL, hostname.domain is the host on which OracleAS Single Sign-On is installed and port is the Infrastructure HTTP Server port.

   You can log in as orcladmin with the orcladmin password.

   
   

   See Also: Oracle Application Server Single Sign-On Administrator's Guide for more information on configuring OracleAS Single Sign-On

   
   

7.2.9.1 Things to Know Before You Start

When you configure Oracle Delegated Administration Services after installation, you will see the following results:

• The URL for Oracle Delegated Administration Services is set up.

• The appropriate privileges are created.

• Oracle Delegated Administration Services are deployed in the OC4J_SECURITY instance.

7.2.9.2 Configuring mod_osso for Oracle Delegated Administration Services

Before you configure Oracle Delegated Administration Services, you must make sure mod_osso is configured, as follows:

1. Check if mod_osso is configured in the Oracle home where you want to configure Oracle Delegated Administration Services. Examine the following file:

   • On UNIX systems:

     ORACLE_HOME/Apache/Apache/conf/httpd.conf
     
     

     Look for the following line in the file:

     include "ORACLE_HOME/Apache/Apache/conf/mod_osso.conf"
     
     

   • On Windows systems:

     ORACLE_HOME\Apache\Apache\conf\httpd.conf
     
     

     Look for the following line in the file:

     include "ORACLE_HOME\Apache\Apache\conf\mod_osso.conf"
     
     

   ORACLE_HOME refers to the directory where you want to configure Oracle Delegated Administration Services.

   If the line starts with #, then it is commented out and mod_osso is not configured in this installation. Perform step 2 to configure mod_osso.

   If the line is not commented out, mod_osso is already configured. You can proceed and configure Oracle Delegated Administration Services using Application Server Control, as described in Section 7.2.9.3, "Configuring Delegated Administration Service".

2. To configure mod_osso manually, perform these steps:

   1. Set the ORACLE_HOME environment variable to the full path of the directory where you want to configure Oracle Delegated Administration Services.

   2. On UNIX systems, set the LD_LIBRARY_PATH, LD_LIBRARY_PATH_64, LIB_PATH, or SHLIB_PATH environment variables to the proper values, as shown in Table 1-1. The actual environment variables and values that you have to set depend on the type of your UNIX operating system.

   3. On Windows systems, set the PATH environment variable to contain %ORACLE_HOME%\lib.

   4. Run the following command (all on one line). Note: for the -classpath parameter, do not type any space characters after the colon (:) and semicolon (;) characters, as indicated by <no spaces>.

      On UNIX:

      $ORACLE_HOME/jdk/bin/java
      -classpath .:$ORACLE_HOME/sso/lib/ossoreg.jar:<no spaces>
      $ORACLE_HOME/jlib/ojmisc.jar:<no spaces>
      $ORACLE_HOME/jlib/repository.jar:<no spaces>
      $ORACLE_HOME/j2ee/home/jazn.jar:$ORACLE_HOME/jdk/lib/dt.jar:<no spaces>
      $ORACLE_HOME/jdk/lib/tools.jar:$ORACLE_HOME/jlib/infratool.jar
      oracle.ias.configtool.UseInfrastructure i
       -f $ORACLE_HOME/config/infratool_mod_osso.properties
       -h OIDhost -p OIDport -u OIDadminName -w OIDclearTextPassword
       -o ORACLE_HOME -m ASinstanceName
       -infra infraGlobalDBName -mh host -sso true
       -sslp sslPort -sslf false
      
      

      On Windows:

      %ORACLE_HOME%\jdk\bin\java
      -classpath .;%ORACLE_HOME%\sso\lib\ossoreg.jar;<no spaces>
      %ORACLE_HOME%\jlib\ojmisc.jar;<no spaces>
      %ORACLE_HOME%\jlib\repository.jar;<no spaces>
      %ORACLE_HOME%\j2ee\home\jazn.jar;<no spaces>
      %ORACLE_HOME%\jdk\lib\dt.jar;<no spaces>
      %ORACLE_HOME%\jdk\lib\tools.jar;%ORACLE_HOME%\jlib\infratool.jar
      oracle.ias.configtool.UseInfrastructure i
       -f %ORACLE_HOME%\config\infratool_mod_osso.properties
       -h OIDhost -p OIDport -u OIDadminName -w OIDclearTextPassword
       -o ORACLE_HOME -m ASinstanceName
       -infra infraGlobalDBName -mh host -sso true
       -sslp sslPort -sslf false
      
      

      Table 7-3 describes the parameters that require values.

      Table 7-3 Parameters for Configuring mod_osso

      Parameter	DescriptionFoot 1
      -h OIDhost	Specifies the name of the computer where Oracle Internet Directory is running. You can determine this value from the OIDhost parameter in the ORACLE_HOME/config/ias.properties file.
      -p OIDport	Specifies the port number on which Oracle Internet Directory is listening. You can determine this value from the OIDport parameter in the ORACLE_HOME/config/ias.properties file.
      -u OIDadminName	Specifies the login name for Oracle Internet Directory. Use the superuser: cn=orcladmin.
      -w OIDclearTextPassword	Specifies the password for the Oracle Internet Directory user.
      -o ORACLE_HOME	Specifies the full path to the directory where you installed OracleAS Infrastructure 10g.
      -m ASinstanceName	Specifies the name of the OracleAS Infrastructure 10g instance where you want to configure mod_osso. You can determine this value from the IASname parameter in the ORACLE_HOME/config/ias.properties file.
      -infra infraGlobalDBname	Specifies the name of the OracleAS Metadata Repository database. You can determine this value from the InfrastructureDBCommonName parameter in the ORACLE_HOME /config/ias.properties file.
      -mh host	Specifies the full hostname (including the domain name) of the computer where you want to configure Oracle Delegated Administration Services.
      -sslp sslPort	Specifies the SSL port for Oracle Internet Directory. You can determine this value from the OIDsslport parameter in the ORACLE_HOME/config/ias.properties file.

      
      

      ^Footnote 1 Paths are shown in UNIX format; invert the slashes for Windows.

3. If you needed to perform the previous step, restart OC4J and Oracle HTTP Server, using the opmnctl command:

   • On UNIX systems:

     ORACLE_HOME/opmn/bin/opmnctl restartproc ias-component=OC4J
     ORACLE_HOME/opmn/bin/opmnctl restartproc ias-component=HTTP_Server
     
     

   • On Windows systems:

     ORACLE_HOME\opmn\bin\opmnctl restartproc ias-component=OC4J
     ORACLE_HOME\opmn\bin\opmnctl restartproc ias-component=HTTP_Server
     

7.2.9.3 Configuring Delegated Administration Service

To configure Oracle Delegated Administration Services, take the following steps:

1. Using the Application Server Control Console, navigate to the Application Server Home page for the Infrastructure instance in which you want to configure Oracle Delegated Administration Services.

2. On the Application Server Home page, in the System Components section, click Configure Component.

3. On the Select Component page, select Delegated Administration Service. Click Continue.

4. On the Login page:

   • User Name: Enter cn=orcladmin.

   • Password: Enter the password for the user.

   The SSL Only check box is grayed out because you cannot change this feature in this operation.

5. Click Finish.

7.2.9.4 Post-Configuration Tasks

When the configuration is finished, take the following steps:

1. In the Application Server Control Console Confirmation page, click OK. The Application Server Home page appears.

2. If you did not have an OC4J_SECURITY instance before, you will have one now. The OC4J_SECURITY instance will have a status of Down. Select the check box next to OC4J_SECURITY and click Start.

3. Select HTTP_Server and click Restart. Stop and restart all components, using the opmnctl command:

   • On UNIX systems:

     ORACLE_HOME/opmn/bin/opmnctl stopall
     ORACLE_HOME/opmn/bin/opmnctl startall
     
     

   • On Windows systems:

     ORACLE_HOME\opmn\bin\opmnctl stopall
     ORACLE_HOME\opmn\bin\opmnctl startall
     
     

4. Verify that Oracle Delegated Administration Services is started by navigating to the following URL:

   http://hostname.domain:port/oiddas
   
   

   In the URL, hostname.domain is the host on which Oracle Delegated Administration Services is installed and port is the Infrastructure HTTP Server port.

   
   

   See Also: Oracle Internet Directory Administrator's Guide for more information on configuring Oracle Delegated Administration Services