Versioning modules and libraries

If a module or library is in a process application or toolkit, it takes on the lifecycle of the process application or toolkit (versions, snapshots, tracks, and so on). Module and library names must be unique within the scope of a process application or toolkit.

This topic describes the versioning of modules and libraries that are used with process applications. Note, however, that if you deploy modules directly from IBM® Integration Designer to Process Server, you can continue to follow the procedure of assigning version numbers to modules during deployment, as described in "Creating versioned modules and libraries".

A module or library that is associated with the IBM Process Center must have its dependent libraries in the same process application or in a dependent toolkit.

The following table lists the selections you can make in the dependency editor in IBM Integration Designer when a library is associated with a process application or toolkit:

Table 1. Dependencies for Module, Process App or Toolkit, and Global libraries
Library scope	Description	Can depend on . . .
Module	A copy of this library exists on the server for each module that uses it.	A module-scoped library can depend on all types of libraries.
Process App or Toolkit	The library is shared among all modules in the scope of the process application or toolkit. This setting takes effect if deployment is done through the IBM Process Center. If deployment occurs outside of the IBM Process Center, the library is copied into each module. Note: Libraries created in IBM Integration Designer version 8 have a sharing level of Process App or Toolkit by default.	A library of this type can depend only on global libraries.
Global	The library is shared among all modules that are running.	A global library can depend only on other global libraries. Note: You must configure a WebSphere shared library in order to deploy the global library. See "Module and library dependencies" for more information.