PaaS customers, in the past, have been able to provision their instances only over the flat network of Oracle Public Cloud (OPC). However, at present, support for PaaS computes with IP networks has been released. As a result, customers now have a choice to provision PaaS instances, e.g. SOA Cloud Service (SOACS), MFT Cloud Service (MFTCS) or Database Cloud Service (DBCS), using IP networks.
This option clearly comes with 2 distinct advantages. Firstly, there is no need to configure GRE tunnels between PaaS compute and the VPN Gateway running in OPC. Secondly, the customers have the flexibility of defining their own network subnet and topology for their PaaS instances running within OPC.
Since this feature is recently released, this blog is an attempt to provide guidance with the basic setup and configuration of PaaS computes using IP networks.
To demonstrate the use case, a 2-node SOACS cluster, with an Oracle Traffic Director (OTD) serving as the load balancer, is provisioned first with IP networks. The steps outlined here are conceptually the same for an MFTCS cluster as well. The cluster is then connected to an on-premises private network over VPN.
The overall solution architecture with the network topology and VPN connectivity is shown in Fig. 1 here.
Fig. 1 PaaS Computes over IP Network with VPN connectivity to on-premises network
Before provisioning of the SOACS cluster, it is necessary to create a DBCS instance for the SOA Infrastructure repository.
Therefore, in summary, 5 compute instances are provisioned in the identity domain within OPC, as listed below.:
For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.