Oracle HTTP Server
Parameters for Oracle HTTP Server are defined in .conf files in theORACLE_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
For detailed information on Oracle HTTP Server and its parameters, see the Oracle HTTP Server Administration Guide.
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 theupdateConfig parameter so that the updated values are copied into the DCM repository. See"About Manually Editing HTTP Server and OC4J Configuration Files" on page 6-2 for details.
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:
1. Update the port number in the Application Web Servers section under the General Configuration section of the Web Cache Home Page.
2. Restart Web Cache.
Oracle Internet Directory:
Change theorcldasurlbase 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).
Oracle HTTP Server
(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.
1. 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 setORACLE_HOME andORACLE_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 thePATH 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.
2. 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 isptlasst.csh for UNIX, ptlasst.cmd for Windows.
For Wireless, the registration tool isreRegisterSSO.sh for UNIX, reRegisterSSO.bat for Windows.
For mod_osso, the registration tool is packaged inossoreg.jar.
See the section"Oracle9iAS Single Sign-On" for details.
(continued in next row) Table 7–1 Changes to Oracle HTTP Server (Cont.)
If you change this: You affect these components:
Oracle HTTP Server
(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):
3. 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.
4. Modify theHTTPMachine property for the Oracle9iAS Single Sign-On target in the fileORACLE_HOME/sysman/emd/targets.xml to match the values used by Oracle HTTP Server.
You do not need to modify theHTTPPort andHTTPProtocol properties. If the port changes, the code detects the new port number and updates theHTTPPort property for the Oracle9iAS Single Sign-On target in thetargets.xml file.
If the name of the machine running the metadata repository database changes, you need to update thessoServerMachineNameproperty for the Oracle9iAS Single Sign-On target in the fileORACLE_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:
1. In the Wireless site configuration section of Oracle Enterprise Manager Web site, update the URL to reflect the new host and port settings.
2. Re-register the Wireless partner application.
See the section"Oracle9iAS Single Sign-On" for details.
(continued in next row) Table 7–1 Changes to Oracle HTTP Server (Cont.)
If you change this: You affect these components:
Oracle HTTP Server
(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:
1. Modify theHTTPPort property for the Portal target in the file ORACLE_HOME/sysman/emd/targets.xml.
2. Modify theHTTPPortproperty for the Oracle HTTP Server target in the fileORACLE_HOME/sysman/emd/targets.xml.
3. 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 onptlasst, 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) Table 7–1 Changes to Oracle HTTP Server (Cont.)
If you change this: You affect these components:
Oracle HTTP Server
(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:
Update thelogFileLoc property inagent.xml.
Port for OC4J
(Specified in theOc4jMount 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 theOc4jMount directive must match the AJP host and port for the OC4J being routed to. The OC4J configuration is specified in the filexxx-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 inmoddav.conf because mod_oradav uses environment variables that are also used for OCI clients
(LD_LIBRARY_PATH, ORACLE_HOME, NLS_LANG, TNS_ADMIN, etc).
Table 7–1 Changes to Oracle HTTP Server (Cont.)
If you change this: You affect these components: