Oracle® Application Server
Administrator's Guide 10g Release 2 (10.1.2) B13995-07 |
|
Previous |
Next |
This chapter describes how to view and change Oracle Application Server port numbers. It contains the following topics:
Many Oracle Application Server components and services use ports. As an administrator, it is important to know the port numbers used by these services, and to ensure that the same port number is not used by two services on your host.
Most port numbers are assigned during installation. Every component and service has an allotted port range, which is the set of port numbers Oracle Application Server attempts to use when assigning a port. Oracle Application Server starts with the lowest number in the range and performs the following checks:
Is the port used by another Oracle Application
Server installation on the host? The installation may be up or down at the time; Oracle Application Server can still detect if the port is used. | |
Is the port used by a process that is currently
running? This could be any process on the host, even a non-Oracle Application Server process. |
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 withstaticports.ini . |
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. In addition, this file is not valid after you upgrade Oracle Application Server. Use Application Server Control Console to view the port numbers. |
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.
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. |
This section contains the following topics:
After you have installed Oracle Application Server, you can change the following Oracle Enterprise Manager 10g ports associated with your Oracle Application Server 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:
bin
directory in the
Oracle Application Server Oracle home.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.
(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
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.
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:(UNIX) ORACLE_HOME/sysman/emd/targets.xml (Windows) ORACLE_HOME\sysman\emd\targets.xml Changes the port value assigned to the (UNIX) ORACLE_HOME/sysman/j2ee/config/emd-web-site.xml (Windows)ORACLE_HOME\sysman\j2ee\config\emd-web-site.xml |
Oracle Management Agent port |
emctl config agent port port_number
|
Changes the
value assigned to the EMD_URL property in the following
configuration file:(UNIX) ORACLE_HOME/sysman/config/emd.properties (Windows) ORACLE_HOME\sysman\config\emd.properties |
OC4J Remote Method Invocation (RMI) port |
emctl config iasconsole rmiport port_number
|
Changes the
port values in the following configuration files:(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 |
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.
Note: Note that because the IIOP, IIOPS1, and IIOPS2 ports are not configured by default, they may not be listed in the Ports page of Application Server Control Console or in opmn.xml. To configure them, you must manually add them to the opmn.xml file.See the J2EE Interoperability chapter of the Oracle Application Server Containers for J2EE Services Guide for more information. |
You can change OC4J port ranges using the Application Server Control Console or manual steps:
Using the Application Server Control Console:
| |
Using manual steps:
(UNIX) ORACLE_HOME/opmn/conf/opmn.xml (Windows) ORACLE_HOME\opmn\conf\opmn.xml home instance,
locate this element:<process-type id="home" ...> 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"/> (UNIX) ORACLE_HOME/opmn/bin/opmnctl reload (Windows) ORACLE_HOME\opmn\bin\opmnctl reload (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 ORACLE_HOME/opmn/bin/opmnctl startproc process-type=home
(UNIX) ORACLE_HOME/dcm/bin/dcmctl updateConfig (Windows) ORACLE_HOME\dcm\bin\dcmctl updateConfig |
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)
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:
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:
For example:
(UNIX) setenv ORACLE_HOME /dev0/private/oracle/appserv1/ (Windows) set ORACLE_HOME=D:\oracle\appserv1\
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 $*
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.
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
is changed automatically. Specifically, the port number of the origin server is updated automatically so that it points to the new Oracle HTTP Server listen port. Note: The |
-start |
Use this
optional argument to stop and start the application
server instance after the portconfig
command performs the configuration changes. The Oracle
Application Server instance must be stopped and
started—or restarted—before the port changes 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 Compare with the |
-restart |
Use this
optional argument to stop and start the application
server instance after the portconfig
command performs the configuration changes. The Oracle
Application Server instance must be restarted—or stopped
and started—before the port changes 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 Compare with the |
-debug |
Use this optional argument 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. The
portconfig command re-registers mod_osso
with the new Oracle HTTP Server Listen port value.
When you use this argument, you must include the 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 |
-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 The value provided with this argument is passed as
the |
-site |
This
argument is optional; however, you can use it only when
you 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 |
-admin |
This
argument is optional; however, you can use it only when
you use the -sso argument.Use this
argument to enter the account name of the |
-vHost |
This
argument is optional; however, you can use it only when
you use the -sso argument.Use this
argument to enter the path to the 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
|
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 |
To change the Oracle HTTP Server Diagnostics port number in any installation type:
dms.conf
file:(UNIX) ORACLE_HOME/Apache/Apache/conf/dms.conf (Windows) ORACLE_HOME\Apache\Apache\conf\dms.conf
(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
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 |
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 tasks involved are:
Task 1: Enable OracleAS Web Cache to Run as Root for Ports Less Than 1024 (UNIX Only)
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:
ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=WebCache
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
-> Administration tab ->
Security) of Application Server
Control Console.
ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=WebCache
Task 2: Change the OracleAS Web Cache Listen Port
Take the following steps:
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:
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:
httpd.conf
file:(UNIX) ORACLE_HOME/Apache/Apache/conf/httpd.conf (Windows) ORACLE_HOME\Apache\Apache\conf\httpd.conf
Do not modify the Listen directive. The OracleAS Web Cache port must be the same as the Oracle HTTP Server Port directive.
(UNIX) ORACLE_HOME/dcm/bin/dcmctl updateConfig -ct ohs (Windows) ORACLE_HOME\dcm\bin\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:
ssl.conf
file:(UNIX) ORACLE_HOME/Apache/Apache/conf/ssl.conf (Windows) ORACLE_HOME\Apache\Apache\conf\ssl.conf
Do not modify the Listen directive. The OracleAS Web Cache SSL port must be the same as the Oracle HTTP Server SSL Port directive.
(UNIX) ORACLE_HOME/dcm/bin/dcmctl updateConfig -ct ohs (Windows) ORACLE_HOME\dcm\bin\dcmctl updateConfig -ct ohs
Task 5: Update the Application Server Control Console
Update the Application Server Control Console with the new port number:
(UNIX) ORACLE_HOME/sysman/emd/targets.xml (Windows) ORACLE_HOME\sysman\emd\targets.xml
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.
(UNIX) ORACLE_HOME/bin/emctl reload (Windows) ORACLE_HOME\bin\emctl reload
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:
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 HTTP listen port to 7779 on middle-tier 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
See Also: Oracle Application Server Single Sign-On Administrator's Guide for more information on registeringmod_osso |
(UNIX) ORACLE_HOME/opmn/bin/opmnctl restartproc process-type=HTTP_Server (Windows) ORACLE_HOME\opmn\bin\opmnctl restartproc process-type=HTTP_Server
mod_osso
with the new port
number by running the following command in the
middle-tier Oracle home:On 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 -virtual_host -config_file path/osso-https.conf
On 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 -virtual_host -config_file path\osso-https.conf
For example, if you want to change the OracleAS Web
Cache HTTPS listen port to 4445 on middle-tier host
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:4445 -virtual_host -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 registeringmod_osso |
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
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
ssl.conf
file, which is also in
the conf
directory, update VirtualHost to
include the osso.conf
file for the virtual
host. Name the file osso-https.conf
to
avoid conflict with the default osso.conf
file. Check that the file name matches the name used in
the registration script.<VirtualHost _default_:4445>
.
.
.
OssoConfigFile ORACLE_HOME/Apache/Apache/conf/osso/osso-https.conf
OssoIpCheck off
<Location /your_protected_url_for_the virtual site>
AuthType basic
Require valid-user
</Location>
.
.
.
</VirtualHost>
(UNIX) ORACLE_HOME/dcm/bin/dcmctl updateConfig -v -d (Windows) ORACLE_HOME\dcm\bin\dcmctl updateConfig -v -d
(UNIX) ORACLE_HOME/opmn/bin/opmnctl restartproc process-type=HTTP_Server (Windows) ORACLE_HOME\opmn\bin\opmnctl restartproc process-type=HTTP_Server
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:
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:
httpsports
parameter in the
following file:ORACLE_HOME/j2ee/OC4J_Portal/applications/portal/portal/WEB-INF/web.xml
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):
portal
).Task 9: Update OracleAS Wireless
If you have OracleAS Wireless configured, update OracleAS Wireless with the new port number:
(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
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. |
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: Update OracleAS Reports Services
You do not need to make any configuration changes to Reports Service to reflect the change. However, if you have built any Web pages that contain links to the middle-tier Reports Service, you need to update those Web pages with the new port number.
Task 12: Restart the Middle-Tier Instance
Restart the middle-tier 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 |
The tasks to change the OracleAS Web Cache administration port are:
Task 1: Change the OracleAS Web Cache Administration Port | |
Task 2: Update OracleAS Portal |
Task 1: Change the OracleAS Web Cache Administration Port
To change the OracleAS Web Cache administration port on any installation type:
Task 2: Update OracleAS Portal
If you have OracleAS Portal configured, update OracleAS Portal configuration with the new port number:
See Also: Oracle Application Server Portal Configuration Guide for more information on updating the Portal Web Cache Settings |
The tasks to change the OracleAS Web Cache invalidation port are:
Task 1: Change the OracleAS Web Cache Invalidation Port | |
Task 2: Update OracleAS Portal | |
Task 3: Update Web Providers |
Task 1: Change the OracleAS Web Cache Invalidation Port
To change the OracleAS Web Cache invalidation port on any installation type:
Task 2: Update OracleAS Portal
If you have OracleAS Portal configured, update OracleAS Portal with 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:
(UNIX) ORACLE_HOME/portal/conf/cache.xml (Windows) ORACLE_HOME\portal\conf\cache.xml
port
attribute to the new port,
and then save the file.To change the OracleAS Web Cache statistics port on any installation type:
If you change the statistics protocol to HTTPS, it is not
possible to view performance statistics in Enterprise Manager
until a certificate named
b64InternetCertificate.txt is uploaded in Base64 format to
ORACLE_HOME/sysman/config
on UNIX and ORACLE_HOME\sysman\config
on Windows.
To change the DCM Discovery port number in any installation type:
dcmCache.xml
file:(UNIX) ORACLE_HOME/dcm/config/dcmCache.xml (Windows) ORACLE_HOME\dcm\config\dcmCache.xml
<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" />
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.
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 |
To change the Java Object Cache port number in any installation type:
javacache.xml
file:(UNIX) ORACLE_HOME/javacache/admin/javacache.xml (Windows) ORACLE_HOME\javacache\admin\javacache.xml
<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" />
(UNIX) ORACLE_HOME/dcm/bin/dcmctl restart -co OC4J_INSTANCE (Windows) ORACLE_HOME\dcm\bin\dcmctl restart -co OC4J_INSTANCE
To change the Log Loader port in any installation type:
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:
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 |
opmn.xml
file:(UNIX) ORACLE_HOME/opmn/conf/opmn.xml (Windows) ORACLE_HOME\opmn\conf\opmn.xml
<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"/>
(UNIX) ORACLE_HOME/opmn/bin/opmnctl start (Windows) ORACLE_HOME\opmn\bin\opmnctl start
(UNIX) ORACLE_HOME/opmn/bin/opmnctl reload (Windows) ORACLE_HOME\opmn\bin\opmnctl reload
(UNIX) ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=OID (Windows) ORACLE_HOME\opmn\bin\opmnctl startproc ias-component=OID
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 |
(UNIX) ORACLE_HOME/dcm/bin/dcmctl updateConfig -ct opmn (Windows) ORACLE_HOME\dcm\bin\dcmctl updateConfig -ct opmn
To change the Port Tunneling port number in any installation type:
opmn.xml
file:(UNIX) ORACLE_HOME/opmn/conf/opmn.xml (Windows) ORACLE_HOME\opmn\conf\opmn.xml
<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
.
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 |
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.
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.
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.
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.
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 |
To change the OracleAS Reports Services bridge port, take the following steps:
(UNIX) ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=bridge_name (Windows) ORACLE_HOME\opmn\bin\opmnctl stopproc ias-component=bridge_name
Alternatively, you can use the following command:
(UNIX) rwbridge.sh name=bridge_name shutdown=immediate (Windows) rwbridge.bat name=bridge_name shutdown=immediate
(UNIX) ORACLE_HOME/reports/conf/repbrg_bridge_name.conf (Windows) ORACLE_HOME\reports\conf\repbrg_bridge_name.conf
<bridge version="10.1.2" port="14012" timeout="1000">
(UNIX) ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=bridge_name (Windows) ORACLE_HOME\opmn\bin\opmnctl startproc ias-component=bridge_name
Alternatively, you can use the following command:
(UNIX) rwbridge.sh name=bridge_name (Windows) rwbridge.bat name=bridge_name
See Also: Oracle Application Server Reports Services Publishing Reports to the Web for more information about the OracleAS Reports Services bridge configuration file. |
To change the OracleAS Reports Services network port, which is used for service discovery, take the following steps:
(UNIX) ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=reports_server (Windows) ORACLE_HOME\opmn\bin\opmnctl stopproc ias-component=reports_server
(UNIX) ORACLE_HOME/reports/conf/rwnetwork.conf
(Windows) ORACLE_HOME\reports\conf\rwnetwork.conf
Because new network configuration files are generated
based on the rwnetwork.template
file, also edit
that file if you want all newly generated network
configuration files to use the new port. The
rwnetwork.template
file is located in the same
directory as the rwnetwork.conf
file.
rwnetwork.conf
file, and optionally
in the rwnetwork.template
file, change the port
attribute of the multicast element, specifying the new port
number. The following example sets the new port to be 14022:<multicast channel="228.5.6.7" port="14022" timeout="1000" retry="3"/>
(UNIX) ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=reports_server (Windows) ORACLE_HOME\opmn\bin\opmnctl startproc ias-component=reports_server
To change the OracleAS Reports Services SQL*Net port number:
tnsnames.ora
file. The default location is:(UNIX) ORACLE_HOME/network/admin/tnsnames.ora (Windows) ORACLE_HOME\network\admin\tnsnames.ora
In the REP_HOSTNAME
entry, update the PORT
parameter with the new
port number.
tnsnames.ora
file. In the REP_HOSTNAME
entry, update the PORT
parameter with the new
port number.This section contains the following topics:
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 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:
(UNIX) ORACLE_HOME/opmn/bin/opmnctl stopall (Windows) ORACLE_HOME\opmn\bin\opmnctl stopall
lsnrctl stop
listener.ora
file, which is located
at:(UNIX) ORACLE_HOME/network/admin/listener.ora (Windows) ORACLE_HOME\network\admin\listener.ora
LISTENER
entry, update the value
for PORT
.SID_DESC
entry to the
SID_LIST_LISTENER
entry:(SID_DESC = (GLOBAL_DBNAME = service_name) (ORACLE_HOME = oracle_home_path) (SID_NAME = sid) )
tnsnames.ora
file. The default
location is:(UNIX) ORACLE_HOME/network/admin/tnsnames.ora (Windows) ORACLE_HOME\network\admin\tnsnames.ora
PORT
value in each entry that
applies to OracleAS Metadata Repository.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.
lsnrctl start
SQL> alter system set local_listener='newnetport' scope=spfile;
SQL> SHUTDOWN SQL> STARTUP
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:
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.) |
orcl
,
select cn=ORCL.PORT
parameter in the orclnetdescstring
field with the new port number.(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:
$ORACLE_HOME/jdk/bin/java -jar $ORACLE_HOME/sso/lib/ossoca.jar reassoc -repos $ORACLE_HOME
(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:
(UNIX) ORACLE_HOME/oca/bin/ocactl updateconnection (Windows) ORACLE_HOME\oca\bin\ocactl updateconnection
(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:
(UNIX) ORACLE_HOME/sysman/emd/targets.xml (Windows) ORACLE_HOME\sysman\emd\targets.xml
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.
(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:
(UNIX) ORACLE_HOME/network/admin/tnsnames.ora (Windows) ORACLE_HOME\network\admin\tnsnames.ora
(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. |
(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:
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:
lsnrctl stop
listener.ora
and
tnsnames.ora
files. In each file, find the following
line:(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC))
Change it to the following:
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
lsnrctl start
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:
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:
Task 3: Change the Oracle Internet Directory Port
Change the Oracle Internet Directory port by taking these steps:
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
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.
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 |
ldap.ora
file:(UNIX) ORACLE_HOME/ldap/admin/ldap.ora (Windows) ORACLE_HOME\ldap\admin\ldap.ora
DIRECTORY_SERVERS=(myhost.myco.com:non_ssl_port:ssl_port)
ias.properties
file:(UNIX) ORACLE_HOME/config/ias.properties (Windows) ORACLE_HOME\config\ias.properties
OIDport
(for an HTTP
port change) or OIDsslport
(for an HTTPS port
change) to the new port number, and then save the file.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 |
$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:
(UNIX) ORACLE_HOME/config/ias.properties (Windows) ORACLE_HOME\config\ias.properties
OIDport
(for an HTTP
port change) or OIDsslport
(for an HTTPS port
change) to the new port number, and then save the file.(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:
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:
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:
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:
| |||||
Using manual steps:
(UNIX) ORACLE_HOME/Apache/Apache/conf/httpd.conf (Windows) ORACLE_HOME\Apache\Apache\conf\httpd.conf 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. (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:
ssl.conf
file, located at:(UNIX) ORACLE_HOME/Apache/Apache/conf/ssl.conf (Windows) ORACLE_HOME\Apache\Apache\conf\ssl.conf
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.
(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:
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:
(UNIX) ORACLE_HOME/sysman/emd/targets.xml (Windows) ORACLE_HOME\sysman\emd\targets.xml
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.
(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.
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. |
Re-register mod_osso
as follows:
PATH=%PATH%;%ORACLE_HOME%\bin;%ORACLE_HOME%\lib
.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
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 |
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
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
(UNIX) ORACLE_HOME/opmn/bin/opmnctl restartproc process-type=HTTP_Server (Windows) ORACLE_HOME\opmn\bin\opmnctl restartproc process-type=HTTP_Server
See Also: Oracle Application Server Single Sign-On Administrator's Guide for more information on registeringmod_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
To update Oracle Delegated Administration Services:
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.
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:
(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.
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.
On each middle-tier instance that uses Identity Management:
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:
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
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.
(UNIX) ORACLE_HOME/dcm/bin/dcmctl updateConfig -ct ohs (Windows) ORACLE_HOME\dcm\bin\dcmctl updateConfig -ct ohs
sqlplus oca/oca_admin_password @$ORACLE_HOME/oca/sql/ocaportchg
(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.
(UNIX) ORACLE_HOME/opmn/bin/opmnctl restartproc type=ohs
(Windows) ORACLE_HOME\opmn\bin\opmnctl restartproc type=ohs
(UNIX) ORACLE_HOME/opmn/bin/opmnctl restartproc type=oc4j instancename=oca
(Windows) ORACLE_HOME\opmn\bin\opmnctl restartproc type=oc4j instancename=oca
(UNIX) ORACLE_HOME/oca/bin/ocactl start (Windows) ORACLE_HOME\oca\bin\ocactl start
OracleAS Developer Kits use the same ports as the J2EE and Web Cache installation type. To change port numbers in an OracleAS Developer Kit installation, refer to the instructions in Section 4.3.
To change the port numbers in an Oracle Content Management Software Development Kit, refer to the instructions in Section D.1.7.