This topic applies only to the IBM Business Automation Workflow Advanced configuration.

Associating a module or library with a process application or toolkit

Edit online
Draft comment:
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15
Draft comment:
This topic was viewed 2 times since its publication
You can associate a module or library with a process application or toolkit to add additional functions to the application, or to take advantage of version control on Workflow Center.

Before you begin

If a module that contains a long-running process has been deployed and you now want to associate the module with a process application, you should first consider whether you want to migrate your process instance:
  • If you want to migrate the process instance, you must create a new process version before you associate the module with the process application. You can create a new process version by right-clicking your module in the Business Integration view and selecting New Process Version.
  • If you do not want to migrate the process instance, you can proceed to associate the module with the process application by following the instructions in this topic.
  • See the guidance and limitations topics listed in the Related reference links for information on working with Workflow Center.
There are wider implications to associating a module or library with a process application or toolkit than you might first see. Modules and libraries associated with toolkits can be shared with other process applications in addition to the one in your workspace. Modules and libraries that are associated with process applications are also visible within the process application. Remember too that when you bring a process application or toolkit into your workspace, you may be bringing in a snapshot, which is a previous point in time.
Note: If you are developing iteratively and have changed the name of a module or library (or the scope of a library) since you first associated it with a process application or toolkit, see the "Scope and naming considerations for associated modules and libraries" link at the end of this topic.

Procedure

To associate a module or library with a process application or toolkit, complete the following steps:

  1. In the Business Integration view, right-click the module or library that you want to add to your process application or toolkit. From the menu, click Associate with Workflow Center. The Associate with a Process Application or Toolkit window opens.
    Tip: The Associate with a Process Application or Toolkit window also appears when you use the wizard to create new artifacts in IBM® Integration Designer such as modules, libraries, and monitor models.
  2. From the Select the process application or toolkit that will contain the projects list, select a process application or toolkit.
  3. In the Select the projects to associate pane, you can see the projects in your workspace that are available for association. Select the modules or libraries that you want to associate with your selection. Click Select All to select all the modules or libraries that have not been associated with a process application or toolkit. Click Select Referenced to select modules or libraries referenced to the selected item. For example, click Select Referenced to add a library to the selected list if a selected module had a dependency on that library.
    Tip: You stop sharing certain file types by setting IBM Integration Designer preferences in Windows > Preferences > Business Integration.
  4. Click Finish. The process application or toolkit is brought into the workspace and you can see the associated modules and libraries below it in the Business Integration view.
    Tip: IBM Integration Designer aggregates all artifacts into one integrated process. See the Guidance topic for more details. For information about limitations that may exist when associating projects with process applications, see the topic "Limitations when working with process applications and toolkits."

What to do next

Transitioning from modules and libraries to process applications and toolkits might require updates to some of your artifacts that are contained in your modules and libraries. For example, if your module contains BPEL processes, human tasks or state machines, the validFrom dates for those artifacts are removed (as versioning for BPEL processes used in process applications or toolkits is done in Workflow Center using snapshots). If a BPEL process migration specification refers to a validFrom date, that process migration specification is also updated.