Java Cloud Service has three offerings that target two broad use cases: one platform for custom business applications, and one for building extensions to Oracle SaaS (such as CRM, HCM, and so on. The three offerings are:
** - JCS-SX includes some of the suite features like use of active gridlink to connect to database cloud service (multi-tenant / schema edition), but not all.
Java Cloud Service public trials are coming soon. Please reach out to your Oracle Sales Rep to enroll you in a private trial program. You can get up-to-speed with the service by reading Getting Started with Oracle Java Cloud Service.
Look at these to learn more:
Java Cloud Service - SaaS Extension is easy to use and understand. To get started, request a trial here. You can get up-to-speed with the service by reading Getting Started with Oracle Java Cloud Service. Look at these to learn more:
See Java Cloud Service Pricing.
All available shapes up to eight OCPUs are supported, both general purpose and high memory configurations. High memory configurations typically have twice as much memory as the corresponding general purpose configuration with the same number of OCPUs. Oracle Traffic Director load balancer may be deployed only onto general purpose configurations. See About Shapes for more information on available compute shapes.
You can deploy any Java application to Java Cloud Service. Our customers have done things like:
Java Cloud Service supports standard Java Platform, Enterprise Edition (Java EE) 6, and Oracle Application Development Framework applications. For details, see Developing Applications in WebLogic Server in Understanding Oracle WebLogic Server 12c (12.1.3). Java Cloud Service—SaaS Extension supports standard Java Platform, Enterprise Edition (Java EE) 5, and Oracle Application Development Framework applications. For details, see Programming Models in Introduction to Oracle WebLogic Server 11g Release 1 (10.3.6)
The service level agreement can be found here.
Yes. See Defining a Custom Domain Name for an Oracle Java Cloud Service Instance Application Environment.
Yes. See Configuring SSL for Your Custom Domain in an Oracle Java Cloud Service Instance Application Environment.
No. While you don't need any specific tools or SDKs to develop applications for Java Cloud Service, you can take advantage of the optional tools Oracle has developed to help simplify implementation and deployment of applications to Java Cloud Service:
By default, any application deployed in Java Cloud Service or Java Cloud Service–Virtual Image can be accessed using the Public IP address attached to the load balancer or the WebLogic Managed Server serving the application. See this document for steps to find out the default URL for you application.
You can always assign your own URL. See question "Can I use my own (custom) domain name (vanity URL) for accessing application on Java Cloud Service?" for more details.
No, you do not need any specific tool or SDK to develop applications for Java Cloud Service–SaaS Extension. However, Oracle has developed the following optional tools to help simplify implementation and deployment of applications to Java Cloud Service–SaaS Extension:
Total execution time for page wcsHomepageExLayout is:302ms
Call opcMetaData ran 1 times with an average time of 4.00ms and a total time of 4.0ms
Call navBarMenu ran 1 times with an average time of 5.00ms and a total time of 5.0ms
Call opcFooter ran 1 times with an average time of 6.00ms and a total time of 6.0ms
Call wcsContactandFooter ran 1 times with an average time of 5.00ms and a total time of 5.0ms