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

Keeping the workspace clean

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
In IBM® Integration Designer, there are numerous ways to maintain a clean workspace. For example, whenever you delete certain kinds of primary workspace resources, you can choose to have their supporting artifacts automatically deleted rather than having them retained and unused in the workspace.

About this task

You can, for example, choose to have workspace XSLT maps and BO maps automatically deleted whenever you delete an associated Mapping primitive or BO Map primitive in the mediation flow editor, as described in the topic "Deleting primitives that use XSLT and Business object maps". Similarly, you can choose to have component implementations or other supporting resources automatically deleted whenever you delete an associated component, export, or import in the assembly editor, as explained in the topics "Deleting components" and "Deleting exports and imports."

If you want to create a new XML map for a Mapping primitive but an XML map already exists, you can create the new XML map and simultaneously choose whether to have the existing XML map overridden, deleted, or retained. This is described in the topic "Creating an XML map."

Another way to keep your workspace clean and organized is to keep the names of your components synchronized with the names of their associated component implementations. This is easily accomplished in the assembly editor. When you refactor and rename a component in the assembly editor, you are given the option of renaming just the component or renaming both the component and its implementation. This is described in the topic "Renaming components."