Deploying the enterprise archive (EAR) on WebLogic


The doc ear does not contain end-user documentation, such as context-sensitive help files. It contains only development-related documentation, including the API Javadoc, ERDs, and XSDs and should not be deployed to a production server. Deploy the doc ear with the application ear on test or development environments. Do not deploy the doc ear on a production environment.

Sterling Configure, Price, Quote provides support for deploying multiple EARs on a single application server. On the same application server, you can:

  • Deploy different customizations of the same or different versions of the application, or
  • Deploy different versions of the same application

Multiple EARs or context roots require additional memory for the application server JVM. Testing has shown that the deployment of a second IBM® EAR file requires 2.5 - 3.5 times the memory of a single EAR. Supporting two deployments may require up to 2.5 GB of heap space and 1.2 GB of permanent space.

must be installed with JDK 1.8.0_131 or later updates because the WebLogic Server 12c ( is not supported on later versions of JDK.

During installation, you can use JVM-specific arguments in your Sandbox.cfg file, such as ADDITIONAL_ANT_JAVA_TASK_ARGS and ADDITIONAL_ANT_COMPILER_TASK_ARGS, to avoid out-of-memory errors.

For instructions on deploying the EAR to your WebLogic application server, see your WebLogic documentation.
Note: If you encounter the java.lang.IllegalStateException: MASM0001: Default configuration file [ jaxws-tubes-default.xml ] was not found error, see Troubleshooting: java.lang.IllegalStateException: MASM0001 error encountered in WebLogic