4 Managing Ports

4.3.1 Changing Oracle Enterprise Manager Ports

After you have installed Oracle Application Server, you can change the following Oracle Enterprise Manager 10g ports associated with your Oracle Application Server instance:

• The Oracle Management Agent port, which is used for communications with the Management Agent

• The Application Server Control Console port, which is used in the Application Server Control Console URL. For example, on UNIX:

  http://appserver1.acme.com:1156
  
  

• The Oracle Application Server Containers for J2EE (OC4J) Remote Method Invocation (RMI) port, which is used by the Application Server Control OC4J instance

To view the current port values for these components, as well as the valid port number range for each component, navigate to the Ports page from the Application Server Home page for the instance.

However, you cannot modify the Enterprise Manager port numbers from the Ports page. Instead, use the following procedure to change the Application Server Control ports:

1. Change directory to the bin directory in the Oracle Application Server Oracle home.

2. Stop the Application Server Control Console.

   On UNIX systems, enter the following command:

   ORACLE_HOME/bin/emctl stop iasconsole
   
   

   On Windows systems, use the Services control panel to stop the Application Server Control service.

3. Use the following command to change one of the Enterprise Manager port values:

   (UNIX) ORACLE_HOME/bin/emctl config {agent port | iasconsole {port | rmiport}} port_number
   (Windows) ORACLE_HOME\bin\emctl config {agent port | iasconsole {port | rmiport}} port_number
   
   

   For example, to change the port used by the Application Server Control Console on UNIX:

   ORACLE_HOME/bin/emctl config iasconsole port 1812
   
   

4. Start Application Server Control.

   On UNIX systems, enter the following command:

   ORACLE_HOME/bin/emctl start iasconsole
   
   

   On Windows systems, use the Services control panel to start the Application Server Control service.

Table 4-1 describes the configuration changes that are automatically performed when you use the emctl config command to change an Application Server Control port number.

emctl config iasconsole port port_number

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

(UNIX) ORACLE_HOME/sysman/j2ee/config/emd-web-site.xml 
(Windows)ORACLE_HOME\sysman\j2ee\config\emd-web-site.xml

emctl config agent port port_number

(UNIX) ORACLE_HOME/sysman/config/emd.properties 
(Windows) ORACLE_HOME\sysman\config\emd.properties 

emctl config iasconsole rmiport port_number

(UNIX) ORACLE_HOME/sysman/j2ee/config/rmi.xml 
(Windows) ORACLE_HOME\sysman\j2ee\config\rmi.xml

(UNIX) ORACLE_HOME/bin/emctl.pl
(Windows) ORACLE_HOME\bin\emctl.pl 

4.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 use a single port number for each type of OC4J port. Instead, it uses a port range for each type of OC4J port and that range is the same for all OC4J instances on the host. During runtime, each OC4J instance on the host is assigned a single free port from the range. For example, if the default AJP range for every OC4J instance on a host is 12501-12600, then each OC4J instance is assigned a single free port from that range for its AJP port.

When changing an OC4J port number, you typically specify a new port range. The range may be a simple port range (12501-12600), a comma separated list of ports (12501, 12504, 12507), or a combination of both (12501-12580, 12583, 12590-12600). By default, the ranges contain 100 ports. If you specify a range that is too narrow, you may encounter problems when starting OC4J instances. The AJP and RMI port ranges are required; the others are optional.

You can change OC4J port ranges using the Application Server Control Console or manual steps:

• Using the Application Server Control Console:

  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 want 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 want to restart now.

• Using manual steps:

  1. Open the opmn.xml file:

     (UNIX) ORACLE_HOME/opmn/conf/opmn.xml
     (Windows) ORACLE_HOME\opmn\conf\opmn.xml
     
     

  2. Locate the element for the OC4J instance that contains the port range you want to change. For example, if you want to change a port range 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="12501-12600"/>
     <port id="rmi" range="12401-12500"/>
     <port id="jms" range="12601-12700"/>
     <port id="iiop" range="13301-13400"/>
     <port id="iiops1" range="13401-13500"/>
     <port id="iiops2" range="13501-13600"/>
     
     

  4. Modify the range parameter for the port you want to change, and then save the file.

  5. Reload OPMN:

     (UNIX) ORACLE_HOME/opmn/bin/opmnctl reload
     (Windows) ORACLE_HOME\opmn\bin\opmnctl reload
     
     

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

     (UNIX) ORACLE_HOME/opmn/bin/opmnctl startproc process-type=OC4J_instance
     (Windows) ORACLE_HOME\opmn\bin\opmnctl startproc process-type=OC4J_instance
     
     

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

     ORACLE_HOME/opmn/bin/opmnctl startproc process-type=home
     
     

  7. Run the following command:

     (UNIX) ORACLE_HOME/dcm/bin/dcmctl updateConfig 
     (Windows) ORACLE_HOME\dcm\bin\dcmctl updateConfig
     

4.3.3 Changing the Oracle HTTP Server Listen Ports

To change the Oracle HTTP Server Listen ports, you change the Oracle HTTP Server Listen directive. When you do this, 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, 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 topics describe how to define the portconfig command and then use it to modify the Oracle HTTP Server HTTP or HTTPS listen port:

• Task 1: Enable Oracle HTTP Server to Run as Root for Ports Set to Less Than 1024 (Unix Only)

• Task 2: Use the portconfig Command to Change the Oracle HTTP Server Listen Ports

• Task 3: Update the portlist.ini File

• Task 4: Restart Oracle HTTP Server

Task 1: Enable Oracle HTTP Server to Run as Root for Ports Set to Less Than 1024 (Unix Only)

If you are on a UNIX system and you are changing the Listen port to a number less than 1024, perform these steps before you change the Oracle HTTP Server Listen port.

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 HTTP Server 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
   

Task 2: Use the portconfig Command to Change the Oracle HTTP Server Listen Ports

Use the following procedure to change the Oracle HTTP Server HTTP or HTTPS listen port:

1. Set the ORACLE_HOME environment variable to the home directory of the Oracle Application Server instance where the Oracle HTTP Server resides.

   For example:

   (UNIX) setenv ORACLE_HOME /dev0/private/oracle/appserv1/ 
   (Windows) set ORACLE_HOME=D:\oracle\appserv1\ 
   
   

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

3. Create an alias (on UNIX systems) or a DOSKEY macro (on Windows systems) to represent the portconfig command.

   For example, to execute the command as an alias on UNIX systems, enter the following command:

   alias portconfig '$ORACLE_HOME/jdk/bin/java -cp 
   $ORACLE_HOME/sysman/webapps/emd/WEB-INF/lib/emd.jar:
   $ORACLE_HOME/dcm/lib/dcm.jar:
   $ORACLE_HOME/sso/lib/ossoreg.jar
   oracle.sysman.ias.sta.tools.PortConfigCmdLine \!*'
   
   

   Similarly, to execute the command as DOSKEY macro on Windows systems, enter the following at the DOS command line:

   doskey portconfig=%ORACLE_HOME%\jdk\bin\java -cp 
   %ORACLE_HOME%/sysman/webapps/emd/WEB-INF/lib/emd.jar;
   %ORACLE_HOME%/dcm/lib/dcm.jar;
   %ORACLE_HOME%/sso/lib/ossoreg.jar
   oracle.sysman.ias.sta.tools.PortConfigCmdLine $*
   
   

4. Use the newly created portconfig command as follows:

   portconfig -oracleHome ORACLE_HOME 
   -oldPort old_port 
   -newPort new_port 
   [-sso -url http://sso_host:port -user http_server_admin_user 
     [-site name_of_sso_partner_application]
     [-admin mod_osso_admin_user]
     [-vHost path_to_mod_osso_configuration_file]]
   [-webCache] [-debug]
   {-start | -restart}
   
   

   For example, on UNIX systems:

   portconfig -oracleHome $ORACLE_HOME -oldPort 7777 -newPort 7778 -webCache
   
   

   For example, on Windows systems:

   portconfig -oracleHome %ORACLE_HOME% -oldPort 80 -newPort 7778 -webCache
   
   

Table 4-2 describes the arguments available when you use the portconfig command to automatically change the Oracle HTTP Server Listen port.

http://sso42.acme.com:7778

ORACLE_HOME/Apache/Apache/conf/osso/vh_name/osso.conf

Task 3: Update the portlist.ini File

After you change the Oracle HTTP Server Listen Port, you should update portlist.ini with the new port number. This will avoid potential problems if you later associate the middle tier with an OracleAS Infrastructure or change the OracleAS Infrastructure associated with the middle tier. The portlist.ini file is located in the following directory:

(UNIX) ORACLE_HOME/install
(Windows) ORACLE_HOME\install

Task 4: Restart Oracle HTTP Server

Restart the application server instance:

• On UNIX systems:

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

• On Windows systems:

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

4.3.4 Changing the Oracle HTTP Server Diagnostic Port

To change the Oracle HTTP Server Diagnostics port number in any installation type:

1. Open the dms.conf file:

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

2. Change the old port number to the new port number everywhere it appears in the file, and then save the file. This update includes the Listen directive, OpmnHostPort directive, Redirect directive, and the VirtualHost.

3. Restart Oracle HTTP Server:

   (UNIX) ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=HTTP_Server
   (UNIX) ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=HTTP_Server
   
   (Windows) ORACLE_HOME\opmn\bin\opmnctl stopproc ias-component=HTTP_Server
   (Windows) ORACLE_HOME\opmn\bin\opmnctl startproc ias-component=HTTP_Server 
   

4.3.5 Changing OracleAS Web Cache Ports

The following sections describe how to change the OracleAS Web Cache ports:

• Changing the OracleAS Web Cache Listen Ports

• Changing theOracleAS Web Cache Administration Port

• Changing the OracleAS Web Cache Invalidation Port

• Changing the OracleAS Web Cache Statistics Port

4.3.6 Changing the DCM Discovery Port

To change the DCM Discovery port number in any installation type:

1. Open the dcmCache.xml file:

   (UNIX) ORACLE_HOME/dcm/config/dcmCache.xml
   (Windows) 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, and then save the file.

   For example:

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

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

   • On UNIX systems:

     ORACLE_HOME/bin/emctl stop iasconsole
     ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=dcm-daemon
     
     

   • On Windows systems:

     ORACLE_HOME\bin\emctl stop iasconsole
     ORACLE_HOME\opmn\bin\opmnctl stopproc ias-component=dcm-daemon
     
     

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

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

   • On UNIX systems:

     ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=dcm-daemon
     ORACLE_HOME/bin/emctl start iasconsole
     
     

   • On Windows systems:

     ORACLE_HOME\opmn\bin\opmnctl startproc ias-component=dcm-daemon
     ORACLE_HOME\bin\emctl start iasconsole
     

4.3.7 Changing the Java Object Cache Port

To change the Java Object Cache port number in any installation type:

1. Open the javacache.xml file:

   (UNIX) ORACLE_HOME/javacache/admin/javacache.xml
   (Windows) 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, and then save the file.

   For example:

   <coordinator discovery-port="7010" />
   
   

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

   (UNIX) ORACLE_HOME/dcm/bin/dcmctl restart -co OC4J_INSTANCE
   (Windows) ORACLE_HOME\dcm\bin\dcmctl restart -co OC4J_INSTANCE
   

4.3.8 Changing the Log Loader Port

To change the Log Loader port in any installation type:

1. Stop the Log Loader:

   1. Using the Application Server Control Console, navigate to the Home page for the instance whose Log Loader port you want 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 Log Loader.

   5. On the Log Loader page, click Stop.

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

4.3.9 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

To change these ports:

1. Stop the Application Server Control Console, OPMN and all OPMN-managed processes:

   • On UNIX systems:

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

   • On Windows systems:

     ORACLE_HOME\bin\emctl stop iasconsole
     ORACLE_HOME\opmn\bin\opmnctl stopall
     
     

2. Open the opmn.xml file:

   (UNIX) ORACLE_HOME/opmn/conf/opmn.xml
   (Windows) ORACLE_HOME\opmn\conf\opmn.xml
   
   

3. Under the <notification-server> element, modify the local, remote, or request parameter, as desired, in the <port> element, and then save the file.

   For example:

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

4. Start OPMN:

   (UNIX) ORACLE_HOME/opmn/bin/opmnctl start
   (Windows) ORACLE_HOME\opmn\bin\opmnctl start
   
   

5. Reload OPMN:

   (UNIX) ORACLE_HOME/opmn/bin/opmnctl reload
   (Windows) ORACLE_HOME\opmn\bin\opmnctl reload
   
   

6. If this is an Infrastructure with Oracle Internet Directory, start Oracle Internet Directory:

   (UNIX) ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=OID
   (Windows) ORACLE_HOME\opmn\bin\opmnctl startproc ias-component=OID
   
   

7. Start the rest of the processes:

   • On UNIX systems:

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

   • On Windows systems:

     ORACLE_HOME\opmn\bin\opmnctl startall
     ORACLE_HOME\bin\emctl start iasconsole
     
     

8. Update DCM:

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

4.3.10 Changing the Port Tunneling Port

To change the Port Tunneling port number in any installation type:

1. Open the opmn.xml file:

   (UNIX) ORACLE_HOME/opmn/conf/opmn.xml
   (Windows) 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. Reload OPMN, then stop and restart all OPMN processes and the Application Server Control Console:

   • On UNIX systems:

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

   • On Windows systems:

     ORACLE_HOME\opmn\bin\opmnctl reload
     ORACLE_HOME\bin\emctl stop iasconsole
     ORACLE_HOME\opmn\bin\opmnctl stopall
     ORACLE_HOME\opmn\bin\opmnctl startall
     ORACLE_HOME\bin\emctl start iasconsole
     

4.3.11 Changing the OracleAS Portal Port

OracleAS Portal uses the OracleAS Web Cache HTTP listen port on the instance. See Section 4.3.5.1 for information about changing the OracleAS Web Cache HTTP listen port.

4.3.12 Changing the OracleAS Wireless Port

OracleAS Wireless uses the OracleAS Web Cache HTTP listen port on the instance. See Section 4.3.5.1 for information about changing the OracleAS Web Cache HTTP listen port.

4.3.13 Changing OracleBI Discoverer Ports

The OracleBI Discoverer Preferences port cannot be changed after installation. Other OracleBI Discoverer services use the OracleAS Web Cache HTTP listen port on the instance. See Section 4.3.5.1 for information about changing the OracleAS Web Cache HTTP listen port.

4.3.14 Changing the OracleAS Forms Services Port

OracleAS Forms Services uses the OracleAS Web Cache HTTP listen port on the instance. See Section 4.3.5.1 for information about changing the OracleAS Web Cache HTTP listen port.

4.3.15 Changing OracleAS Reports Services Ports

The following sections describe how to change OracleAS Reports Services ports:

• Changing the OracleAS Reports Services Bridge Port

• Changing the OracleAS Reports Services Network Port

• Changing the OracleAS Reports Services SQL*Net Port

4.4.1 Changing the OracleAS Metadata Repository Net Listener Port

First, determine if it is necessary to change the OracleAS 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 OracleAS 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 and Oracle Database10g databases can share the same Oracle Net listener port. If you install a OracleAS Metadata Repository on a host that contains Oracle9i and Oracle Database 10g databases, they can all use port 1521. There is no need to change the OracleAS Metadata Repository port number.

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

If you determine that you want to change the OracleAS Metadata Repository Listener Port, follow the steps in this section. An OracleAS 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 OracleAS Metadata Repository:

Task 1: Stop Middle-tier Instances

Stop all middle-tier instances that use the Metadata Repository by running the following command in each middle-tier Oracle home:

(UNIX) ORACLE_HOME/opmn/bin/opmnctl stopall
(Windows) ORACLE_HOME\opmn\bin\opmnctl stopall 

Task 2: Change the OracleAS Metadata Repository Oracle Net Listener Port

On the OracleAS Metadata Repository host:

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

2. If OPMN is running, stop it:

   (UNIX) ORACLE_HOME/opmn/bin/opmnctl stopall
   (Windows) ORACLE_HOME\opmn\bin\opmnctl stopall
   
   

3. Stop the OracleAS Metadata Repository listener:

   lsnrctl stop
   
   

4. Open the listener.ora file, which is located at:

   (UNIX) ORACLE_HOME/network/admin/listener.ora
   (Windows) ORACLE_HOME\network\admin\listener.ora
   
   

   1. Under the LISTENER entry, update the value for PORT.

   2. Add the following SID_DESC entry to the SID_LIST_LISTENER entry:

      (SID_DESC =
        (GLOBAL_DBNAME = service_name)
        (ORACLE_HOME = oracle_home_path)
        (SID_NAME = sid)
      )
      
      

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

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

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

   2. Add an entry like the following:

      newnetport =
        (DESCRIPTION =
          (ADDRESS = (PROTOCOL = tcp) (HOST = hostname) (PORT = port)))
      
      

      In the example, hostname is the fully-qualified hostname and port is the new port number.

6. Start the OracleAS Metadata Repository listener:

   lsnrctl start
   
   

7. Using SQL*Plus, log in to the OracleAS Metadata Repository as the SYSTEM user with SYSDBA privileges and run the following command:

   SQL> alter system set local_listener='newnetport' scope=spfile;
   
   

8. Using SQL*Plus, restart OracleAS Metadata Repository:

   SQL> SHUTDOWN
   SQL> STARTUP
   
   

9. Start the directory server:

   • On UNIX systems:

     ORACLE_HOME/opmn/bin/opmnctl start
     ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=OID
     
     

   • On Windows systems:

     ORACLE_HOME\opmn\bin/opmnctl start
     ORACLE_HOME\opmn\bin\opmnctl startproc ias-component=OID
     

Task 3: Update Oracle Internet Directory

On the Identity Management host, update Oracle Internet Directory with the new Oracle Net listener port number:

1. Start Oracle Directory Manager:

   • On UNIX, use the following command:

     ORACLE_HOME/bin/oidadmin
     
     

   • On Windows, navigate to Oracle Directory Manager (Start > Programs > Oracle Application Server Oracle_Home > Integrated Management Tools > Oracle Directory Manager.)

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 OracleAS Metadata Repository. For example, if the DBName is the default, orcl, select cn=ORCL.

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

5. Click Apply.

6. Start OPMN in the Oracle Internet Directory Oracle home:

   (UNIX) ORACLE_HOME/opmn/bin/opmnctl startall
   (Windows) ORACLE_HOME\opmn\bin\opmnctl startall 
   

Task 4: Update OracleAS Single Sign-On

On the OracleAS Single Sign-On host:

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. Update OracleAS Single Sign-On with the new repository port number by running the following command in the OracleAS Single Sign-On Oracle home:

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

3. In the OracleAS Single Sign-On Oracle home, restart OC4J:

   (UNIX) ORACLE_HOME/opmn/bin/opmnctl restartproc ias-component=OC4J
   (Windows) ORACLE_HOME\opmn\bin\opmnctl restartproc ias-component=OC4J 
   

Task 5: Update OracleAS Certificate Authority

If the Identity Management installation has OracleAS Certificate Authority:

1. Run the following command:

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

2. Restart OracleAS Certificate Authority:

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

If you are not sure if OracleAS Certificate Authority is configured, examine the Application Server Control Home page to see if it is listed in the Components section.

Task 6: Update the Application Server Control Console

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

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

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

2. Update the old OracleAS Metadata Repository port number with the new port number, and then save the file.

   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. Reload the Application Server Control Console:

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

Task 7: Update Middle-Tier Instances

In each middle-tier Oracle home that uses OracleAS Metadata Repository:

1. Update the following file with the new Oracle Net listener port number:

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

2. Check the following file:

   (UNIX) ORACLE_HOME/Apache/modplsql/conf/dads.conf
   (Windows) ORACLE_HOME\Apache\modplsql\conf\dads.conf
   
   

   Locate the line that begins with PlsqlDatabaseConnectString.

   • If the line ends with ServiceNameFormat or SIDFormat, update the line with the new OracleAS Metadata Repository port number, save the file, and restart Oracle HTTP Server.

   • If the line ends with NetServiceNameFormat, you do not need to do anything.

3. Start the middle-tier instance:

   (UNIX) ORACLE_HOME/opmn/bin/opmnctl startall
   (Windows) ORACLE_HOME\opmn\bin\opmnctl startall 
   

Task 8: Update J2EE and Web Cache Instances

If the Metadata Repository is not registered with Oracle Internet Directory and is used as an OracleAS Database-Based Farm, you must update each J2EE and Web Cache instance that uses the Metadata Repository as follows:

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

2. Click the Infrastructure link.

3. On the Infrastructure page, in the OracleAS Farm Repository Management section, click Change.

4. Select Existing Database.

5. Follow the steps in the wizard for supplying the new Metadata Repository port number.

6. When the wizard is finished, navigate to the instance Home page and start your instance by clicking Start All.

4.4.2 Changing Oracle Internet Directory Ports

This section describes how to change the Oracle Internet Directory HTTP or HTTPS 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 tasks describe how to update 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:

• Task 1: Prepare the Middle-Tier Instances

• Task 2: Prepare the Infrastructure Instances

• Task 3: Change the Oracle Internet Directory Port

• Task 4: Reconfigure OracleAS Certificate Authority

• Task 5: Restart the Identity Management Instance

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

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

Prepare the Infrastructure instances by taking these steps:

1. Make sure that 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 a different OracleAS Metadata Repository for their product metadata and DCM repositories, make sure those repositories are started. In short, make sure all Metadata Repositories in your environment are started.

Task 3: Change the Oracle Internet Directory Port

Change the Oracle Internet Directory port by taking these steps:

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.

      For HTTP:

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

      For HTTPS:

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

   2. Run the following command:

      For HTTP:

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

      For HTTPS:

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

      Note that oid_port is the old Oracle Internet Directory port number. If you are changing the HTTPS port, provide the additional -U argument to specify the SSL authentication mode. Use one of the following values for SSLAuth: 1 for no authentication required; 2 for one-way authentication required; 3 for two-way authentication required.

2. On the Oracle Internet Directory host, stop the entire instance that contains Oracle Internet Directory, as well as the Application Server Control Console:

   • On UNIX systems:

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

   • On Windows systems:

     ORACLE_HOME\bin\emctl stop iasconsole
     ORACLE_HOME\opmn\bin\opmnctl stopall
     
     

3. Perform this step in the Oracle Internet Directory Oracle home. If you have OracleAS Metadata Repository 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. Open the ldap.ora file:

      (UNIX) ORACLE_HOME/ldap/admin/ldap.ora
      (Windows) ORACLE_HOME\ldap\admin\ldap.ora
      
      

   2. Modify the following line to contain the new port number, and then save the file:

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

   3. Open the ias.properties file:

      (UNIX) ORACLE_HOME/config/ias.properties
      (Windows) ORACLE_HOME\config\ias.properties
      
      

   4. Change the value of OIDport (for an HTTP port change) or OIDsslport (for an HTTPS port change) to the new port number, and then save the file.

4. On the Oracle Internet Directory host, start the instance that contains Oracle Internet Directory, and start the Application Server Control Console:

   • On UNIX systems:

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

   • On Windows systems:

     ORACLE_HOME\opmn\bin\opmnctl startall
     ORACLE_HOME\bin\emctl start iasconsole
     
     

5. Perform this step in the OracleAS Single Sign-On Oracle home:

   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 the following command in the OracleAS Single Sign-On Oracle home:

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

Task 4: Reconfigure OracleAS Certificate Authority

Perform this task if you are using OracleAS Certificate Authority:

1. If OracleAS Certificate Authority is running in a different Oracle home, do the following steps in the OracleAS Certificate Authority Oracle home:

   1. Open the ias.properties file:

      (UNIX) ORACLE_HOME/config/ias.properties
      (Windows) ORACLE_HOME\config\ias.properties
      
      

   2. Change the value of OIDport (for an HTTP port change) or OIDsslport (for an HTTPS port change) to the new port number, and then save the file.

2. Update OracleAS Certificate Authority with the new Oracle Internet Directory port number 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, portnum is the OracleAS Certificate Authority Server Authentication Virtual Host (SSL) port; the default is 6600.

   
   

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

   
   

Task 5: Restart the Identity Management Instance

Restart the Identity Management instance:

• On UNIX systems:

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

• On Windows systems:

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

4.4.3 Changing the HTTP Server Port on an Identity Management Installation

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.

The following tasks describe how to update 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:

• Task 1: Prepare the Middle-Tier Instances

• Task 2: Prepare the Infrastructure Instances

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

• Task 4: Enable Oracle HTTP Server to Run as Root for Ports Less Than 1024 (UNIX Only)

• Task 5: Update the Application Server Control Console

• Task 6: Update OracleAS Single Sign-On

• Task 7: Re-register mod_osso

• Task 8: Update Oracle Delegated Administration Services

• Task 9: Update OracleAS Certificate Authority

• Task 10: Restart the Identity Management Instance

• Task 11: Restart OracleAS Certificate Authority

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

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

Prepare the Infrastructure by taking the following steps:

1. Make sure that 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, make sure those are started. In short, make sure all Metadata Repositories in your environment are started.

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

If you are changing the HTTP port, change both the Listen and Port directives to the new port number in the Oracle HTTP Server httpd.conf file. You can perform this task using the Application Server Control Console or manual steps.

• Using the Application Server Control Console:

  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. Open the httpd.conf file:

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

  2. Update the non-SSL Listen and Port directives with the new port number, and then save the file.

     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. Run the following command:

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

If you are changing the HTTPS port, change both the SSL Listen and Port directives to the new port number in the Oracle HTTP Server ssl.conf file. You must do this using the following manual steps:

1. Edit the ssl.conf file, located at:

   (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, and then save the file.

   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
   
   

   Save and close the file.

3. 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 (UNIX Only)

Perform this task if you are changing the port to a value 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, you must enable Oracle HTTP Server to run as root, as follows:

1. Log in as root.

2. Run the following commands in the Infrastructure 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. Open the targets.xml 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, and then save the file.

   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. Reload the Application Server Control Console:

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

Task 6: Update OracleAS Single Sign-On

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

Re-register mod_osso as follows:

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. On Windows systems, set the path, for example: PATH=%PATH%;%ORACLE_HOME%\bin;%ORACLE_HOME%\lib.

3. If you are changing the Oracle HTTP Server listen port, take the following steps:

   1. Re-register mod_osso to take care of the default partner applications by running the following command in the 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, if you want to change the Oracle HTTP Server listen port to 7779 on host myhost on UNIX:

      $ORACLE_HOME/sso/bin/ssoreg.sh
      -oracle_home_path /disk1/oracleas
      -site_name myhost:7779
      -config_mod_osso TRUE
      -mod_osso_url http://myhost.mydomain:7779
      
      

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
      
      

      
      

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

      
      

   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. If you have configured or modified any additional partner applications, you must also re-register those.

Task 8: Update Oracle Delegated Administration Services

If you have Oracle Delegated Administration Services configured, and Oracle Delegated Administration Services uses the new port number, follow these steps to update the Oracle Delegated Administration Services URL entry in Oracle Internet Directory.

You can find out what port Oracle Delegated Administration Services uses with the following command:

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

To update Oracle Delegated Administration Services:

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 OracleAS 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, portnum is the OracleAS Certificate Authority Server Authentication Virtual Host (SSL) port; the default is 6600.

   
   

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

   
   

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

   • On UNIX systems:

     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
     
     

   • On Windows systems:

     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:

• On UNIX systems:

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

• On Windows systems:

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

Now that you have changed the Oracle HTTP Server 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. Note that the wizard does not prompt you for the new port number; it retrieves the port number internally.

   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 Administrator tab.

   3. Click the global settings link.

   4. Click the SSO/OID tab.

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

4.4.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. Open the ocm_apache.conf file in the Oracle home of the Infrastructure that contains OracleAS Certificate Authority:

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

   1. Modify the Server or Mutual port, or both, and then save the file.

      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. Run the following command:

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

2. Run the following command (make sure your ORACLE_HOME environment variable is set first):

   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 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, portnum is the OracleAS Certificate Authority Server Authentication Virtual Host (SSL) port; the default is 6600.

   
   

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

   
   

4. Restart Oracle HTTP Server:

   (UNIX) ORACLE_HOME/opmn/bin/opmnctl restartproc type=ohs
   (Windows) ORACLE_HOME\opmn\bin\opmnctl restartproc type=ohs
   
   

5. Restart the OracleAS Certificate Authority OC4J instance:

   (UNIX) ORACLE_HOME/opmn/bin/opmnctl restartproc type=oc4j instancename=oca
   (Windows) ORACLE_HOME\opmn\bin\opmnctl restartproc type=oc4j instancename=oca
   
   

6. Start Oracle Application Server Certificate Authority:

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