Changing the Oracle WebLogic Server Listen Ports Using the Administration Console

Managing Ports 5-5

5.3.2.2 Changing the Oracle HTTP Server Non-SSL Listen Port

To change the Oracle HTTP Server non-SSL HTTP Listen port, follow the procedures in the following tasks. Note that, on a UNIX system, if you are changing the Listen port to a number less than 1024, you must first perform the steps in Section 5.3.2.1 . ■ Task 1, Modify the Oracle HTTP Server Listen Port ■ Task 2, Update Oracle Web Cache ■ Task 3, Restart the System Components Task 1 Modify the Oracle HTTP Server Listen Port To change the Oracle HTTP Server 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 HTTP 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 Restart the System Components Restart OPMN and all system components in that Oracle instance: opmnctl stopall opmnctl startall

5.3.2.3 Changing the Oracle HTTP Server SSL Listen Port

To change the Oracle HTTP Server SSL HTTPS Listen port, follow the procedures in the following tasks. Note that, on a UNIX system, if you are changing the Listen port to a number less than 1024, you must perform the steps in Section 5.3.2.1 . ■ Task 1, Modify the Oracle HTTP Server SSL Listen Port ■ Task 2, Update Oracle Web Cache ■ Task 3, Re-register mod_osso 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.