asked on

WS 8.5 - Associating Application With Shared Reference Library

Using WebSphere 8.5, we've created a shared library, set to use an isolated class loader. In the Admin console, we can associate this shared library with our application and confirm that it the jars in the shared library are in effect. But whenever the application is redeployed, the association is lost.

We'd like to adjust the Manifest.MF, or a deployment descriptor, to reference the shared library so that the application can be redeployed without needing to reset the association in the Admin console. We're unable to make sense of the WebSphere documentation around this. Does anyone have an example of how to make this association?

AdminRAM

if you really want to have a shared library in a loose-config scenario then you should use the Enhanced EAR editor to define the shared libraries. This would be done in the EAR Deployment Descriptor editor under: Deployment Tab : Shared Libraries .

IBM Enhanced EAR deployment and the isolated class loader attribute for a shared library - United States
http://www-01.ibm.com/support/docview.wss?uid=swg21677153

jkavx

ASKER

Well, we're working with Eclipse, developing locally with Apache.

ASKER CERTIFIED SOLUTION

AdminRAM

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

jkavx

ASKER

Thx. I'm looking at the WebSphere documentation for Installed Optional Packages which seems to require modification to the application's Manifest.mf, but also modification of the manifest of the jar files in the shared library.

app1.ear:
META-INF/application.xml
ejb1.jar:
META-INF/MANIFEST.MF:
Extension-List: util
util-Extension-Name: com/example/util
util-Specification-Version: 1.4
META-INF/ejb-jar.xml

util.jar:
META-INF/MANIFEST.MF:
Extension-Name: com/example/util
Specification-Title: example.com's util package
Specification-Version: 1.4
Specification-Vendor: example.com
Implementation-Version: build96