Versioning Java Class Libraries

AquaLogic BPM Enterprise allows you to include Java libraries as part of the resources of an ALBPM project.

AquaLogic BPM has two ways of handling Java class library versions.
Versionable Libraries Libraries that may change after a process has been deployed in a production environment. When using this type of library, each version of a process must be associated with a specific version of a library. Library versioning is useful when you want to ensure that upgrades to a Java library do not change the behavior of an existing version of a process.

Versionable class libraries are included as part of an exported project file. They are an integral piece of a project similar to other project resources.

Non-versionable Libraries Non-versionable libraries are libraries that generally do not change after a process has been deployed. When changes are required they are propagated to all deployed process in the engine.
Non-versionable libraries must be copied manually into the correct directories. They are stored in the following directories:
  • INSTALL_DIR/webapps/webconsole/WEB-INF/lib
  • INSTALL_DIR/ext
  • INSTALL_DIR/webapps/portal/WEB-INF/lib