Table of Contents
Advertisement
3. Click the Edit icon to modify the properties.
4. Click Save.
Supporting ebMS
WebSphere Partner Gateway supports ebXML Message Service (ebMS) mechanism.
The ebMS defines the message enveloping and header document schema used to
transfer ebXML messages in a communications protocol. ebMS is defined as a set
of layered extensions to the base SOAP and SOAP with attachments, specifications.
It contains structures for a message header used to route and deliver the message,
and a payload section. ebMS focuses on transporting a payload from one party to
another, which may include intermediaries. It is important to keep in mind that
ebMS does not validate the business processes or the correctness of the ebXML
content being sent. The function of ebMS is to assure the sender of a secure and
intact transmission of the ebXML payload. ebMS uses Collaboration Protocol
Agreements (CPA) to determine how and what kind of data is transmitted between
two parties.
Uploading a CPA to WebSphere Partner Gateway
A CPA defines all the valid, visible, and enforceable electronic data interactions
between two parties. The CPA is an agreement between two parties as to how they
will exchange electronic data. If a CPA is provided, it can be uploaded into
WebSphere Partner Gateway to aid in configuring the product. If a CPA has not
been provided, the product can be configured manually.
There are two ways to upload a CPA: from the Document Definition page or from
the Hub Admin page.
Uploading from the Document Definition page
About this task
Perform the following to upload a CPA:
1. Click Hub Admin > Hub Configuration > Document Definition.
2. Click the Upload/Download Packages link on the top of the screen.
3. Select ebMS CPA as the package type and click Submit.
4. Click the Upload CPA link on the top of the screen.
5. Click Browse, locate the appropriate file, and click Open.
6. Ensure that ebMS Version 2.0 is selected.
7. Click Upload.
After a successfully completing the upload, you will have both the internal and
external partners created. The internal and external partner business-to-business
capabilities are enabled, interactions and connections made, and respective
destinations created as well. It is important to note that if an error occurs during a
CPA upload then any configuration made during the upload is not rolled back.
Note: To prevent the accidental replacement of existing certificates, you must
manually upload any certificates in the CPA that are stored in the file system.
While creating the interaction the default action is set to Pass Through. The
following are the additional flows made for supporting ebMS:
v Ping
v Status Request
36
IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide
Advertisement
Table of Contents
