How Does One Load Shared Dependent Libraries and Properties For Process Extensions Connecting to Agile PLM Running on WebLogic?
(Doc ID 1064424.1)
Last updated on DECEMBER 04, 2019
Applies to:Oracle Agile PLM Framework - Version 220.127.116.11 and later
Information in this document applies to any platform.
Agile PLM 9.3 running in WebLogic 10.3
***Checked for relevance on 02-Feb-2015***
How to register shared libraries and properties resource files to be used by internal custom action Process Extensions (PX) for Agile PLM 9.3 hosted on WebLogic 10.3 .
When deploying multiple PXs that depend on the same set of libraries, and access the same set of properties resource files, it makes sense to make the shared libraries and properties files accessible from the WebLogic server instead of packaging them in each PX deployment archive. Any update to the libraries or properties resource files can then be done in the central location without having to re-package and re-deploy the PXs.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|How to register shared libraries and properties resource files to be used by internal custom action Process Extensions (PX) for Agile PLM 9.3 hosted on WebLogic 10.3 .|
|To deploy the 3rd party dependent jar files not dependent on Agile jar files:|
|To deploy the 3rd party dependent jar files whether it is dependent on Agile jar files or not:|
|To deploy the properties files:|