About the Default Access Ports
To use Oracle resources through Oracle SOA Cloud Service, access them through the default ports.
Ports Available from Within the Oracle Cloud Network
| Resource | Protocol | Default Port for Release 16.4.5 and Earlier | Default Port for Release 17.1.3 and Later |
|---|---|---|---|
|
Oracle WebLogic Server Administration Console |
HTTP |
7001 |
9071 |
|
Oracle Fusion Middleware Control |
HTTP |
7001 |
9071 |
|
Managed Server |
HTTP HTTPS |
8001 8002 |
9073 9074 |
|
Database |
SQL Net |
1521 |
1521 |
Ports Available from Outside the Oracle Cloud Network
| Resource | Protocol | Default Port |
|---|---|---|
|
Oracle WebLogic Server Administration Console |
HTTPS |
7002 |
|
Oracle Fusion Middleware Control |
HTTPS |
7002 |
|
Oracle Traffic Director Administration Console |
HTTPS |
8989 |
|
End user applications when the load balancer is enabled |
HTTP HTTPS |
80* 443 |
|
End user applications when the load balancer is disabled and there are multiple managed servers |
HTTP HTTPS |
9073* 9074 |
|
End user applications when the load balancer is disabled and there is only one managed server |
HTTP HTTPS |
80* 443 |
|
Service instance VM |
SSH |
22 |
|
Oracle Traffic Director VM |
SSH |
22 |
The diagram in About the Deployment Topology in Administering Oracle Java Cloud Service illustrates port allocation in an Oracle SOA Cloud Service VM deployment topology.
Note:
If a service instance is created with the Create New Oracle SOA Cloud Service Instance wizard, the HTTP port is disabled. You cannot enable the HTTP port for such a service instance through any of the interfaces to Oracle SOA Cloud Service, such as the Service Console or the REST API.* For end user applications, the default ports depend on how the service instance was created:
If the service instance was created by using the Create New Oracle SOA Cloud Service Instance wizard, the default ports are as follows:
-
If a load balancer is enabled, the HTTP port is disabled and the HTTPS port is 443 by default.
-
If a load balancer is not present and the service instance contains more than one managed server, the HTTP port is disabled and the HTTPS port is 8002/9074.
-
If a load balancer is not present and the Oracle SOA Cloud Service instance contains only one managed server, the server ports are 443 for HTTPS and disabled for HTTP.
If the service instance was created by using the REST API, the default ports are as follows:
-
If a load balancer is present, the default ports for applications are 80 for HTTP and 443 for HTTPS. You can reconfigure these ports.
-
If a load balancer is not present and the Oracle SOA Cloud Service instance contains more than one managed server, the default ports are 8001/9073 for HTTP and 8002/9074 for HTTPS.
-
If a load balancer is not present and the Oracle SOA Cloud Service instance contains only one managed server, the managed server ports are set to 80 and 443 respectively. You can reconfigure these ports.
You can continue to use HTTPS port 8081 to access an application running on an existing service instance that was created by using the Create New Oracle SOA Cloud Service Instance wizard. In this case, HTTP port 8080 is disabled and you can no longer use this port to access your application.
For information about creating a service instance by using the REST API, see Provision a New Service Instance in REST API for Oracle SOA Cloud Service.
Accessing Oracle SOA Cloud Service URLs Externally Using a Public IP Address
Oracle SOA Cloud Service URLs can be accessed externally using a public IP address. Use port 80 with the HTTP protocol and port 443 with the HTTPS protocol. This redirects access to port 8001. For example, to access the B2B console using HTTPS:
https://public_IP_address:443/b2bconsole