We are excited to announce the new enhancements to Oracle Application Container Cloud and Oracle Java Cloud Service that were rolled out as part of the 17.4.2 release.
New Language runtime Support – Go
ACCS now has support for Go language (a.k.a. golang) in addition to its list of existing runtimes (Java SE, Node, PHP, Python, Ruby, and Java EE).
Go ahead (pun intended!) and try out our quick start tutorial!
You can now deploy your backend applications (a.k.a. Worker) without exposing them to the public internet i.e. ACCS will not generate a publicly accessible URL for your application, but it will have all the other capabilities of a regular ACCS application. All you require is an explicit declaration in the manifest.json (example below).
"command": "java -jar accs-worker.jar",
"notes": "ACCS worker app"
Check out the Resources section for a blog pointer on this topic.
ACCS now allows seamless integration with Oracle Identity Cloud Service to enable authentication and authorization for your applications. This capability is currently available to the applications deployed to the Node.js and Java SE application runtime.
Runtime Updates - Java EE 7 and Java 9
Until now, you were required to bring your own containers to run Java EE applications (embedded or packaged Tomcat, JBoss, Payara Micro etc). Since release 17.3.5, Java EE 7 is supported as a first class runtime that allows you to simply deploy your WAR files to ACCS.
Support for Java SE runtime now is upgraded to include recently released Java 9. You can now deploy new Java 9 applications or upgrade from older versions (Java 7, 8)
Java Cloud Service
If a subscription to Oracle Identity Cloud Service is included, Oracle Java Cloud Service can integrate the WebLogic Server security realm with Oracle Identity Cloud Service during provisioning of a new service instance. Thereafter, users that access the administration consoles or the involved applications are authenticated against Oracle Identity Cloud 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.