4 Changing the HTTP Listener Ports

4.1 Changing the HTTP Server Listen Port on Middle-Tier Instances

This section describes how to change port numbers in middle-tier instances and update any other affected components. It contains the procedure to change the Oracle HTTP Server listen port (SSL or Non-SSL).

When you change the Oracle HTTP Server Listen directive, there are often dependencies that must also be set. For example, if you are using OracleAS Web Cache to improve the performance of your Oracle Application Server instance, then you must modify the OracleAS Web Cache origin server settings whenever you modify the Oracle HTTP Server Listen ports.

To be sure the port dependencies are modified correctly, you can use a single command to change the Oracle HTTP Server Listen port. The portconfig command automatically modifies the necessary configuration files within the Oracle home and optionally restarts the required components within the Oracle home.

The following sections describe how to define the portconfig command and then use it to modify the Oracle HTTP Server Listen SSL or non-SSL port:

• Enabling Oracle HTTP Server to Run as Root for Ports Set to Less Than 1024 (UNIX only)

• Using the portconfig Command to Change the Oracle HTTP Server Listen Port

4.2 Changing the HTTP Server Listen Port on Identity Management Installations

This section describes how to change the Oracle HTTP Server HTTP or HTTPS listen port on an Identity Management installation. When you change this port number, you also effectively change the OracleAS Single Sign-On port number. This means you must update any middle-tier instances that use the OracleAS Single Sign-On port.

Task 1: Prepare the Middle-Tier Instances

Perform this task only if the Identity Management installation is being used by middle-tier instances. On each middle-tier instance that uses Oracle Identity Management, stop the middle-tier instance as follows:

1. On the Application Server Home page of the Application Server Control Console, click Stop All.

2. Leave the Application Server Control Console running.

It is important that you leave the Application Server Control Console running in each of the middle-tier instances while you perform this procedure.

Task 2: Prepare the Infrastructure Instances

1. Ensure that Oracle Identity Management and its associated OracleAS Metadata Repository are started on the infrastructure whose port number you are changing.

2. If any middle-tier instances use different Metadata Repositories for their product metadata and DCM repositories, then ensure that those are up. In short, ensure all Metadata Repositories in your environment are up.

Task 3: Modify the Oracle HTTP Server Listen and Port Directives

If you are changing the HTTP port, change both the non-SSL Listen and Port directives to the new port number. Perform the following steps:

1. Navigate to the Application Server Home page and click Ports.

2. On the Ports page, locate the Oracle HTTP Server Listen port and click the icon in the Configure column.

3. On the Server Properties page:

   • Enter the new port number in the Default Port field. This is for the Port directive.

   • Enter the new port number in the Listening Port column. This is for the Listen directive. There may be more than one listening port listed. The only way to tell which is the non-SSL listen port is to choose the one with the old non-SSL listen port value.

4. At the bottom of the page, click Apply.

5. On the Confirmation page, click No, you would not like to restart now.

If you are changing the HTTPS port, change both the SSL Listen and SSL Port directives to the new port number, perform the following steps:

1. Edit the following file:

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

2. Update the SSL Listen and SSL Port directives with the new port number. The value for Listen and Port must be the same port number.

3. Save and close the file.

4. Run the following command:

   (UNIX) ORACLE_HOME/dcm/bin/dcmctl updateConfig -ct ohs
   (Windows) ORACLE_HOME\dcm\bin\dcmctl updateConfig -ct ohs
   

Task 4: Enable Oracle HTTP Server to Run as Root for Ports Less Than 1024 on UNIX

By default, Oracle HTTP Server runs as a non-root user (the user that installed Oracle Application Server). On UNIX systems, if you change the Oracle Application Server non-SSL listen port number to a value less than 1024, then you must enable Oracle HTTP Server to run as root, as follows:

1. Log in as root.

2. Run the following commands in the middle tier Oracle home:

   cd ORACLE_HOME/Apache/Apache/bin
   chown root .apachectl
   chmod 6750 .apachectl
   

Task 5: Update the Application Server Control Console

Update the Application Server Control Console with the new port number:

1. Edit the following file:

   (UNIX) ORACLE_HOME/sysman/emd/targets.xml
   (Windows) ORACLE_HOME\sysman\emd\targets.xml
   
   

2. Update each occurrence of the old Oracle HTTP Server listen port number with the new port number.

3. Save and close the file.

4. Reload the Application Server Control Console:

   (UNIX) ORACLE_HOME/bin/emctl reload
   (Windows) ORACLE_HOME\bin\emctl reload
   

Task 6: UpdateOracleAS Single Sign-On

In the example, hostname is the host on which OracleAS Single Sign-On is running and new_port_number is the new SSL Oracle HTTP Server listen port number.

Perform this task if OracleAS Single Sign-On is configured to use the Oracle HTTP Server HTTP listen port in the installation where you are changing the port.

1. 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 must set depend on the type of your UNIX operating system.

2. Run one or both of the following commands in the OracleAS Single Sign-On Oracle home:

   To change the non-SSL port:

   (UNIX) ORACLE_HOME/sso/bin/ssocfg.sh http hostname new_non_ssl_port_number
   (Windows) ORACLE_HOME\sso\bin\ssocfg.bat http hostname new_non_ssl_port_number
   
   

   To change the SSL port:

   (UNIX) ORACLE_HOME/sso/bin/ssocfg.sh https hostname new_ssl_port_number
   (Windows) ORACLE_HOME\sso\bin\ssocfg.bat https hostname new_ssl_port_number
   
   

   In the examples:

   • hostname is the host on which OracleAS Single Sign-On is running.

   • new_non_ssl_port_number is the new non-SSL Oracle HTTP Server listen port number.

   • new_ssl_port_number is the new SSL Oracle HTTP Server listen port number.

Task 7: Re-register mod_osso

To re-register mod_osso, perform the following steps:

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

2. On Windows systems, set the path, for example: PATH=%PATH%;%ORACLE_HOME%\bin;%ORACLE_HOME%\lib.

3. If you are changing the non-SSL listen port, then re-register mod_osso to take care of the default partner applications by running the following command in Oracle Identity Management Oracle home:

   UNIX:

   ORACLE_HOME/sso/bin/ssoreg.sh
   -oracle_home_path identity_management_oracle_home
   -site_name identity_management_hostname:new_port_number
   -config_mod_osso TRUE
   -mod_osso_url mod_osso_url
   
   

   Windows:

   ORACLE_HOME\sso\bin\ssoreg.bat
   -oracle_home_path middle_tier_oracle_home
   -site_name identity_management_hostname:new_port_number
   -config_mod_osso TRUE
   -mod_osso_url mod_osso_url
   
   

   For example, to change the Oracle HTTP Server listen port to 7779 on host myhost:

   ORACLE_HOME/jdk/bin/java -jar $ORACLE_HOME/sso/lib/ossoreg.jar
   -oracle_home_path /disk1/oracleas
   -site_name myhost:7779
   -config_mod_osso TRUE
   -mod_osso_url http://myhost.mydomain:7779
   -u oracle
   
   

4. If you are changing the Oracle HTTP Server SSL listen port, perform the following steps.

   1. Re-register mod_osso with the new port number by running the following command in the middle-tier Oracle home:

      UNIX:

      ORACLE_HOME/sso/bin/ssoreg.sh
      -oracle_home_path identity_management_oracle_home
      -site_name identity_management_hostname:new_port_number
      -config_mod_osso TRUE
      -mod_osso_url mod_osso_url
      -config_file path/osso-https.conf
      
      

      Windows:

      ORACLE_HOME\sso\bin\ssoreg.bat
      -oracle_home_path identity_management_oracle_home
      -site_name identity_management_hostname:new_port_number
      -config_mod_osso TRUE
      -mod_osso_url mod_osso_url
      -config_file path\osso-https.conf
      
      

      For example, if you want to change the Oracle HTTP Server SSL listen port to 7778 on myhost on UNIX:

      $ORACLE_HOME/sso/bin/ssoreg.sh
      -oracle_home_path /disk1/oracleas
      -site_name myhost:4445
      -config_mod_osso TRUE
      -mod_osso_url http://myhost.mydomain:7778
      -config_file $ORACLE_HOME/Apache/Apache/conf/osso/osso-https.conf
      
      

   2. Edit the mod_osso.conf file, which is located at:

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

      In the mod_osso.conf file, comment the following directive, if you have not previously done so:

      On UNIX:

      LoadModule osso_module libexec/mod_osso.so
      
      

      On Windows:

      LoadModule osso_module modules\ApacheModuleOsso.dll
      
      

   3. In the httpd.conf file, which is found in the same (conf) directory, add the directive that you just commented in the preceding step (if you have not previously done so). In a default setup, place the directive right after:

      LoadModule wchandshake_module libexec/mod_wchandshake.so
      
      

5. Restart the Oracle HTTP Server:

   (UNIX) ORACLE_HOME/opmn/bin/opmnctl restartproc process-type=HTTP_Server
   (Windows) ORACLE_HOME\opmn\bin\opmnctl restartproc process-type=HTTP_Server
   
   

6. Re-register any additional partner applications that you configured or modified.

   
   

   See Also: Oracle Application Server Single Sign-On Administrator's Guide for more information about registering mod_osso

   
   

Task 8: Update Oracle Delegated Administration Services

If you have Oracle Delegated Administration Services configured, and Oracle Delegated Administration Services uses the SSL and non-SSL port numbers, take the following steps to update the Oracle Delegated Administration Services URL entry in Oracle Internet Directory.

ldapsearch -h oid_host -p oid_port -D "cn=orcladmin"
-w "password" -b "cn=OperationURLs,cn=DAS,cn=Products,cn=OracleContext"
-s base "objectclass=*" orcldasurlbase

1. Create a file named mod.ldif with the following contents (you can create the file in any directory):

   dn:cn=OperationURLs,cn=DAS,cn=Products,cn=OracleContext
   changetype:modify
   replace:orcldasurlbase
   orcldasurlbase:http://hostname:new_http_port_number/
   
   

   Note the slash at the end of the orcldasurlbase URL.

2. Run the following command:

   ldapmodify -D cn=orcladmin -w password -p oid_port -f mod.ldif
   

Task 9: Update Oracle Application Server Certificate Authority

If you are using OracleAS Certificate Authority:

1. Re-register OracleAS Certificate Authority with the OracleAS Single Sign-On server by running the following command in the OracleAS Certificate Authority Oracle home:

   (UNIX) ORACLE_HOME/oca/bin/ocactl changesecurity -server_auth_port portnum
   (Windows) ORACLE_HOME\oca\bin\ocactl changesecurity -server_auth_port portnum
   
   

   In the example, port_number is the OracleAS Certificate Authority Server Authentication Virtual Host (SSL) port. The default value is 4400.

   
   

   See Also: Oracle Application Server Certificate Authority Administrator's Guide for more information

   
   

2. If OracleAS Certificate Authority is located in a different Oracle home than the OracleAS Single Sign-On server, then restart Oracle HTTP Server and the oca instance in the OracleAS Certificate Authority Oracle home. For example, on UNIX:

   ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=HTTP_Server
   ORACLE_HOME/opmn/bin/opmnctl stopproc process-type=oca
   ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=HTTP_Server
   ORACLE_HOME/opmn/bin/opmnctl startproc process-type=oca
   

Task 10: Restart the Identity Management Instance

Restart the Identity Management instance. For example, on UNIX:

ORACLE_HOME/bin/emctl stop iasconsole
ORACLE_HOME/opmn/bin/opmnctl stopall
ORACLE_HOME/opmn/bin/opmnctl startall
ORACLE_HOME/bin/emctl start iasconsole

Task 11: Restart OracleAS Certificate Authority

If OracleAS Certificate Authority is configured in this instance, then restart it:

(UNIX) ORACLE_HOME/oca/bin/ocactl start
(Windows) ORACLE_HOME\oca\bin\ocactl start

Task 12: Update the Middle-Tier Instances to Use the New Port Number

After you change the Oracle HTTP Server non-SSL port on the Identity Management installation, you must update all middle-tier instances to use the new port number.

1. Update each middle-tier instance using the Change Identity Management wizard in the Application Server Control Console.

   On each middle-tier instance that uses Identity Management:

   1. Using the Application Server Control Console, navigate to the Application Server Home page for the middle-tier instance.

   2. Click the Infrastructure link.

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

   4. Follow the steps in the wizard.

   5. When the wizard is finished, navigate to the Application Server Home page and start the middle-tier instance by clicking Start All.

2. Refresh the Oracle Internet Directory cache in your applications:

   1. Log in to the Portal.

   2. Click the global settings link.

   3. Click the SSO/OID tab.

   4. Check the refresh Oracle Internet Directory cache settings and click Apply.