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

Disassociating a module or library from 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
When you disassociate a module or library from a process application or toolkit, you remove the association between the workspace and Workflow Center artifacts. You disassociate a module or library when it is no longer needed by the process application.

About this task

You can disassociate a module while you are connected to the Process Center. After you disassociate, you can (if you so choose) move that disassociated module to another process application or toolkit. If you are disconnected from the Process Center, you can disassociate a module only if you plan to copy that module to another process application, toolkit or process center. You need to switch to the advanced view so you can see the module that you are disassociating. See the "Switching between simple and advanced mode" topic in the related link section.
Restriction: When you disassociate a default project (for example, the default module: PA_Implementation or the default library: PA_Library), you cannot then reassociate the same default project that you have disassociated. To associate the disassociated default project back to the Process Center, you must rename the project before you can associate it to the same process application or toolkit in the Process Center. If a process application does not have a default project associated to it (for example, the default module: PA_Implementation or the default library: PA_Library), when you open that process application in your workspace, a default project is automatically created.

Procedure

To disassociate a module or library from a process application or toolkit, complete the following steps:

  1. To disassociate a module or library:
    1. If you are connected to the Process Center, right-click the module or library you want to disassociate from a process application or toolkit. From the menu, click Disassociate from Process Center. A message warns that the module or library will be disassociated from the Workflow Center, where other people might have been using it.
    2. If you are disconnected from the Process Center, right-click the module or library you want to disassociate from a process application or toolkit. From the menu, click Disassociate. A message warns that the module or library will be disassociated from the process application or toolkit only in your workspace. Your modules and libraries will still be in the Process Center.
  2. Check if there are other modules and libraries with a dependency on the module or library that is being disassociated. Disassociate those modules and libraries also and remove their dependency. If the module or library is refactored and is still needed by these other modules and libraries, associate them again with the refactored module or library and add the dependencies back.
  3. Click Yes to continue or No to leave the module or library in its present state.

Results

When a module or library is disassociated:
  • Connected to the Process Center - When you disassociate a module or library while you are connected to the Process Center, it is removed in the Process Center and your workspace from the process application or toolkit it was associated to. The module or library that was disassociated remains in your workspace, outside of the process application or toolkit, in the Business Integration view.
  • Disconnected form the Process Center - When you disassociate a module or library while you are disconnected from the Process Center, it is removed only in your workspace from the process application or toolkit it was associated to. The module or library that was disassociated remains in your workspace, outside of the process application or toolkit, in the Business Integration view. You cannot reassociate the same module to the process application or toolkit it was disassociated from.

What to do next

Transitioning from process applications and toolkits to modules and libraries might also require updates to some of your artifacts that are contained in your modules and libraries. For example, if your process application or toolkit contains a BPEL process migration specification (that might use the snapshot versioning process), all BPEL process migration specifications will be deleted.