Defining document flows and interactions

After you have created all the targets you need to receive documents from community participants and the Community Manager, the next step is to specify the types of documents you expect to receive at the hub. You do this from the Manage Document Flow Definition page.

A document flow definition is made up of, at minimum, a package, a protocol, and a document flow. For some protocols, an activity, action, and signal can be specified.

Using system-supplied packages and protocols

When you install WebSphere Business Integration Connect, a set of default packages (AS, None, Backend Integration) is displayed on this page. All the default packages are enabled (by default) for use. When you expand the packages, you see the choice of protocols that can be used with that package.

Figure 23. The default packages

For example, under AS, you see EDI-X12. If you selected EDI-X12 under AS, WebSphere Business Integration Connect would be able to send or receive EDI-X12 documents wrapped in AS2 packaging. If you selected None and then Web Service, WebSphere Business Integration Connect would be able to request a Web service of a participant or provide a Web service to a participant.

If you are going to send or receive documents with the Web Service protocol, you must upload the WSDL file that is associated with the Web service, which is described in Uploading packages For more detailed information about using Web services, see Appendix C. Setting up Web service requests.

With the exception of Web services, if your hub community will use only these combinations of packages and protocols, you can skip ahead to Creating interactions. However, if you want to use a package or protocol that is not provided on the Manage Document Flow Definitions page, or if you want to support Web services, follow the procedures in the remainder of this section. Also, if you want to modify the inbound or outbound workflow steps or create or modify actions, see Configuring document processing.

Uploading packages

Business Integration Connect provides a way to import predefined RNIF Document Flow Definitions and WSDL files. RNIF Document Flow Definitions are uploaded in ZIP archives called packages. WSDL files can be uploaded individually or together in a ZIP archive. If you are not exchanging RosettaNet documents or supporting Web services, skip this section and go on to Configuring document processing.

Uploading WSDL packages

This section describes how to upload a WSDL package associated with a Web service. See Appendix C. Setting up Web service requests for more complete information about using Web services with WebSphere Business Integration Connect.

To upload a WSDL package, perform the following steps:

  1. Click Hub Admin >Hub Configuration > Document Flow Definition.
  2. Click Upload/Download Packages.
    Figure 24. The Upload/Download Packages page
  3. Select Yes for WSDL Package.
  4. For Web Service Public URL, enter the public URL of the Web service provided by the Community Manager to the participant or by the participant to the Community Manager.
  5. Click Browse and select the WSDL file.
  6. Make sure Commit to Database is set to Yes.
  7. Click Upload.

    The WSDL file is installed into the system.

Uploading RNIF packages

This section describes how to upload an RNIF package to be used to send and receive RosettaNet documents. See Appendix B. Setting up RosettaNet exchanges for more complete information about using RosettaNet documents with WebSphere Business Integration Connect.

To upload an RNIF package:

  1. Click Hub Admin > Hub Configuration > Document Flow Definition.
  2. Click Upload/Download Packages.
  3. Select No for WSDL Package.
  4. Click Browse and select the RNIF package.
    Note: The file in the ZIP archive must be within a directory titled Packages (for example: Packages/AS1.xml).
  5. Make sure Commit to Database is set to Yes.
  6. Click Upload.

    The package is installed into the system.

Copyright IBM Corp. 2003, 2004