Module deployment editor

In WebSphere® Integration Developer, the module deployment editor is the designated tool for editing module deployment properties for Web services import and exports. 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. 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 Export WS-Security
  • 2 Import WS-Security

All of the tasks that you can perform in the module deployment editor are either initiated or performed in these two pages. The Export WS-Security and Import WS-Security pages are described in the following sections.

Export WS-Security page

The Export WS-Security page enables you to configure WS-Security module deployment properties for Web services exports. It maps to the Web services editor that is used to edit Web services deployment descriptors in the J2EE perspective of Rational Application Developer. The Export WS-Security page is shown in the following figure:

Picture of the Export WS-Security page of the module deployment editor

As shown in the figure, the Export WS-Security page has two subpages:
  • 1 Extensions
  • 2 Binding Configurations

These two subpages map to the Extensions and Binding Configurations pages of the Web services editor.

The Extensions subpage is used to manage the security extensions for exports. The security extensions specify what security constraints are required; for example, signing the message body or encrypting a token.

By comparison, the Binding Configurations subpage is used to manage binding configurations for exports. The binding configurations specify how to apply the required security constraints defined in the security extensions; for example, which keys are used for signing or encryption and how to authenticate a needed security token.

Import WS-Security page

The Import WS-Security page enables you to configure WS-Security module deployment properties for Web services imports. It maps to the EJB deployment descriptor editor that is used to edit EJB deployment descriptors in the J2EE perspective of Rational Application Developer. The Import WS-Security page is shown in the following figure:

Picture of the Import WS-Security page of the module deployment editor

As shown in the figure, the Import WS-Security page has two subpages:
  • 1 WS Extension
  • 2 WS Binding

These two subpages map to the WS Extension and WS Binding pages of the EJB deployment descriptor editor.

The WS Extension subpage is used to manage the security extensions for imports. The security extensions specify what security constraints are required; for example, signing the message body or encrypting a token.

By comparison, the WS Binding subpage is used to manage bindings for imports. The bindings specify how to apply the required security constraints defined in the security extensions; for example, which keys are used for signing or encryption and how to authenticate a needed security token.

Related concepts
Module deployment properties
WS-Security specification
Related tasks
Opening the module deployment editor
Editing WS-Security properties
Implementing authentication

Feedback
(C) Copyright IBM Corporation 2005, 2006. All Rights Reserved.