What’s New for Oracle Java Cloud Service

This document describes what's new in Oracle Java Cloud Service on all infrastructure platforms where it's available:

For each infrastructure platform, information is organized by the date a specific feature or capability became available. Additionally, the document provides historical “what’s new” information for the past 12 months.

On Oracle Cloud Infrastructure and Oracle Cloud Infrastructure Classic

The following sections describe what’s new in Oracle Java Cloud Service on Oracle Cloud Infrastructure and Oracle Cloud Infrastructure Classic.

As soon as new features become available, cloud tools for managing Oracle Java Cloud Service instances are upgraded in the data centers where Oracle Cloud services are hosted. You don't need to request an upgrade to be able to use the new features.

Except where noted, upgrades to cloud tools are available to use on your existing Oracle Java Cloud Service instances. However, new features that change how service instances are created do not affect your existing service instances.

September 2020

Feature Description

Adding storage for user defined partition extends the existing partition

When you add block storage volume to a node that has a user-defined partition, instead of adding a new mount point, the existing storage volume expands. See About Adding Block Storage to a Node in Administering Oracle Java Cloud Service.

WebLogic Server 12.1.3.0 not supported

You can no longer create an Oracle Java Cloud Service instance based on WebLogic Server 12.1.3.0. You can create service instances on WebLogic Server releases 11.1.1.7, 12.2.1.3, and 12.2.1.4.

For Oracle Cloud at Customer, you can create an Oracle Java Cloud Service instance using WebLogic Server 12.1.3.0. However, as WebLogic Server 12.1.3.0 is not supported, we recommend to use supported versions to create an instance.

Apply new patches

New 12.2.1.2 bundle 12.2.1.2.200809 is available with the following bug fixes:

  • WS 31111141
  • XDK 30385564
  • XDK 30252137
  • XDK 29772498
  • XDK 28256791

You can see the availability of a patch on the Administration tile and on the Patching page. See Applying a Patch and Exploring the Patching Page in Administering Oracle Java Cloud Service.

August 2020

Feature Description

Controlled Availability

Oracle Java Cloud Service is in Controlled Availability phase from August 31, 2020. For more information, see WLS Version Support in JCS, and JCS Controlled Availability.

REST API to update Email Notificaton Post Provision

You can update an email after service instance creation via REST API using the notificationEmail parameter. See View a Service Instance and Update a Service Instance Configuration in REST API for Oracle Java Cloud Service.

Apply new patches

ADR for Oracle WebLogic Server July critical patch updates (CPUs) are available.

You can see the availability of a patch on the Administration tile and on the Patching page. See Applying a Patch and Exploring the Patching Page in Administering Oracle Java Cloud Service.

July 2020

Feature Description

Delete the Oracle-managed load balancer provisioned with a service instance

You can now remove the Oracle-managed instance of Oracle Cloud Infrastructure Load Balancing that's provisioned when you created your Oracle Java Cloud Service instance (with or without Oracle Identity Cloud Service). This removal feature is implemented in the REST API only. See Delete the Oracle-Managed Load Balancer in REST API for Oracle Java Cloud Service.

To use your own instance of Oracle Cloud Infrastructure Load Balancing for the Oracle Java Cloud Service instance, see Use an Oracle Cloud Infrastructure Load Balancer in Administering Oracle Java Cloud Service.

If the sample application was originally deployed to the Oracle Java Cloud Service instance, you can use the REST API to update the sample application URL that's shown on the Oracle Java Cloud Service Console. See Update a Service Instance Configuration in REST API for Oracle Java Cloud Service.

Apply new patches

New patch set updates (PSUs) are available.

You can see the availability of a patch on the Administration tile and on the Patching page. See Applying a Patch and Exploring the Patching Page in Administering Oracle Java Cloud Service.

May 2020

Feature Description

DB System based on Logical Volume Manager

Oracle Java Cloud Service supports using an Oracle Cloud Infrastructure 1-node virtual machine (VM) DB system that uses Logical Volume Manager (LVM) as the storage management software. Previously you could not provision an instance if it's associated with a 1-node VM DB System created by the fast provisioning option that uses LVM.

See Create an Oracle Cloud Infrastructure Database in Administering Oracle Java Cloud Service.

T3 and tunneling are disabled

(Updated June 2020)

When you create an Oracle Java Cloud Service instance, the WebLogic administration server is configured with network channels on ports 7001 and 7002 that support HTTP and HTTPS traffic only. The channels do not support the T3 and T3 over SSL (T3S) protocols, and they do not support tunneling.

To connect to the administration server with tools that use the T3 or T3S protocols, you must use the default network channels on ports 9071 and 9072. These ports are not accessible from outside of Oracle Cloud.

Similarly, WebLogic managed servers are configured with network channels on ports 8001 and 8002 that support HTTP and HTTPS traffic only. Tunneling is also disabled on the managed servers. Internal T3 and T3S communication is done using ports 9073 and 9074.

As a result of the port and protocol changes, you'll need to use the Oracle Cloud Infrastructure Console to configure security ingress rules for the administration server VM and the managed server VMs before you can perform certain tasks such as deploying applications via Oracle JDeveloper. See Create an Ingress Rule in Administering Oracle Java Cloud Service.

On existing Oracle Java Cloud Service instances, we recommend you restrict access to the WebLogic administration server from the Internet by configuring security ingress rules using a fixed set of IPs or a restricted CIDR matching your organization's network addresses. On applicable service instances, restrict also access to the Oracle Traffic Director administration server. See the My Oracle Support Document ID 2664435.1.

If your Oracle Java Cloud Service instance is assigned to the predefined Virtual Cloud Network (VCN) named svc-vcn (found in the ManagedCompartmentForPaaS compartment), submit a Service Request (SR) with Oracle Support Services to obtain access for updating ports and security ingress rules in svc-vcn.

Apply new patches

New patch set updates (PSUs) are available:

  • PSU for Oracle WebLogic Server

  • PSU for Java Development Kit (JDK)

You can see the availability of a patch on the Administration tile and on the Patching page. See Applying a Patch and Exploring the Patching Page in Administering Oracle Java Cloud Service.

April 2020

Feature Description

Apply new patch

A patch is available for service instances based on Oracle WebLogic Server 12.2.1.2.

See Applying a Patch and Exploring the Patching Page in Administering Oracle Java Cloud Service.

March 2020

Feature Description

Upgrade the WebLogic Server release to 12.2.1.4

You can now upgrade the WebLogic Server release from 12c (12.1.3, 12.2.1.0, 12.2.1.2, 12.2.1.3) or 11g (11.1.1.7) to WebLogic Server release 12c (12.2.1.4) for an existing Oracle Java Cloud Service instance. If a service instance includes Oracle Traffic Director (OTD) and is running WebLogic Server release 12.2.1.3, 12.2.1.2 or 12.2.1.0, both OTD and WebLogic Server versions are upgraded to 12.2.1.4 at the same time.

See Upgrade the WebLogic Server Release for an Oracle Java Cloud Service Instance in Administering Oracle Java Cloud Service.

February 2020

Feature Description

Support for WebLogic Server version 12.2.1.4

Create service instances on Oracle WebLogic Server version 12.2.1.4.

If you create a service instance that runs WebLogic Server 12.2.1.4 and includes a user-managed load balancer, the load balancer runs Oracle Traffic Director 12.2.1.4.

See What's New in Oracle WebLogic Server.

Support for DB Systems running 19c

Create a service instance and associate it with an Oracle Cloud Infrastructure Database running Oracle Database 19c.

Oracle Database 19c is supported only for service instances running Oracle WebLogic Server 12.2.1.3 or later.

Scale Oracle Cloud Infrastructure nodes

Scale up or down nodes in service instances running in Oracle Cloud Infrastructure regions.

Previously, this feature was available only for Oracle Cloud Infrastructure Classic service instances.

See Scale an Oracle Java Cloud Service Node in Administering Oracle Java Cloud Service.

Add a vanity URL to an Oracle-managed load balancer

Add a custom vanity URL to an Oracle-managed load balancer for a service instance in Oracle Cloud Infrastructure. For example, myapp.example.net.

See Configure a Vanity Domain Name for a Service Instance in Administering Oracle Java Cloud Service.

Apply new patches

New patch set updates (PSUs) are available:

  • PSU for Oracle WebLogic Server

  • PSU for Java Development Kit (JDK)

You can see the availability of a patch on the Administration tile and on the Patching page. See Applying a Patch and Exploring the Patching Page in Administering Oracle Java Cloud Service.

December 2019

Feature Description

Limit load balancer access

After provisioning an Oracle-managed load balancer for an Oracle Java Cloud Service instance in an Oracle Cloud Infrastructure region, you can specify which IP address is allowed to access the load balancer. You can create, update, or delete access control rules. Previously, all traffic from the public Internet was enabled and you could not restrict access. This feature is implemented in the REST API only.

See Add an Access Control Rule to a Load Balancer in REST API for Oracle Java Cloud Service.

November 2019

Feature Description

Apply new patches

New patch set updates (PSUs) are available:

  • PSU for Oracle WebLogic Server

  • PSU for Java Development Kit (JDK)

You can see the availability of a patch on the Administration tile and on the Patching page. See Applying a Patch and Exploring the Patching Page in Administering Oracle Java Cloud Service.

October 2019

Feature Description

Oracle Enterprise Linux 7 supported

Oracle Java Cloud Service now runs on the Oracle Enterprise Linux 7 platform.

September 2019

Feature Description

Universal Credit accounts do not use My Services Dashboard

After signing into Oracle Cloud, you use the Oracle Cloud Infrastructure Console to access your Platform Services. Previously you were required to access these services from the My Services Dashboard. See Access Oracle Java Cloud Service from the Infrastructure Console in Administering Oracle Java Cloud Service.

August 2019

Feature Description

Select among multiple identity domains

You can create a service instance within a specific identity domain in Oracle Identity Cloud Service. Each identity domain has an independent set of users. For example, you might create separate identity domains for test users and production users. By default, service instances are created in the primary identity domain in Oracle Identity Cloud Service.

See:

Apply new patches

New patch set updates (PSUs) are available:

  • PSU for Oracle WebLogic Server

  • PSU for Java Development Kit (JDK)

You can see the availability of a patch on the Administration tile and on the Patching page. See Applying a Patch and Exploring the Patching Page in Administering Oracle Java Cloud Service.

June 2019

Feature Description

Select regional subnet for an Oracle-Managed Load Balancer

(Available only on Oracle Cloud Infrastructure)

When you configure an Oracle-Managed Load Balancer for an Oracle Java Cloud Service instance in an Oracle Cloud Infrastructure region, you can specify one regional subnet. Subnets marked as Regional can contain resources in any of the region's availability domains, and are not specific to one availability domain. This enables automatic failover from one availability domain to another if needed.

See:

Apply new patches

New patch set updates (PSUs) are available:

  • PSU for Oracle WebLogic Server

  • PSU for Java Development Kit (JDK)

You can see the availability of a patch on the Administration tile and on the Patching page. See Applying a Patch and Exploring the Patching Page in Administering Oracle Java Cloud Service.

May 2019

Feature Description

Migrate an Oracle Java Cloud Service instance with authentication by Oracle Identity Cloud Service to Oracle Cloud Infrastructure

If you provisioned your existing Oracle Java Cloud Service instance with authentication by Oracle Identity Cloud Service on an Oracle Cloud Infrastructure Classic region, you can migrate your service instance to an Oracle Cloud Infrastructure region.

See Migrating Oracle Java Cloud Service Instances to Oracle Cloud Infrastructure.

Upgrade the WebLogic Server release from 11.1.1.7 to 12.2.1.3

You can now upgrade the WebLogic Server release from 11g (11.1.1.7) to WebLogic Server release 12c (12.2.1.3) for an existing Oracle Java Cloud Service instance. As in the previous release, you can also upgrade from WebLogic Server releases 12.1.3, 12.2.1.0, and 12.2.1.2 to release 12.2.1.3.

See Upgrade the WebLogic Server Release for an Oracle Java Cloud Service Instance in Administering Oracle Java Cloud Service.

Update the infrastructure schema password for an Oracle Cloud Infrastructure Database or Oracle Autonomous Transaction Processing database deployment

You can now use the REST API to update the infrastructure schema password for an Oracle Java Cloud Service instance provisioned using Oracle Cloud Infrastructure Database or Oracle Autonomous Transaction Processing.

See Change the Database Schema Password in REST API for Oracle Java Cloud Service.

April 2019

Feature Description

Migrate an Oracle Java Cloud Service instance to Oracle Cloud Infrastructure

If you provisioned your existing Oracle Java Cloud Service instance on an Oracle Cloud Infrastructure Classic region, you can migrate your service instance to an Oracle Cloud Infrastructure region.

See Migrating Oracle Java Cloud Service Instances to Oracle Cloud Infrastructure.

Upgrade the WebLogic Server release to 12.2.1.3

You can upgrade the WebLogic Server release from 12.1.3, 12.2.1.0, or 12.2.1.2 to WebLogic Server release 12.2.1.3 for an existing Oracle Java Cloud Service instance. The upgrade procedure leverages the tools you would use to upgrade an on-premises instance.

See Upgrade the WebLogic Server Release for an Oracle Java Cloud Service Instance in Administering Oracle Java Cloud Service.

WebLogic Server 12.2.1.2 not supported You can no longer create an Oracle Java Cloud Service instance based on WebLogic Server 12.2.1.2. You can create service instances on WebLogic Server releases 11.1.1.7, 12.1.3, and 12.2.1.3.

WebLogic Server 12.2.1.2 is still supported for Oracle Cloud at Customer.

Oracle Identity Cloud Service supported for service instances on Oracle Cloud Infrastructure You can now create an Oracle Java Cloud Service instance in an Oracle Cloud Infrastructure region and enable authentication with Oracle Identity Cloud Service.

See:

Provisioning wizard shows Oracle Cloud Infrastructure Database and Oracle Autonomous Transaction Processing databases in the root compartment When you create an Oracle Java Cloud Service service, the provisioning wizard now enables you to select an Oracle Cloud Infrastructure Database or Oracle Autonomous Transaction Processing database in the root compartment. In previous releases, only Oracle Cloud Infrastructure Database and Oracle Autonomous Transaction Processing databases in the immediate child compartments of the root compartment were shown.

See Configure the Databases in Administering Oracle Java Cloud Service.

Message displayed if backups are disabled automatically due to repeated errors A message is now displayed if scheduled backups have been disabled automatically due to repeated errors during backup attempts, and the activity log shows backup failure details. In previous releases, you could only obtain backup failure details using the REST API.

See Explore the Backup Page in Administering Oracle Java Cloud Service.

Provisioning wizard shows Oracle Cloud Infrastructure Database and Oracle Autonomous Transaction Processing databases in nested compartments When you create an Oracle Java Cloud Service service, the provisioning wizard now enables you to select an Oracle Cloud Infrastructure Database or Oracle Autonomous Transaction Processing database in a nested compartment in the root compartment.

See Configure the Databases in Administering Oracle Java Cloud Service.

On Oracle Cloud at Customer

The following sections describe what’s new in Oracle Java Cloud Service on Oracle Cloud at Customer.

The Oracle Cloud at Customer family of products provides the capabilities of Oracle Cloud in your data center. Oracle upgrades your Oracle Cloud at Customer environment at regular intervals.

The January 2019 release of Oracle Java Cloud Service (18.4.6) on Oracle Cloud at Customer is now supported.

Note:

With some exceptions, Oracle Java Cloud Service on Oracle Cloud Infrastructure Classic, Oracle Cloud Infrastructure, and Oracle Cloud at Customer share the same features. In the cases a feature is not available on Oracle Cloud at Customer, the topic describing the feature is marked as follows:

Not Oracle Cloud at Customer This topic does not apply to Oracle Cloud at Customer.

For individual features, exceptions are indicated as follows in the text: (Not available on Oracle Cloud at Customer)

July 2019

Feature Description
Oracle Documaker Enterprise Edition certified

Oracle Documaker Enterprise Edition is now certified on Oracle Java Cloud Service. See Oracle Applications Certified on Oracle Java Cloud Service in Administering Oracle Java Cloud Service.

Clone legacy instances

You can now clone Oracle Java Cloud Service instances created on Oracle Cloud at Customer before October 2017 (Release 17.4.1).
Associate a service instance with a different database You can now associate an Oracle Java Cloud Service instance with a different infrastructure schema database after you have created the service instance.

See Associate an Oracle Java Cloud Service Instance with a Different Database in Administering Oracle Java Cloud Service.

Support for WebLogic Server version 12.2.1.3 You can now create service instances on WebLogic Server version 12.2.1.3. WebLogic Server versions 12.2.1.2, 12.1.3, and 11.1.1.7 are still supported.

Update protected context roots

After creating an Oracle Java Cloud Service instance with Oracle Identity Cloud Service enabled for authentication, you can now use the REST API to replace the protected context roots for custom JavaEE applications to be deployed onto the service instance.

See:

Change the WebLogic Server console URL

Use the REST API to change the domain name in WebLogic Server console URL after a service instance has been provisioned. Previously, the URL contained the public IP address of the service instance and you could not change it.

See Update a Service Instance Configuration in REST API for Oracle Java Cloud Service.

Assign a private static IP address when restarting an instance

For a service instance that is attached to an IP network, you can set a private static IP address or remove the static IP configuration when you restart a node or start a node that was stopped. This feature ensures that a node continues to use the same private IP address after it's restarted. This feature is supported by the REST API only.

See Stop and Start a Service Instance and Individual VMs in REST API for Oracle Java Cloud Service.

Update the Node Manager password

You can now use the REST API to change the Node Manager password for the WebLogic domain of an Oracle Java Cloud Service instance after the service instance has been created. This feature is available in the REST API only.

See Change the Node Manager Credentials in REST API for Oracle Java Cloud Service.

Backup scheduled after restart

If you stop an Oracle Java Cloud Service instance before a scheduled backup occurs, the backup begins at its next scheduled time after the service instance restarts. Previously, the overdue backup started immediately after the service instance restarted.

See About Backup and Restoration in Administering Oracle Java Cloud Service.

Forced scale-in operation when restoring an instance

If you performed a scale–out operation on an Oracle Java Cloud Service instance after a backup was created, the restoration operation can automatically remove nodes from the service instance if the topology of the backup and service instance differ.

See:

Scale the load balancer nodes

You can now scale the Oracle Traffic Director (OTD) load balancer nodes up or down. Previously, you could only scale WebLogic Server nodes.

See:

Available only on Oracle Cloud Infrastructure Classic.

Create public or private load balancers

When you create an Oracle Java Cloud Service instance, you can select whether you want to create a public or private load balancer. A public load balancer enables access to the Oracle Java Cloud Service instance from the public Internet. A private load balancer can be used to enable access to private workloads over VPN from your on-premises network.

This feature is available only if you have specified an Oracle Cloud Infrastructure Classic region and an IP network, and you have selected Oracle Identity Cloud Service as the authentication provider.

See:

Available only on Oracle Cloud Infrastructure Classic.

Change the license type

If your account has both Bring Your Own License (BYOL) and Oracle Java Cloud Service entitlements, you can change the license type for an existing Oracle Java Cloud Service instance. You can change the license type from the BYOL type to the cloud license type and vice versa.

See:

Changes to Database menu selection and tile on the My Services Dashboard

On the My Services Dashboard, the Database selection on the Navigation menu and the Open Service Console option on the Database tile now open the Oracle Cloud Infrastructure Database console.

To access the Oracle Database Classic Cloud Service console, select Database Classic from the Navigation menu or the Open Service Console option on the Database Classic tile.

Platform Services menu is removed

You can access other platform services from the Navigation menu in the top-left corner of the Oracle Java Cloud Service console. Previously, you could also use the Platform Services menu in the top-right corner of the console.

August 2018

Feature Description

Provision service instances quickly and easily

You can quickly create an Oracle Java Cloud Service by using one of three easy-to-use QuickStart templates: Simple Java Web App, Multi-Tier Java EE App with High Availability, and Highly Available Java EE App with Caching. You don’t need to complete any prerequisites such as creating SSH keys or an Oracle Database Classic Cloud Service database deployment — the QuickStart software creates them for you. See Creating an Oracle Java Cloud Service Instance with QuickStart in Administering Oracle Java Cloud Service.

You can continue to create a custom Oracle Java Cloud Service instance by using the provisioning wizard you used in previous releases. See Creating a Custom Oracle Java Cloud Service Instance in Administering Oracle Java Cloud Service.

Select an IP network

If you select a region on the Service page of the instance creation wizard, an IP Network drop-down list is displayed. For that region, you can select an IP network that you created using Oracle Cloud Infrastructure Compute Classic. If you specify No Preference in this field, your service will be placed on a shared network in your identity domain as in previous releases.

See:

Clone an instance

You can take snapshots of an instance and use the snapshots to quickly create clones of the original instance. See About Snapshots and Clones in Administering Oracle Java Cloud Service.

Create multiple clusters

If you have an account enabled for Oracle Identity Cloud Service and you enable WebLogic access with Oracle Identity Cloud Service, you can create up to 8 application clusters for your service instance. In the console, you can create multiple clusters while you are creating the service instance. In the REST API, you can create multiple clusters after you have created the service instance. Each cluster can have its own compute shape and server count. See Design Considerations for an Oracle Java Cloud Service and Specifying WebLogic Configuration in Administering Oracle Java Cloud Service.

Use tags to categorize service instances

You can create tags for categorizing Oracle Java Cloud Service instances, for example, by purpose, owner, or environment. You can easily identify and search for service instances based on the tags you have assigned to the service instances.

You can:

  • Create tags

  • Assign and unassign tags after an instance is created

  • Search for instances by using tags

See:

Backups disabled after repeated failures

If scheduled backups fail three consecutive times with the same type of errors, scheduled and on-demand backups are automatically disabled. If you provided an email address when you provisioned the service instance, a notification email is sent after each failure and when the backups are disabled.

See About Backup and Restoration in Administering Oracle Java Cloud Service.

Default URL in the object storage container field

The object storage container field in the instance creation wizard is autopopulated with a default container URL in the format restEndpointUrl/JaaS, where restEndpointUrl is the REST endpoint URL of the Object Storage service in the account, and JaaS is the default container name. You can override this value with a REST endpoint URL and container name of your choice.

Note that if the account doesn’t include an Object Storage service entitlement or if the region selected is an Oracle Cloud Infrastructure region, then the container field is not autopopulated.

See Configuring Backup and Recovery in Administering Oracle Java Cloud Service.

Protect custom context roots with the REST API

You can use the new protectedRootContexts parameter in the REST API provisioning payload to specify custom web context roots that are protected by Oracle Identity Cloud Service. Clients that access these protected context roots require authentication. Previously, the only protected context root was the default: __protected. See Create a Service Instance in REST API for Oracle Java Cloud Service.

Changes to the user interface

Some elements in the Oracle Java Cloud Service user interface have a new look and feel. For example, there are changes to page layout, tabs, icons, and menus.

See Exploring the Oracle Java Cloud Service Console and Exploring the Oracle Java Cloud Service Instance Overview Page in Administering Oracle Java Cloud Service.

Enhancements to the Platform Service Manager CLI

There are some general enhancements to the Platform Service Manager CLI. You can use OAuth for authentication, and also create multiple configuration profiles.

See Configuring the Command Line Interface in PaaS Service Manager Command Line Interface Reference.

Leverage existing licenses

The Bring Your Own License (BYOL) option enables you to bring your on-premises Oracle WebLogic Server licenses to Oracle Cloud. BYOL instances are billed at a lower rate than other instances. See Frequently Asked Questions: Oracle BYOL to PaaS.

You must have a Universal Credit subscription in order to use the BYOL feature. See Specifying Basic Service Information in Administering Oracle Java Cloud Service. If using the REST API, set the request parameter isBYOL to true.

December 2017

Feature Description

Authenticate users in Oracle Identity Cloud Service

By default, the WebLogic Server domain in a service instance is configured to use the local WebLogic identity store for administrators, application users, groups and roles. Alternatively, if your account includes a subscription to Oracle Identity Cloud Service, Oracle Java Cloud Service can integrate the WebLogic Server security realm with Oracle Identity Cloud Service when you provision a new service instance. As a result, users that access the administration consoles or your applications are authenticated against Oracle Identity Cloud Service.

See Specifying the Service Instance Details and Using Oracle Identity Cloud Service with Oracle Java Cloud Service in Administering Oracle Java Cloud Service.

Use a managed load balancer service

If you enable Oracle Identity Cloud Service on a service instance, an Oracle managed load balancer is configured automatically. This load balancer runs external to your service instance. If you do not enable Oracle Identity Cloud Service on the service instance, you can configure a local load balancer as in previous releases. See Configuring the Load Balancer in Administering Oracle Java Cloud Service.

No Coherence capacity units

When you create an Oracle Java Cloud Service instance based on the Enterprise Edition with Coherence service edition, you no longer use capacity units when configuring the data tier. Now, you select whether you want to provision a data grid cluster, and then specify the following information:

  • Compute shape

  • Cluster size

  • Managed servers per node

See Configuring the Coherence Data Tier in Administering Oracle Java Cloud Service.

New and deprecated REST endpoints

Some REST endpoints for service instances are new and others will be deprecated in the near future. See Deprecation Notice for Service Instances in REST API for Oracle Java Cloud Service.

Updated Command Line Interface

The PaaS Service Manager Command Line Interface (CLI) has been updated in this release. The psm jcs command syntax has been replaced with psm jaas syntax. The psm jcs syntax will no longer work if you are running PSM CLI version 1.1.17, released in October 2017, or later. This change results in a number of commands being replaced and new commands added.

The following commands have been removed:

  • scale-up

  • scale-down

  • auto-scaling-policy

  • create-auto-scaling-rules

  • update-auto-scaling-policy

  • delete-auto-scaling-policy

  • auto-scaling-activities

The following commands were added:

  • scale (replaced deprecated scaling and auto-scaling commands)

  • check-health

  • add-storage

  • add-backup-service

Additionally, a number of new parameters were added to numerous commands. See Using the Command Line Interface in PaaS Service Manager Command Line Interface Reference.

Load Balancer page removed

The Load Balancer page has been removed from the Oracle Java Cloud Service UI. The action menu adjacent to the instance name on the Instance Overview page now has an option to enable or disable the load balancer.

See Disabling or Enabling the Load Balancer for an Oracle Java Cloud Service Instance in Administering Oracle Java Cloud Service.

Changes to the provisioning wizard

The Service Details page of the provisioning wizard now has two tabs: Simple and Advanced. In addition to input fields on the Simple tab, the Advanced tab enables you to:

  • Specify domain partitions

  • Enable access to administration consoles

  • Deploy the sample application

  • Configure backup and recovery

  • Provision a load balancer

See Specifying the Service Instance Details in Administering Oracle Java Cloud Service.

Minor changes to the user interface

The Oracle Java Cloud Service user interface has minor changes in this release, for example:

  • Information on in-progress operations is displayed on the Instance Overview page

  • A new Service Restart icon is displayed on the Instance Overview page

  • The Add Storage feature has moved from the Scale Up/Scale Down dialog to the action menu adjacent to a Managed Server details on the Overview page

  • The following options have been added to the action menu adjacent to the service instance name on the Instance Overview page: Restart, Disable/Enable Load Balancer, Add Backup, View Activity. Add Load Balancer and console access choices have been removed.

  • Menus and dialogs for creating a data grid in Oracle Java Cloud Service with Coherence have changed

  • An action menu has replaced the buttons on the Backup page

  • The Add Node dialog includes options for both WebLogic and load balancer nodes

  • The AppToCloud wizard has the same layout and options as the standard instance creation wizard

Service name changes

The names of several Infrastructure as a Service (IaaS) services have changed, including:

  • Oracle Compute Cloud Service has been renamed Oracle Cloud Infrastructure Compute Classic

  • Oracle Storage Cloud Service has been renamed Oracle Cloud Infrastructure Object Storage Classic

August 2017

Feature Description

Select a region for your service instance

If your identity domain is enabled for compute regions, you can select a region during provisioning, where your Oracle Java Cloud Service will reside. The region is a geographical location.

If you do not select a region by specifying No Preference in the service creation wizard, the provisioning flow is the same as in previous releases: Oracle selects a location for you.

See Design Considerations for an Oracle Java Cloud Service Instance and Specifying Basic Service Instance Information in Using Oracle Java Cloud Service.

Use reserved IP addresses

If your identity domain is enabled for compute regions and you have selected a region, you can reserve IP addresses for the VMs in the Oracle Java Cloud Service instance you are creating. To create IP addresses, use the new IP Reservations tab on the Oracle Java Cloud Service Console. If you delete a service instance with a reserved IP address, you can reuse the IP address for a new service instance.

See Reserving IP Addresses in Using Oracle Java Cloud Service.

Control access to your service instance

Access rules enable you to control network access to the VMs that make up your Oracle Java Cloud Service instance. Each rule has a source, a destination, a destination port and a transport protocol. See Creating an Access Rule in Using Oracle Java Cloud Service.

Use a storage container for service instance backups

You no longer use an NFS remote backup location for service instance backups. You use an Oracle Cloud Infrastructure Object Storage Classic container for backups. See:

Specify the name of the Oracle Required Schema database deployment

Select the name of the Oracle Database Classic Cloud Service database deployment you want to use for the Oracle Required Schema from the drop-down menu. You no longer specify a connection string unless your are creating an Oracle Java Cloud Service—Virtual Image instance and specifying an Oracle Database Classic Cloud Service—Virtual Image database. See Configuring the Databases in Administering Oracle Java Cloud Service.

Configure a second database for your application schema

You can optionally specify a second Oracle Database Classic Cloud Service deployment when you provision an Oracle Java Cloud Service instance. The second database is dedicated for your application schema. See Configuring the Databases in Administering Oracle Java Cloud Service.

Support for Database 12.2

Oracle Java Cloud Service instances based on WebLogic Server 12.2.1.2.0 now fully support the Database 12.2 version for containing the Oracle required schema and for the application database. If you specify a Database 12.2 database for the schema, there are no restrictions on what type of database you can specify for the application database. Previously, Database 12.2 was supported only as an application database.

Create rules for automatic scaling

You can configure Oracle Java Cloud Service to automatically scale a cluster in or out by defining an auto-scaling rule, based on CPU utilization, that determines when to add or remove nodes. You can also edit and/or delete existing rules. See About Automatic Scaling in Using Oracle Java Cloud Service.

Disable backups when creating a service instance

When creating a service instance, set the Backup Destination field to None to disable backups.

See Configuring Backup and Recovery in Using Oracle Java Cloud Service.

Migrate applications with AppToCloud

Oracle’s AppToCloud infrastructure allows you to export an existing Oracle WebLogic Server domain configuration and Java applications, and to then provision a new Oracle Java Cloud Service instance with the same domain resources and applications. See Typical Workflow for Migrating Applications to Oracle Java Cloud Service in Administering Oracle Java Cloud Service.

Provision Oracle Fusion Middleware on service instances

You can now choose the Oracle Java Cloud Service for Fusion Middleware service level, and select either Oracle Data Integrator or Oracle WebCenter Portal, depending on your entitlements, when you use the Oracle Java Cloud Service provisioning wizard. Oracle Java Cloud Service provides scripts and tools to help you quickly provision these products on your service instance. See:

Create instances with Cloud Stack Manager

Oracle Cloud Stack Manager includes a certified Oracle template to automate the provisioning of both Oracle Java Cloud Service and Oracle Database Cloud Service instances in a single operation. Quickly create cloud stacks with the Oracle-JCS-DBCS-Template . See these topics in Using Oracle Cloud Stack Manager:

Display monitoring information

The monitoring information on the Instance Overview page has changed. Now the page shows an Instance field followed by an icon. When you click on the icon, a Health Check Details dialog shows information such as how long the service instance has been running and its current heap usage.

See Exploring the Oracle Java Cloud Service Instance Overview Page and Viewing the Service Metrics for an Oracle Java Cloud Service Instance in Using Oracle Java Cloud Service.

Use the PSM Command Line Interface (CLI)

You can now use the PaaS Service Manager (PSM) Command Line Interface (CLI) to create and manage Oracle Java Cloud Service instances from a command shell or script. See Using the Command Line Interface in PaaS Service Manager Command Line Interface Reference.

Find help for a page in the UI

For each page of the Oracle Java Cloud Service user interface, you can find links to help resources for that specific page.

The Help Drawer contains links to documentation topics, tutorials, videos, and FAQs. You display the Help Drawer by clicking the tab on the right side of the screen.

See Accessing Oracle Java Cloud Service and Exploring the Oracle Java Cloud Service Console in Using Oracle Java Cloud Service.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

There are several types of related resources available to you.

See Oracle Java Cloud Service documentation, videos, and tutorials.