What s New for Oracle Java Cloud Service. On Oracle Cloud Infrastructure and Oracle Cloud Infrastructure Classic. Topics: Oracle Cloud

Transcription

1 Oracle Cloud What's New for Oracle Java E December 2018 What s New for Oracle Java This document describes what's new in Oracle Java on all infrastructure platforms where it's available: On Oracle Cloud Infrastructure and Oracle Cloud Infrastructure Classic On Oracle Cloud at Customer 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 on Oracle Cloud Infrastructure and Oracle Cloud Infrastructure Classic. As soon as new features become available, cloud tools for managing Oracle Java 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 instances. However, new features that change how service instances are created do not affect your existing service instances. Topics: December 2018 November 2018 September 2018 August 2018 July

2 May 2018 April 2018 March 2018 February 2018 December 2018 Feature Support for Oracle Autonomous Transaction Processing databases and Oracle Cloud Infrastructure databases (DB System) (Available only on Oracle Cloud Infrastructure) Oracle Documaker Enterprise Edition certified QuickStart unsupported for accounts with Oracle Cloud Infrastructure regions You can now associate an Oracle Autonomous Transaction Processing database or Oracle Cloud Infrastructure Database (DB System) as the infrastructure schema database when you provision your Oracle Java instance. Provisioning with Oracle Cloud Infrastructure Database VM-based and Exadata-based databases is supported in both the UI and REST API. Provisioning with Oracle Cloud Infrastructure Database bare metal-based databases is supported only with the REST API. Previously, you could only specify an Oracle Database Cloud Service deployment as the infrastructure schema database. Overview of the Database Service in the Oracle Cloud Infrastructure documentation Prerequisites for Oracle Platform Services on Oracle Cloud Infrastructure in the Oracle Cloud Infrastructure documentation Configure the Databases in Administering Oracle Java Cloud Service Create a Service Instance in REST API for Oracle Java Oracle Documaker Enterprise Edition is now certified on Oracle Java. See Oracle Applications Certified on Oracle Java in Administering Oracle Java. If your account has only Oracle Cloud Infrastructure regions, or has a mix of Oracle Cloud Infrastructure and Oracle Cloud Infrastructure Classic regions, then you cannot use a QuickStart template to create an Oracle Java instance. The QuickStarts link is not visible in the console. 2

3 Apply new patches New patch set updates (PSUs) are available for: Oracle WebLogic Server Java Development Kit (JDK) You can see the availability of a patch on the Administration tile and on the Patching page. Apply a Patch and Explore the Patching Page in Administering Oracle Java Apply a Patch in REST API for Oracle Java Note that applying the PSU does not upgrade a service instance to WebLogic Server 12c ( ). Upgrade an Oracle Java Instance in Administering Oracle Java Apply a Patch in REST API for Oracle Java November 2018 Feature Create service instances attached to private subnets (Available only on Oracle Cloud Infrastructure) Instance nodes are distributed evenly across fault domains (Available only on Oracle Cloud Infrastructure) Using the REST API, you can now create a service instance that is attached to a private subnet in Oracle Cloud Infrastructure. This feature enables you to deploy private enterprise applications to Oracle Java instances. Create an Oracle Java Instance Attached to a Private Subnet in Oracle Cloud Infrastructure in Administering Oracle Java Create a Service Instance in REST API for Oracle Java For service nodes created in Oracle Cloud Infrastructure regions in release or later, the compute nodes of the instances are distributed evenly across the fault domains within the availability domain that you specify while creating the instance. This nodedistribution logic is used even when you restart the service instance or its nodes. Each fault domain is an isolated grouping of hardware and infrastructure within an availability domain. An outage in one fault domain does not affect the compute nodes running in the other fault domains. 3

4 Update protected context roots (Available only on Oracle Cloud Infrastructure Classic) Change the WebLogic Server console URL Create a service instance with multiple WebLogic Clusters on Oracle Cloud Infrastructure Upgrade the WebLogic Server release for an existing service instance After creating an Oracle Java instance with Oracle Identity 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. Use Oracle Identity with Oracle Java Cloud Service in Administering Oracle Java Update the Web Tier Policy in REST API for Oracle Java 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. You can now provision multiple WebLogic clusters when you provision an Oracle-managed load balancer for an Oracle Java instance on Oracle Cloud Infrastructure. Specify WebLogic Configuration in Administering Oracle Java Create a Service Instance in REST API for Oracle Java You can now upgrade the WebLogic Server release on which an Oracle Java was created to release Previously, if you needed a service instance based on the more recent WebLogic Server release, you had to create a new service instance. Upgrade an Oracle Java Instance in Administering Oracle Java Apply a Patch in REST API for Oracle Java September 2018 Feature 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. Available only on Oracle Cloud Infrastructure Classic. 4

5 Update the Node Manager password Backup scheduled after restart Forced scale-in operation when restoring an instance Scale the load balancer nodes Create public or private load balancers 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. If you stop an Oracle Java 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. 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. Restoring a Backup in Administering Oracle Java Cloud Service Restore a Service Instance in REST API for Oracle Java You can now scale the Oracle Traffic Director (OTD) load balancer nodes up or down. Previously, you could only scale WebLogic Server nodes. About Scaling an Oracle Java Node in Administering Oracle Java Scale Up or Scale Down a Service Instance in REST API for Oracle Java Available only on Oracle Cloud Infrastructure Classic. When you create an Oracle Java 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 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 as the authentication provider. Configuring the Load Balancer in Administering Oracle Java Create a Service Instance in REST API for Oracle Java Available only on Oracle Cloud Infrastructure Classic. 5

6 Change the license type Changes to Database menu selection and tile on the My Services Dashboard Platform Services menu is removed If your account has both Bring Your Own License (BYOL) and Oracle Java entitlements, you can change the license type for an existing Oracle Java instance. You can change the license type from the BYOL type to the cloud license type and vice versa. Changing the License Type for an Oracle Java Instance in Administering Oracle Java Update a Service Instance Configuration in REST API for Oracle Java 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 console, select Database Classic from the Navigation menu or the Open Service Console option on the Database Classic tile. You can access other platform services from the Navigation menu in the top-left corner of the Oracle Java console. Previously, you could also use the Platform Services menu in the top-right corner of the console. August 2018 Feature Bring Your Own License capability is enabled by default If you have a Universal Credits subscription and your account has Bring Your Own License (BYOL) resources, then the BYOL capability is enabled by default when you create an Oracle Java instance. This default behavior means that you no longer need to specify that you want Oracle Java to apply an existing, unused, on-premises license for Oracle WebLogic Server when you create a service instance. If your account only has BYOL resources, then you cannot disable this behavior; otherwise, you can disable it. Create a QuickStart Instance in Administering Oracle Java Specifying the Basic Instance Information in Administering Oracle Java Create a Service Instance in REST API for Oracle Java 6

7 Clone legacy instances Newly-certified Oracle applications Apply new patches You can now create a snapshot of a Oracle Java instance provisioned prior to November 2017 (Release ), and then clone the service instance from the snapshot. Creating a Snapshot of an Oracle Java Instance in Administering Oracle Java Cloning an Instance Using a Snapshot in Administering Oracle Java Snapshots REST Endpoints in REST API for Oracle Java Three more Oracle applications have been certified on Oracle Java : Oracle Health Insurance Components Oracle Insurance Policy Administration for Life and Annuity Oracle Insurance Policy Administration for Group Benefits See Oracle Applications Certified on Oracle Java in Administering Oracle Java. New patch set updates (PSUs) are available: PSU for Oracle WebLogic Server PSU for Java Development Kit (JDK) Note that applying the PSU does not upgrade a service instance based on WebLogic Server 12c ( ) to WebLogic Server 12c ( ). 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. July 2018 Feature Subnet selected automatically for a service instance in an Oracle Cloud Infrastructure region You are no longer required to select a subnet when you create an Oracle Java instance on an Oracle Cloud Infrastructure region. A subnet is selected automatically if you don t specify one. You can still create your own subnet and select the subnet in the provisioning wizard or specify it with the REST API if you want. Specifying the Basic Instance Information in Administering Oracle Java Create a Service Instance in REST API for Oracle Java 7

8 New shapes are available Simplified way to manage tags for instances already having tags Support for VPN as a Service Configure local backup retention policy The OC8 and OC9 shapes are available for creating instances on Oracle Cloud Infrastructure Classic. Design Considerations for an Oracle Java Instance in Administering Oracle Java Create a Service Instance in REST API for Oracle Java You can use the Manage Tags menu option to assign or unassign tags, even for instances that already have tags assigned to them. In previous releases, if an instance already had one or more tags assigned to it, you had to hover over the Tags field, wait for a pop-up window, and then click the More link in the window. See Creating, Assigning, and Unassigning Tags in Administering Oracle Java. VPN as a Service (VPNaaS) is now officially certified and supported for Oracle Java instances. VPNaaS enables you to set up a VPN connection between the IP network your service instance s nodes are attached to and your onpremises gateway device. See Setting Up a VPN Connection Using VPNaaS in Using Oracle Cloud Infrastructure Compute Classic. For faster restorations of instances from backups, recent backups are also copied to a dedicated storage volume that s attached to a node in your service instance. You can now change the local (disk copy) retention policy by using the localretention REST API parameter. See Update the Backup Configuration in REST API for Oracle Java. This feature is available in the REST API only. May 2018 Feature Change the schema database password in the Oracle Java console You can now easily change the schema database password by using the Oracle Java console. See Changing the Schema Password with the Console. You can also use the REST API to change the schema password. See Change the Database Schema Password in REST API for Oracle Java. This feature doesn t apply to the application database password. Previously, you could only change the schema password manually. See Changing the Schema Password Manually in Administering Oracle Java. When you restore a service instance from a backup taken before you changed the schema password, you will be prompted for the new password. See Restoring a Backup in Administering Oracle Java. 8

9 Download provisioning parameters in JSON format Snapshots and clones supported in Oracle Cloud Infrastructure regions Swift password term change April 2018 You can now download a JSON-formatted file containing the instance parameters that you ve specified in the provisioning wizard. This feature is available on the Confirmation page of the wizard. You can use the JSON-formatted file as a sample to construct the request body for creating instances using the REST API. Confirming Your Oracle Java Instance Creation (for Oracle Cloud Infrastructure Classic) in Administering Oracle Java Confirming Your Oracle Java Instance Creation (for Oracle Cloud Infrastructure) in Administering Oracle Java You can now create snapshots of Oracle Java instances in Oracle Cloud Infrastructure regions, and create clones of these service instances. Previously, you could only create snapshots and clones for service instances in Oracle Cloud Infrastructure Classic regions. See Creating a Snapshot of an Oracle Java Instance and Creating a Clone from a Snapshot in Administering Oracle Java. Instances on Oracle Cloud Infrastructure use a Swift password to access object storage for storing and retrieving instance backups. The term "Swift password" has been changed to "Auth token". There is no change in the backup or authentication behavior. Feature No backup storage credentials needed for service instances enabled with Oracle Identity Cloud Service Enable authentication with Oracle Identity Cloud Service for an instance attached to an IP network If the current cloud user is entitled to use Oracle Cloud Infrastructure Object Storage Classic, and you have enabled authentication by Oracle Identity with either the REST API or the Oracle Java console, then a username and password are unnecessary for storage access. In the console, the username and password fields are unavailable. See Configuring Backup and Recovery and Configuring Scheduled Backups in Administering Oracle Java. (Not available on Oracle Cloud Infrastructure) You can now enable authentication with Oracle Identity Cloud Service for an instance that you attach to an IP network. Previously, authentication with Oracle Identity was supported only for instances attached to a shared network. (Available only on Oracle Cloud Infrastructure Classic) March

10 Create a private instance with no public IP addresses Changing infrastructure database associations Recover a deleted service with the REST API Support for an additional WebLogic Server software release Certified Oracle Applications As you create a Oracle Java instance on an IP network in an Oracle Cloud Infrastructure Classic region, you can now choose whether to assign public IP addresses to the nodes in the service instance. If you choose not to assign public IP addresses when you provision your service instance, then none of the nodes, including those you add later via scaling, will receive a public IP address. You will not be able to access your deployed applications from the public Internet, but you can access the applications within your IP network or from your on-premises data center over a VPN network, for example. By default, public IP addresses are assigned to all nodes. See Design Considerations for an Oracle Java Instance and Specifying the Basic Service Instance Information in Administering Oracle Java. (Not available on Oracle Cloud Infrastructure) You can now associate a different infrastructure database with a service instance you already created. You cannot associate a different application database after the service instance has been created. See Managing Associations for a Service Instance in Administering Oracle Java. Note that this feature existed in the previous release, but was undocumented. We re highlighting it now. If your account was terminated and you lose the Oracle Java instance you created, you can recover this service instance from a backup preserved in a cloud storage container. This feature is available only in the REST API. See Recovering a Deleted Service Instance from a Backup in Administering Oracle Java. Software release WebLogic Server 12c ( ) is now supported in addition to WebLogic Server 12c ( ), which has been supported in previous releases. WebLogic Server 12c ( ) is the software release default value in the provisioning wizard. The Oracle Java Fusion Middleware service level is not supported for the WebLogic Server 12c ( ) software release. Design Considerations for an Oracle Java Instance in Administering Oracle Java Documentation Update History in What's New in Oracle WebLogic Server The following Oracle applications are now certified on Oracle Java : Oracle Health Insurance Components Oracle Insurance Policy Administration for Life and Annuity See Oracle Applications Certified on Oracle Java in Administering Oracle Java. 10

11 Apply new patches New patch set updates (PSUs) are available: PSU for Oracle WebLogic Server PSU for Java Development Kit (JDK) Note that applying the PSU does not upgrade a service instance based on WebLogic Server 12c ( ) to WebLogic Server 12c ( ). If you want to upgrade, you must apply the 1.3 patch manually. 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. February 2018 Feature AppToCloud support for multiple clusters Use the console to manage tags for categorizing service instances Backups disabled after repeated failures New shapes available If your account includes Oracle Identity, you can migrate an on-premises, multi-cluster domain configuration to an Oracle Java multi-cluster domain environment. See Migrating Applications to Oracle Java in Administering Oracle Java. (Not available on Oracle Cloud Infrastructure) You can now use the Oracle Java console to create and manage 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 Previously, this feature was available only in the REST API. See Managing Tags in Administering Oracle Java. 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 address when you provisioned the service instance, a notification is sent after each failure and when the backups are disabled. See About Backup and Restoration in Administering Oracle Java. The Standard2.* shapes are now available for provisioning an Oracle Java instance on Oracle Cloud Infrastructure. See Specifying WebLogic Configuration and Design Considerations for an Oracle Java Instance in Administering Oracle Java. 11

12 On Oracle Cloud at Customer The following sections describe what s new in Oracle Java 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 February 2018 release of Oracle Java (18.1.4) on Oracle Cloud at Customer is now supported. Note: With some exceptions, Oracle Java 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: 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) Topics: August 2018 December 2017 August 2017 August

13 Provision service instances quickly and easily Select an IP network Clone an instance Create multiple clusters Use tags to categorize service instances You can quickly create an Oracle Java 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 database deployment the QuickStart software creates them for you. See Creating an Oracle Java Instance with QuickStart in Administering Oracle Java. You can continue to create a custom Oracle Java instance by using the provisioning wizard you used in previous releases. See Creating a Custom Oracle Java Instance in Administering Oracle Java. 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. Creating an IP Network in Using Oracle Compute Service (IaaS) Specifying Basic Service Instance Information in Using Oracle Java. 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. If you have an account enabled for Oracle Identity 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 and Specifying WebLogic Configuration in Administering Oracle Java. You can create tags for categorizing Oracle Java 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 Tags and Assignments REST endpoints in REST API for Oracle Java Managing Tags in Administering Oracle Java 13

14 Backups disabled after repeated failures Default URL in the object storage container field Protect custom context roots with the REST API Changes to the user interface Enhancements to the Platform Service Manager CLI Leverage existing licenses 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 address when you provisioned the service instance, a notification is sent after each failure and when the backups are disabled. See About Backup and Restoration in Administering Oracle Java. 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. 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. 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. Some elements in the Oracle Java 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 Console and Exploring the Oracle Java Instance Overview Page in Administering Oracle Java. 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. 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. If using the REST API, set the request parameter isbyol to true. December

15 Authenticate users in Oracle Identity Cloud Service Use a managed load balancer service No Coherence capacity units New and deprecated REST endpoints 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 can integrate the WebLogic Server security realm with Oracle Identity when you provision a new service instance. As a result, users that access the administration consoles or your applications are authenticated against Oracle Identity. See Specifying the Service Instance Details and Using Oracle Identity with Oracle Java in Administering Oracle Java. If you enable Oracle Identity 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 on the service instance, you can configure a local load balancer as in previous releases. See Configuring the Load Balancer in Administering Oracle Java. When you create an Oracle Java 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. 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. 15

16 Updated Command Line Interface Load Balancer page removed Changes to the provisioning wizard 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 , 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. The Load Balancer page has been removed from the Oracle Java 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 Instance in Administering Oracle Java Cloud Service. 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. 16

17 Minor changes to the user interface Service name changes The Oracle Java 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 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 The names of several Infrastructure as a Service (IaaS) services have changed, including: Oracle Compute has been renamed Oracle Cloud Infrastructure Compute Classic Oracle Storage has been renamed Oracle Cloud Infrastructure Object Storage Classic August 2017 Feature 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 Instance and Specifying Basic Service Instance Information in Using Oracle Java. 17

18 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 instance you are creating. To create IP addresses, use the new IP Reservations tab on the Oracle Java Console. If you delete a service instance with a reserved IP address, you can reuse the IP address for a new service instance. Control access to your service instance Use a storage container for service instance backups Specify the name of the Oracle Required Schema database deployment Configure a second database for your application schema Support for Database 12.2 Create rules for automatic scaling Disable backups when creating a service instance See Reserving IP Addresses in Using Oracle Java. Access rules enable you to control network access to the VMs that make up your Oracle Java instance. Each rule has a source, a destination, a destination port and a transport protocol. See Creating an Access Rule in Using Oracle Java. 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. Creating an Oracle Storage Container in Administering Oracle Java Configuring the Databases in Administering Oracle Java Select the name of the Oracle Database 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 Virtual Image instance and specifying an Oracle Database Cloud Service Virtual Image database. See Configuring the Databases in Administering Oracle Java. You can optionally specify a second Oracle Database 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. Oracle Java instances based on WebLogic Server 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. You can configure Oracle Java 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. When creating a service instance, set the Backup Destination field to None to disable backups. See Configuring Backup and Recovery in Using Oracle Java. 18

19 Migrate applications with AppToCloud Provision Oracle Fusion Middleware on service instances Create instances with Cloud Stack Manager Display monitoring information Use the PSM Command Line Interface (CLI) Find help for a page in the UI 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 in Administering Oracle Java Cloud Service. You can now choose the Oracle Java 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 provisioning wizard. Oracle Java provides scripts and tools to help you quickly provision these products on your service instance. Provisioning Oracle WebCenter Portal tutorial Provisioning Oracle Data Integrator tutorial Specifying Basic Service Instance Information in Using Oracle Java Oracle Cloud Stack Manager includes a certified Oracle template to automate the provisioning of both Oracle Java and Oracle Database instances in a single operation. Quickly create cloud stacks with the Oracle-JCS- DBCS-Template. See these topics in Using Oracle Cloud Stack Manager: About Oracle Cloud Stack Manager Creating a Cloud Stack 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 Instance Overview Page and Viewing the Service Metrics for an Oracle Java Cloud Service Instance in Using Oracle Java. 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. For each page of the Oracle Java 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 and Exploring the Oracle Java Console in Using Oracle Java Cloud Service. Documentation Accessibility 19

20 For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at 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 lookup?ctx=acc&id=info or visit ctx=acc&id=trs if you are hearing impaired. Related Documents There are several types of related resources available to you. See Oracle Java documentation, videos, and tutorials. Oracle Cloud What's New for Oracle Java, E Copyright 2015, 2018, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government. This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of thirdparty content, products, or services, except as set forth in an applicable agreement between you and Oracle. 20