7 Reconfiguring Application Server Instances

7.2.1 Configuring JServ After Installation

It is recommended that you use Oracle Application Server Containers for J2EE (OC4J) for your servlet environment—it is the default configuration for Oracle Application Server. However, you may want or need to use JServ in your Oracle Application Server installation. This section describes how to configure JServ after installation.

Things to Know Before You Start

During installation, Oracle Application Server assigns a port number to JServ. It writes the port number into the JServ configuration files, but leaves the lines commented out. So, even though JServ is not enabled, it does have a port number assigned to it.

You can find the port number by looking in the following file:

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

It is listed as:

Oracle HTTP Server Jserv port = port_number

When you configure JServ, you will edit the configuration files. You can use the port number that was assigned, or choose a different port number. Just make sure to use a unique port number.

Configuring JServ

To configure JServ, you must perform manual steps and configure it in the Application Server Control Console.

1. Perform manual steps to enable JServ.

   At a minimum, you must:

   1. Edit the following file:

      (UNIX) ORACLE_HOME/Apache/Apache/conf/httpd.conf
      (Windows) ORACLE_HOME\Apache\Apache\conf\httpd.conf
      
      

   2. Uncomment the following line (remove #):

      #include "ORACLE_HOME/Apache/Jserv/etc/jserv.conf"
      
      

   3. Save and close the file.

   There are additional directives and options you can manually configure for JServ.

   
   

   See Also: Refer to the mod_jserv section in Oracle HTTP Server Administrator's Guide for more details

   
   

2. Configure JServ in the Application Server Control Console

   This step enables the Application Server Control Console to display JServ as a configured component, and allows you to use the JServ Home Pages.

   1. Use the Application Server Control Console to navigate to the Application Server home page for the instance in which you would like to configure JServ.

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

   3. On the Select Component page, select JServ in the dropdown menu. Click Continue.

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

Post-Configuration Tasks

1. When the configuration is finished, click OK. The Application Server home page will appear.

2. Restart Oracle HTTP Server:

   opmnctl stopproc ias-component=HTTP_Server
   opmnctl startproc ias-component=HTTP_Server
   
   

3. On the Application Server home page, verify that JServ is listed in the System Components section with an up status. It may take a few minutes for the JServ status and metrics to show up on the Application Server Control Console.

4. Verify JServ is working by accessing the JServ demo at the following URL:

   http://hostname.domain:port_number/servlets/IsItWorking
   
   

   Where hostname.domain is the JServ host and port_number is the HTTP port number for the instance (default 7777).

   
   

   See Also: Oracle HTTP Server Administrator's Guide for more information on using JServ

   
   

7.2.2 Configuring Web Cache After Installation

This section describes how to configure Web Cache after installation.

Things to Know Before You Start

During installation, port numbers were reserved for 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

They 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 Web Cache. If you would like to use different port numbers, you can change them after you configure Web Cache.

Configuring Web Cache

1. Use the Application Server Control Console to navigate to the Application Server home page for the instance in which you would like to configure 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 in the dropdown menu. Click Continue.

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

Post-Configuration Tasks

1. When the configuration is finished, click OK. The Application Server home page will appear.

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

3. Verify that Web Cache shows an up status. Click the "Web Cache" instance and verify that the Web Cache Home Page is displayed.

4. On the Web Cache Home Page, in the Administration, click Web Cache Administration.

5. You can log in to the Web Cache Manager as either the ias_admin or administrator user. The password for both users is the ias_admin password you supplied during installation. If you have changed the ias_admin password since installation, you must still supply the original ias_admin password.

   
   

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

   
   

7.2.3 Configuring Portal After Installation

This section describes how to configure Portal after installation.

Configuring Portal

1. Use the Application Server Control Console to navigate to the Application Server home page for the instance in which you would like to configure Portal.

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

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

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

Post-Configuration Tasks

1. When the configuration is finished, click OK. The Application Server home page will appear.

2. Verify that OC4J_Portal and Portal:portal are listed in the System Components section. OC4J_Portal will have a down status and Portal:portal will have no status. Select the checkbox next to OC4J_Portal and click Start.

3. Verify that OC4J_Portal and Portal:portal have an up status. Click the OC4J_Portal instance and verify that the OC4J_Portal Page is displayed. Click the Portal:portal instance and verify that the Portal page is displayed.

4. If you perform this step, Portal is going write configuration entries into the Metadata Repository. This is fine if this is the first instance of Portal to use the Metadata Repository. However, if you already have Portal instances using the Metadata Repository, you should not perform this step, because you will overwrite the existing Portal configuration entries in the Metadata Repository.

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

   (UNIX) ORACLE_HOME/portal/conf/ptlconfig -dad portal
   (Windows) ORACLE_HOME\portal\conf\ptlconfig -dad portal
   
   

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

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

   Where hostname.domain is the Portal host and port is the Web Cache HTTP port number for the instance (default 7777).

   You can log in to Portal as portal. If this is the first instance of Portal to use the Metadata Repository, then the password is portal10g. Otherwise, the password is the original ias_admin password of the first Portal instance associated to this Metadata Repository.

   
   

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

   
   

7.2.4 Configuring Wireless After Installation

This section describes how to configure Wireless after installation.

Configuring Wireless

1. Use the Application Server Control Console to navigate to the Application Server home page for the instance in which you would like to configure Wireless.

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

3. On the Select Component page, select Wireless in the dropdown menu. 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 indicates if Wireless is enabled to access Oracle Internet Directory in SSL-mode only. It is grayed out because you cannot change this feature in this operation.

   Click Finish.

Post-Configuration Tasks

1. When the configuration is finished, click OK. The Application Server home page will appear.

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

3. Verify that OC4J_Wireless and Wireless have an up status. Click the OC4J_Wireless instance and verify that the OC4J_Wireless Page is displayed. Click the Wireless instance and verify that the Wireless page is displayed.

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

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

   Where hostname.domain is the Wireless host and port is the Web Cache HTTP port number for the instance (default 7777).

   You can log in as orcladmin with the orcladmin password.

   
   

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

   
   

7.2.5 Configuring Discoverer After Installation

This section describes how to configure Discoverer after installation.

Things to Know Before You Start

During installation, a port number was reserved for Discoverer. You can find the port number in the following file:

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

It is listed as:

Discoverer OSAgent Port = port_number

This port number will be used when you configure Discoverer. You cannot change the port number.

Configuring Discoverer

1. Use the Application Server Control Console to navigate to the Application Server home page for the instance in which you would like to configure Discoverer.

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

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

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

Post-Configuration Tasks

1. When the configuration is finished, click OK. The Application Server home page will appear.

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 down status. You will also have a Discoverer instance with a down status. Select the checkboxes next to OC4J_BI_forms and Discoverer, and click Start.

3. Verify that OC4J_BI_Forms and Discoverer have an up status. Click the OC4J_BI_Forms instance and verify that the OC4J_BI_Forms page is displayed. Click the Discoverer instance and verify that the Discoverer page is displayed.

4. Check that Discoverer services are up.

   For all of these URLs, hostname.domeain is the host Discoverer is on and port is the Web Cache HTTP port number (default 7777).

   1. Discoverer Viewer:

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

   2. Discoverer Plus:

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

   3. Discoverer Portlet Provider:

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

      
      

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

      
      

7.2.6 Configuring Forms After Installation

This section describes how to configure Forms after installation.

Configuring Forms

1. Use the Application Server Control Console to navigate to the Application Server home page for the instance in which you would like to configure Forms.

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

3. On the Select Component page, select Forms in the dropdown menu. 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 indicates if Forms is enabled to access Oracle Internet Directory in SSL-mode only. It is grayed out because you cannot change this feature in this operation.

   Click Finish.

Post-Configuration Tasks

1. When the configuration is finished, click OK. The Application Server home page will appear.

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 down status. You will also have a Forms instance with a down status. Select the checkbox next to OC4J_BI_Forms and click Start.

3. Verify that OC4J_BI_Forms and Forms have an up status. Click the OC4J_BI_Forms instance and verify that the OC4J_BI_Forms page is displayed. Click the Forms instance and verify that the Forms page is displayed.

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

   http://hostname.domain:port/forms90/f90servlet/admin
   
   

   Where hostname.domain is the Forms host and port is the Web Cache HTTP port number (default 7777).

   Try to access the links on this page to verify that the Forms servlet is available.

5. Refer to the Forms online help for more information on configuring Forms. Specifically, note that if you would like to manage Forms 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, in order to view Forms trace output, the entry for "allow_debug" in that section should be set to "true".

   
   

   See Also: Oracle Application Server Forms Services Deployment Guide for more information

   
   

7.2.7 Configuring Reports After Installation

This section describes how to configure Reports after installation.

Things to Know Before You Start

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

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

They are listed as:

Reports Services SQL*Net port = port_number
Reports Services Visigenics CORBA port = port_number

These port numbers will be used when you configure Reports. If you would like to use a different SQL*Net port number, you can change it after you configure Reports. You cannot change the Visigenics CORBA port number.

Configuring Reports

1. Use the Application Server Control Console to navigate to the Application Server home page for the instance in which you would like to configure Reports.

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

3. On the Select Component page, select Reports Server in the dropdown menu. 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 indicates if Reports is enabled to access Oracle Internet Directory in SSL-mode only. It is grayed out because you cannot change this feature in this operation.

   Click Finish.

Post-Configuration Tasks

1. When the configuration is finished, click OK. The Application Server home page will appear.

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 down status. You will also have a Reports Server:rep_server instance with a down status. Select the checkboxes next to OC4J_BI_forms and Reports Server: rep_server and click Start.

3. Verify that OC4J_BI_Forms and Reports Server: rep_server have an up status. Click the OC4J_BI_Forms instance and verify that the OC4J_BI_Forms page is displayed. Click the Reports Server: rep_server instance and verify that the Reports page is displayed.

4. Specify your outgoing mail server.

   1. Edit the following file:

      (UNIX) ORACLE_HOME/reports/conf/rep_server.conf
      (Windows) ORACLE_HOME\reports\conf\rep_server.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 Reports is running with the following URL:

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

   Where hostname.domain is the Reports host and port is the Web Cache HTTP 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 Configuring Single Sign-On (SSO) After Installation

This section describes how to configure SSO after installation.

Configuring SSO

1. Use the Application Server Control Console to navigate to the Application Server home page for the Infrastructure instance in which you would like to configure SSO.

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 in the dropdown menu. 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 indicates if SSO is enabled to access Oracle Internet Directory in SSL-mode only. It is grayed out because you cannot change this feature in this operation.

   Click Finish.

Post-Configuration Tasks

1. When the configuration is finished, click OK. The Application Server home page will appear.

2. If you did not have an OC4J_SECURITY instance before, you will have one now. The OC4J_SECURITY instance will have a down status. You will also have a Single Sign-On:orasso instance with a down status. Select the checkbox next to OC4J_SECURITY nd 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. Verify that OC4J_SECURITY has an up status.

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

4. Verify that you can access SSO at the following URL:

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

   Where hostname.domain is the host SSO is installed on and port is the Infrastructure HTTP Server port (default 7777).

   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 and using SSO

   
   

7.2.9 Configuring Delegated Administration Service (DAS) After Installation

This section describes how to configure DAS after installation.

Things to Know Before You Start

When you configure DAS after installation using the Application Server Control Console, the following happens:

• The URL for DAS is set up

• The appropriate privileges are created

• DAS services are deployed in the OC4J_SECURITY instance

Configuring DAS

1. Use the Application Server Control Console to navigate to the Application Server home page for the Infrastructure instance in which you would like to configure DAS.

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 in the dropdown menu. Click Continue.

4. On the Login page:

   • User Name: Enter cn=orcladmin

   • Password: Enter the password for the user.

   • The SSL Only check box indicates if DAS is enabled to access Oracle Internet Directory in SSL-mode only. It is grayed out because you cannot change this feature in this operation.

   Click Finish.

Post-Configuration Tasks

1. When the configuration is finished, click OK. The Application Server home page will appear.

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

3. Verify that DAS is running by navigating to the following URL:

   http://hostname.domain:port/oiddas
   
   

   Where hostname.domain is the host DAS is installed on and port is the Infrastructure HTTP Server port (default 7777).

   
   

   See Also: Oracle Internet Directory Administrator's Guide for more information on configuring and using DAS

   
   

7.2.10 Configuring Directory Integration and Provisioning (DIP) After Installation

This section describes how to configure DIP after installation.

Configuring DIP

1. Use the Application Server Control Console to navigate to the Application Server home page for the Infrastructure instance in which you would like to configure DIP.

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

3. On the Select Component page, select Directory Integration and Provisioning in the dropdown menu. Click Continue.

4. On the Login page:

   • User Name: Enter cn=orcladmin

   • Password: Enter the password for the user.

   • The SSL Only check box indicates if DIP is enabled to access Oracle Internet Directory in SSL-mode only. It is grayed out because you cannot change this feature in this operation.

   Click Finish.

5. When the configuration is finished, click OK. The Application Server home page will appear.

   
   

   See Also: Oracle Internet Directory Administrator's Guide for more information on configuring and using DIP

   
   

7.5.1 Using Identity Management

This section describes how to configure a J2EE and Web Cache instance to use Identity Management, as shown in Figure 7-3.

Figure 7-3 J2EE and Web Cache Using Identity Management

Description of the illustration assoc2.gif

Before You Start

• Make sure the Identity Management instance is up.

• Make sure you know the Oracle Internet Directory host and port numbers.

• Make sure you know the password for cn=orcladmin, or another user that is a member of the iASAdmins group.

Procedure

1. Using the Application Server Control Console, navigate to the Application Server home page for the J2EE and Web Cache instance.

2. Click Infrastructure.

3. On the Infrastructure page, in the Identity Management section, click Configure.

4. On the Internet Directory page:

   • Host: Enter the fully-qualified name of the OID host.

   • Port: If you do not check "Use only SSL connections with Internet Directory", enter the non-SSL OID port number. Otherwise, enter the SSL OID port number.

   • Use only SSL connections with Internet Directory: By default, some middle-tier components connect to OID using non-SSL connections. If you want components to only connect to OID using SSL, check this box and make sure you entered the SSL OID port number in the Port field.

   Click Next.

5. 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.

   Click Next.

6. On the Validation page, you will receive informational messages regarding the validation of this operation. If you receive any error message, follow the instructions for investigating them. Otherwise, if the operation is valid, click Finish.

7. When the operation is finished, you must restart the components in the J2EE and Web Cache instance.

   1. Click Home to navigate back to the J2EE and Web Cache Home Page.

   2. Click Start All.

Your J2EE and Web Cache instance is now configured to use Identity Management services.

7.5.2 Using an OracleAS Metadata Repository with Identity Management

This section describes how to configure a J2EE and Web Cache instance to use an OracleAS Metadata Repository for OracleAS Clusters. This procedure requires that the J2EE and Web Cache instance is already using Identity Management, and the OracleAS Metadata Repository is registered with that Identity Management, as shown in Figure 7-4.

Figure 7-4 J2EE and Web Cache Using an OracleAS Metadata Repository (with Identity Management)

Description of the illustration assoc3.gif

Before You Start

• Make sure the OracleAS Metadata Repository is up

• Make sure the Identity Management instance is up

• Make sure you know the password for cn=orcladmin, or another user that is a member of the iASAdmins group

Procedure

1. Using the Application Server Control Console, navigate to the Application Server home page for the J2EE and Web Cache instance.

2. Click Infrastructure.

3. On the Infrastructure page, in the OracleAS Clusters Managed Using Database Repository section, click Configure.

4. On the Source page, choose OracleAS Metadata Repository.

   Click Next.

5. On the Internet Directory page:

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

   • Password: Enter the password for the user.

   You will notice that "Use Only SSL connections with Internet Directory" is grayed out. This is because you cannot specify this option in this operation.

   Click Next.

6. On the Location page, select the OracleAS Metadata Repository you would like to use from the Repository dropdown list. The Default Schema is always DCM.

   Click Next.

7. On the Validation page, you will receive informational messages regarding the validation of this operation. If you receive any error message, follow the instructions for investigating them. Otherwise, if the repository you specified is valid, click Finish.

8. When the operation is finished, you must restart the components in the J2EE and Web Cache instance.

   1. Click Home to navigate back to the Application Server home page.

   2. Click Start All.

Your J2EE and Web Cache instance is now in the OracleAS Metadata Repository's farm and can join an OracleAS Cluster in that farm.

7.5.3 Using an Existing Database

This section describes how to configure a J2EE and Web Cache instance to use an Existing Database (a Metadata Repository that is not registered with OID) for OracleAS Clusters. The J2EE and Web Cache may use Identity Management, as shown in Figure 7-5, or it may not, as shown in Figure 7-6.

Figure 7-5 J2EE and Web Cache Using an Existing Database (with Identity Management)

Description of the illustration assoc4.gif

Figure 7-6 J2EE and Web Cache Using an Existing Database (without Identity Management)

Description of the illustration assoc1.gif

Before You Start

• Make sure the Existing Database is up

• Make sure you know the Net listener port and the service name for the Existing Database. These are listed in the entry for the Existing Database in the following file:

  (UNIX) EXISTING_DB_ORACLE_HOME/network/admin/tnsnames.ora
  (Windows) EXISTING_DB_ORACLE_HOME\network\admin\tnsnames.ora
  
  

• Make sure the DCM schema in the database is unlocked and that you know the password.

  If you have just installed the Existing Database and have not used the DCM schema yet, the DCM schema is locked and the password is expired. You must unlock it and set a new password as follows (be sure to set the ORACLE_HOME and ORACLE_SID environment variables first):

  sqlplus "sys/SYS_PASSWORD as sysdba"
  SQL> alter user dcm identified by NEW_PASSWORD account unlock;
  

Procedure

1. Using the Application Server Control Console, navigate to the Application Server home page for the J2EE and Web Cache instance.

2. Click Infrastructure.

3. On the Infrastructure page, in the OracleAS Clusters Managed Using Database Repository section, click Configure.

4. On the Source page, choose Existing Database. (Note: If the OracleAS Metadata Repository option is grayed out, it is because the J2EE and Web Cache instance is not using Identity Management).

   Click Next.

5. On the Login page, fill in the following fields:

   • User Name: DCM

   • Password: Enter the DCM schema password

   • Hostname and Port: Enter the hostname and Net listener port for the Existing Database. For example: myhost:1521.

   • Service Name: Enter the service name for the Existing Database. For example, asdb.myco.com.

   Click Next.

6. On the Validation page, you will receive informational messages regarding the validation of this operation. If you receive any error message, follow the instructions for investigating them. Otherwise, if the operation is valid, click Finish.

7. When the operation is finished, you must restart the components in the J2EE and Web Cache instance.

   1. Click Home to navigate back to the Application Server home page.

   2. Click Start All.

Your J2EE and Web Cache instance is now in the Existing Database's farm and can join an OracleAS Cluster in that farm.

7.5.4 Using an OracleAS Metadata Repository without Identity Management

This section describes how to configure a J2EE and Web Cache instance to use an OracleAS Metadata Repository for OracleAS Clusters. This procedure requires that the J2EE and Web Cache instance is not using Identity Management, as shown in Figure 7-7.

Figure 7-7 J2EE and Web Cache Using an OracleAS Metadata Repository (without Identity Management)

Description of the illustration assoc5.gif

Before You Start

• Make sure the OracleAS Metadata Repository is up

• Make sure you know the DCM schema password. If you do not know the password, you can obtain it from Oracle Internet Directory:

  ldapsearch -h oid_host -p oid_port -D cn=orcladmin -w orcladmin_password -b "orclresourcename=DCM, orclreferencename=global_db_name, cn=ias infrastructure databases, cn=ias, cn=products, cn=oraclecontext" -s base "objectclass=*" orclpasswordattribute
  
  

  oid_host is the hostname of the Oracle Internet Directory the OracleAS Metadata Repository is registered with.

  oid_port is the non-SSL Oracle Internet Directory port number.

  global_db_name is the entry name for the OracleAS Metadata Repository in ORACLE_HOME/network/admin/tnsnames.ora. For example, asdb.myco.com.

• Make sure the Identity Management instance that the OracleAS Metadata Repository is registered with is up

• Make sure you know the password for cn=orcladmin, or another user that is a member of the iASAdmins group

Procedure

1. Using the Application Server Control Console, navigate to the Application Server home page for the J2EE and Web Cache instance.

2. Click Infrastructure.

3. On the Infrastructure page, in the OracleAS Clusters Managed Using Database Repository section, click Configure.

4. On the Source page, choose Existing Database. (Note: The OracleAS Metadata Repository option is grayed out because the J2EE and Web Cache instance is not using Identity Management).

   Click Next.

5. On the Login page, fill in the following fields:

   • User Name: DCM

   • Password: Enter the DCM schema password

   • Hostname and Port: Enter the hostname and Net listener port for the Existing Database. For example: myhost:1521.

   • Service Name: Enter the service name for the Metadata Repository. For example, asdb.myco.com.

   Click Next.

6. On the Validation page, you will receive informational messages regarding the validation of this operation. If you receive any error message, follow the instructions for investigating them. Otherwise, if the operation is valid, click Finish.

7. When the operation is finished, you must restart the components in the J2EE and Web Cache instance.

   1. Click Home to navigate back to the Application Server home page.

   2. Click Start All.

Your J2EE and Web Cache instance is now in the OracleAS Metadata Repository's farm and can join an OracleAS Cluster in that farm.