7
Component Configuration Dependencies

If you change a configuration value for a component, for example, the port number for Web Cache or the host for Oracle Internet Directory, your change may affect other components. You may need to update parameters in other components to ensure that all the components still function.

Each section in this chapter describes a component and its parameters that can affect other components.

J2EE and Web Cache install type:

• Oracle HTTP Server

• Web Cache

• OPMN

Portal and Wireless install type:

• Portal

• Web Providers (for Portals)

• Provider Groups (for Portals)

• Wireless

Infrastructure

• Oracle9iAS Single Sign-On

• Oracle Internet Directory

• Metadata Repository

Oracle HTTP Server

Parameters for Oracle HTTP Server are defined in .conf files in the ORACLE_HOME/Apache area. For example:

• ORACLE_HOME/Apache/Apache/conf/httpd.conf

• Module configuration files, such as:
  • ORACLE_HOME/Apache/Apache/conf/mod_oc4j.conf

  • ORACLE_HOME/Apache/modplsql/conf/dads.conf

  • ORACLE_HOME/Apache/modplsql/conf/plsql.conf

  • ORACLE_HOME/Apache/oradav/conf/moddav.conf

    Note: You need to use Oracle Enterprise Manager Web site to edit the configuration files. If you edit them manually, you need to run dcmctl with the updateConfig parameter so that the updated values are copied into the DCM repository. See "About Manually Editing HTTP Server and OC4J Configuration Files" for details.

For detailed information on Oracle HTTP Server and its parameters, see the Oracle HTTP Server Administration Guide.

Table 7-1 Changes to Oracle HTTP Server  

If you change this:	You affect these components:
Listener port number (Port or Listen directive in httpd.conf) or Host (ServerName directive in httpd.conf) or Protocol (HTTP or HTTPS)	Oracle9iAS Web Cache: Update the port number in the Application Web Servers section under the General Configuration section of the Web Cache Home Page. Restart Web Cache. Oracle Internet Directory: Change the orcldasurlbase attribute in the "cn=OperationURLs, cn=DAS, cn=Products, cn=OracleContext" entry to reflect the new port number in the URL. The value of the attribute is the Oracle HTTP Server's URL (for example, http://mymachine.oracle.com:7777/). You can make the change using Oracle Internet Directory Manager (see the Oracle Internet Directory Administrator's Guide for details). (continued in next row)
(continued from previous row) Listener port number (Port or Listen directive in httpd.conf) or Host (ServerName directive in httpd.conf) or Protocol (HTTP or HTTPS)	Oracle9iAS Single Sign-On: If you change the host, port, or protocol for Oracle HTTP Server, you need to update these values for Oracle9iAS Single Sign-On. When you make these changes in Single Sign-On, you affect the partner applications (Portal, Wireless, and mod_osso) in Single Sign-On. You then have to re-register the partner applications with Single Sign-On using the new host, port, or protocol. Update the hostname, port, or protocol data in the Oracle9iAS Single Sign-On schema on the Infrastructure machine. You do this by running the script: (UNIX) ORACLE_HOME/sso/bin/ssocfg.sh (Windows) ORACLE_HOME\sso\bin\ssocfg.bat on the Infrastructure machine to update tables in the Oracle9iAS Single Sign-On schema with the new data. The script has the following syntax: ssocfg.{sh,bat} protocol host port Before running the command: (UNIX and Windows) You need to set ORACLE_HOME and ORACLE_SID. (UNIX) You need to include $ORACLE_HOME/lib in the LD_LIBRARY_PATH environment variable. (Windows) You need to include %ORACLE_HOME%\lib and %ORACLE_HOME%\bin in the PATH environment variable. For details on the script, see Chapter 2, "Administering Oracle Single Sign-On," of the Oracle9iAS Single Sign-On Administrator's Guide. Look in the "Enabling the Single Sign-On Server for SSL" section. Re-register Oracle9iAS Single Sign-On partner applications (Portal, Wireless, mod_osso) by running their registration tools. The tool varies for each partner application: For Portal, the registration tool is ptlasst.csh for UNIX, ptlasst.cmd for Windows. For Wireless, the registration tool is reRegisterSSO.sh for UNIX, reRegisterSSO.bat for Windows. For mod_osso, the registration tool is packaged in ossoreg.jar. See the section "Oracle9iAS Single Sign-On" for details. (continued in next row)
(continued from previous row) Listener port number (Port or Listen directive in httpd.conf) or Host (ServerName directive in httpd.conf) or Protocol (HTTP or HTTPS)	Oracle9iAS Single Sign-On (continued): Remove the old partner application using the Administer Partner Applications page. Click the "x" in the Delete column to delete the application. You need to delete the application because when you re-register a partner application, the registration tool creates a new entry for the partner application instead of updating the existing application. You can determine which application is the older one by looking at the application ID (click Edit to view details for the application -- applications with low IDs were created first). You can also look at the URLs used by the application. If an application uses an incorrect host, port, or protocol for its URLs, you should delete the application. Modify the HTTPMachine property for the Oracle9iAS Single Sign-On target in the file ORACLE_HOME/sysman/emd/targets.xml to match the values used by Oracle HTTP Server. You do not need to modify the HTTPPort and HTTPProtocol properties. If the port changes, the code detects the new port number and updates the HTTPPort property for the Oracle9iAS Single Sign-On target in the targets.xml file. If the name of the machine running the metadata repository database changes, you need to update the ssoServerMachineName property for the Oracle9iAS Single Sign-On target in the file ORACLE_HOME/sysman/emd/targets.xml. Note that if you have multiple repository database instances, Oracle9iAS Single Sign-On uses only one of the instances. You need to update the ssoServerMachineName property to point to the machine that hosts that instance. Oracle9iAS Wireless: In the Wireless site configuration section of Oracle Enterprise Manager Web site, update the URL to reflect the new host and port settings. Re-register the Wireless partner application. See the section "Oracle9iAS Single Sign-On" for details. (continued in next row)
(continued from previous row) Listener port number (Port or Listen directive in httpd.conf) or Host (ServerName directive in httpd.conf) or Protocol (HTTP or HTTPS)	Oracle9iAS Portal: Modify the HTTPPort property for the Portal target in the file ORACLE_HOME/sysman/emd/targets.xml. Modify the HTTPPort property for the Oracle HTTP Server target in the file ORACLE_HOME/sysman/emd/targets.xml. To create a new association of Portal with the Oracle9iAS Single Sign-On server, with the modified port, run the script: (UNIX) ORACLE_HOME/assistants/opca/ptlasst.csh (Windows) ORACLE_HOME\assistants\opca\ptlasst.cmd If Web Cache is used, run the script in midtier mode (that is, -mode MIDTIER). If Web Cache is not used, run the script in SSOPARTNERCONFIG mode (that is, -mode SSOPARTNERCONFIG). For details on ptlasst, see the Oracle9iAS Portal Configuration Guide. mod_osso: Re-register the mod_osso partner application with Single Sign-On. See the section "Oracle9iAS Single Sign-On" for details. Oracle Enterprise Manager: Create a virtual host with the original hostname. You can do this by adding the following lines to httpd.conf: NameVirtualHost * <VirtualHost *> ServerName original_hostname DocumentRoot /path_to_default_document_root </VirtualHost> Oracle9iAS Reports Services: Update your reports links. Oracle9iAS Discoverer: If the hostname or port for the HTTP Server is changed, then it affects the Oracle9iAS Discoverer Portlet Provider. You should update the registration of the Discoverer Portlet Provider with Oracle Portal. For details, see the Oracle9iAS Discoverer Configuration Guide. (continued in next row)
(continued from previous row) Listener port number (Port or Listen directive in httpd.conf) or Host (ServerName directive in httpd.conf) or Protocol (HTTP or HTTPS)	OPMN: No changes required. JServ: No changes required.
Log directory (CustomLog directive in httpd.conf)	Oracle9iAS Clickstream Intelligence: Update the logFileLoc property in agent.xml.
Port for OC4J (Specified in the Oc4jMount directive where the destination is ajp13://host:port. The directive is typically found in mod_oc4j.conf.) Note: Changing this directive is not recommended.	Oracle9iAS Containers for J2EE: The host and port used for the Oc4jMount directive must match the AJP host and port for the OC4J being routed to. The OC4J configuration is specified in the file xxx-web-site.xml (for example, http-web-site.xml).
Any	mod_oradav: If you make any configuration changes in Oracle HTTP Server, you should not have to make any changes in moddav.conf because mod_oradav uses environment variables that are also used for OCI clients (LD_LIBRARY_PATH, ORACLE_HOME, NLS_LANG, TNS_ADMIN, etc).

Web Cache

You manage Web Cache using Oracle Web Cache Manager, which is a Web-based administration tool. You can use this tool to change the various Web Cache port numbers and passwords. See the Oracle9iAS Web Cache Administration and Deployment Guide for a full description of the tool.

Table 7-2 Changes to Web Cache  

If you change this:	You affect these components:
Administration port	Oracle9iAS Portal: Run the script: (UNIX) ORACLE_HOME/assistants/opca/ptlasst.csh (Windows) ORACLE_HOME\assistants\opca\ptlasst.cmd in midtier mode (that is, -mode MIDTIER) and specify the new administration port value in the -cport_a parameter. For details on ptlasst, see the Oracle9iAS Portal Configuration Guide.
Listener port or machine running Web Cache	Oracle9iAS Wireless: In the Wireless site configuration section of Oracle Enterprise Manager Web site, update the URL to reflect the new host and port settings. Oracle9iAS Reports Services: Manually update your reports links. Oracle9iAS Portal: Run the script: (UNIX) ORACLE_HOME/assistants/opca/ptlasst.csh (Windows) ORACLE_HOME\assistants\opca\ptlasst.cmd in midtier mode (that is, -mode MIDTIER) and specify the new port and hostname values using the appropriate parameters: - new listener port in the -port parameter - new listener hostname in the -host parameter - new cache hostname in the -chost parameter For details on ptlasst, see the Oracle9iAS Portal Configuration Guide. Update the Port or ServerName directive in the file httpd.conf for Oracle HTTP Server, as appropriate. Restart Oracle HTTP Server. Portal (JPDK): Modify the configuration file for the JPDK invalidation API.
Invalidation port	Oracle9iAS Wireless: In the Wireless site configuration section of Oracle Enterprise Manager Web site, update the Web Cache Invalidation Port field to reflect the new value. Oracle9iAS Portal: Run the script: (UNIX) ORACLE_HOME/assistants/opca/ptlasst.csh (Windows) ORACLE_HOME\assistants\opca\ptlasst.cmd in midtier mode (that is, -mode MIDTIER) and specify the new invalidation port value in the -cport_i parameter. For details on ptlasst, see the Oracle9iAS Portal Configuration Guide. Portal (JPDK): Modify the configuration file for the JPDK invalidation API.
Invalidation password	Oracle9iAS Wireless: In the Wireless site configuration section of Oracle Enterprise Manager Web site, update the Web Cache Invalidation Password field to reflect the new value. Oracle9iAS Portal: Run the script: (UNIX) ORACLE_HOME/assistants/opca/ptlasst.csh (Windows) ORACLE_HOME\assistants\opca\ptlasst.cmd in midtier mode (that is, -mode MIDTIER) and specify the new invalidation password in the -wc_i_pwd parameter. For details on ptlasst, see the Oracle9iAS Portal Configuration Guide.
Web Cache timeout (OSRECV_TIMEOUT parameter in webcache.xml)	Oracle9iAS Wireless: In the Wireless site configuration section of Oracle Enterprise Manager Web site, update the Web Cache Timeout field to reflect the new value. Oracle9iAS Portal: Update the PPE (Portal Parallel Page Engine) minTimeout parameter in the file ORACLE_HOME/j2ee/OC4J_Portal/applications/portal/portal/WEB-INF/web.xml. Note that the Web Cache timeout must be longer than the PPE timeout.

OPMN

Oracle Process Management Notification (OPMN) keeps track of Oracle9iAS processes. It uses the configuration file ORACLE_HOME/opmn/conf/opmn.xml.

Table 7-3 Changes to OPMN   

If you change this:	You affect these components:
instanceName attribute of the oc4j element in the opmn.xml	Oracle HTTP Server (mod_oc4j): You need to update the OC4J instance name in the Oc4jMount directive in mod_oc4j.conf.

Portal

The Portal feature in Oracle9iAS enables you to aggregate pages from different data sources and display them on a single page. Users can customize the pages that they want to see on their page. For details on Portals, see the Oracle9iAS Portal Configuration Guide.

Table 7-4 Changes to Portal  

If you change this:	You affect these components:
Mobile gateway URL	Oracle9iAS Wireless: Run the script: (UNIX) ORACLE_HOME/wireless/sample/portalRegistrar.sh (Windows) ORACLE_HOME\wireless\sample\portalRegistrar.bat to reregister the mobile gateway parameter with Portal. Syntax: portalregistrar.{sh,bat} <wireless_admin_user> <new_wireless_portal_URL> Example: portalregistrar.sh orcladmin http://new.myCompany.com/ptg/rm
Portal database schema password (using Portal UI or SQL*Plus)	HTTP Server (mod_plsql): Use Oracle Enterprise Manager Web site to change the Database Password field for the DAD that accesses the Portal schema to match the new password. This changes the PlsqlDatabasePassword parameter in the ORACLE_HOME/Apache/modplsql/conf/dad.conf file. Restart HTTP Server. Oracle Internet Directory and DIP (Directory Integration Profile) Synchronization: Run the script: (UNIX) ORACLE_HOME/bin/oidprovtool (Windows) ORACLE_HOME\bin\oidprovtool.bat to modify (or delete or recreate) the Portal's provisioning profile to update the password that is maintained in Oracle Internet Directory so the DIP agent can connect to the portal to send the notifications.
Moving Portal to a different database	Oracle Enterprise Manager: Add the new database target to the ORACLE_HOME/sysman/emd/targets.xml file and update iasDatabaseTargetName in targets.xml in the portal target instance to point to the new database.
Portal port, DAD name, URL of Home Page	Oracle9iAS Wireless and Oracle9iAS Single Sign-On: Run the script: (UNIX) ORACLE_HOME/assistants/opca/ptlasst.csh (Windows) ORACLE_HOME\assistants\opca\ptlasst.cmd to update Oracle9iAS Single Sign-On. This also updates the Portal repository with the host, port, and DAD information. For details on ptlasst, see the Oracle9iAS Portal Configuration Guide. Use the Wireless administration tool to identify the service that represents Portal, and update the URL associated with the service.

Web Providers (for Portals)

A Web provider owns portlets that can be placed on portal pages. Web provider details are maintained using the Add/Edit Provider screens in the portal. These pages are used to maintain both Web Providers and Database Providers.

Table 7-5 Changes to Portal Web Service Provider  

If you change this:	You affect these components:
Web provider URL or port	Oracle9iAS Portal: Update provider registration information with new URL or port.
Web provider service ID	Oracle9iAS Portal: Update provider registration information with new service ID.
Web provider mount point	Oracle9iAS Portal: Update provider registration information with new mount point.
Adding Web Cache in front of Web provider	Oracle9iAS Portal: Do one of the following: Configure Web Cache so it has the hostname/port of Web provider listener and assign a new host/port to Web provider. OR Update provider registration information with the new URL, then create a Web Cache configuration file and associate the file with OC4J so that the Web provider can send invalidation requests to Web Cache. The location of the configuration file is a Java system parameter. See the Oracle9iAS Web Cache Administration and Deployment Guide for details.
Removing Web Cache from Web provider	Oracle9iAS Portal: Do one of the following: Configure the Web provider listener to point to the host and port of the origin HTTP Server. OR Update the provider registration information with the new URL.
Moving Web Cache to a different host or port	Oracle9iAS Portal: Update the Web Cache configuration file with the new host or port.
Changing the service name or location of the database that stores provider preference	Oracle9iAS Containers for J2EE: Update the OC4J data-sources.xml file with the new database location or service name.
Changing domain of portal or Web provider	Oracle9iAS Portal: If you have applications that rely on "same cookie domain" (where portal delegates Web provider cookie management to the browser), you have to change the scope of the Web provider cookie so that both portal and Web provider listeners fall within the domain or change the Web provider to create "authenticated links" for any deep links from portlets to external or partner applications. Partner applications would have to be treated as external applications.
Moving provider UI servlet	Oracle9iAS Portal: Update location of the provider UI in General Settings.

Provider Groups (for Portals)

A provider group is a grouping of Portal Web providers. A provider group lets you publish information about many providers in a simple way. The provider group may be published from a portal, or it could be established independent of any portal. A portal administrator can register a provider group with a portal and view the contents (that is, the Web providers) of the group. The portal administrator can then selectively register one or more providers from the provider group with the portal and then use that provider as if it had been registered normally.

Table 7-6 Changes to Web Service Provider Groups  

If you change this:	You affect these components:
Host, port, or mount point of SOAP engine Service ID of provider groups service	Oracle9iAS Portal: Update provider group registration information.
Location of group XML file	Oracle9iAS SOAP Service: Update service descriptors for the SOAP service.
Provider group name in progrp.xml	Oracle9iAS Portal: Update provider group registration information.

Wireless

You manage Oracle9iAS Wireless using Oracle Enterprise Manager Web site. The management pages enable you to perform tasks such as starting and stopping the wireless server, setting the number of connections in the connection pool, setting up logging, and configuring devices.

See the Oracle9iAS Wireless Getting Started and System Guide for details.

Table 7-7 Changes to Wireless  

If you change this:	You affect these components:
Add a new service to refer to portal	Oracle9iAS Portal: Go to the Mobile tab of Global Settings and update the registered URL.

Oracle9iAS Single Sign-On

Oracle9iAS Single Sign-On enables users to sign in only once for all applications for which they are authorized to access. Oracle9iAS Single Sign-On is commonly used with portals, which can display multiple applications on a single page. Users enter their username and password only once to access the applications on the page.

You configure Oracle9iAS Single Sign-On using a Web-based interface. You can perform tasks such as setting the maximum session length, adding partner applications, and changing the administrator password.

See the Oracle9iAS Single Sign-On Administrator's Guide for details.

Table 7-8 Changes to Oracle9iAS Single Sign-On  

If you change this:	You affect these components:
Hostname, Port, or Protocol (HTTP or HTTPS)	If you change the hostname, port, or protocol of Oracle HTTP Server, this affects Single Sign-On. See the section "Oracle HTTP Server" for details. Oracle9iAS Portal: Three cases are possible (for details on ptlasst, see the Oracle9iAS Portal Configuration Guide): Case 1: If you are running Portal and Oracle9iAS Single Sign-On on the same machine, and you changed the name of the machine, you need to run the script: (UNIX) ORACLE_HOME/assistants/opca/ptlasst.csh (Windows) ORACLE_HOME\assistants\opca\ptlasst.cmd in SSOPARTNERCONFIG mode: ptlasst.csh -i typical -mode SSOPARTNERCONFIG -s portal -sp portal -c webdbsvr2.us.oracle.com:1521:s901dev3 -sdad portal -o orasso -odad orasso -host webdbsvr1.us.oracle.com -port 3000 -silent -verbose -sso_c webdbsvr2.us.oracle.com:1521:s901dev3 -sso_h webdbsvr1.us.oracle.com -sso_p 3000 -pa orasso_pa -pap orasso_pa -ps orasso_ps -pp orasso_ps -pd portal_dblink -p_tns websso_ps -s_tns portal -iasname myIAS Note: Running ptlasst in SSOPARTNERCONFIG mode creates a new row for the partner application instead of updating the existing row. This does not prevent Portal from working, but it can become a usability issue when the list of partner applications builds up on the Global Logout screen and some links might break. (continued in next row)
(continued from previous row) Hostname, Port, or Protocol (HTTP or HTTPS)	Oracle9iAS Portal (continued): Case 2: If you are running Portal and the Oracle9iAS Single Sign-On server on separate machines and you just changed the name of the Oracle9iAS Single Sign-On machine (the name of the Portal machine did not change), you need to run the script: (UNIX) ORACLE_HOME/assistants/opca/ptlasst.csh (Windows) ORACLE_HOME\assistants\opca\ptlasst.cmd in SSOPARTNERCONFIG mode. Specify the new Oracle9iAS Single Sign-On server name and port in the Oracle9iAS Single Sign-On server name and port parameters: ptlasst.csh -i typical -mode SSOPARTNERCONFIG -s portal -sp portal -c webdbsvr2.us.oracle.com:1521:s901dev3 -sdad portal -o orasso -odad orasso -host webdbsvr1.us.oracle.com -port 3000 -silent -verbose -sso_c webdbsvr2.us.oracle.com:1521:s901dev3 -sso_h webdbsvr1.us.oracle.com -sso_p 3000 -pa orasso_pa -pap orasso_pa -ps orasso_ps -pp orasso_ps -pd portal_dblink -p_tns websso_ps -s_tns portal -iasname myIAS Case 3: If you are pointing a Portal instance from one Oracle9iAS Single Sign-On server to another one, you need to do the following: Add the Portal as a partner application to the new Oracle9iAS Single Sign-On server. See the section "Adding a Partner Application" in Chapter 2 of the Oracle9iAS Single Sign-On Administrator's Guide for details. Run the script: (UNIX) ORACLE_HOME/assistants/opca/ptlasst.csh (Windows) ORACLE_HOME\assistants\opca\ptlasst.cmd in SSOPARTNERCONFIG mode to associate Portal with the new Oracle9iAS Single Sign-On server: ptlasst.csh -i typical -mode SSOPARTNERCONFIG -s portal -sp portal -c webdbsvr2.us.oracle.com:1521:s901dev3 -sdad portal -o orasso -odad orasso -host webdbsvr1.us.oracle.com -port 3000 -silent -verbose -sso_c webdbsvr2.us.oracle.com:1521:s901dev3 -sso_h webdbsvr1.us.oracle.com -sso_p 3000 -pa orasso_pa -pap orasso_pa -ps orasso_ps -pp orasso_ps -pd portal_dblink -p_tns websso_ps -s_tns portal -iasname myIAS Case 2 and Case 3 above assume that the Oracle Internet Directory server that the Oracle9iAS Single Sign-On servers point to is the same. If not, you also need to run ssooconf.sql. See the section "Oracle Internet Directory" for details. (continued in next row)
(continued from previous row) Hostname, Port, or Protocol (HTTP or HTTPS)	mod_osso: Run the Single Sign-On registration tool to re-register mod_osso. See the section "Reregistering the Oracle HTTP Server with the Single Sign-On Server" in the Oracle9iAS Single Sign-On Release Notes for details. Note: Running the registration tool creates a new row for the partner application instead of updating the existing row. This does not prevent the application from working, but it can become a usability issue when the list of partner applications builds up on the Global Logout screen and some links might break. Oracle9iAS Wireless: The registration tool for the Wireless partner application is: (UNIX) ORACLE_HOME/wireless/sample/reRegisterSSO.sh (Windows) ORACLE_HOME\wireless\sample\reRegisterSSO.bat Syntax: reRegisterSSO.{sh,bat} <new_host_URL> <ORACLE_HOME> Example: reRegisterSSO.sh http://new.myco.com:4567/ptg/rm /private/OraHome Note: Running reRegisterSSO creates a new row for the partner application instead of updating the existing row. This does not prevent the application from working, but it can become a usability issue when the list of partner applications builds up on the Global Logout screen and some links might break.
Password of ORASSO schema You can change the password using the SSO Administration page or SQL*Plus.	Oracle HTTP Server and Oracle9iAS Portal: Use Oracle Enterprise Manager Web site to change the Database Password field for the DAD that accesses the Oracle9iAS Single Sign-On schema to match the new password. This changes the PlsqlDatabasePassword parameter in the ORACLE_HOME/Apache/modplsql/conf/dads.conf file. Restart HTTP Server. Oracle9iAS Portal: Update the ssoServerPassword property for the Oracle9iAS Single Sign-On target in the ORACLE_HOME/sysman/emd/targets.xml file.
Password of ORASSO_PS schema	Oracle9iAS Portal: No changes required if Portal uses the Metadata Repository API to retrieve the password. If Portal stores the password in a database table, then it has to update the table.
Password of the lightweight SSO administrator (DN: cn=orcladmin, cn=users, o=company, dc=com)	No repercussions on other components.
Logout_url, success_url, failure_url, or home_url of partner applications, including mod_osso module	Oracle9iAS Single Sign-On: You can change these URLs through the SSO Server Administration Page.
Disable Oracle9iAS Single Sign-On	Oracle9iAS Reports Services: Edit ORACLE_HOME/reports/conf/rwservlet.properties to set SINGLESIGNON=NO (default is YES).
Any	DAS: Changes to Oracle9iAS Single Sign-On are reflected by mod_osso, from which DAS gets Oracle9iAS Single Sign-On information.
Oracle9iAS Single Sign-On application entry password, which is stored in Oracle Internet Directory at: orclApplicationCommonName=ORASSO, cn=SSO, cn=Products, cn=OracleContext You can change the password by changing the userPassword attribute using ODM or a command-line utility.	Oracle9iAS Single Sign-On: Run ORACLE_HOME/sso/admin/plsql/sso/ssooconf.sql in SQL*Plus as the ORASSO user to update the password in the Oracle9iAS Single Sign-On preference store. This enables Oracle9iAS Single Sign-On to connect to Oracle Internet Directory.
Load balancing	Oracle HTTP Server and Load Balancer: If Oracle HTTP Server for the Oracle9iAS Single Sign-On server is behind a load balancer, you need to set the KeepAlive directive in the file ORACLE_HOME/Apache/Apache/conf/httpd.conf to off. If this directive is set to on, the load balancer maintains state with Oracle HTTP Server for the same connection, and this results in a HTTP 503 error code.

Oracle Internet Directory

Oracle Internet Directory enables you to manage entities such as users and applications. You change configuration parameters for Oracle Internet Directory using Oracle Directory Manager or command-line tools such as oidpasswd.

See the Oracle Internet Directory Administrator's Guide for details.

Table 7-9 Changes to Oracle Internet Directory  

If you change this:	You affect these components:
Oracle Internet Directory port, hostname, or application password In the file ORACLE_HOME/config/ias.properties, change the value of OIDhost and OIDport accordingly.	Components that depend on Oracle Internet Directory can pick up changes in Oracle Internet Directory's host and port if the components use the Repository API. JAAS with LDAP: If you are using JAAS with LDAP, edit the location attribute in the jazn tag in the file ORACLE_HOME/j2ee/home/config/jazn.xml. The tag looks like the following: <jazn provider="LDAP" location="ldap://oidhost:port" /> If you specify the Oracle Internet Directory host and port as part of your application, then you have to edit your application deployment file. JAAS with XML: No changes necessary. Oracle9iAS Single Sign-On: If you move to a new Oracle Internet Directory instance, the new instance must be a replication of the old Oracle Internet Directory instance. In particular, the GUID of the users must be the same. Run ORACLE_HOME/sso/admin/plsql/sso/ssooconf.sql in SQL*Plus as the ORASSO user to enter the values for the new Oracle Internet Directory instance.
Portal application entry password, which is stored in Oracle Internet Directory at: orclApplicationCommonName=Portal, cn=Portal, cn=Products, cn=OracleContext You can change the password by changing the userPassword attribute using ODM or a command-line utility.	Oracle9iAS Portal: Run wwc/secupoid.sql in the Portal schema. This updates the password in the Portal preference store, which allows Portal to connect to Oracle Internet Directory. Example of running secupoid.sql in SQL*Plus (you enter the values in bold): SQL> @secupoid Current Configuration --------------------- OID Host: oid.domain.com OID Port: 389 Application DN: orclApplicationCommonName=PORTAL,cn=Portal, cn=Products,cn=OracleContext Application Password: 3E8C2D1B87CB61011757239C5AA9B390 Use SSL? N PL/SQL procedure successfully completed. Updating OID Configuration Entries Press [Enter] to retain the current value for each parameter For SSL Connection to LDAP, specify "Y"es or "N"o ------------------------------------------------ Enter value for oid_host: Enter value for oid_port: Enter value for app_password: mynewpassword Enter value for use_ssl_to_connect_to_ldap: Y Enter value for refresh_with_new_settings: N PL/SQL procedure successfully completed. No errors.
Oracle9iAS Single Sign-On application entry password, which is stored in Oracle Internet Directory at: orclApplicationCommonName=ORASSO, cn=SSO, cn=Products, cn=OracleContext You can change the password by changing the userPassword attribute using ODM or a command-line utility.	Oracle9iAS Single Sign-On: Run ORACLE_HOME/sso/admin/plsql/sso/ssooconf.sql in SQL*Plus as the ORASSO user to update the password in the Oracle9iAS Single Sign-On preference store. This enables Oracle9iAS Single Sign-On to connect to Oracle Internet Directory.
Password for the cn=orcladmin account You must use the oidpasswd utility to change the password; you cannot use any other tool.	JAAS: No effect. Oracle9iAS Portal: No effect. Oracle9iAS Single Sign-On: No effect.

Metadata Repository

The metadata repository database contains schemas owned by various components. The database is installed when you install the Infrastructure for Oracle9i Application Server. Typically, you do not change anything in this database directly. Instead, you use provided interfaces, such as Oracle Enterprise Manager or utilities.

Table 7-10 Changes to the Metadata Repository 

If you change this:	You affect these components:
Hostname for the repository database	Oracle9iAS Single Sign-On: Update the ssoServerMachineName property for the Oracle9iAS Single Sign-On target in the file ORACLE_HOME/sysman/emd/targets.xml. Note: If you have multiple repository database instances, Oracle9iAS Single Sign-On uses only one of the instances. You need to update the ssoServerMachineName property to point to the machine that hosts that instance.
Port for the repository database	Oracle9iAS Discoverer: Update the port for the discodemo service name in the tnsnames.ora file.