You can deploy a Java EE web application to Oracle Application Container Cloud Service with minimal changes to how it’s packaged.
Your Java EE web application must meet some standard Oracle Application Container Cloud Service requirements, while others are optional or not applicable.
Only Java EE version 7 is supported.
Your web application doesn’t need to read the APP_HOME and PORT environment variables.
Your web application doesn’t use a launch command.
Your web application must include all dependent classes that are not included in WebLogic Server.
manifest.jsonfile is optional. You can deploy either a single
.warfile or a
.tar.gzfile with an optional
manifest.jsonfile and a single
.warfile at the root. The
isClusteredparameter is not supported.
If your web application requires a service binding to a DBCS or MySQLCS database, you must specify it in a
deployment.jsonfile. A WebLogic data source is automatically created with the default name
jdbc/service-binding-nameDS. You can specify database driver and data source parameters in this file if necessary. Names of data source properties align with WebLogic data source MBean properties.
You can define any needed environment variables and system properties in a
Your web application can interact with a cache using the Java API or the REST API.
For details about the
deployment.json files, see Create Metadata Files.
After deployment, your web application has these features:
Your web application is deployed to WebLogic Server on the back end.
You can scale memory and instances just as you can with any application.
You can stop, start, and restart just as you can with any application.
Most standard web application features are supported, with a few exceptions.
XA and RAC integration are not supported.
ADF is not supported.
weblogic.xmlfile isn’t required, it is used if present.
To learn more about how to deploy an application, see Deploy an Application.