2 Differences Between the Cloud and On-Premises Environments

Many of the Oracle SOA Cloud Service components differ slightly depending on which environment you are using. This chapter highlight these differences.

Topics

Platform Differences Between the Cloud and On-Premises Environments

This table describes high-level differences between running Oracle SOA in the cloud and on-premises environments.

Oracle SOA Cloud Service Oracle SOA Suite On-Premises

Available by subscription.

You install Oracle SOA Suite on your own hardware.

Provisioning of Oracle SOA Cloud Service automatically includes Oracle Java Cloud Service, which provides an Oracle WebLogic Server domain.

You create the complete domain.

Oracle SOA Cloud Service provides OPC-based backup services.

You must develop your own archival infrastructure.

You can either select an existing database (Oracle Database Cloud Service) in the tenant or enter the connection string of an on-premises database.

You must install a database.

High availability functionality is provided by default using a virtual machine restart.

You must set up an environment based on your high availability requirements.

Load balancing is provided by the built-in Oracle Traffic Director.

Oracle HTTP Server serves as the load balancer.

Application deployment directly from Oracle JDeveloper to the cloud is not supported. You must use one of the deployment mechanisms described in Deploying and Undeploying Applications for an Oracle SOA Cloud Service Instance.

Applications can be deployed directly from Oracle JDeveloper.

  • External network access must be configured at the virtual machine level and the Oracle Traffic Director level.

  • Logins to the virtual machine can be done through an SSH tunnel.

Network access for on-premises networks varies from site to site, as well as logic processes. Usually it is completely open to employees, as long as they have the right credentials.

Oracle Business Process Management Suite is not available with Oracle SOA Cloud Service. Instead, you can subscribe to Oracle Process Cloud Service or run Oracle Business Process Management Suite on Oracle Java Cloud Service.

Tutorial iconTutorial

After installing Oracle SOA Suite Cloud Service, you can install Oracle Business Process Management Suite on top of it.

Oracle Integration Continuous Availability features such as the following are not supported:

  • Circuit Breaker

  • Composite Instance Patching

  • Automatic Service Migration (ASM) support

  • Integration Workload Statistics

  • In-Memory SOA

Oracle Integration Continuous Availability features are supported.

For information about specific feature differences between the Oracle SOA and Oracle Service Bus cloud and on-premises environments, see Differences in Oracle SOA Behavior in the Cloud.

Differences Between Oracle SOA Cloud Service on Oracle Cloud Machine and on Oracle Public Cloud

Some features of Oracle SOA Suite behave differently on Oracle Cloud Machine than they do on Oracle Public Cloud. Here are some of the differences.

  • During provisioning on Oracle Cloud Machine, you do not specify a database connection. Instead you specify a connection to a network that provides access to a database.

  • Oracle Cloud Machine supports direct connection to an external database. Oracle Database Cloud Service is not required.

  • Oracle Cloud Machine uses NFS directories for storage.

  • Oracle API Manager is not supported on Oracle Cloud Machine.

  • Database backup is not provided in Oracle Cloud Machine. Oracle Cloud Machine provides domain backup, you back up the database using your normal procedures.

Differences in Oracle SOA Behavior in the Cloud

Some features of Oracle SOA behave differently in the cloud than in an on-premises environment.

  • Because shared disk is currently not available, writing to a shared file from multiple managed servers running in a cluster is not possible. To make this work in the cloud, managed servers would have to write to a file on their own local disks, and then an additional process would have to consolidate the files on one of the VMs.

  • File adapter read actions — each managed server only reads from its local directory.

  • JMS store and JTA transaction logs must use the Oracle database instead of file stores.

  • Oracle B2B large file processing - Files are written to the local file system of the managed server that processes the message. The Oracle B2B Console cannot read the file unless it is running on the same managed server (you see random behavior).

  • Connectivity between Oracle SOA Cloud Service adapters and on-premises applications might be blocked by your corporate firewall. Connections can be established by using an SSH tunnel from the application server to which the adapter connects.

  • The SOA debugger and automatic SOA composite application tester (unit tester) in Oracle JDeveloper are not supported when connecting to the SOA Cloud Service server.

  • Reports are not supported in Oracle Real-Time Integration Business Insight, installed as part of the Integration Analytics Cluster service type.

  • The iWay application adapters listed under Application Adapters (iWay) on Oracle Cloud Adapters Documentation are not supported by Oracle SOA Cloud Service.

  • The Oracle Traffic Director high availability features 12.2.1.2/12.1.3 are not supported with Oracle SOA Cloud Service.

  • Dehydration does work in the cloud as it does in the on-premises environment as described in Fusion Middleware Administering Oracle SOA Suite and Oracle Business Process Management Suite 12.2.1.2/12.1.3