The cloud services are rapidly changing and are becoming easier all the time. This blog is an example of that.
One of the things that has changed is the network configuration of Oracle Java Cloud Service and Oracle SOA Cloud Service. It’s been a common task to create communication channels with these services to administer the environments. So that means creating specific security rules and typically it is a usual practice of creating different ports specific for the administration network traffic. Now, this already been done for you.
Here’s some of the changes that makes it easier.
#1 – Default Listen Ports
The default listen ports have now changed. These are mapped to 80 and 443. These port numbers seem to be arbitrary and only accessible through 80 and 443. With the other changes, it’s likely that we won’t need to change these configurations. This applies to both the non-secured and secured ports.
#2 – Admin Server Network Channel Additions
The admin server now has some additional network channels pre-defined. Note that configuring access to 7001 / 7002 now doesn’t impact external traffic and specific security rules can be configured. We can do this in the compute cloud service console. There’s also another 9001 pre-defined. Not sure specifically why it’s there. But it’s bound to localhost so I assume it for locally run WLST scripts. Even though it’s not shown in the image – the public address is the external public IP address of the compute instance – this was something that Carlos did in his blogs.
#3 – Managed Server Network Channel Additions
The managed server now also has some additional network channels pre-defined. Note that configuring access to 8001 / 8002 are typically the old network ports used by managed servers and are required for deployments (especially for JDeveloper). So same again – setting security rules can be configured in the compute cloud service cloud. Even though it’s not shown in the image – the public address is the external public IP address of the compute instance.
So … What’s the result?
It just means that things are a little easier to do …
- The network channels for administration are already available. You will still need to securely expose these ports.
- No need to muck around with public addresses and modifying the network configuration. What we need is now standard.
- Connecting JDeveloper or Maven to deploy and test against Java Cloud and SOA Cloud is easier.
2 thoughts on “Network Channels with Java Cloud + SOA Cloud has become a little easier”
So in Simple terms you are saying that we need to open port numbers 8001 & 8002 to public internet using Access rules? And what should be the port number used to connect from JDEV?
This is blog is a little out-dated as it was written in 2017. The OCI networking and how Java Cloud (has moved to WLS on OCI) is now different – with public / private subnets, VPNs and gateways. So, in short opening 8001 / 8002 to the public internet is not a requirement. From memory, it’s still the admin server port(s).