5
Managing Ports

This chapter describes how to view and change Oracle Application Server port numbers. It contains the following topics:

• About Managing Ports

• Viewing Port Numbers

• Changing Ports Common to All Middle-Tier Instances

• Changing Portal and Wireless Ports

• Changing Business Intelligence and Forms Ports

• Changing Infrastructure Ports

5.1 About Managing Ports

Many Oracle Application Server components and services use ports. As an administrator, it is important to know the port numbers used by these services, and to ensure that the same port number is not used by two services on your host.

Most port numbers are assigned during installation. Every component and service has an allotted port range, which is the set of port numbers Oracle Application Server attempts to use when assigning a port. Oracle Application Server starts with the lowest number in the range and performs the following checks:

• Is the port used by another Oracle Application Server installation on the host?

  The installation may be up or down at the time; Oracle Application Server can still detect if the port is used.)

• Is the port used by a process that is currently running?

  This could be any process on the host, even a non-Oracle Application Server process.

• Is the port listed in the /etc/services files?

If the answer to any of the above questions is yes, Oracle Application Server moves to the next highest port in the allotted port range and continues checking until it finds a free port.

You can override this behavior for some ports, and specify a port number assignment during installation. To do this, you edit a template file called staticports.ini, and launch Oracle Universal Installer with special options.

See Also: Appendix C, "Oracle Application Server Port Numbers" for a complete list of allotted port ranges. Refer to Oracle Application Server 10g Installation Guide for directions on overriding port assignments during installation with staticports.ini.

5.2 Viewing Port Numbers

You can view port numbers in the following ways:

• Immediately after installation, you can view port number assignments in:

  ORACLE_HOME/install/portlist.ini
  
  

  If you change a port number, it is not updated in this file, so you can only rely on this file immediately after installation.

• Another file that displays two important ports, the Application Server Control port and the HTTP Server port is:

  ORACLE_HOME/Apache/Apache/setinfo.txt
  
  

  Since the Application Server Control port number cannot be changed, this is always a good place to locate the URL for Application Server Control. However, you may change the HTTP Server port after installation, so it is not reliable for that.

• The main way to view port numbers once your installation is up and running is on the Application Server Control Ports Page. You can view the Ports Page by clicking the ports link on the Application Server home page. The Ports Page displays the current port numbers and is updated any time you change a port number. It also contains links to pages that allow you do change port numbers.

Querying the Runtime JServ Port

If you have JServ configured, you can query the runtime port used by JServ with the following URL:

http://hostname.domain:http_port/oprocmgr-status

5.3 Changing Ports Common to All Middle-Tier Instances

This section provides complete instructions for changing port numbers in middle-tier instances. The instructions explain how to change the port number, and update any other components that might be affected.

See Also: Appendix C, "Oracle Application Server Port Numbers" for more information on changing port numbers

Note: You can change a port number to any number you want, as long as it is an unused port. You do not have to use a port in the allotted port range for the component.

It contains the following topics:

• Changing Oracle Enterprise Manager Ports

• Changing OC4J Ports

• Changing Oracle HTTP Server Ports

• Changing the Web Cache Non-SSL Listener Port (Middle-Tier Installations)

• Changing the Web Cache SSL Listener Port (Middle-Tier Installations)

• Changing the Web Cache Administration Port

• Changing the Web Cache Invalidation Port

• Changing the Web Cache Statistics Port

• Changing the DCM Java Object Cache Port

• Changing the Java Object Cache Port

• Changing the JServ Servlet Engine Port

• Changing the Log Loader Port

• Changing OPMN Ports (ONS Local, Request, and Remote)

• Changing the Oracle HTTP Server Diagnostic Port

• Changing the Port Tunneling Port

5.3.1 Changing Oracle Enterprise Manager Ports

You cannot change Oracle Enterprise Manager ports after installation.

See Also: Appendix C, "Oracle Application Server Port Numbers"

5.3.2 Changing OC4J Ports

This section describes how to change the following OC4J port numbers:

• AJP

• JMS

• RMI

• IIOP

• IIOPS1 (Server only)

• IIOPS2 (Server and client)

By default, Oracle Application Server does not specify a single port number for each OC4J port. Instead, it specifies a port range for each type of OC4J port and that range is the same for all instances on the host. During runtime, each instance is assigned a single free port from the range.

For example, the default AJP range for every OC4J instance on a host is 3301-3400. Each OC4J instance is assigned a single free port from that range for its AJP port.

In order to change an OC4J port number, you typically change the range of port numbers for a service, and then a free port from that range will be assigned.

You can change OC4J port numbers using Application Server Control or manual steps:

• Using Application Server Control
  1. Navigate to the Application Server Instance Home Page.

  2. Click Ports.

  3. On the Ports Page, locate the OC4J Instance and OC4J port range you would like to change. Click the icon in the Configure column.

  4. On the Server Properties Page, enter the new port range in the appropriate field. Click Apply.

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

• Using Manual Steps
  1. Edit the following file:

     ORACLE_HOME/opmn/conf/opmn.xml
     
     

  2. Locate the element for the OC4J instance that contains the port number you would like to change. For example, if you want to change a port number for the home instance, locate this element:

     <process-type id="home" ...>
     
     

  3. Within the OC4J instance element, there is a port element for each type of port. For example:

     <port id="ajp" range="3301-3400"/>
     <port id="rmi" range="3201-3300"/>
     <port id="jms" range="3701-3800"/>
     <port id="iiop" range="3401-3500"/>
     <port id="iiops1" range="3501-3600"/>
     <port id="iiops2" range="3601-3700"/>
     
     

     Modify the range parameter for the port you would like to change.

  4. Save and close the file.

  5. Reload OPMN:

     opmnctl reload
     
     

  6. Restart the OC4J instance that contains the port number you changed:

     opmnctl restartproc process-type=OC4J_instance
     
     

     For example, if you changed a port number in the home instance:

     opmnctl restartproc process-type=home
     
     

  7. Run the following command:

     dcmctl updateConfig
     

5.3.3 Changing Oracle HTTP Server Ports

This section describes how to change the Oracle HTTP Server Listen directive on a middle-tier instance. It contains the following procedures:

• Changing the Oracle HTTP Server Non-SSL Listen Port (with Web Cache)

  Follow this procedure to change the Oracle HTTP Server Listen port on a middle-tier instance. In this procedure, you update the Oracle HTTP Server Listen directive and register the new port number with Web Cache. The Web Cache port and the Oracle HTTP Server Port directive remain unchanged.

• Changing the Oracle HTTP Server SSL Listen Port (with Web Cache)

  Follow this procedure to change the Oracle HTTP Server SSL Listen port on a middle-tier instance. In this procedure, you update the Oracle HTTP Server SSL Listen directive and register the new port number with Web Cache. The Web Cache SSL port and the Oracle HTTP Server SSL Port directive remain unchanged.

• Changing the Oracle HTTP Server Non-SSL Listen Port (No Web Cache)

  Follow this procedure on a J2EE and Web Cache installation that does not have Web Cache configured. It involves changing the Listen directive and Port directive with the new port number.

• Changing the Oracle HTTP Server SSL Listen Port (No Web Cache)

  Follow this procedure on a J2EE and Web Cache installation that does not have Web Cache configured. It involves changing the SSL Listen directive and SSL Port directive with the new port number.

5.3.3.1 Changing the Oracle HTTP Server Non-SSL Listen Port (with Web Cache)

This section describes how to change the Oracle HTTP Server non-SSL listen port on an installation that has Web Cache front-ending the Oracle HTTP Server.

Step 1: Modify the Oracle HTTP Server Listen Directive

You can do this using Application Server Control or manual steps:

• Using the Application Server Control:
  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, in the Listening Addresses and Ports section, enter the new port number in the Listening Port column. There may be more than one listening port listed. The only way to tell which is the non-SSL listening port is to choose the one with the old non-SSL listening 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.

• Using Manual Steps:
  1. Edit the following file:

     ORACLE_HOME/Apache/Apache/conf/httpd.conf
     
     

  2. Update the Listen directive with the new port number. Do not update the Port directive.

     There may be multiple Listen directives in this file. Modify the Listen directive that is not enclosed in an SSL virtual host container. The easiest way to locate the proper Listen directive is to search the file for the old listen port number.

  3. Save and close the file.

  4. Run the following command:

     dcmctl updateConfig -ct ohs
     

Step 2: Enable Oracle HTTP Server to Run as Root for Ports < 1024 on UNIX

Perform this step if you are changing the port to a number < 1024.

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, you must enable Oracle Application 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
   

Step 3: Update Application Server Control

Update Application Server Control with the new port number:

1. Edit the following file:

   ORACLE_HOME/sysman/emd/targets.xml
   
   

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

   Depending on your configuration, this file may not contain any occurrences of the Oracle HTTP Server listen port, or it may contain many occurrences. The listen port may occur as a parameter on its own, or it may be part of a URL. The easiest way to edit this file is to search for all occurrences of the old Oracle HTTP Server listen port number, and replace them with the new port number. Be sure to update only the Oracle HTTP Server listen port; do not update the Web Cache listener port or any other port numbers.

3. Save and close the file.

4. Reload Application Server Control:

   ORACLE_HOME/bin/emctl reload
   

Step 4: Update OracleAS Web Cache

1. Using Application Server Control, navigate to the Web Cache home page.

2. In the Administration section, click Web Cache Administration. Log in to Web Cache Administrator.

3. In the navigator frame, select Origin Servers, Sites, and Load Balancing > Origin Servers. The Origin Servers page appears.

4. Select the Oracle HTTP Server port that has HTTP in the Protocol column. Click Edit Selected.

5. Enter the new port number in the Port field. Click Submit.

6. Click Apply Changes.

Step 5: Restart the Middle-Tier Instance

Restart the middle-tier instance:

opmnctl stopall
opmnctl startall

5.3.3.2 Changing the Oracle HTTP Server SSL Listen Port (with Web Cache)

This section describes how to change the Oracle HTTP Server non-SSL listen port on an installation that has Web Cache front-ending the Oracle HTTP Server.

Step 1: Modify the Oracle HTTP Server Listen Directive

1. Edit the following file:

   ORACLE_HOME/Apache/Apache/conf/ssl.conf
   
   

2. Update the Listen directive with the new port number. Do not update the Port directive.

3. Save and close the file.

4. Run the following command:

   ORACLE_HOME/dcm/bin/dcmctl updateConfig -ct ohs
   

Step 2: Enable Oracle HTTP Server to Run as Root for Ports < 1024 on UNIX

Perform this step if you are changing the port to a number < 1024.

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 SSL listen port number to a value less than 1024, you must enable Oracle Application 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
   

Step 3: Update Application Server Control

Update Application Server Control with the new port number:

1. Edit the following file:

   ORACLE_HOME/sysman/emd/targets.xml
   
   

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

   Depending on your configuration, this file may not contain any occurrences of the Oracle HTTP Server SSL listen port, or it may contain many occurrences. The listen port may occur as a parameter on its own, or it may be part of a URL. The easiest way to edit this file is to search for all occurrences of the old Oracle HTTP Server SSL listen port number, and replace them with the new port number. Be sure to update only the Oracle HTTP Server SSL listen port; do not update the Oracle HTTP Server non-SSL listen port, the Web Cache listener port, or any other port numbers.

3. Save and close the file.

4. Reload the Application Server Control:

   ORACLE_HOME/bin/emctl reload
   

Step 4: Update OracleAS Web Cache

1. Using Application Server Control, navigate to the Web Cache home page.

2. In the Administration section, click Web Cache Administration. Log in to Web Cache Administrator.

3. In the navigator frame, select Origin Servers, Sites, and Load Balancing > Origin Servers.

4. The Origin Servers page appears.

5. Select the Oracle HTTP Server port that has HTTPS in the Protocol column.Click Edit Selected.

6. Enter the new port number in the Port field. Click Submit.

7. Click Apply Changes.

Step 5: Restart the Middle-Tier Instance

Restart the middle-tier instance:

opmnctl stopall
opmnctl startall

5.3.3.3 Changing the Oracle HTTP Server Non-SSL Listen Port (No Web Cache)

This section describes how to change the Oracle HTTP Server non-SSL listen port on an installation that does not have Web Cache front-ending the Oracle HTTP Server.

Step 1: Modify the Oracle HTTP Server Listen and Port Directives

You can do this using Application Server Control or manual steps:

• Using the Application Server Control:
  1. Navigate to the instance 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.

• Using Manual Steps:
  1. Edit the following file:

     ORACLE_HOME/Apache/Apache/conf/httpd.conf
     
     

  2. Update the non-SSL Listen and Port directives with the new port number. The value for Listen and Port must be the same port number, for example, to change the listener port to 7779:

     Listen 7779
     Port 7779
     
     

     There may be multiple Listen and Port directives in this file. Modify the Listen and Port directives that are not enclosed in an SSL virtual host container. The easiest way to locate the proper Listen and Port directives is to search the file for the old listen port number.

  3. Save and close the file.

  4. Run the following command:

     dcmctl updateConfig -ct ohs
     

Step 2: Enable Oracle HTTP Server to Run as Root for Ports < 1024 on UNIX

Perform this step if you are changing the port to a number < 1024.

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, you must enable Oracle Application 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
   

Step 3: Update Application Server Control

Update Application Server Control with the new port number:

1. Edit the following file:

   ORACLE_HOME/sysman/emd/targets.xml
   
   

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

   Depending on your configuration, this file may not contain any occurrences of the Oracle HTTP Server listen port, or it may contain many occurrences. The listen port may occur as a parameter on its own, or it may be part of a URL. The easiest way to edit this file is to search for all occurrences of the old Oracle HTTP Server listen port number, and replace them with the new port number.

3. Save and close the file.

4. Reload the Application Server Control:

   ORACLE_HOME/bin/emctl reload
   

Step 4: Re-register mod_osso

If you are using Single Sign-On, re-register mod_osso with the new port number:

1. Make sure the LD_LIBRARY_PATH environment variable contains $ORACLE_HOME/lib.

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

   $ORACLE_HOME/jdk/bin/java -jar $ORACLE_HOME/sso/lib/ossoreg.jar
   -oracle_home_path middle_tier_oracle_home
   -site_name middle_tier_hostname:new_http_port_number
   -config_mod_osso TRUE
   -mod_osso_url mod_osso_url
   -u user
   
   

   Note that user is the user that starts Oracle HTTP Server. By default, this is the user that installed Oracle Application Server. If you have changed the Oracle HTTP Server listen port number to a value < 1024, then this user is root.

   For example, if you want to change the Oracle HTTP Server listen port to 7779 on middle-tier host myhost:

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

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

Step 5: Restart the Middle-Tier Instance

Restart the middle-tier instance:

opmnctl stopall
opmnctl startall

5.3.3.4 Changing the Oracle HTTP Server SSL Listen Port (No Web Cache)

This section describes how to change the Oracle HTTP Server SSL listen port on an installation that has Web Cache front-ending the Oracle HTTP Server.

Step 1: Modify the Oracle HTTP Server Listen and Port directives

1. Edit the following file:

   ORACLE_HOME/Apache/Apache/conf/ssl.conf
   
   

2. Update the Listen and Port directives with the new port number. The value for Listen and Port must be the same port number, for example, to change the listener port to 4445:

   Listen 4445
   Port 4445
   
   

3. Save and close the file.

4. Run the following command:

   dcmctl updateConfig -ct ohs
   

Step 2: Enable Oracle HTTP Server to Run as Root for Ports < 1024 on UNIX

Perform this step if you are changing the port to a number < 1024.

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 SSL listen port number to a value less than 1024, you must enable Oracle Application 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
   

Step 3: Update Application Server Control

Update Application Server Control with the new port number:

1. Edit the following file:

   ORACLE_HOME/sysman/emd/targets.xml
   
   

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

   Depending on your configuration, this file may not contain any occurrences of the Oracle HTTP Server SSL listen port, or it may contain many occurrences. The listen port may occur as a parameter on its own, or it may be part of a URL. The easiest way to edit this file is to search for all occurrences of the old Oracle HTTP Server SSL listen port number, and replace them with the new port number. Be sure to update only the Oracle HTTP Server SSL listen port; do not update the Oracle HTTP Server non-SSL listen port or any other port numbers.

3. Save and close the file.

4. Reload the Application Server Control:

   ORACLE_HOME/bin/emctl reload
   

Step 4: Re-register mod_osso

If you have registered your SSL virtual host as an SSO partner application, follow these steps to re-register your SSL virtual host:

1. Make sure the LD_LIBRARY_PATH environment variable contains $ORACLE_HOME/lib.

2. Re-register your SSL virtual host with the new port number by running the following command in the middle-tier Oracle home:

   $ORACLE_HOME/jdk/bin/java -jar $ORACLE_HOME/sso/lib/ossoreg.jar
   -oracle_home_path middle_tier_oracle_home
   -site_name middle_tier_hostname:new_https_port_number
   -config_mod_osso TRUE
   -mod_osso_url mod_osso_url
   -virtualhost -u user
   
   

   Note that user is the user that starts Oracle HTTP Server. By default, this is the user that installed Oracle Application Server. If you have changed the Oracle HTTP Server listen port number to a value < 1024, then this user is root.

   For example, if you want to change the Oracle HTTP Server SSL listen port to 4445 on middle-tier host myhost:

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

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

Step 5: Restart the Middle-Tier Instance

Restart the middle-tier instance:

opmnctl stopall
opmnctl startall

5.3.4 Changing the Web Cache Non-SSL Listener Port (Middle-Tier Installations)

This section describes how to change the Web Cache non-SSL listener port. It involves changing the Web Cache port number and updating other components in the middle tier with the new port number.

Step 1: Change the Web Cache Non-SSL Listener Port

1. Using the Application Server Control, navigate to the Web Cache home page.

2. In the Administration section, click Web Cache Administration. Log in to Web Cache Administrator.

3. In the navigator frame, select Ports > Listen Ports. The Listen Ports page appears.

4. Select the port appropriate port that has HTTP in the Protocol column. Click Edit Selected.

5. Enter the new port number in the Port field. Click Submit.

6. Click Apply Changes. It is not necessary to restart Web Cache at this time since you are going to restart the entire instance at the end of this procedure.

Step 2: Change the Web Cache Logical Site Port

If the Web Cache non-SSL listener port is the same as the logical site port, update the logical site port as follows:

1. In Web Cache Manager, in the navigator frame, select Origin Servers, Sites, and Load Balancing > Site Definitions.

2. On the Site Definitions page, locate the appropriate site using the old port number. If there is no site using the old port number, then the Web Cache listener and site do not share the same port number. Skip to Step 3: Enable Web Cache to Run as Root for Ports < 1024 on UNIX.

3. Select the appropriate site with the old port number. Click Edit Site.

4. In the Edit Site dialog box, enter the new port number. Click Submit.

5. In the navigator frame, select Origin Servers, Sites, and Load Balancing > Site-to-Server Mapping.

6. On the Site-to-Server Mapping page, you may see one or more mappings using the old port number. For each site:
   1. Select the site and click Edit Selected.

   2. In the Edit/Add Site-to-Server Mapping dialog box, change the Port Number field to the new port number. Click Submit.

7. Click Apply Changes.

Step 3: Enable Web Cache to Run as Root for Ports < 1024 on UNIX

Perform this step if you are changing the port to a number < 1024.

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

1. Log in as the user that installed Oracle Application Server and stop Web Cache:

   opmnctl stopproc ias-component=WebCache
   
   

2. Log in as root.

3. Run the following command in the middle-tier Oracle home:

   ORACLE_HOME/webcache/bin/webcache_setuser.sh setroot userID
   
   

   Where userid is the current user Web Cache is running under. This is usually the user that installed Oracle Application Server. This user is listed on the Process Identity screen in Web Cache Manager.

4. Log in as the user that installed Oracle Application Server and start Web Cache:

   opmnctl startproc ias-component=WebCache
   

Step 4: Update the Oracle HTTP Server Port directive

1. Edit the following file:

   ORACLE_HOME/Apache/Apache/conf/httpd.conf
   
   

2. Update the Port directive with the new port number. Do not modify the Listen directive. The Web Cache port must equal the Oracle HTTP Server Port directive.

3. Save the file.

4. Run the following command:

   dcmctl updateConfig -ct ohs
   

Step 5: Update Application Server Control

Update Application Server Control with the new port number:

1. Edit the following file:

   ORACLE_HOME/sysman/emd/targets.xml
   
   

2. Update each occurrence of the old Web Cache listener port number with the new port number.

   Depending on your configuration, this file may not contain any occurrences of the Web Cache listener port, or it may contain many occurrences. The listener port may occur as a parameter on its own, or it may be part of a URL. The easiest way to edit this file is to search for all occurrences of the old Web Cache listener port number, and replace them with the new port number.

3. Save and close the file.

4. Reload the Application Server Control:

   ORACLE_HOME/bin/emctl reload
   

Step 6: Update mod_osso

1. Make sure the LD_LIBRARY_PATH environment variable contains $ORACLE_HOME/lib.

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

   $ORACLE_HOME/jdk/bin/java -jar $ORACLE_HOME/sso/lib/ossoreg.jar
   -oracle_home_path middle_tier_oracle_home
   -site_name middle_tier_hostname:new_http_port_number
   -config_mod_osso TRUE
   -mod_osso_url mod_osso_url
   -u user
   
   

   Note that user is the user that starts Oracle HTTP Server. By default, this is the user that installed Oracle Application Server. If you have changed the Oracle HTTP Server listen port number to a value < 1024, then this user is root.

   For example, if you want to change the Web Cache listener port to 7779 on middle-tier 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
   

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

Step 7: Update OracleAS Portal

If you have OracleAS Portal configured, update Portal with the new listener port number.

1. Using the Application Server Control, navigate to the Portal home page.

2. In the Administration section, click Portal Web Cache Settings.
   • If Listening Port SSL Enabled is set to No, update the Listening Port field with the new port number. Click OK.

   • If Listening Port SSL Enabled is set to Yes, you do not need to update anything on this page. Click Cancel.

Step 8: Update Web Providers with OracleAS Portal

If you are using Web Providers with OracleAS Portal, you must update them as follows (note that locally hosted Web Providers run on the same middle-tier instance as OracleAS Portal):

1. Log in to OracleAS Portal as the administrator (for example, PORTAL).

2. Click the Administrator tab.

3. Click the Portlets sub-tab.

4. Repeat this step for all locally hosted Web Providers registered in your Portal:
   1. In the Remote Providers portlet, enter the provider name (for example, WEBCLIPPING) in the Name field. Click Edit.

   2. Click the Connection tab.

   3. In the URL field, update the port to the new port number. Click OK.

Step 9: Update OracleAS Wireless

If you have OracleAS Wireless configured, update Wireless with the new port number:

1. Re-register Wireless with SSO by running the following command on the middle-tier host:

   ORACLE_HOME/wireless/bin/reRegisterSSO.sh new_wireless_url oracle_home 
   administrator_dn
   
   

   new_wireless_url: Wireless HTTP URL with the new Web Cache listener port.

   oracle_home: Middle-tier Oracle home whose Web Cache port you are changing.

   administrator_dn: OID administrator.

   For example, if you have changed the Web Cache listener port to 7779 on the middle-tier installation in /home/oracle on host myhost:

   ORACLE_HOME/wireless/bin/reRegisterSSO.sh http://myhost:7779/ptg/rm 
   /home/oracle cn=orcladmin
   
   

2. Update the Wireless HTTP configuration information:
   1. Navigate to the Wireless home page on Application Server Control.

   2. Select the Site Administration link.

   3. In the General Configuration section, select the HTTP, HTTPS Configuration link.

   4. In the URL section, update each URL that contains the non-SSL Web Cache listener port with the new port number.

   5. Click OK.

3. Update the instance URLs:
   1. Navigate to the Wireless home page on the Application Server Control.

   2. In the Instance Configuration Section, select the Instance URLs link.

   3. On the Instance URLs page:
      • If the Use the Wireless Site URLs radio button is selected, you do not need to make any changes to this page.

      • If the Use the WIreless Instance URLs radio button is selected, update each URL that contains the non-SSL Web Cache listener port with the new port number.

   4. Click OK.

Step 10: Update OracleAS Discoverer

If you have OracleAS Discoverer configured, and you are using the non-SSL port for the URL of the Discoverer Portlet Provider, edit the URL of the Discoverer Portlet Provider to use the new port number.

See Also: Refer to the instructions on "How to edit Discoverer Portlet Provider" in Oracle Application Server Discoverer Configuration Guide.

Step 11: Update OracleAS Reports Services

You do not need to make any configuration changes to Reports Service to reflect the change. However, if you have built any Web pages that contain links to the middle-tier Reports Service, you need to update those Web pages with the new port number.

Step 12: Restart the Middle-Tier Instance

Restart the middle-tier instance:

opmnctl stopall
opmnctl startall

5.3.5 Changing the Web Cache SSL Listener Port (Middle-Tier Installations)

This section describes how to change the Web Cache SSL listener port. It involves changing the Web Cache port number and updating other components in the middle tier with the new port number.

Step 1: Change the Web Cache SSL Listener Port

1. Using the Application Server Control, navigate to the Web Cache home page.

2. In the Administration section, click Web Cache Administration. Log in to Web Cache Administrator.

3. In the navigator frame, select Ports > Listen Ports. The Listen Ports page appears.

4. Select the port appropriate port that has HTTPS in the Protocol column. Click Edit Selected.

5. Enter the new port number in the Port field. Click Submit.

6. Click Apply Changes. It is not necessary to restart Web Cache at this time since you are going to restart the entire instance at the end of this procedure.

Step 2: Change the Web Cache Logical Site Port

If the Web Cache SSL listener port is the same as the logical site port, update the logical site port as follows:

1. In Web Cache Manager, in the navigator frame, select Origin Servers, Sites, and Load Balancing > Site Definitions.

2. On the Site Definitions page, locate the appropriate site using the old port number. If there is no site using the old port number, then the Web Cache listener and site do not share the same port number. Skip to Step 3: Enable Web Cache to Run as Root for Ports < 1024 on UNIX.

3. Select the appropriate site with the old port number. Click Edit Site.

4. In the Edit Site dialog box, enter the new port number. Click Submit.

5. In the navigator frame, select Origin Servers, Sites, and Load Balancing > Site-to-Server Mapping.

6. On the Site-to-Server Mapping page, you may see one or more mappings using the old port number. For each site:
   1. Select the site and click Edit Selected.

   2. In the Edit/Add Site-to-Server Mapping dialog box, change the Port Number field to the new port number. Click Submit.

7. Click Apply Changes.

Step 3: Enable Web Cache to Run as Root for Ports < 1024 on UNIX

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

1. Log in as the user that installed Oracle Application Server and stop Web Cache:

   opmnctl stopproc ias-component=WebCache
   
   

2. Log in as root.

3. Run the following command in the middle-tier Oracle home:

   ORACLE_HOME/webcache/bin/webcache_setuser.sh setroot userID
   
   

   Where userid is the current user Web Cache is running under. This is usually the user that installed Oracle Application Server. This user is listed on the Process Identity screen in Web Cache Manager.

4. Log in as the user that installed Oracle Application Server and start Web Cache:

   opmnctl startproc ias-component=WebCache
   

Step 4: Update the Oracle HTTP Server Port directive

1. Edit the following file:

   ORACLE_HOME/Apache/Apache/conf/ssl.conf
   
   

2. Update the SSL Port directive with the new port number. Do not modify the Listen directive. The Web Cache SSL port must equal the Oracle HTTP Server SSL Port directive.

3. Save the file.

4. Run the following command:

   dcmctl updateConfig -ct ohs
   

Step 5: Update Application Server Control

Update Application Server Control with the new port number:

1. Edit the following file:

   ORACLE_HOME/sysman/emd/targets.xml
   
   

2. Update each occurrence of the old Web Cache SSL listener port number with the new port number.

   Depending on your configuration, this file may not contain any occurrences of the Web Cache SSL listener port, or it may contain many occurrences. The listen port may occur as a parameter on its own, or it may be part of a URL. The easiest way to edit this file is to search for all occurrences of the old Web Cache SSL listener port number, and replace them with the new port number. Be sure to update only the Web Cache SSL listener port; do not update any other port numbers.

3. Save and close the file.

4. Reload the Application Server Control:

   ORACLE_HOME/bin/emctl reload
   

Step 6: Update mod_osso

If you have registered your SSL virtual host as an SSO partner application, follow these steps to re-register your SSL virtual host:

1. Make sure the LD_LIBRARY_PATH environment variable contains $ORACLE_HOME/lib.

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

   $ORACLE_HOME/jdk/bin/java -jar $ORACLE_HOME/sso/lib/ossoreg.jar
   -oracle_home_path middle_tier_oracle_home
   -site_name middle_tier_hostname:new_https_port_number
   -config_mod_osso TRUE
   -mod_osso_url mod_osso_url
   -virtualhost -u user
   
   

   Note that user is the user that starts Oracle HTTP Server. By default, this is the user that installed Oracle Application Server. If you have changed the Oracle HTTP Server listen port number to a value < 1024, then this user is root.

   For example, if you want to change the Web Cache SSL listen port to 4445 on middle-tier host myhost:

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

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

Step 7: Update OracleAS Portal

If you have OracleAS Portal configured, update Portal with the new SSL listener port number.

1. Using the Application Server Control, navigate to the Portal home page.

2. In the Administration section, click Portal Web Cache Settings.
   • If Listening Port SSL Enabled is set to Yes, update the Listening Port field with the new port number. Click OK.

   • If Listening Port SSL Enabled is set to No, you do not need to update anything on this page. Click Cancel.

3. Update the following file to use the new port number:

   ORACLE_HOME/Apache/modplsql/conf/dads.conf
   
   

4. Run the following command:

   dcmctl updateConfig
   
   

5. Update the httpsports parameter in the following file:

   ORACLE_HOME/j2ee/OC4J_Portal/applications/portal/portal/WEB-INF/web.xml
   

Step 8: Update Wireless

If you have Wireless configured, update Wireless with the new port number:

1. Re-register Wireless with SSO by running the following command on the middle-tier host:

   ORACLE_HOME/wireless/bin/reRegisterSSO.sh new_wireless_url oracle_home 
   administrator_dn
   
   

   new_wireless_url: Wireless HTTPS URL with the new Web Cache SSL listener port.

   oracle_home: Middle-tier Oracle home whose Web Cache port you are changing.

   administrator_dn: OID administrator.

   For example, if you have changed the Web Cache SSL listener port to 80 on the middle-tier installation in /home/oracle on host myhost:

   ORACLE_HOME/wireless/bin/reRegisterSSO.sh https://myhost:80/ptg/rm 
   /home/oracle cn=orcladmin
   
   

2. Update the Wireless HTTPS configuration information:
   1. Navigate to the Wireless home page on the Application Server Control.

   2. Select the Site Administration link.

   3. In the General Configuration section, select the HTTP, HTTPS Configuration link.

   4. In the URL section, update each URL that contains the SSL Web Cache listener port with the new port number.

   5. Click OK.

3. Update the instance URLs:
   1. Navigate to the Wireless home page on the Application Server Control.

   2. In the Instance Configuration Section, select the Instance URLs link.

   3. On the Instance URLs page:
      • If the Use the Wireless Site URLs radio button is selected, you do not need to make any changes to this page.

      • If the Use the WIreless Instance URLs radio button is selected, update each URL that contains the SSL Web Cache listener port with the new port number.

   4. Click OK.

Step 9: Update OracleAS Discoverer

If you have OracleAS Discoverer configured, and you are using the SSL port for the URL of the Discoverer Portlet Provider, edit the URL of the Discoverer Portlet Provider to use the new port number.

See Also: Refer to the instructions on "How to edit Discoverer Portlet Provider" in Oracle Application Server Discoverer Configuration Guide.

Step 10: Update OracleAS Reports Services

You do not need to make any configuration changes to Reports Services to reflect the change. However, if you have built any Web pages that contain links to the middle-tier Reports Service, you need to update those Web pages with the new port number.

Step 11: Restart the Middle-Tier Instance

Restart the middle-tier instance:

opmnctl stopall
opmnctl startall

5.3.6 Changing the Web Cache Administration Port

To change the Web Cache administration port on any installation type:

Step 1: Change the Web Cache Administration Port

1. Navigate to the Web Cache Manager using the following URL:

   http://web_cache_hostname:current_web_cache_admin_port/webcacheadmin
   
   

   For example:

   http://web_cache_hostname:4000/webcacheadmin
   
   

2. Log in to the Web Cache Manager as ias_admin or administrator.

3. In the navigator frame, select Ports > Operations Ports. The Operations Ports page appears.

4. Select the cache for which to modify the administration port. Click Edit Selected.

5. In the ADMINISTRATION row, change the Port Number field. Click Submit.

6. Click Apply Changes.

7. Exit out of the Web Cache Manager.

8. Restart Web Cache

   Note that you must restart from the command-line; do not use the Web Cache Manager to restart. You can restart in either of the following ways:

   • The preferred method is to restart your Web Cache server as follows:

     ORACLE_HOME/opmn/bin/opmnctl restartproc ias-component=WebCache
     
     

   • If you do not want to restart the Web Cache server, you can restart only the Web Cache Manager:

     ORACLE_HOME/opmn/bin/opmnctl restartproc process-type=WebCacheAdmin
     
     

     If you choose this method, Web Cache will operate properly, however, Web Cache Manager will display the following message until you restart the entire Web Cache server: "Restart Web Cache to make configuration changes take effect."

Step 2: Update Application Server Control

Update the Application Server Control with the new Web Cache administration port number as follows:

1. Edit the following file:

   ORACLE_HOME/sysman/emd/targets.xml
   
   

2. In the target type oracle_webcache, update the AdminPort property with the new port number.

3. Save and close the file.

4. Reload Oracle Enterprise Manager Application Server Control:

   ORACLE_HOME/bin/emctl reload
   

Step 3: Update OracleAS Portal

If the Web Cache is front-ending Portal, update Portal with the new administration port number:

1. Using the Application Server Control, navigate to the Portal home page.

2. In the Administration section, click Portal Web Cache Settings.

3. Update the Administration Port field with the new port number. Click OK.

5.3.7 Changing the Web Cache Invalidation Port

To change the Web Cache invalidation port on any installation type:

Step 1: Change the Web Cache Invalidation Port

1. Using the Application Server Control, navigate to the Web Cache home page.
   1. In the Administration section, click Web Cache Administration. Log in to Web Cache Administrator.

   2. In the navigator frame, select Ports > Operations Ports. The Operations Ports page appears.

   3. Select the cache for which to modify the invalidation port. Click Edit Selected.

   4. In the INVALIDATION row, change the Port Number field. Click Submit.

   5. Click Apply Changes.

   6. Click Restart.

Step 2: Update OracleAS Portal

If the Web Cache is front-ending Portal, update Portal with the new invalidation port number.

1. Using the Application Server Control, navigate to the Portal home page.

2. In the Administration section, click Portal Web Cache Settings.

3. Update the Invalidation Port field with the new port number. Click OK.

5.3.8 Changing the Web Cache Statistics Port

To change the Web Cache statistics port on any installation type:

1. Using the Application Server Control, navigate to the Web Cache home page.

2. In the Administration section, click Web Cache Administration. Log in to Web Cache Administrator.

3. In the navigator frame, select Ports > Operations Ports. The Operations Ports page appears.

4. Select the cache for which to modify the statistics port. Click Edit Selected.

5. In the STATISTICS row, change the Port Number field. Click Submit.

6. Click Apply Changes.

7. Click Restart.

5.3.9 Changing the DCM Java Object Cache Port

This section describes how to change the DCM Java Object Cache port number in any installation type. To change the DCM Java Object Cache port number:

1. Edit the following file:

   ORACLE_HOME/dcm/config/dcmCache.xml
   
   

2. Under the <communication> element, update the discovery-port parameter in the <coordinator> element with the new port number. For example:

   <coordinator discovery-port="7110" original="true" />
   
   

3. Save the file.

4. In every instance in the farm, stop Application Server Control and stop the DCM daemon:

   emctl stop iasconsole
   opmnctl stopproc ias-component=dcm-daemon
   
   

   It is important that you make sure all Application Server Control instances and DCM daemons in the farm are stopped before you proceed to the next step.

5. In every instance in the farm, start the DCM daemon and Application Server Control:

   opmnctl startproc ias-component=dcm-daemon
   emctl start iasconsole
   

5.3.10 Changing the Java Object Cache Port

This section describes how to change the Java Object Cache port number in any installation type. To change the Java Object Cache port number:

1. Edit the following file:

   ORACLE_HOME/javacache/admin/javacache.xml
   
   

2. Under the <communication> element, update the discovery-port parameter in the <coordinator> element with the new port number. For example:

   <coordinator discovery-port="7010" />
   
   

3. Save the file.

4. Restart all OC4J instances which contain J2EE applications that use JavaCache:

   dcmctl restart -co OC4J_INSTANCE
   

5.3.11 Changing the JServ Servlet Engine Port

This section describes how to change the JServ Servlet Engine port number in any installation type. To change the JServ Servlet Engine port:

1. Edit the following file:

   ORACLE_HOME/Apache/Jserv/etc/jserv.properties
   
   

2. Update the port parameter with the new port number.

3. Save the file.

4. Restart Oracle HTTP Server:

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

5.3.12 Changing the Log Loader Port

This section describes how to change the Log Loader port on any installation type. To change the Log Loader port:

1. Stop the Log Loader:
   1. In Application Server Control, navigate to the Application Server home page for the instance whose Log Loader port you would like to change.

   2. Click Logs in the upper-right corner.

   3. On the View Logs page, click Search Log Repository.

   4. On the View Logs page, click the Log Loader button.

   5. On the Log Loader page, click the Stop button.

2. Change the Log Loader port number:
   1. On the Log Loader page, in the Administration section, click Log Loader Properties.

   2. On the Log Loader Properties page, enter the new port number in the Log Loader Port field.

   3. Click Apply.

3. Start the Log Loader:
   1. At the top of the Log Loader Properties page, click Log Loader to get back to the Log Loader page.

   2. On the Log Loader page, click the Start button.

5.3.13 Changing OPMN Ports (ONS Local, Request, and Remote)

This section describes how to change any of the following port numbers:

• ONS Local port

• ONS Request port

• ONS Remote port

You can change ONS port using Application Server Control or manual steps:

• Using Application Server Control:
  1. Navigate to the Application Server home page and click Process Management.

  2. On the Process Management page, modify the local, remote, or request parameter, as desired, in the <port> element. For example:

     <port local="6101" remote="6201" request="6004"/>
     
     

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

  4. Restart OPMN and OPMN-managed processes:

     opmnctl stopall
     opmnctl startall
     
     

• Using Manual Steps:
  1. Edit the following file:

     ORACLE_HOME/opmn/conf/opmn.xml
     
     

  2. Under the <notification-server> element, modify the local, remote, or request parameter, as desired, in the <port> element. For example:

     <port local="6101" remote="6201" request="6004"/>
     
     

  3. Reload and restart OPMN and OPMN-managed processes:

     opmnctl reload
     opmnctl stopall
     opmnctl startall
     

5.3.14 Changing the Oracle HTTP Server Diagnostic Port

This section describes how to change the Oracle HTTP Server Diagnostics port number in any installation type. To change the Oracle HTTP Server Diagnostics port number:

1. Edit the following file:

   ORACLE_HOME/Apache/Apache/conf/dms.conf
   
   

2. Change the old port number to the new port number everywhere it appears in the file. This includes the Listen directive, OpmnHostPort directive, Redirect directive, and the Virtual Host.

3. Save the file.

4. Restart Oracle HTTP Server:

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

5.3.15 Changing the Port Tunneling Port

This section describes how to change the Port Tunneling port on any installation type. To change the Port Tunneling port number:

1. Edit the following file:

   ORACLE_HOME/opmn/conf/opmn.xml
   
   

2. Under the <ias-component id="IASPT"> element, update the range parameter in the <port> element with the new range. For example:

   <port id="ajp" range="7501-7503"/>
   
   

   Note that the port number range specified in opmn.xml overrides any port number specified in iaspt.conf. So you only need to update the port number in opmn.xml.

3. Restart OPMN:

   opmnctl reload
   opmnctl stopall
   opmnctl startall
   

5.4 Changing Portal and Wireless Ports

This section contains the following topics:

• Changing OracleAS Portal Ports

• Changing OracleAS Wireless Ports

5.4.1 Changing OracleAS Portal Ports

OracleAS Portal uses the Web Cache HTTP server port on the instance.

See Also: Section 5.3.4, "Changing the Web Cache Non-SSL Listener Port (Middle-Tier Installations)"

5.4.2 Changing OracleAS Wireless Ports

OracleAS Wireless uses the Web Cache HTTP server port on the instance.

See Also: Section 5.3.4, "Changing the Web Cache Non-SSL Listener Port (Middle-Tier Installations)"

5.5 Changing Business Intelligence and Forms Ports

This section contains the following topics:

• Changing OracleAS Discoverer Ports

• Changing OracleAS Forms Services Ports

• Changing the OracleAS Reports Services SQL*Net Port

5.5.1 Changing OracleAS Discoverer Ports

The OracleAS Discoverer OSAgent port cannot be changed after installation. Other OracleAS Discoverer services use the Web Cache HTTP server port on the instance.

See Also: Section 5.3.4, "Changing the Web Cache Non-SSL Listener Port (Middle-Tier Installations)"

5.5.2 Changing OracleAS Forms Services Ports

OracleAS Forms Services uses the Web Cache HTTP server port on the instance.

See Also: Section 5.3.4, "Changing the Web Cache Non-SSL Listener Port (Middle-Tier Installations)"

5.5.3 Changing the OracleAS Reports Services SQL*Net Port

To change the Reports Services SQL*Net port number:

1. On the Reports Services host, edit the tnsnames.ora file. The default location is:

   ORACLE_HOME/network/admin/tnsnames.ora
   
   

   In the REP_HOSTNAME entry, update the PORT parameter with the new port number.

2. On all client hosts, edit the tnsnames.ora file. In the REP_HOSTNAME entry, update the PORT parameter with the new port number.

5.6 Changing Infrastructure Ports

This section contains the following topics:

• Changing the Metadata Repository Net Listener Port

• Changing Oracle Internet Directory Ports

• Changing the HTTP Server (SSO) Port on Identity Management

• Changing OracleAS Certificate Authority Ports

5.6.1 Changing the Metadata Repository Net Listener Port

First, determine if it is necessary to change the Metadata Repository listener port number. If you are concerned about the fact that you have another database on your host using the same port, it is possible that the Metadata Repository and the other database can use the same port.

The following are guidelines for port usage by multiple databases on the same host:

• Multiple Oracle9i databases can share the same Net listener port. So, if the other databases on your host are Oracle9i databases, the Metadata Repository can all use port 1521 as the Net listener port. There is no need to change the port number.

• If the other databases on your system are Oracle8i databases running Oracle Net8 listener, then the Metadata Repository must use a different port. They cannot share the same port.

  Note: If you want to run two listeners that use the same key value on one host, refer to Section 5.6.1.1, "Changing the KEY value for an IPC Listener"

If you determine that you would like to change the Metadata Repository Listener Port, follow the steps in this section. A Metadata Repository may be used in several different ways. Use the following table to determine the steps that are required for changing your type of Metadata Repository:

If the Metadata Repository is used as follows:	Follow these steps to change its Net Listener port:
Identity Management Repository, Product Metadata Repository, and Management (DCM) Repository Registered with OID	Step 1: Make Sure OID and SSO Are Running Step 2: Change the Metadata Repository Net Listener Port Step 3: Update Oracle Internet Directory Step 4: Update Single Sign-On Step 5: Update OracleAS Certificate Authority Step 6: Update Application Server Control Step 8: Update the Middle-Tier Instances
Identity Management Repository only Registered with OID	Step 1: Make Sure OID and SSO Are Running Step 2: Change the Metadata Repository Net Listener Port Step 3: Update Oracle Internet Directory Step 4: Update Single Sign-On Step 5: Update OracleAS Certificate Authority Step 6: Update Application Server Control
Product Metadata and Management (DCM) Repository Registered with OID	Step 1: Make Sure OID and SSO Are Running Step 2: Change the Metadata Repository Net Listener Port Step 3: Update Oracle Internet Directory Step 8: Update the Middle-Tier Instances
Management (DCM) Repository only Not registered with OID	Step 2: Change the Metadata Repository Net Listener Port Step 7: Update DCM Schema Information

Step 1: Make Sure OID and SSO Are Running

If the Metadata Repository is registered with OID, make sure that the Identity Management instance (SSO and OID) is up and running before you proceed.

Step 2: Change the Metadata Repository Net Listener Port

On the Metadata Repository host:

1. Make sure your ORACLE_HOME environment variable and ORACLE_SID are set.

2. Stop the Metadata Repository listener:

   lscnrctl stop
   
   

3. Edit the following file:

   ORACLE_HOME/network/admin/listener.ora
   
   

   Under the LISTENER entry, update the value for PORT.

4. Edit the tnsnames.ora file. The default location is:

   ORACLE_HOME/network/admin/tnsnames.ora
   
   

   Update the PORT value in each entry that applies to the Metadata Repository.

5. Start the Metadata Repository listener:

   lsnrctl start
   

Step 3: Update Oracle Internet Directory

On the Identity Management host, update OID with the new Net Listener port number:

1. Start Oracle Directory Manager:

   ORACLE_HOME/bin/oidadmin
   
   

2. Log in to Oracle Directory Manager.

3. In the System Objects frame:
   1. Expand Entry Management.

   2. Expand cn=Oracle Context.

   3. Select the DBName for the Metadata Repository. For example, if the DBName is the default, asdb, select cn=ASDB.

4. On the Properties tab, update the PORT parameter in the orclnetdescstring field with the new port number.

5. Click Apply.

Step 4: Update Single Sign-On

On the SSO host:

1. Make sure the LD_LIBRARY_PATH environment variable contains $ORACLE_HOME/lib.

2. Update Single-Sign on with the new repository port number by running the following command in the SSO Oracle home:

   ORACLE_HOME/jdk/bin/java -jar $ORACLE_HOME/sso/lib/ossoca.jar reassoc -repos 
   $ORACLE_HOME
   

Step 5: Update OracleAS Certificate Authority

If the Identity Management installation has OracleAS Certificate Authority:

1. Launch the OracleAS Certificate Authority management GUI:

   https://infrastructure_hostname:http_ssl_port/oca/admin
   
   

   Where http_ssl_port is the HTTP SSL listener port.

2. Select the Configuration Management tab.

3. Select the General sub-tab.

4. Under Database Settings, update the Database Connect String with the new port number.

Step 6: Update Application Server Control

Update Application Server Control with the new port number:

1. In the Identity Management Oracle home, edit the following file:

   ORACLE_HOME/sysman/emd/targets.xml
   
   

2. Update the old Metadata Repository port number with the new port number.

   Locate the oracle_ldap target and update the PORT parameter in the ConnectDescriptor value with the new port number. The easiest way to find this is to search the file for the old port number.

3. Save and close the file.

4. Reload Application Server Control:

   ORACLE_HOME/bin/emctl reload
   

Step 7: Update DCM Schema Information

In each middle-tier Oracle home uses the Metadata Repository for its Management (DCM) schema:

1. Edit the following file:

   ORACLE_HOME/config/iasschema.xml
   
   

2. Locate the <SchemaConfigData> entry for the DCM schema.

3. In this entry, update the <DBConnect> entry with the new port number.

4. Save and close the file.

5. Restart the DCM daemon:

   opmnctl restartproc ias-component=dcm-daemon
   

Step 8: Update the Middle-Tier Instances

In each middle-tier Oracle home that uses the Metadata Repository, update the following file with the new Net Listener port number:

ORACLE_HOME/network/admin/tnsnames.ora

5.6.1.1 Changing the KEY value for an IPC Listener

It is not possible to run two listeners at the same time that are configured to use the same KEY value in their IPC protocol address. By default, the OracleAS Metadata Repository listener has its IPC KEY value set to EXTPROC. Hence, if your computer has another IPC listener that uses the EXTPROC key, you should configure the Metadata Repository listener to use some other key value such as EXTPROC1.

To change the KEY value of an IPC listener:

1. Stop the listener:

   ORACLE_HOME/bin/lsnrctl stop
   
   

2. Edit the listener.ora and tnsnames.ora files. In each file, change the line that says:

   (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC))
   
   

   to something like:

   (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
   
   

3. Restart the listener:

   ORACLE_HOME/bin/lsnrctl start
   

5.6.2 Changing Oracle Internet Directory Ports

This section describes how to change the Oracle Internet Directory port on an Identity Management installation. When you change this port number, you must update any middle-tier instances that use the Identity Management installation.

The following procedures contain complete instructions for updating the Oracle Internet Directory port number on Identity Management, including updating other components in the Infrastructure and updating the middle-tier instances that use the port:

• Changing the Oracle Internet Directory Non-SSL Port

• Changing the Oracle Internet Directory SSL Port

5.6.2.1 Changing the Oracle Internet Directory Non-SSL Port

This procedure describes how to change the Oracle Internet Directory non-SSL port on an Identity Management installation. Review all steps before you begin.

Step 1: Prepare the Middle-Tier Instances

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

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

2. Leave Application Server Control running.

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

Step 2: Prepare the Infrastructure Instances

1. Make sure that Identity Management and its associated Metadata Repository are up and running 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, make sure those are up. In short, make sure all Metadata Repositories in your environment are up.

Step 3: Change the Oracle Internet Directory port

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

      dn:cn=configset0, cn=osdldapd, cn=subconfigsubentry
      changetype:modify
      replace:orclnonsslport
      orclnonsslport:new_port_number
      
      

   2. Run the following command:

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

   3. On the Oracle Internet Directory host, restart OID:

      opmnctl stopproc ias-component=OID
      opmnctl startproc ias-component=OID
      
      

2. Perform this step in the Oracle Internet Directory Oracle home. If you have Metadata Repositories installed in other Oracle homes that are registered with this Oracle Internet Directory, perform this step in each of those Oracle homes as well.
   1. Edit the following file:

      ORACLE_HOME/network/admin/ldap.ora
      
      

      Modify the following line to contain the new non-SSL port number:

      DIRECTORY_SERVERS=(myhost.myco.com:non_ssl_port:ssl_port)
      
      

      Save and close the file.

   2. Edit the following file:

      ORACLE_HOME/config/ias.properties
      
      

      Change the value of OIDport to the new non-SSL port number.

      Save and close the file.

3. Perform this step in the SSO Oracle home:
   1. Make sure the LD_LIBRARY_PATH environment variable contains $ORACLE_HOME/lib.

   2. Run the following command in the SSO Oracle home:

      ORACLE_HOME/jdk/bin/java -jar $ORACLE_HOME/sso/lib/ossoca.jar reassoc 
      -repos $ORACLE_HOME
      

Step 4: Reconfigure OracleAS Certificate Authority

Follow this step if you are using OCA:

1. If OCA is running in a different Oracle home, do the following step in the OCA Oracle home:
   1. Edit the following file:

      ORACLE_HOME/config/ias.properties
      
      

   1. Change the value of OIDport to the new non-SSL port number.

   2. Save and close the file.

2. Update OCA with the new OID port number by running the following command in the OCA Oracle home:

   ORACLE_HOME/oca/bin/ocactl changesecurity -server_auth_port port_number
   
   

   Where port_number is the OCA Server Authentication Virtual Host (SSL) port; the default is 4400.

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

Step 5: Restart the Identity Management Instance

Restart the Identity Management instance:

emctl stop iasconsole
opmnctl stopall
opmnctl startall
emctl start iasconsole

Step 6: Update the Middle-Tier Instances to Use the New Port Number

On each middle-tier instance that uses the Identity Management installation, run the Change Identity Management Services wizard and start the instance:

1. On Application Server Control, 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 for supplying the new Identity Management information (the new port number).

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

5.6.2.2 Changing the Oracle Internet Directory SSL Port

This procedure describes how to change the Oracle Internet Directory SSL port on an Identity Management installation. Review all steps before you begin.

Step 1: Prepare the Middle-Tier Instances

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

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

2. Leave Application Server Control running.

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

Step 2: Prepare the Infrastructure Instances

1. Make sure that Identity Management and its associated Metadata Repository are up and running 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, make sure those are up. In short, make sure all Metadata Repositories in your environment are up.

Step 3: Change the Oracle Internet Directory port

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

      dn:cn=configset0, cn=osdldapd, cn=subconfigsubentry
      changetype:modify
      replace:orclsslport
      orclsslport:new_ssl_port_number
      
      

   2. Run the following command:

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

   3. On the Oracle Internet Directory host, restart OID:

      opmnctl stopproc ias-component=OID
      opmnctl startproc ias-component=OID
      
      

2. Perform this step in the Oracle Internet Directory Oracle home. If you have Metadata Repositories installed in other Oracle homes that are registered with this Oracle Internet Directory, perform this step in each of those Oracle homes as well.
   1. Edit the following file:

      ORACLE_HOME/network/admin/ldap.ora
      
      

      Modify the following line to contain the new SSL port number:

      DIRECTORY_SERVERS=(myhost.myco.com:non_ssl_port:ssl_port)
      
      

      Save and close the file.

   2. Edit the following file:

      ORACLE_HOME/config/ias.properties
      
      

      Change the value of OIDsslport to the new SSL port number.

      Save and close the file.

3. Perform this step in the SSO Oracle home:
   1. Make sure the LD_LIBRARY_PATH environment variable contains $ORACLE_HOME/lib.

   2. Run the following command in the SSO Oracle home:

      ORACLE_HOME/jdk/bin/java -jar $ORACLE_HOME/sso/lib/ossoca.jar reassoc 
      -repos $ORACLE_HOME
      

Step 4: Reconfigure OracleAS Certificate Authority

Follow this step if you are using OCA:

1. If OCA is running in a different Oracle home, perform the following step in the OCA Oracle home:
   1. Edit the following file:

      ORACLE_HOME/config/ias.properties
      
      

   1. Change the value of OIDsslport to the new SSL port number.

   2. Save and close the file.

2. Update OCA with the new OID port number by running the following command in the OCA Oracle home:

   ORACLE_HOME/oca/bin/ocactl changesecurity -server_auth_port port_number
   
   

   Where port_number is the OCA Server Authentication Virtual Host (SSL) port; the default is 4400.

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

Step 5: Restart the Identity Management Instance

Restart the Identity Management instance:

emctl stop iasconsole
opmnctl stopall
opmnctl startall
emctl start iasconsole

Step 6: Update the Middle-Tier Instances to Use the New Port Number

On each middle-tier instance that uses the Identity Management installation, run the Change Identity Management Services wizard and start the instance:

1. On Application Server Control, 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 for supplying the new Identity Management information (the new port number).

5. When the wizard is finished, navigate to the Instance Home Page and start your instance by clicking Start All.

5.6.3 Changing the HTTP Server (SSO) Port on Identity Management

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

The following procedures contain complete instructions for updating the Oracle HTTP Server port number on Identity Management, including updating other components in the Infrastructure and updating the middle-tier instances that use the port:

• Changing the Oracle HTTP Server Non-SSL Listen Port on Identity Management

• Changing the Oracle HTTP Server SSL Listen Port on Identity Management

5.6.3.1 Changing the Oracle HTTP Server Non-SSL Listen Port on Identity Management

This procedure describes how to change the non-SSL listen port on an Identity Management installation. When you do this, you must update both the Listen and Port directives with the new port number.

Step 1: Prepare the Middle-Tier Instances

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

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

2. Leave Application Server Control running.

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

Step 2: Prepare the Infrastructure Instances

1. Make sure that Identity Management and its associated Metadata Repository are up and running 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, make sure those are up. In short, make sure all Metadata Repositories in your environment are up.

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

Change both the Listen and Port directive to the new port number. You can perform this step using Application Server Control or manual steps.

• Using the Application Server Control:
  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.

• Using Manual Steps:
  1. Edit the following file:

     ORACLE_HOME/Apache/Apache/conf/httpd.conf
     
     

  2. Update the non-SSL Listen and Port directives with the new port number. The value for Listen and Port must be the same port number, for example, to change the listener port to 7779:

     Listen 7779
     Port 7779
     
     

     There may be multiple Listen and Port directives in this file. Modify the Listen and Port directives that are not enclosed in an SSL virtual host container. The easiest way to locate the proper Listen and Port directives is to search the file for the old port number.

  3. Save and close the file.

  4. Run the following command:

     dcmctl updateConfig -ct ohs
     

Step 4: Enable Oracle HTTP Server to Run as Root for Ports < 1024 on UNIX

Perform this step if you are changing the port to a value less than 1024.

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, 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
   

Step 5: Update Application Server Control

Update Application Server Control with the new port number:

1. Edit the following file:

   ORACLE_HOME/sysman/emd/targets.xml
   
   

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

   Depending on your configuration, this file may not contain any occurrences of the Oracle HTTP Server listen port, or it may contain many occurrences. The listen port may occur as a parameter on its own, or it may be part of a URL. The easiest way to edit this file is to search for all occurrences of the old Oracle HTTP Server listen port number, and replace them with the new port number.

3. Save and close the file.

4. Reload Application Server Control:

   ORACLE_HOME/bin/emctl reload
   

Step 6: Update Single Sign-On

Perform this step if SSO is configured to use the non-SSL Oracle HTTP Server listen port in the installation where you are changing the port.

1. Make sure the LD_LIBRARY_PATH environment variable contains $ORACLE_HOME/lib.

2. Run the following command in the SSO Oracle home:

   ORACLE_HOME/sso/bin/ssocfg.sh http hostname new_port_number
   
   

   Where:

   hostname is the host on which SSO is running

   new_port_number is the new non-SSL Oracle HTTP Server listen port number

Step 7: Re-register mod_osso

Re-register mod_osso as follows:

1. Make sure the LD_LIBRARY_PATH environment variable contains $ORACLE_HOME/lib.

2. Re-register mod_osso to take care of the default partner applications by running the following command in the Identity Management Oracle home:

   $ORACLE_HOME/jdk/bin/java -jar $ORACLE_HOME/sso/lib/ossoreg.jar
   -oracle_home_path middle_tier_oracle_home
   -site_name middle_tier_hostname:new_http_port_number
   -config_mod_osso TRUE
   -mod_osso_url mod_osso_url
   -u user
   
   

   Note that user is the user that starts Oracle HTTP Server. By default, this is the user that installed Oracle Application Server. If you have changed the Oracle HTTP Server listen port number to a value < 1024, then this user is root.

   For example, if you want 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
   
   

3. If you have configured or modified any additional partner applications, you must also re-register those.

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

Step 8: Update DAS

If you have DAS configured, and DAS uses the non-SSL port number, follow these steps to update the DAS URL entry in Oracle Internet Directory.

Note: You can find out what port DAS uses with the following command:

ORACLE_HOME/bin/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:

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

3. Refresh the OID cache in your applications:
   1. Log in to the Portal.

   2. Click on the global settings link.

   3. Click the OID/DAS tab.

   4. Check the refresh OID cache settings and click Apply.

Step 9: Update Oracle Application Server Certificate Authority

If you are using OracleAS Certificate Authority:

1. Re-register OCA with the SSO server by running the following command in the OCA Oracle home:

   ORACLE_HOME/oca/bin/ocactl changesecurity -server_auth_port port_number
   
   

   Where port_number is the OCA Server Authentication Virtual Host (SSL) port; the default is 4400.

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

2. If OCA is located in a different Oracle home than the SSO server, restart Oracle HTTP Server and the oca instance in the OCA Oracle home:

   opmnctl stopproc ias-component=HTTP_Server
   opmnctl stopproc process-type=oca
   opmnctl startproc ias-component=HTTP_Server
   opmnctl startproc process-type=oca
   

Step 10: Restart the Identity Management Instance:

Restart the Identity Management instance:

opmnctl stopall
opmnctl startall

Step 11: Restart OracleAS Certificate Authority

If OCA is configured in this instance, restart it:

ORACLE_HOME/oca/bin/ocactl start

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

On each middle-tier instance that uses the Identity Management installation, run the Change Identity Management Services wizard and start the instance:

1. On Application Server Control, 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 for supplying the new Identity Management information (the new port number).

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

5.6.3.2 Changing the Oracle HTTP Server SSL Listen Port on Identity Management

This procedure describes how to change the SSL listen port on an Identity Management installation. When you do this, you must update both the SSL Listen and SSL Port directives with the new port number.

Step 1: Prepare the Middle-Tier Instances

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

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

2. Leave Application Server Control running.

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

Step 2: Prepare the Infrastructure Instances

1. Make sure that Identity Management and its associated Metadata Repository are up and running 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, make sure those are up. In short, make sure all Metadata Repositories in your environment are up.

Step 3: Modify the Oracle HTTP Server SSL Listen and SSL Port Directives

Change both the SSL Listen and SSL Port directives to the new port number. You must do this using manual steps.

1. Edit the following file:

   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, for example, to change the listener port to 4445:

   Listen 4445
   Port 4445
   
   

3. Save and close the file.

4. Run the following command:

   dcmctl updateConfig -ct ohs
   

Step 4: Enable Oracle HTTP Server to Run as Root for Ports < 1024 on UNIX

Perform this step if you are changing the port to a value less than 1024.

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, 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
   

Step 5: Update Application Server Control

Update Application Server Control with the new port number:

1. Edit the following file:

   ORACLE_HOME/sysman/emd/targets.xml
   
   

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

   Depending on your configuration, this file may not contain any occurrences of the Oracle HTTP Server SSL listen port, or it may contain many occurrences. The listen port may occur as a parameter on its own, or it may be part of a URL. The easiest way to edit this file is to search for all occurrences of the old Oracle HTTP Server SSL listen port number, and replace them with the new port number. Be sure to update only the Oracle HTTP Server SSL listen port; do not update the Oracle HTTP Server non-SSL listen port or any other port numbers.

3. Save and close the file.

4. Reload Application Server Control:

   ORACLE_HOME/bin/emctl reload
   

Step 6: Update Single Sign-On

Perform this step if SSO is configured to use the non-SSL Oracle HTTP Server listen port in the installation where you are changing the port.

1. Make sure the LD_LIBRARY_PATH environment variable contains $ORACLE_HOME/lib.

2. If SSO is configured to use the SSL Oracle HTTP Server listen port in the installation where the listen port is being changed, run the following command in the SSO Oracle home:

   ORACLE_HOME/sso/bin/ssocfg.sh https hostname new_port_number
   
   

   Where:

   hostname is the host on which SSO is running

   new_port_number is the new SSL Oracle HTTP Server listen port number

Step 7: Re-register mod_osso

Re-register mod_osso as follows:

1. Make sure the LD_LIBRARY_PATH environment variable contains $ORACLE_HOME/lib.

2. Re-register mod_osso to take care of the default partner applications by running the following command in the Identity Management Oracle home:

   $ORACLE_HOME/jdk/bin/java -jar $ORACLE_HOME/sso/lib/ossoreg.jar
   -oracle_home_path middle_tier_oracle_home
   -site_name middle_tier_hostname:new_https_port_number
   -config_mod_osso TRUE
   -mod_osso_url mod_osso_url
   -virtualhost -u user
   
   

   Note that user is the user that starts Oracle HTTP Server. By default, this is the user that installed Oracle Application Server. If you have changed the Oracle HTTP Server listen port number to a value < 1024, then this user is root.

   For example, if you want to change the Oracle HTTP Server listen port to 4445 on host myhost:

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

3. If you have configured or modified any additional partner applications, you must also re-register those.

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

Step 8: Update DAS

If you have DAS configured, and DAS uses the SSL port number, update the DAS URL entry in Oracle Internet Directory.

Note: You can find out what port DAS uses with the following command:

ORACLE_HOME/bin/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:https://hostname:new_https_port_number/
   
   

   Note the slash at the end of the orcldasurlbase URL.

2. Run the following command:

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

3. Refresh the OID cache in your applications:
   1. Log in to the Portal.

   2. Click on the global settings link.

   3. Click the OID/DAS tab.

   4. Check the refresh OID cache settings and click Apply.

Step 9: Update Oracle Application Server Certificate Authority

If you are using OracleAS Certificate Authority:

1. Re-register OCA with the SSO server by running the following command in the OCA Oracle home:

   ORACLE_HOME/oca/bin/ocactl changesecurity -server_auth_port port_number
   
   

   Where port_number is the OCA Server Authentication Virtual Host (SSL) port; the default is 4400.

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

2. If OCA is located in a different Oracle home from the SSO server, restart Oracle HTTP Server and the oca instance in the OCA Oracle home:

   opmnctl stopproc ias-component=HTTP_Server
   opmnctl stopproc process-type=oca
   opmnctl startproc ias-component=HTTP_Server
   opmnctl startproc process-type=oca
   

Step 10: Restart the Identity Management Instance

Restart the Identity Management instance:

opmnctl stopall
opmnctl startall

Step 11: Restart OracleAS Certificate Authority

If OCA is configured in this instance, restart it:

ORACLE_HOME/oca/bin/ocactl start

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

On each middle-tier instance that uses the Identity Management installation, run the Change Identity Management Services wizard and start the instance:

1. On Application Server Control, 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 for supplying the new Identity Management information (the new port number).

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

5.6.4 Changing OracleAS Certificate Authority Ports

This section describes how to change the following port numbers:

• OracleAS Certificate Authority Server Authentication Virtual Host (SSL)

• OracleAS Certificate Authority Mutual Authentication Virtual Host (SSL)

To change either of these port numbers:

1. Edit the following file in the Oracle home of the Infrastructure that contains OracleAS Certificate Authority:

   ORACLE_HOME/Apache/Apache/conf/ocm_apache.conf
   
   

   1. Modify the Server or Mutual port, or both. Note that each port number is listed in the file in two places:
      • As a Listen directive

      • As a default virtual host

      The easiest way to find these is to search for the old port number.

   2. Save and close the file.

   3. Run the following command:

      dcmctl updateConfig -ct ohs
      
      

2. Run the following command:

   sqlplus oca/oca_admin_password @$ORACLE_HOME/oca/sql/ocaportchg
   
   

   1. Enter the Server Authentication Only port when prompted. If you do not want to change this port number, enter the old port number.

   2. Enter the Mutual Authentication port when prompted. If you do not want to change this port number, enter the old port number.

3. Re-register OCA with the SSO server by running the following command in the OCA Oracle home:

   ORACLE_HOME/oca/bin/ocactl changesecurity -server_auth_port port_number
   
   

   Where port_number is the OCA Server Authentication Virtual Host (SSL) port; the default is 4400.

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

4. Restart Oracle HTTP Server:

   opmnctl restartproc type=ohs
   
   

5. Restart the OCA OC4J instance:

   opmnctl restartproc type=oc4j instancename=oca
   
   

6. Start Oracle Application Server Certificate Authority:

   ORACLE_HOME/oca/bin/ocactl start