1. Using Oracle Java Cloud Service - SaaS Extension
  2. Administering Instances with JCS-SaaS Extension Control
  3. Managing Shared Libraries with JCS-SaaS Extension Control
  4. About Shared Java EE Libraries and Optional Packages

About Shared Java EE Libraries and Optional Packages

The shared Java EE library feature in WebLogic Server provides an easy way to share one or more different types of Java EE modules among multiple Enterprise applications.

A shared Java EE library is a single module or collection of modules that is registered with the Java EE application container upon deployment. It can be any of the following:

  • Standalone EJB module

  • Standalone web application module

  • Multiple EJB modules packaged in an enterprise application

  • Multiple web application modules package in an enterprise application

  • Single plain JAR file

WebLogic Server also supports optional packages, which provide similar functionality to Java EE libraries, allowing you to easily share a single JAR file among multiple applications. As with Java EE libraries, optional packages must first be registered with WebLogic Server by deploying the associated JAR file as an optional package. After registering the package, you can deploy Java EE modules that reference the package in their manifest files.

The shared Java EE libraries and optional packages supported in WebLogic Server are described in detail in Supported Deployment Units in Oracle Fusion Middleware Deploying Applications to Oracle WebLogic Server.