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

Module deployment editor

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, the module deployment editor is the designated tool for editing module deployment properties for web services exports and imports. It enables you to specify and persist changes to module deployment properties in deployment descriptor files. The module deployment editor features a simple user interface that enables you to easily manage module deployment properties.

You can open the module deployment editor from either the Business Integration view or the Physical Resources view of the Business Integration perspective, or from the properties of web service exports in the assembly diagram editor. The module deployment editor is shown in the following figure:

Picture of the module deployment editor

As shown in the figure, there are two main pages of the module deployment editor:
  • 1 Design
  • 2 Source

These two pages are described in the following sections.

Design page

The Design page provides a graphical user interface that enables you to view and configure deployment properties. The Design page contains two main sections:
  • An Overview section on the left side of the Design page.
  • A details section on the right side of the Design page.
The Overview section contains a list of artifact types, such as Web Services Exports. The details section enables you to view and configure deployment properties for any artifact that is selected in the Overview section.

Source page

The Source page displays the underlying XML source code for artifacts in the Module Deployment Editor. Using the Source page, you can view and configure deployment properties. The Design and Source pages are automatically synchronized with each other whenever changes are made in one page or the other. Although you can use the Source page to configure deployment properties, it is a best practise to always use the Design page to configure deployment properties, and use the Source page for viewing the underlying XML source code.