To view the port numbers for Oracle WebLogic Server, you can use the WLST get command, with an attribute. For example, to get the Administration Port, use the following command:

wls:/WLS_domain/serverConfig> get('AdministrationPort')
9002

You can view the port numbers of the domain, the Administration Server, Managed Servers, or components, such as Oracle HTTP Server, using Fusion Middleware Control.

For example, to view the ports of a domain:

The Port Usage detail table shows the ports that are in use, the IP Address, the component, the channel, and the protocol.

You can also view similar pages for the Administration Server, Managed Servers, and components, such as Oracle HTTP Server, by navigating to the target and choosing Port Usage from the target's menu.

You can change the Node Manager listen port using Fusion Middleware Control or WLST, as described in the following topics:

If your environment includes an Oracle Database that functions as a metadata repository, and you want to change the listener port number for that database, perform the procedure in this section.

First, determine if it is necessary to change the listener port number. If you are concerned that you have another database on your host using the same port, both databases can possibly use the same port.

Note that multiple Oracle Database 10g, Oracle Database 11g, Oracle Database 12c, Oracle Database 14c databases can share the same Oracle Net listener port. If you are using an Oracle Database as a metadata repository on the same host that contains another Oracle Database 10g, Oracle Database 11g, Oracle Database 12c, Oracle Database 14c database, they can all use port 1521. There is no need to change the listener port number.

To change the database listener port:

1. Stop all components that use the metadata repository. See Starting and Stopping Oracle Fusion Middleware for instructions.

2. On the metadata repository host, change the Oracle Net listener port for the metadata repository:

   1. Ensure that the ORACLE_HOME and ORACLE_SID environment variables are set.

   2. Stop the metadata repository listener:

      lsnrctl stop
      

   3. Edit the listener.ora file, which is located at:

      (UNIX) ORACLE_HOME/network/admin/listener.ora
      (Windows) ORACLE_HOME\network\admin\listener.ora
      

      Under the LISTENER entry, update the value for PORT. Save the file.

   4. Edit the tnsnames.ora file. The default location is:

      (UNIX) ORACLE_HOME/network/admin/tnsnames.ora
      (Windows) ORACLE_HOME\network\admin\tnsnames.ora
      

      Make the following changes to the file:

      • Update the PORT value in each entry that applies to MDS Repository.

      • Add an entry similar to the following:

        newnetport =
          (DESCRIPTION =
            (ADDRESS = (PROTOCOL = tcp) (HOST = hostname) (PORT = port)))
        

        In the example, hostname is the fully qualified host name and port is the new port number.

   5. Start the metadata repository listener:

      lsnrctl start
      

   6. Using SQL*Plus, log in to the metadata repository as the SYSTEM user with SYSDBA privileges and run the following command:

      SQL> ALTER SYSTEM SET local_listener='newnetport' scope=spfile;
      

   7. Using SQL*Plus, restart the metadata repository:

      SQL> SHUTDOWN
      SQL> STARTUP
      

3. Change the system data source to use the new port number for the metadata repository. To do so, you can use Fusion Middleware Control:

   1. In the Change Center, click Lock & Edit.

   2. In the navigation pane, expand select the domain.

      The WebLogic Domain page is displayed.

   3. From the WebLogic Domain menu, select JDBC Data Sources.

      The Summary of JDBC Data Sources page is displayed.

   4. Select the data source you want to change.

      The JDBC Data Source page is displayed.

   5. Select the Connection Pool tab.

   6. To change the database port, modify the Database URL field. For example:

      jdbc:oracle:thin:@hostname.domainname.com:1522/orcl
      

   7. Click Save.

   8. Restart the servers that use this data source. (Click the Targets tab to see the servers that use this data source.)