Differences Between Oracle SOA Suite On-Premises and Oracle SOA Suite on Marketplace

Review the high-level differences between Oracle SOA Suite on-premises and Oracle SOA Suite on Marketplace in Oracle Cloud Infrastructure.

Oracle SOA Suite On-Premises	Oracle SOA Suite on Marketplace
Installed on your own hardware.	Provisioned on Oracle Cloud.
You create the complete domain.	Provisioning an Oracle SOA Suite on Marketplace instance automatically creates an Oracle WebLogic Server domain.
You must install a database.	During Oracle SOA Suite on Marketplace provisioning, you select the database to use. Note: You must provision a database prior to provisioning a Oracle SOA Suite on Marketplace instance.
You must set up an environment based on your high availability requirements.	High availability functionality is provided by default using a virtual machine.
Oracle HTTP Server serves as the load balancer.	Load balancing is provided by the Oracle Cloud Infrastructure load balancer.
You typically use shared storage.	Shared storage is available through Database File System (DBFS) or OCI File Storage Service (FSS) in the cloud. You can use a combination of database direct configuration for JMS and JTA logs and use DBFS for other shared file use cases. Log files are local to each virtual machine. Managed Servers by default will write to a file on their own local disks. Optionally, you can configure adapters to read/write files from shared storage (DBFS/FSS).
Additional memory and storage must be manually added to address high load.	Supports scaling up and adding storage to add more memory and storage when needed.
Stopping and starting the servers requires many manual steps.	Supports stop and start operations to reboot the VMs, node manager, load balancer, and SOA servers.
The domain must be manually extended to add a new Managed Server or add a new node.	Supports scaling out to add a new node and complete required configuration changes, and scaling in to remove a node from a cluster.
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.	External network access must be configured at the virtual machine level and the load balancer level. Logins to the virtual machine can be done through an SSH tunnel.
There should not be any connectivity issues blocking Oracle SOA Suite and your on-premises applications.	Connectivity between Oracle SOA Suite on Marketplace adapters and on-premises applications may be blocked by your corporate firewall. Connections can be established by setting up a VPN connection between Oracle Cloud and your on-premises network.
The SOA debugger and automatic SOA composite application tester (unit tester) in Oracle JDeveloper are supported when connecting to on-premises SOA Server.	The SOA debugger and automatic SOA composite application tester (unit tester) in Oracle JDeveloper are not supported when connecting to SOA Server in the cloud.
JMS store and JTA transaction logs can use either Oracle database or file stores.	JMS store and JTA transaction logs will use Oracle database instead of file stores.
Supports Oracle SOA for Healthcare.	Oracle SOA for Healthcare is not available.
After installing Oracle SOA Suite you can install Oracle Business Process Management Suite on top of it.	Oracle Business Process Management Suite is not available.