Below is the procedure to change the ports for OHS.
NOTE: Changing all OHS ports.
As discussed above OHS comes with three ports.
i)Non SSL http port (default 7777, range 7777-7877)
ii)SSL http port (default 4443, range 4443-4543)
iii)Proxy MBean or Admin port(default 9999)
(used internally by Oracle HTTP Server to communicate with Fusion Middleware Control.)
To change the Oracle HTTP Server Listen ports (non-SSL or SSL), there are often dependencies that must also be set. For example, if you are using Oracle Web Cache to improve the performance of your Oracle Fusion Middleware environment, you must modify the Oracle Web Cache origin server settings whenever you modify the Oracle HTTP Server Listen ports.
::Steps to change the Non SSL http port and SSL http port::
Go to EM
From the navigation pane, expand the farm, then Web Tier, then select the Oracle HTTP Server instance.
From the Oracle HTTP Server menu, choose Administration, then Ports Configuration.
Select the Listen port that uses the HTTP(S) protocol, then click Edit.
Change the port number, then click OK.
Restart Oracle HTTP Server. (From the Oracle HTTP Server menu, choose Control,then Restart.)
As a result of this, the http port gets updated in ORACLE_INSTANCE/config/OHS/<ohs_name>/httpd.conf file
and
the https port gets updated in ORACLE_INSTANCE/config/OHS/<ohs_name>/ssl.conf file
(In addition to this, if you are editing the ssl port, make additional changes in the ssl.conf file
edit the SSL Virtual Host Context to the same value as of the changed ssl port number. else
you may find wierd behavior .. the ssl port can turn into a non ssl port.)
If you are using Oracle Web Cache as a reverse proxy, you must update Oracle WebCache. From the Fusion Middleware Control navigation pane, expand the farm, then Web Tier. Select the Oracle Web Cache instance. From the Web Cache menu, choose Administration, then Origin Servers. Select the origin server for which you have changed the port, and click Edit.
The Edit Origin Server page is displayed. In the Port field, change the port number. Click OK. Restart Oracle Web Cache. (From the Web Cache menu, choose Control, then Restart.)
Note: For the OHS that comes along with OID, its not associated with Web Cache, So the above step is not necessary. But if you choose to change the ports of the OHS that was the part of Web Tier, the above step is necessary. The step is just included for sanity purpose.
Restart OPMN and all system components in that Oracle instance:
opmnctl stopall
opmnctl startall
Note: If you change the port or make other changes that affect the URL, such as changing the hostname, enabling or disabling SSL, you need to re-register partner applications with the SSO server using the new URL.
(Here its not required as such application is not configured)
::Steps to change the Proxy MBean or Admin port(default 9999)::
When editing a port number, the Admin port cannot be edited using Fusion Middleware Control.
Also The Oracle HTTP Server administration (proxy MBean) virtual host and its configuration, defined in the admin.conf file,
must not be edited with the WebLogic Scripting Tool (WLST).
Although this is a port Oracle HTTP Server uses for its
internal communication with Fusion Middleware Control, in most of the cases it
does not need to be changed. If you really want to change it, manually edit the
ORACLE_INSTANCE/config/OHS/<ohs_name>/admin.conf file.
In an Oracle Instance that is registered with a WebLogic domain, if the Oracle HTTP Server administration port (proxy MBean port in the admin.conf file) is changed after creating the component, then you must update the component registration with the WebLogic domain using the opmnctl updatecomponentregistration command, as follows:
opmnctl updatecomponentregistration -componentType OHS -componentName name
-proxyPort port
For example, if the proxy port of an Oracle HTTP Server component named ohs1 has
been changed to 9998, then use the following command:
opmnctl updatecomponentregistration -componentType OHS -componentName ohs1 -proxyPort 9998
sample run:
C:\Oracle\Middleware\asinst_1\bin>opmnctl updatecomponentregistration -componentType OHS -componentName ohs1 -proxyPort 9998
Command requires login to weblogic admin server (localhost):
Username: weblogic
Password:
Updating component registration on admin server.
Command succeeded.
This page resolved a 2 year outstanding production issue. Thanks!
ReplyDelete