FAQ

Choosing Java Cloud Service

What is Java Cloud Service?

Java Cloud Service provides an enterprise-grade platform to develop and deploy business Java applications in the cloud. With Java Cloud Service, you can maximize productivity with instant access to cloud environments that support any Java EE application, complete with integrated security and database access, and powered by Oracle WebLogic Server.

How do I choose between Java Cloud Service offerings?

Java Cloud Service has two 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.

 
  1. Java Cloud Service
  2. Java Cloud Service–SaaS Extension
If you need a platform for deploying custom business applications, Java Cloud Service is the right choice for you. Java Cloud Service is a purpose-built for environments with higher availability needs, such as user acceptance testing, staging and production.

If you are building extensions to one of the Oracle Software as a Service (SaaS) offerings like Oracle Sales Cloud, Oracle Service Cloud, Oracle Marketing Cloud, and so on, Java Cloud Service–SaaS Extensions is the best choice. You can also find some pre-built extensions from Oracle partners at Oracle Cloud Marketplace.

Which releases of WebLogic Server and product packages are supported by each Java Cloud Service offering?

WebLogic Release Product Level Java Cloud Service Java Cloud Service
–SaaS Extension
11g (11.1.1.7) Standard  
  Enterprise  
  Suite ✓(Limited**)
12c (12.1.3) Standard  
  Enterprise  
  Suite  
12c (12c2.1.3) Standard  
  Enterprise  
  Suite  

** 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.

I cannot see support for WebLogic Server 12.1.2 anymore when I create a new service?

The latest version of WebLogic Server 12c (12.1.3) is supported now. Any new service creation request for 12c will use the latest version 12.1.3. Any existing service instance created earlier using version 12.1.2 will continue to work. All admin operations will work as-is. You can continue using your JCS instance built on WebLogic Server 12.1.2.

Is Database Cloud Service included in Java Cloud Service?

No. Database Cloud Service is a prerequisite of Java Cloud Service and is priced separately. When provisioning a Java Cloud Service instance, you will be asked to provide the name of a Database Cloud Service instance that you have previously created. If you haven't previously created a Database Cloud Service instance, you will have to exit the Java Cloud Service instance creation instance wizard and do so before you can proceed.

Can I use Oracle Autonomous Transaction Processing (ATP) database with Java Cloud Service?

Yes. Starting December 2018, Java Cloud Service supports Oracle Autonomous Transaction Processing (ATP) database or Oracle Cloud Infrastructure database both for Infrastructure DB and Application DB.

Is a load balancer included in Java Cloud Service?

Yes, you can use Oracle Traffic Director (OTD) load balancer or Oracle-Managed Load Balancer with JCS on Oracle Cloud Infrastructure (OCI). The load balancer, which directs traffic across a cluster of WebLogic nodes, is an optional feature that you can select when creating a Java Cloud Service instance. For new installations, it is recommended to use Oracle Managed Load Balancer with JCS. Oracle Traffic Director is priced the same as Java Cloud Service. For example, if you buy two OCPUs for Java Cloud Service and one OCPU for Oracle Traffic Director, you will be charged for Java Cloud Service on three OCPUs.

What other cloud services are prerequisites for Java Cloud Service?

  Java Cloud Service Java Cloud Service
– SaaS Extension
Database Cloud Service (DBaaS, ATP, DBCS*)  
Database Cloud Service–
Schema Service
 
Object and Block Storage  

What are Java Cloud Service - SaaS Extension prerequisites?

Oracle Database Cloud Multitenant Service is a prerequisite of Java Cloud Service - SaaS Extension and is priced separately, both services are listed on the Oracle Fusion Cloud price list.

What's the best way to get started with Java Cloud Service?

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:

Documentation Click Here
Forum to ask questions Click Here
Training Click Here
Blogs Click Here

What's the best way to get started with Java Cloud Service - SaaS Extension?

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:

Documentation Click Here
Forum to ask questions Click Here
Training Click Here
Blogs Click Here

What does Java Cloud Service cost?

What's the recommended Java Cloud Service offering for integrating with Oracle Software as a Service offerings?

Java Cloud Service–SaaS Extension is recommended for building and deploying extensions to Oracle Software as a Service offerings. See the response to "How do I choose between Java Cloud Service offerings?" above for more details.

Can Java Cloud Service be used to integrate with Oracle SaaS?

Ideally, you'll want to use the Java Cloud Service–SaaS Extension offering because it's designed specifically for extension use cases. But if your extension use case is very loosely coupled with a SaaS service, you may be able to use the Java Cloud Service. Please reach out to your Oracle contact to further evaluate your use case and determine which offering suits your need the best.

What use cases are supported by Java Cloud Service?

You can deploy any Java application to Java Cloud Service. Our customers have done things like:

  1. Allow their own users to access a Software as a Service offering built on Java platform
  2. Create internal/departmental websites, or portals used by employees, partners, or customers
  3. Create e-commerce websites
  4. Build mobile back-end applications hosting APIs and services
  5. Launch ad-hoc projects that require quick time-to-market, such as campaigns, promotions, and proof-of-concepts
  6. Create environments for development and testing

What kind of applications can be deployed on Java Cloud Service and Java Cloud Service–SaaS Extension?

Java Cloud Service supports standard Java Platform, Enterprise Edition (Java EE 6 and 7), and Oracle Application Development Framework applications. For details, see Develop Applications using WebLogic Server 12c (12.2.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)

Who uses Java Cloud Service?

Java Cloud Service is used by a variety of roles within your organization. IT administrators use the service to stand up an environment for their business groups, and to deploy and manage production applications running in the environment. Architects and developers use the environment to develop applications. Quality assurance engineers use it for testing applications. And end users access the applications deployed in the environment.

Can I deploy multiple applications to the same Java Cloud Service instance?

Yes. You can deploy multiple Java EE archives to the same Java Cloud Service instance. The number of different Java EE archives that you can deploy to a particular Java Cloud Service instance depends on the instance's available file storage, Java VM heap space, and each deployment archive's need for these resources.

What is the availability SLA for Java Cloud Service?

The service level agreement can be found here.

In what regions is Java Cloud Service is available?

Currently, Java Cloud Service–SaaS Extension is available in North America and Europe. For Java Cloud Service, the information can be found on the data regions page.

Can I port an application running on JBoss or WebShere to Java Cloud Service?

Yes. Java Cloud Service is built on standard Java Enterprise Edition technology. RedHat JBoss and IBM WebSphere are Java Enterprise Edition containers (i.e., application servers), which means that any application running in these containers can run in Java Cloud Service.

What LDAP solution is available to Java Cloud Service?

You can use the embedded LDAP solution in WebLogic Server or an alternative to LDAP, such as using a database security provider in WebLogic Server and then authenticating against an Oracle Database Cloud Service data store.

Can I use my own (custom) domain name for accessing application on Java Cloud Service?

Can I use my own SSL certificate for my Java Cloud Service application?

Coherence Feature

What is the Coherence feature of Java Cloud Service?

The Coherence feature is the automated provisioning capability in Oracle Java Cloud Service that enables you to create a Coherence caching and data grid tier within an Oracle Java Cloud Service instance, and use cloud tooling for scaling in or scaling out the Coherence data tier.

Why use the Coherence feature in Java Cloud Service?

Coherence allows customers to cache frequently-used data to avoid expensive round-trips to underlying data sources, scale applications’ data in-memory to quickly support growth, offload and protect shared cloud services and databases and provide transparency and high-availability of data stored within the Coherence data tier.

What editions of Coherence are supported in the Coherence feature of Java Cloud Service?

Currently the Coherence Enterprise Edition feature set is supported in the Coherence feature of Java Cloud Service.

Which Java Cloud Service product packages and product levels support the Coherence feature of Java Cloud Service?

The Coherence feature of the Java Cloud Service is supported when choosing the WebLogic Server 12c version and the "High Performance Edition" option in the Java Cloud Service.

Is it possible to use Coherence in previous versions of WebLogic Server running within Java Cloud Service?

Yes. However, we do not provide cloud tooling for provisioning Coherence in WebLogic Server 11g within Java Cloud Service, and you won't be able to use the one-click cloud tooling for scaling to add or remove capacity.

Is it possible to add a Coherence data tier to an existing Java Cloud Service instance?

Yes, it is possible to add a Coherence data tier to an existing Java Cloud Service instance via the REST-API. We are working on integrating this functionality into the Java Cloud Service console as well.

Can I get a Coherence cluster without Java Cloud Service?

Currently Coherence is only available in the Oracle Cloud as an optional feature of the Java Cloud Service.

How do I scale the capacity of the Coherence data tier?

You can scale in or scale out the Coherence data tier either from the Oracle Java Cloud Service Console or by using the REST API.

How does patching work for the Coherence feature of Java Cloud Service?

Patching of the Coherence data tier is very similar to the patching of the Java Cloud Service itself. Patches are applied in a rolling fashion with no application or caching tier downtime. Individual Managed Coherence Servers are brought down gracefully, the high availability status of the data stored in the Coherence data tier is verified, the patch is applied, and the Managed Coherence Server is brought back up. This process is followed for each Managed Coherence Server in the environment until the patch has been applied to all managed servers.

Can I use Oracle Java Cloud Service tooling to back up and restore the Coherence data tier?

Currently, Oracle Java Cloud Service tooling backs up and restores only the details of the deployment environment. Oracle Java Cloud Service tooling does not back up or restore the data that is stored in the Coherence data tier.

Managing Java Cloud Service

How can I manage and monitor my Java Cloud Service instances?

You can monitor and manage Java Cloud Service through the Java Cloud Service console (a web-based interface) and via REST APIs. See REST API for Oracle Java Cloud Service.

For Java Cloud Service, can I access the configuration of the underlying application server, JVM, and/or operating system for my instances?

Yes. You have complete control of the underlying infrastructure. You can SSH into your virtual machines and change any aspect of the configuration you wish. Alternatively, you can use either the WebLogic Administration Console or Oracle Enterprise Manager Cloud Control to manage and monitor your application and deployment environment. You can also use WLST to make configuration changes to the WebLogic Server instance.

Does Oracle provide automatic Disaster Recovery of my environment?

Oracle offers its cloud services in multiple data centers within a region. The services have built-in tools to stand up environments in different data centers in a region. If you have immediate need for a disaster recover site, you can create a duplicate environment in a second data center and keep them synchronized.

How do I manage the users of applications deployed to an Java Cloud Service instance?

Each Java Cloud Service instance is automatically configured with an identity store associated with its identity domain. You can share the same identity store among multiple Java Cloud Service instances by placing them in the same identity domain. The content of the identity store (that is, the individual users and their roles that are associated with a Java Cloud Service instance) is managed through the Oracle Cloud identity management console. For more information, see About Oracle Java Cloud Service Roles and User Accounts.

Are there REST APIs available to manage my environment?

Yes. REST APIs are available for all operations that you can perform using the Web-based portal. Refer to the REST API reference documentation for more information.

What Single Sign-On (SSO) solution is available to Java Cloud Service?

SSO is not included in Java Cloud Service, but can be configured in WebLogic using the administration console. See Configuring Single Sign-On with Web Browsers and HTTP Clients.

Managing Java Cloud Service–SaaS Extension

How can I manage and monitor my Java Cloud Service–SaaS Extension instances?

Java Cloud Service–SaaS Extension can be managed and monitored through the Java Cloud Service console (a web-based interface) and a command-line interface which can be found within the Java Cloud Service–SaaS Extension SDK. For more information about these interfaces, see the Oracle Java Cloud Service-SaaS Extension documentation and About the Oracle Java Cloud Service–SaaS Extension SDK.

For Java Cloud Service–SaaS Extension, can I access the configuration of the underlying application server, JVM, and/or operating system for my instances?

No. Java Cloud Service–SaaS Extension simplifies the effort needed to deliver Enterprise Java applications by simplifying the complexity of the infrastructure layer and automating its maintenance. As a result, Java Cloud Service–SaaS Extension does not expose any of the underlying execution environment's operating system, middleware, or JVM configurations to its users. Selected application metrics are exposed through the Java Cloud Service–SaaS Extension monitoring interfaces. For more information, see  Oracle Java Cloud Service–SaaS Extension.

Does Oracle provide automatic scalable Java Cloud Service–SaaS Extension environment in the cloud?

You can easily scale out a Java Cloud Service–SaaS Extension environment from the web-based portal. You can go from a one-node S1 environment to a two-node S2 or a four-node S4 environment at any time. The scale-out operation is in place and does not require any downtime.

How do I manage the users of applications deployed to a Java Cloud Service–SaaS Extension instance?

Each Java Cloud Service–SaaS Extension service instance is automatically configured with an identity store associated with its identity domain, which contains users and roles. You can share the same identity store among multiple service instances by placing them in the same identity domain. For more information about managing users and roles, see  Managing Users and Roles.

Are there REST APIs available to manage my Java Cloud Service–SaaS Extension environment?

No. However, a command line interface is available from the Java Cloud Service–SaaS Extension SDK, which is downloadable from  here. The SDK contains documentation for all supported commands. You can also find a command reference in the online documentation.

Can I use my own (custom) domain name (vanity URL) for accessing application on Java Cloud Service–SaaS Extension?

No. Your Java Cloud Service–SaaS Extension application has a predefined URL and an associated SSL certificate created by Oracle, so you don't have to worry about creating a new URL for your application.

What Single Sign-On (SSO) solution is available to Java Cloud Service–SaaS Extension?

Single-Sign On (SSO) between applications deployed on Java Cloud Service–SaaS Extension and Oracle Software as a Service offerings (like Sales Cloud, Service Cloud, Marketing Cloud, and so on) is supported out of the box. You don't have to do anything to enable SSO capabilities. This is one of the key benefits of using Java Cloud Service–SaaS Extension, as it automatically takes care of all security setup, including SSO, with other SaaS services offered in Oracle Cloud. For details, see Securing Oracle WebLogic Server 11g Release 1 (10.3.6)

Developing with Java Cloud Service

What types of applications can I deploy to Java Cloud Service instances?

Java Cloud Service supports standard Java Platform, Enterprise Edition (Java EE 6 and Java EE 7), and Oracle Application Development Framework applications. For details, see Developing Applications in WebLogic Server in Understanding Oracle WebLogic Server 12c (12.1.3).

Do I have to use specific development tools to write applications for Java Cloud Service?

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 and cloud services Oracle has developed to help simplify implementation and deployment of applications to Java Cloud Service:
 

  • Java Cloud Service productivity tools: Contained within Oracle JDeveloper, Oracle Enterprise Platform for Eclipse, and NetBeans IDEs, these tools enable you to directly deploy enterprise applications to Java Cloud Service instances and to inspect service instance logs directly from the IDE.
  • Developer Cloud Service: Hosted team development and delivery platform including issue tracking, code versioning, wiki, agile-development tools, continuous integration and delivery automation.

Can JDeveloper, Netbeans or Eclipse deploy to Java Cloud Service?

Yes. If the Java Cloud Service instance is setup to accept T3 protocol over HTTP, applications can be deployed from a correctly configured JDeveloper, Eclipse or Netbeans IDE. Refer to the official documentation  for information on using IDEs with Java Cloud Service.

How do I deploy my application to Java Cloud Service?

How do I copy files from on-premises to the Java Cloud Service instance?

You can use SCP and your SSH key to move files to a Java Cloud Service instance virtual machine and storage location. See Accessing a VM Through Secure Shell (SSH).

Can I use Developer Cloud Service to build and deploy my application to Java Cloud Service?

Yes, Developer Cloud Service can deploy to both Java Cloud Service and Java Cloud Service SaaS Extension.

What is the default Java heap size when a managed WebLogic Server is created?

The default heap size is 2GB, but you can change this using the WebLogic administration console. For the change to take effect, you must restart (stop/start) the managed servers. See Increasing the Java Heap size for a managed server and Start Managed Servers from the Administration Console for more information.

What is the default port for accessing applications deployed on my Java Cloud Service?

Refer to this document for the default port to access your applications.

Can I change the port to access my Java Cloud Service applications to 80/443?

Yes. You can use any port for your applications running on Java Cloud Service instance. Refer to the documentation for details on using other ports with your service.

What is the default URL for accessing my application deployed on Java Cloud Service?

By default, any application deployed in Java Cloud Service instance 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.

Can I use any Java frameworks and libraries in an application deployed to Java Cloud Service?

Yes, there are no restrictions on what software frameworks or libraries can be included in applications deployed to Java Cloud Service.

What inbound and outbound protocols does Java Cloud Service support?

By default only HTTP and HTTPS are enable but other protocols like RMI/T3 can be enabled in the Compute Service console by opening the necessary port for your Java Cloud Service instance.

Developing with Java Cloud Service–SaaS Extension

What types of applications can I deploy to Java Cloud Service–SaaS Extension instances?

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).

Do I have to use specific development tools to write applications for Java Cloud Service–SaaS Extension?

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:

  • Java Cloud Service Software Development Kit (SDK): Contains a command-line interface, Apache Ant tasks, and Maven plugins for interaction with Java Cloud Service–SaaS Extension.
  • Java Cloud Service productivity tools: Contained within the Oracle JDeveloper, Oracle Enterprise Platform for Eclipse, and NetBeans IDEs. These tools support features such as the direct deployment of enterprise applications to Java Cloud Service–SaaS Extension instances and the inspection of the service instance logs directly from the IDE.

Can JDeveloper, Netbeans or Eclipse deploy to Java Cloud Service–SaaS Extension?

Yes, if the Java Cloud Service—SaaS Extension instance is setup to accept T3 protocol over HTTP, applications can be deployed from a correctly configured JDeveloper, Eclipse or Netbeans IDE. Please refer to the official documentation to use IDEs with Java Cloud Service-SaaS Extension.

How do I deploy my application to Java Cloud Service–SaaS Extension?

Can I use Developer Cloud Service to build and deploy my application to Java Cloud Service–SaaS Extension?

Yes, Developer Cloud Service can be used to build and deploy applications to Java Cloud Service–SaaS Extension.

Can I change the port to access my Java Cloud Service–SaaS Extension applications to 80/443?

No. You can not change the ports where your application are running on Java Cloud Service–SaaS Extension. The default port is 443 (HTTPS). The URL is automatically created for you application with appropriate SSL certificate. So you don't have worry about setting URLs or certificates.

What is the default URL for accessing my application deployed on Java Cloud Service–SaaS Extension?

Your application has a predefined URL and an associated SSL certificate created by Oracle. You do not have to worry about creating a new URL for your application. The URL depends on the data center and region your service is running. Please go to the Java Cloud Service–SaaS Extension console to see the list of your applications deployed. On that list, there is a small icon for testing the application. If you click on that icon, the console will show you the URL of your application. Typically the URL follows this pattern: https:// - . .oraclecloudapps.com.

Can I run any Java frameworks, libraries in Java Cloud Service–SaaS Extension?

No. For technical and security reasons, a small number of specific APIs are prevented from executing in Java Cloud Service–SaaS Extension instances. Applications using these APIs are not deployable because they will not pass the whitelist phase of the Java Cloud Service—SaaS Extension deployment process. The Java Cloud Service SDK includes a whitelist tool that enables you to check whether an application is in violation of the Java Cloud Service whitelist. To learn more, see " Downloading the Oracle Java Cloud Service - SaaS Extension SDK".

What inbound and outbound protocols does Java Cloud Service–SaaS Extension support?

Only HTTP and HTTP/S are supported.

When will other protocols be supported for outbound communication from Java Cloud Service–SaaS Extension?

Oracle is working on a long-term plan to provide a virtual private cloud secure connection to non-Oracle Cloud environments.

Other Questions

Is Windows Operating System supported in Java Cloud Service on Oracle Cloud?

No, Windows operating system is not currently supported. Oracle Linux is the supported operating system.

Can I bring my own Operating System for Java Cloud Service to Oracle Cloud?

No, currently you can not bring your own operating system for Java Cloud Service (JCS). JCS is a platform service that runs on top of Oracle Linux Operating System.

Who is responsible for Operating System patching of Java Cloud Service Virtual Machines?

You are responsible for patching the Operating System as you have full access to the Virtual Machine. Oracle Linux patches and support is included with your JCS subscription.
×
Call us now
1-800-633-0738 (United States)

Contact
×
Call us now
1-800-633-0738 (United States)

Technical Support

Oracle Cloud Discussion Forums