What’s New in Oracle Java Cloud Service – SaaS Extension

See Deprecated Features for important information regarding the roadmap for Oracle Java Cloud Service - SaaS Extension.

Deprecated Features

IMPORTANT: Effective February 29, 2024, Oracle Java Cloud Service – SaaS Extension will reach End of Life (EOL).

Once the Java Cloud Service – SaaS Extension Service (JCS-SX) reaches EOL:
  • New instances of JCS-SX cannot be created
  • JCS-SX will no longer be supported
  • All JCS-SX instances will be deleted
  • JCS-SX customer data will be automatically deleted 60 days after EOL

JCS-SX, which is based on Oracle WebLogic Server, provides an environment to extend SaaS with customer apps. However, JCS-SX runs on Oracle Cloud Classic Gen 1, which has been deprecated in favor of Oracle Cloud Infrastructure (OCI) Gen 2 Cloud.

Recommendations:
  • If you are building a new SaaS extension, use Oracle Visual Builder Studio (VB Studio), which provides a complete set of development tools, including low-code options as well as SingleSign-On (SSO) and web service security.
  • If you want to continue running your existing app, move it to Oracle WebLogic Server (WLS) for Oracle Cloud Infrastructure (OCI). WLS on OCI provides the ability to run Java EE apps on the latest versions of Java technology (like Java EE 7 and JDK 8), as well as to directly leverage the modern compute, networking, and storage services available in OCI. Customer-managed WLS for OCI also provides upgrades to newer versions of the technology stack, so your apps can take advantage of future improvements. For more information, see Migrate JCS-SX Extensions to WLS on OCI.

    Note:

    Although JCS-SX is no longer available as a subscription for new customers, subscription renewals are available while you migrate existing applications from JCS-SX to WLS on OCI.
See also:

What's New Updates

Topics:

May 2019

Feature Description
Updates to the Oracle Java Cloud Service - SaaS Extension Administration Console

The Oracle Java Cloud Service - SaaS Extension Administration Console has been enhanced in this release.

  • The home page now displays memory and CPU usage statistics at the server level.

  • The home page now also displays granular storage usage statistics, so you can know where storage consumption is taking place.

  • You can now proactively restart a server whose resource consumption is growing beyond safe levels.

August 2018

Feature Description
New way to set the UseSunHttpHandler property

Oracle Java Cloud Service - SaaS Extension no longer allows you to set the UseSunHttpHandler property via the System Properties section. Instead, enable the sun.http.handler.enabled configuration; the UseSunHttpHandler property is set when the instance restarts.

See Managing System Properties in Using Oracle Java Cloud Service - SaaS Extension.

New Related Deployments selection box in the provisioning wizard

If a Fusion Application instance is detected in any of the domains configured within your account, then the instance creation wizard shows a Related Deployments selection box. You select the target domain where you want to create the instance. If you do not make a selection, a new domain is created. If you create the instance in an identity domain where the Fusion Application is located, then you can use Single Sign-On (SSO).

See Provisioning a JCS-SaaS Extension Instance in Using Oracle Java Cloud Service - SaaS Extension.

February 2018

Feature Description
New user interface This version of JCS-SaaS Extension introduces the JCS-SaaS Extension Administration Console. This new UI is a multi-page console from which you can deploy applications and libraries. It also provides certificate and property management tools and allows you to view statistics on performance, data sources, response and load, JCS– SaaS Extension jobs, applications, and resource usage.

The JCS-SaaS Extension Administration Console does not completely replace JCS–SaaS Extension Control, the Enterprise Manager interface commonly used with this service. The JCS-SaaS Extension Administration Console is primarily designed to use with JCS-SaaS Extension instances created after the February 2018 update (18.1.2). If you have instances created before 2018 and want to use JCS-SaaS Extension Administration Console, be aware that the Java Console button for each instance in the My Services dashboard will point to JCS-SaaS Extension Control.

See Administering Instances with the JCS-SaaS Extension Administration Console in Using Oracle Java Cloud Service - SaaS Extension.

New service instance provisioning process Previously, when you ordered a subscription to Oracle Java Cloud Service - SaaS Extension, a single Oracle Java Cloud Service - SaaS Extension instance and an Oracle Database Cloud Service would be provisioned before you could access the service. In other words, the instances arrived with the service. Going forward, you will need to provision instances for both of these services by using a simple provisioning wizard..

See Getting Started with Your JCS-SaaS Extension Subscription in Using Oracle Java Cloud Service - SaaS Extension.

Updated access procedure In addition to being able to access JCS-SaaS Extension from a URL, you can now access your service from: in Using Oracle Java Cloud Service - SaaS Extension.

October 2017

Feature Description
New configuration added to to SDK that determines OPSS datasources transaction protocol The internal.datasource.opss.global.txn configuration can now be used with the set-config command to determine the transaction protocol (global transaction processing behavior) for the internal OPSS datasource. This configuration was added to address issues arising because the OPSS datasource doesn’t support XA Commits distributed transactions (see the Troubleshooting issue java_OPSS_wlsaas Resource Could Not be Prepared Because JDBC Driver Does Not Support XA (Global) Transactions in Using Oracle Java Cloud Service - SaaS Extension.

Also, see Managing Configurations in Using Oracle Java Cloud Service - SaaS Extension.

.

August 2017

Feature Description
Synchronizing data between the resource management UI and the SDK. This release of JCS-SaaS Extension introduces the SDK command sync-system, which you can use to synchronize data between the resource management UI and the SDK.

See Synchronizing UI and SDK Data in Using Oracle Java Cloud Service - SaaS Extension.

New code caching configurations added. Two new flattened configurations that enable better control of code caching have been added:

  • jvm.arg.reserved.code.cache.size determines the maximum size of the code cache.

  • jvm.arg.use.code.cache.flushing turns code cache flushing on and off.

See Managing Configurationsin Using Oracle Java Cloud Service - SaaS Extension.

July 2017

Feature Description
Welcome App now shows service version details You can now use the Welcome App to access version details about the following components running on your service:

  • JCS-SaaS Extension

  • Java

  • Weblogic Server

  • Application Development Framework (ADF)

  • Fusion Middleware Components (FMW) or Java-Required File (JRF)

See Using the Welcome App in Using Oracle Java Cloud Service - SaaS Extension.

June 2017

Feature Description
Migrate and Revert CLI commands renamed The SDK CLI commands–introduced in release 17.2.3 (May 2017)–that let you safely migrate your JCS-SaaS Extension instances provisioned with JCS-SaaS Extension 16.4.5 (or earlier) between FMW 11.1.1.7 binaries and FMW 11.1.1.9, have been renamed as follows:

  • jrf-migrate-to-ps7 is now called upgrade-service-instance.

  • jrf-revert-to-ps6 is now called downgrade-service-instance.

While the old commands will still work, you should only use them when required to ensure backward compatibility.

See Upgrading an Instance from FMW 11.1.1.7 to FMW 11.1.1.9 and Reverting a Migrated Instance in Using Oracle Java Cloud Service - SaaS Extension.

May 2017

Feature Description
Instance migration and revert between FMW 11.1.1.7 and FMW 11.1.1.9 now enabled by new CLI commands. Two new commands let you use the CLI to safely migrate your JCS-SaaS Extension instances provisioned with JCS-SaaS Extension 16.4.5 (or earlier) from FMW 11.1.1.7 binaries to FMW 11.1.1.9 and, if necessary, revert those specific instances back from FMW 11.1.1.9 to FMW 11.1.1.7.

See Upgrading an Instance from FMW 11.1.1.7 to FMW 11.1.1.9 and Reverting a Migrated Instance in Using Oracle Java Cloud Service - SaaS Extension.

April 2017

Feature Description
-refresh command introduced in SDK CLI The -refresh command downloads and redeploys applications to a JCS-SaaS Extension instance. You can use this command to refresh any application and it is particularly useful in resolving an issue wherein a blank screen would appear after logging in to an ADF application deployed on a JCS-SaaS Extension instance provisioned before version 17.1.3 but subsequently upgraded to that version. See Refreshing an Application.

March 2017

Feature Description
Relocating a service instance from one identity domain to another. You can easily move your service instance from one identity domain to another so long as both identity domains are in the same data center. See Relocating the Service Instance. See Relocating the Service Instance.
ID Propagation with OAuth. JCS-SaaS Extension supports OAuth 2.0, an open standard for authorization. This protocol allows Internet users to authorize websites or applications to access their information on other websites but without sharing passwords, making it easy for users to share information about their accounts with third party applications or websites. See Identity Propagation with OAuth
Setting the Maximum Capacity of JDBC Datasources. By using the set-config command with the configuration jdbc.datasource.max.capacity, you can set the maximum number of physical connections that a connection pool can contain, so long as you stay within the JDBC Pool maximum connection values. See Managing Configurations.
Enabling/Disabling System Loggers. By using the set-config command with the configuration logging.system.loggers.enabled, you can now enable or disable system loggers, such as oracle.wsm, during runtime. See Managing Configurations.

February 2017

Feature Description
New commands added to CLI that allow you to view the service and application logs. You can now use the command-line tool query-access-logs to view information in the access.log file.

See Viewing Access Logs.

October 2016

Feature Description
New command added to establish trust from on-premises environment to JCS-SaaS Extension instance. You can now use the command-line tool setup-wss-trust to automate the process of establishing Web Service Security (WSS) trust from a local WebLogic Server domain to a JCS-SaaS Extension instance in the cloud. You can also run this command if you need to set up point-to-point WSS trust between two JCS-SaaS Extension instances running in separate identity domains. Note that this command doesn’t allow you to establish trust from JCS-SaaS Extension to the local WebLogic Server environment.

See Setting Up Trust Between WebLogic Domains and JCS-SaaS Extension
New configurations added to Flattened Configuration Management feature.

You can now modify three new configurations from the command line by using the Flattened Configuration Management feature introduced in June 2016. These configurations are:

  • credential.custom.map.enabled

    Specifies whether the Credential Store custom map is enabled.

  • security.SSL.minimum.protocol.version

    Sets the minimum version of SSL or TLS protocols enabled for SSL connections.

  • sun.http.handler.enabled

    Indicates whether or not the Sun HTTP handler is enabled.

See Managing Configurations.

August 2016

Feature Description
New configurations added to Flattened Configuration Management feature. You can now modify nine new configurations from the command line by using the Flattened Configuration Management feature introduced in June 2016. These configurations are:

  • jdbc.datasource.timeout

  • jdbc.datasource.min.capacity

  • jdbc.datasource.max.capacity

  • jdbc.datasource.initial.capacity

  • jdbc.datasource.idle.trust.seconds

  • jdbc.datasource.shrink.frequency

  • jdbc.datasource.inactive.timeout

  • jdbc.datasource.statement.timeout

  • server.max.thread.stuck.time

See Managing Configurations.

July 2016

Feature Description
Enable applications to trigger email notifications. You can now enable applications deployed on JCS-SaaS Extension to use the JavaMail APIs to send emails to specified users when certain, specified events occur. See Enabling Email Notifications in JCS-SaaS Extension.

June 2016

Feature Description
Flattened configuration management to allow system configuration from the command line. You can use the command-line interface to view a limited set of configurations and then easily modify them by specifying a name/value pair. This allows you to avoid any internal implementation when you need to configure certain parts of your application. See Managing Configurations.

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 – SaaS Extension documentation, videos, and tutorials.