To get the SoaCS, you follow a wizard that guides you through the steps of setting up the Cloud. In here you choose what kind of services you want, Service Bus, SOA Suite, a combination of both or the API Manager. You enter the database credentials to connect to the database in the cloud and select how much CPU and memory you want to run on. You even have control in which data center the cloud is going to be hosted. This whole wizard is based on a webservice API, so if you want you can script and automate this process. 30 to 60 minutes later your SoaCS is ready and you can start using it.
So now you got your automated provisioned & back upped SOA Cloud Service. You can connect to an on premise ldap. You can set up an ssh tunnel, not a vpn yet, although this is on the roadmap. Oracle will apply the patches for you, but you are in control whether you want them or not. There is a precheck whether the patch can be applied or not, but you cannot schedule the patch for now, you can choose to apply or to wait with it, but if you choose to apply the patch, it will be done directly.
Oracle will not force you to upgrade, however, they only support the latest and the latest minus 1 version, so you cannot keep creating older versions once newer versions have come out.
Off course one of the great benefits of the cloud is the scaling, so when needed, you can add a node manually. The elastic scaling of nodes is on the roadmap, but not yet there. This means that in the near future you can add rules like ‘If the CPU uses more than 80%, add another one’.
You will have full EM and console access to your cloud instance.
Oracle is working on a white paper with best practices, this should come out soon. But if you can not wait, you can start a 30 days free trail, you will have to go through the JCS set up for this though. Click the ‘Try It’ button on the Java Cloud page for more info.
No comments:
Post a Comment