Enabling Oracle HTTP Server to Run as Root for Ports Set to Less Than 1024 UNIX Only

5-6 Oracle Fusion Middleware Administrators Guide ■ Task 4, Restart System Components Task 1 Modify the Oracle HTTP Server SSL Listen Port To change the Oracle HTTP Server SSL Listen port using Fusion Middleware Control: 1. From the navigation pane, expand the farm, then Web Tier, then select the Oracle HTTP Server instance. 2. From the Oracle HTTP Server menu, choose Administration, then Ports Configuration. 3. Select the Listen port that uses the HTTPS protocol, then click Edit. 4. Change the port number, then click OK. 5. Restart Oracle HTTP Server. From the Oracle HTTP Server menu, choose Control, then Restart. Task 2 Update Oracle Web Cache If you are using Oracle Web Cache as a reverse proxy, you must update Oracle Web Cache: 1. From the Fusion Middleware Control navigation pane, expand the farm, then Web Tier. Select the Oracle Web Cache instance. 2. From the Web Cache menu, choose Administration, then Origin Servers. 3. Select the origin server for which you have changed the port, and click Edit. The Edit Origin Server page is displayed. 4. In the Port field, change the port number. 5. Click OK. 6. Restart Oracle Web Cache. From the Web Cache menu, choose Control, then Restart. Task 3 Re-register mod_osso If you are using Oracle Single Sign-On, you must use Release 10.1.4.3. If you have enabled Oracle Single Sign-On authentication that is, you registered mod_osso, follow these steps to re-register mod_osso: 1. On the Oracle Single Sign-On host, set the environment variables ORACLE_ HOME and ORACLE_SID. 2. On the Oracle Single Sign-On host, run the ssoreg script, using the -remote_ midtier option. The script is located at: UNIX ORACLE_HOMEssobinssoreg.sh WindowsORACLE_HOME\sso\bin\ssoreg.bat For example, on LINUX: ORACLE_HOMEssobinssoreg.sh -oracle_home_path ORACLE_HOME -config_mod_osso TRUE -site_name example.com:7778 -remote_midtier -config_file ORACLE_HOMEApacheApacheconfossomyosso.conf -mod_osso_url http:example.com:7778 The resulting configuration file myosso.conf in the example is an obfuscated osso configuration file. Managing Ports 5-7 3. Copy the obfuscated osso configuration file to the Oracle HTTP Server host moduleconf directory for editing: ORACLE_INSTANCEconfigOHSohs_namemoduleconf Task 4 Restart System Components Restart OPMN and the system components in that Oracle instance: opmnctl stopall opmnctl startall

5.3.3 Changing Oracle Web Cache Ports

You can change the HTTP and HTTPS listen ports, the administration port, the statistics port and the invalidation port for Oracle Web Cache using Fusion Middleware Control. To change the port number: 1. From the navigation pane, expand the farm, then Web Tier, then select the Oracle Web Cache instance. 2. From the Web Cache menu, choose Administration, then Ports Configuration. 3. Select a port, then click Edit. 4. Change the port number, then click OK. 5. Restart Oracle Web Cache. From the Web Cache menu, choose Control, then Restart. 6. If you reconfigure the Web Cache invalidation port and you use Oracle Portal, you must update the port information maintained by Oracle Portal, as described in Section 5.3.5.2 .

5.3.4 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 OPMN, and all OPMN-managed processes: UNIX ORACLE_INSTANCEbinopmnctl stopall WindowsORACLE_INSTANCE\bin\opmnctl stopall 2. Open the opmn.xml file: UNIX ORACLE_INSTANCEconfigOPMNopmn Windows ORACLE_INSTANCE\config\OPMN\opmn 3. Under the notification-server element, modify the local, remote, or request parameter, depending on the port you are changing, in the port element, and then save the file. For example: port local=6101 remote=6201 request=6004