Skip Headers
Oracle® Application Server Administrator's Guide
10g Release 2 (10.1.2)
Part No. B13995-01
  Go To Documentation Library
Home		 Go To Product List
Solution Area		 Go To Table Of Contents
Contents		 Go To Index
Index
Previous
Previous 		Next
Next 		 

4 Managing Ports

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

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

If the answer to any of the preceding 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 D for a complete list of allotted port ranges. Refer to Oracle Application Server Installation Guide for directions on overriding port assignments during installation with staticports.ini

4.2 Viewing Port Numbers

You can view port numbers on the Application Server Control Console Ports page. Click the Ports tab on the Application Server home page. The Ports page displays the current port numbers and is updated any time you change a port number. For selected components, it also provides links to pages that allow you to change port numbers.


Note:

Immediately after installation, you can view port number assignments in: 
(UNIX) ORACLE_HOME/install/portlist.ini
(Windows) 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.


4.3 Changing Middle-Tier Ports

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

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 the port used for communications with the Management Agent

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

    http://appserver1.acme.com:1810

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

From the Ports page of the Application Server home page, you can view the current port values for these components, as well as the valid port number range for each component.


See Also:

Section 4.2, "Viewing Port Numbers"

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

  1. Change directory to the bin directory in the application server Oracle home.

  2. Stop the Application Server Control.

    On UNIX systems, enter the following command: 

    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: 

    emctl config {agent port | iasconsole {port | rmiport}} port_number

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

    emctl config iasconsole port 1812

  4. Start Application Server Control.

    On UNIX systems, enter the following command: 

    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.

Table 4-1 Changing Application Server Control Ports Using the emctl Command Line

Port Command Line Actions Performed
Application Server Control port 
emctl config iasconsole port port_number
Changes the port value assigned to the StandaloneConsoleURL property in following configuration file: 
ORACLE_HOME/sysman/emd/targets.xml (UNIX)
ORACLE_HOME\sysman\emd\targets.xml (Windows)

Changes the port value assigned to the web-site tag in the following configuration file: 

ORACLE_HOME/sysman/j2ee/config/emd-web-site.xml (UNIX)
ORACLE_HOME\sysman\j2ee\config\emd-web-site.xml (Windows)
Oracle Management Agent port 
emctl config agent port
port_number
Changes the value assigned to the EMD_URL property in the following configuration file: 
ORACLE_HOME/sysman/config/emd.properties (UNIX)
ORACLE_HOME\sysman\config\emd.properties (Windows)
OC4J Remote Method Invocation (RMI) port 
emctl config iasconsole 
rmiport port_number
Changes the port values in the following configuration files: 
ORACLE_HOME/sysman/j2ee/config/rmi.xml (UNIX)
ORACLE_HOME\sysman\j2ee\config\rmi.xml (Windows)

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

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 3301-3400, 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 (3301-3400), a comma separated list of ports (3301, 3304, 3307), or a combination of both (3301-3380, 3383, 3390-3400). 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 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. 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 would like 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="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"/>

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

    5. Reload OPMN: 

      opmnctl reload

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

      opmnctl startproc process-type=OC4J_instance

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

      opmnctl startproc process-type=home

    7. Run the following command: 

      dcmctl updateConfig

4.3.3 Changing the Oracle HTTP Server Listen Port

When you change the Oracle HTTP Server Listen directive, there are often dependencies that must also be set. For example, if you are using OracleAS Web Cache to improve the performance of your Oracle Application Server instance, 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 Java command to change the Oracle HTTP Server listen port. The Java command automatically modifies the necessary configuration files within the Oracle home and optionally restarts the required components within the Oracle home.

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

4.3.3.1 Enabling Oracle HTTP Server to Run as Root for Ports Set to Less Than 1024 on UNIX Systems

Perform this step before you change the Oracle HTTP Server listen port if you are on a UNIX system and you are changing the listen port to a number 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 HTTPS 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

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

Use the following procedure to change the Oracle HTTP Server HTTP or HTTPS 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: 

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

  2. On UNIX systems, set the LD_LIBRARY_PATH, LD_LIBRARY_PATH_64, or SHLIB_PATH environment variables to the proper values, as shown in Table 1-1. The actual environment variables and values that you have to 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/bin/ssoreg.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/bin/ssoreg.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] 
{-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 7777 -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.

    Table 4-2 Arguments for the portconfig Command

    Argument Description
    -oracleHome The Oracle home of the Oracle Application Server instance. The portconfig command modifies only components that are part of the selected Oracle home. You can use an environment variable to represent the Oracle home.
    -oldPort The old (current) value of the Oracle HTTP Server Listen port.
    -newPort The new value for the Oracle HTTP Server Listen port.
    -webCache Use this optional argument if you are using OracleAS Web Cache to improve the performance and reliability of your Web server. When this argument is included on the command line, the dependent OracleAS Web Cache port assignment will be changed automatically.

    Specifically, the port number of the origin server will be updated automatically so it points to the new Oracle HTTP Server listen port.

    Note: The portconfig command updates the OracleAS Web Cache instance only if it resides in the current Oracle home.

    -start When you use this optional argument, the portconfig command performs the configuration changes, and then stops and starts the application server instance. The Oracle Application Server instance must be stopped and started—or restarted—before the port changes will take effect.

    Note that during startup, all enabled components of the application server are started, even those that were originally down before you ran the portconfig command to change the Oracle HTTP Server Listen port.

    Compare with the -restart argument. Each time you run the command you can use the -restart or -start options, but not both.

    -restart When you use this optional argument, the portconfig command performs the configuration changes, and then restarts the application server instance. The Oracle Application Server instance must be restarted—or stopped and started—before the port changes will take effect.

    With this option, only already running components are restarted after the configuration changes are complete. Components that were down before you ran the portconfig command to change the Oracle HTTP Server Listen port will remain down.

    Compare with the -start argument. Each time you run the command you can use the -restart or -start options, but not both.

    -debug Use this optional argument if you want to display debugging information as the command executes. This argument can be useful if you are troubleshooting a problem or working with Oracle Support.
    -sso Use this optional argument when the Listen port you are changing is protected by OracleAS Single Sign-On.

    When you use this argument, the portconfig command re-registers mod_osso with the new Oracle HTTP Server Listen port value.

    When you use the -sso argument, then you must include the -url and -user arguments. In addition, you can optionally use the -site, -admin and -vHost arguments.

    For more information about registering mod_osso, see "Configuring and Administering Partner Applications" in the Oracle Application Server Single Sign-On Administrator's Guide.

    -url This argument is required when you use the -sso argument.

    Use this argument to provide the new Oracle HTTP Server URL, which is also used by OracleAS Single Sign-On and uses the new Listen port.

    For example: 

    http://sso42.acme.com:7778

    This URL is passed as the -mod_osso_url parameter in the ssoreg.sh and ssoreg.bat scripts.

    -user This argument is required when you use the -sso argument.

    Use this argument to enter the name of the account that is used to start Oracle HTTP Server. On UNIX systems, this is usually root. On Windows, it is usually SYSTEM.

    The value provided with this argument is passed as the -u parameter in the ssoreg.sh and ssoreg.bat scripts.

    -site This argument is optional; however, it can be used only when you also use the -sso argument.

    Use this argument to enter the site name of OracleAS Single Sign-On partner application. The site name is displayed by the OracleAS Single Sign-On administration pages.

    The value of this argument is passed as the -site_name parameter in the ssoreg.sh and ssoreg.bat scripts. If the -site argument is not specified, the application server instance name is passed to ssoreg.sh and ssoreg.bat scripts as the value of the -site_name parameter.

    -admin This argument is optional; however, it can be used only when you also use the -sso argument.

    Use this argument to enter the account name of the mod_osso administrator. This value is displayed in the OracleAS Single Sign-On administration pages. In most cases, this value should be the same as the distinguished name (dn) of the user who installed Oracle Application Server. The value of this argument is passed as the -admin_info parameter in the ssoreg.sh and ssoreg.bat scripts.

    -vHost This argument is optional; however, it can be used only when you also use the -sso argument.

    Use this argument to enter the path to the osso.conf file for the virtual host being configured. For example: 

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

    Use this argument only when you are registering an HTTP virtual host with the OracleAS Single Sign-On server. The value of this argument is passed as the -config_file parameter, along with the -virtualhost parameter, in the ssoreg.sh and ssoreg.bat scripts.


  5. Restart the application server instance: 

    (UNIX)
ORACLE_HOME/bin/emctl stop iasconsole
ORACLE_HOME/opmn/bin/opmnctl stopall
ORACLE_HOME/opmn/bin/opmnctl startall
ORACLE_HOME/bin/emctl start iasconsole

(Windows)
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 OracleAS Web Cache Listen Port

This section describes how to change the OracleAS Web Cache HTTP or HTTPS listen port. It involves changing the OracleAS Web Cache port number and updating other components in the middle tier with the new port number. The relevant tasks include the following:

Task 1: Enable OracleAS Web Cache to Run as Root for Ports Less Than 1024 on UNIX

Perform this task only if you are changing the port to a number less than 1024.

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

  1. Log in as the user that installed Oracle Application Server and stop OracleAS 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 user_ID

    The parameter user_ID is the user ID associated with the OracleAS Web Cache processes. This is usually the user that installed Oracle Application Server. This user is listed on the Security page (Web Cache Home page -> Administration tab -> Properties -> Application -> Origin Servers) of Application Server Control Console or the Process Identity page (Properties -> Process Identity) of OracleAS Web Cache Manager.

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

    opmnctl startproc ias-component=WebCache

Task 2: Change the OracleAS Web Cache Listen Port

Take the following steps:

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

  2. Click the Administration tab to display the Administration page.

  3. On the Administration page, click Ports to display the Ports page.

  4. In the Listen Ports section, locate the appropriate port that has HTTP or HTTPS in the Protocol column.

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

  6. Click OK to apply changes.

  7. When prompted, click Restart Web Cache to restart the cache.

Task 3: Change the OracleAS Web Cache Logical Site Port

If the OracleAS Web Cache listen port is the same as the logical site port, update the logical site port as follows:

  1. On the Administration page, click Sites to display the Sites page.

  2. Locate the appropriate sites using the old port number. If there is no site using the old port number, then the OracleAS Web Cache listener and site do not share the same port number.

  3. For each site using the old port number:

    1. Click Edit.

    2. In the Edit Named Site or Edit Unnamed Site page, enter the new port number in the Port field.

  4. Click OK to apply changes.

  5. When prompted, click Restart Web Cache to restart the cache.

Task 4: Update the Oracle HTTP Server Port Directive

If you are changing the OracleAS Web Cache HTTP listen port to be the same as the logical site port, update the Port directive in the Oracle HTTP Server httpd.conf file:

  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 Port directive with the new port number, and then save the file.

    Do not modify the Listen directive. The OracleAS Web Cache port must be the same as the Oracle HTTP Server Port directive.

  3. Run the following command: 

    dcmctl updateConfig -ct ohs

If you are changing the OracleAS Web Cache HTTPS listen port, update the Port directive in the Oracle HTTP Server ssl.conf file:

  1. Open the ssl.conf file: 

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

  2. Update the SSL Port directive with the new port number, and then save the file.

    Do not modify the Listen directive. The OracleAS Web Cache SSL port must be the same as the Oracle HTTP Server SSL Port directive.

  3. Run the following command: 

    dcmctl updateConfig -ct ohs

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 OracleAS Web Cache 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 OracleAS Web Cache 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 OracleAS Web Cache listen port number, and replace them with the new port number.

  3. Reload the Application Server Control Console: 

    emctl reload

Task 6: Update mod_osso

If you have registered your virtual host as an OracleAS Single Sign-On partner application, follow these steps to re-register your virtual host with the new port number:

  1. On UNIX systems, set the LD_LIBRARY_PATH, LD_LIBRARY_PATH_64, or SHLIB_PATH environment variables to the proper values, as shown in Table 1-1. The actual environment variables and values that you have to set depend on the type of your UNIX operating system.

  2. 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 middle_tier_oracle_home
-site_name middle_tier_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 middle_tier_hostname:new_port_number
-config_mod_osso TRUE
-mod_osso_url mod_osso_url

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

    $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

    See Also:

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

  3. If you are changing the OracleAS Web Cache HTTPS listen port, perform the following steps. These steps do not apply if you are changing the OracleAS Web Cache HTTP listen port.

    1. Open the mod_osso.conf file: 

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

    2. Replace references to osso.conf with middle_tier_hostname.middle_tier_domain.https-osso.conf, and save the file.

      For example, if you have the following entry in the mod_osso.conf file: 

      /disk1/oracleas/Apache/Apache/conf/mod_osso.conf

      You would make the following change for the HTTPS listen port on middle-tier host myhost.mydomain: 

      /disk1/oracleasApache/Apache/conf/myhost.mydomain.https-osso.conf

  4. If you are changing the OracleAS Web Cache HTTP listen port, perform these additional steps:

    1. Open the mod_osso.conf file: 

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

    2. Replace references to osso.conf with middle_tier_hostnamemiddle_tier_domain.https-osso.conf, and save the file.

      For example, if you have the following entry in the mod_osso.conf file: 

      $ORACLE_HOME/Apache/Apache/conf/mod_osso.conf

      You would make the following change for OracleAS Web Cache HTTPS listen port on middle-tier host myhost.mydomain: 

      $ORACLE_HOME/Apache/Apache/conf/myhost.mydomain.https-osso.conf

Task 7: Update OracleAS Portal Configuration

If you are changing the OracleAS Web Cache HTTP listen port in a configuration with OracleAS Portal, update OracleAS Portal configuration with the new port number:

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

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

  3. In the Listening Port field, enter the new port number.

  4. Click Apply.

If you are changing the OracleAS Web Cache HTTPS listen port in a configuration with OracleAS Portal, update OracleAS Portal configuration with the new port number:

  1. Update OracleAS Portal configuration:

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

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

    3. In the Listening Port field, enter the new port number.

    4. From the Listening Port SSL Enabled list, select Yes.

    5. Click Apply.

  3. Update the httpsports parameter in the following file: 

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

  4. Restart the OC4J_Portal:

    1. Using the Application Server Control Console, navigate to the OC4J: OC4J_Portal home page.

    2. In the General section, click Start.


    See Also:

    Oracle Application Server Portal Configuration Guide for more information on updating the Portal Web Cache Settings

Task 8: Update Web Providers

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

    4. Click OK.

Task 9: Update OracleAS Wireless

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

  1. Re-register OracleAS Wireless with OracleAS Single Sign-On by running the following command on the middle-tier host: 

    (UNIX) ORACLE_HOME/wireless/bin/reRegisterSSO.sh new_wireless_url oracle_home administrator_dn
(Windows) ORACLE_HOME\wireless\bin\reRegisterSSO.bat
 new_wireless_url oracle_home administrator_dn

    In the example:

    • new_wireless_url: Wireless HTTP URL with the new OracleAS Web Cache listen port.

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

    • administrator_dn: Oracle Internet Directory administrator.

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

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

  2. Update the Wireless HTTP and HTTPS configuration information:

    1. Navigate to the Wireless home page on the Application Server Control Console.

    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 OracleAS Web Cache listen 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 Console.

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

    3. On the Instance URLs page:

      • If Use the Wireless Site URLs is selected, you do not need to make any changes to this page.

      • If Use the Wireless Instance URLs is selected, update each URL that contains the OracleAS Web Cache listen port with the new port number.

    4. Click OK.

Task 10: Update OracleBI Discoverer

If you have OracleBI Discoverer configured, and you are using the 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:

Section "How to edit Discoverer Portlet Provider" in Oracle Business Intelligence Discoverer Configuration Guide.

Task 11: Restart the Middle-Tier Instance

Restart the middle-tier instance: 

emctl stop iasconsole
opmnctl stopall
opmnctl startall
emctl start iasconsole

4.3.5 Changing the OracleAS Web Cache Administration Port

The tasks to change the OracleAS Web Cache invalidation port include the following:

Task 1: Change the OracleAS Web Cache Administration Port

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

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

  2. Click the Administration tab to display the Administration page.

  3. On the Administration page, click Ports to display the Ports page.

  4. In the Operation Ports section, locate the Administration row.

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

  6. Click OK to apply changes.

  7. When prompted, click Restart Web Cache to restart the cache.

Task 2: Update OracleAS Portal

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

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

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

  3. In the Administration Port field, enter the new port number.


    See Also:

    Oracle Application Server Portal Configuration Guide for more information on updating the Portal Web Cache Settings

4.3.6 Changing the OracleAS Web Cache Invalidation Port

The tasks to change the OracleAS Web Cache invalidation port include the following:

Task 1: Change the OracleAS Web Cache Invalidation Port

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

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

  2. Click the Administration tab to display the Administration page.

  3. On the Administration page, click Ports to display the Ports page.

  4. In the Operation Ports section, locate the Invalidation row.

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

  6. Click OK to apply changes.

  7. When prompted, click Restart Web Cache to restart the cache.

Task 2: Update OracleAS Portal

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

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

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

  3. In the Invalidation Port field, enter the new port number.


    See Also:

    Oracle Application Server Portal Configuration Guide for more information on updating the Portal Web Cache Settings

Task 3: Update Web Providers

If you are using Web Providers with OracleAS Portal, you must update them to use the new port as follows:

  1. Open the cache.xml file: 

    (UNIX) ORACLE_HOME/portal/conf/cache.xml
(Windows) ORACLE_HOME\portal\conf\cache.xml

  2. Update the port attribute to the new port, and then save the file.

  3. Restart OC4J_Portal:

    1. Using the Application Server Control Console, navigate to the OC4J: OC4J_Portal home page.

    2. In the General section, click Start.

4.3.7 Changing the OracleAS Web Cache Statistics Port

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

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

  2. Click the Administration tab to display the Administration page.

  3. On the Administration page, click Ports to display the Ports page.

  4. In the Operation Ports section, locate the Statistics row.

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

  6. Click OK to apply changes.

  7. When prompted, click Restart Web Cache to restart the cache.

If you change the statistics protocol to HTTPS, it is not possible to view performance statistics in Enterprise Manager until a certificate is uploaded in Base64 format named b64InternetCertificate.txt to ORACLE_HOME/sysman/config on UNIX and ORACLE_HOME\sysman\config on Windows.

4.3.8 Changing the DCM Discovery Port

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

  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: 

    emctl stop iasconsole
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: 

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

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

    dcmctl restart -co OC4J_INSTANCE

4.3.10 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. Using the Application Server Control Console, 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 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.11 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: 

    emctl stop iasconsole
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: 

    opmnctl start

  5. Reload OPMN: 

    opmnctl reload

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

    opmnctl startproc ias-component=OID

  7. Start the rest of the processes: 

    opmnctl startall
emctl start iasconsole

  8. Update DCM: 

    dcmctl updateConfig -ct opmn

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

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

4.3.13 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. 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. Restart OPMN: 

    opmnctl reload
emctl stop iasconsole
opmnctl stopall
opmnctl startall
emctl start iasconsole

4.3.14 Changing OracleAS Portal Ports

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


See Also:

Section 4.3.4, "Changing the OracleAS Web Cache Listen Port"

4.3.15 Changing OracleAS Wireless Ports

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


See Also:

Section 4.3.4, "Changing the OracleAS Web Cache Listen Port"

4.3.16 Changing OracleBI Discoverer Ports

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


See Also:

Section 4.3.4, "Changing the OracleAS Web Cache Listen Port"

4.4 Changing Infrastructure Ports

This section contains the following topics:

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.


Note:

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

If you determine that you would like 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:

If the Metadata Repository is used as follows: Follow these tasks to change its Oracle Net listener port:
  • Identity Management Repository, Product Metadata Repository, and Management (DCM) Repository

  • Registered with Oracle Internet Directory

Task 1: Stop Middle-tier Instances

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

Task 3: Update Oracle Internet Directory

Task 4: Update OracleAS Single Sign-On

Task 5: Update OracleAS Certificate Authority

Task 6: Update the Application Server Control Console

Task 7: Update Middle-Tier Instances


  • Identity Management Repository only

  • Registered with Oracle Internet Directory

Task 1: Stop Middle-tier Instances

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

Task 3: Update Oracle Internet Directory

Task 4: Update OracleAS Single Sign-On

Task 5: Update OracleAS Certificate Authority

Task 6: Update the Application Server Control Console


  • Product Metadata and Management (DCM) Repository

  • Registered with Oracle Internet Directory

Task 1: Stop Middle-tier Instances

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

Task 3: Update Oracle Internet Directory

Task 7: Update Middle-Tier Instances


  • Management (DCM) Repository only

  • Not registered with Oracle Internet Directory

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

Task 8: Update J2EE and Web Cache Instances



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 environment variable and ORACLE_SID 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: 

    (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 and 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. Restart OracleAS Metadata Repository: 

    SQL> shutdown
SQL> startup

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: 

    (UNIX) ORACLE_HOME/bin/oidadmin
(Windows) Start > Programs > Oracle Application Server - OracleHome >
 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, or SHLIB_PATH environment variables to the proper values, as shown in Table 1-1. The actual environment variables and values that you have to 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: 

    ocactl stop
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: 

    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 Application Server 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.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 OracleAS 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 (make sure your ORACLE_HOME environment variable is set first): 

    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: 

    lsnrctl start

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 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. The relevant tasks are as follows:

Task 1: Prepare the Middle-Tier Instances

Follow 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

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

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

      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: 

    emctl stop iasconsole
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, as well as the Application Server Control Console: 

    opmnctl startall
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, or SHLIB_PATH environment variables to the proper values, as shown in Table 1-1. The actual environment variables and values that you have to 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

Follow this task if you are using OracleAS Certificate Authority:

  1. If OracleAS Certificate Authority is running in a different Oracle home, do the following step 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: 

    ocactl changesecurity -server_auth_port port_number

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

Task 5: Restart the Identity Management Instance

Restart the Identity Management instance: 

emctl stop iasconsole
opmnctl stopall
opmnctl startall
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 Identity Management

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 procedure contains 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. The relevant tasks are as follows:

Task 1: Prepare the Middle-Tier Instances

Follow 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

  1. Make sure that Identity Management and its associated OracleAS 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.

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: 

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

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

  2. Update the SSL Listen and SSL Port directives with the new port number, 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

  3. Run the following command: 

    dcmctl updateConfig -ct ohs

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

Perform this task 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 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: 

    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, or SHLIB_PATH environment variables to the proper values, as shown in Table 1-1. The actual environment variables and values that you have to set depend on the type of your UNIX operating system.

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

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

    • new_port_number is the new non-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, or SHLIB_PATH environment variables to the proper values, as shown in Table 1-1. The actual environment variables and values that you have to set depend on the type of your UNIX operating system.

  2. On Windows systems, set PATH=%PATH%;$ORACLE_HOME%\bin;%ORACLE_HOME%\lib.

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

    $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. These steps do not apply if you are changing the non-SSL listen port.

    1. Open the mod_osso.conf file: 

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

    2. Replace references to osso.conf with middle_tier_hostname.middle_tier_domain.https-osso.conf, and save the file.

      For example, if you have the following entry in the mod_osso.conf file: 

      /disk1/oracleas/Apache/Apache/conf/mod_osso.conf

      You would make the following change for the Oracle HTTP Server SSL listen port on middle-tier host myhost.mydomain: 

      /disk1/oracleasApache/Apache/conf/myhost.mydomain.https-osso.conf

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

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

  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: 

    ocactl changesecurity -server_auth_port port_number

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

  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: 

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

Task 10: Restart the Identity Management Instance

Restart the Identity Management instance: 

emctl stop iasconsole
opmnctl stopall
opmnctl startall
emctl start iasconsole

Task 11: Restart OracleAS Certificate Authority

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

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

    Where portnum is the OracleAS Certificate Authority Server Authentication Virtual Host (SSL) port; the default is 4400.

  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

4.5 Changing OracleAS Developer Kit Ports

To change port numbers in an OracleAS Developer Kit installation, refer to the instructions in Section 4.3, "Changing Middle-Tier Ports".

4.6 Changing Oracle Content Management Software Development Kit Ports

To change the port numbers in an Oracle Content Management Software Development Kit, refer to the instructions in Section D.3.7, "Oracle Content Management Software Development Kit Ports".

  Previous
Previous 		Next
Next
  Go To Documentation Library
Home		 Go To Product List
Solution Area		 Go To Table Of Contents
Contents		 Go To Index
Index