Extending the basic configuration

This section shows you how to modify the basic configuration described in this appendix. Using the same partners and setup described earlier (a Community Manager named PartnerOne, using a DUNS ID of 123456789 and a file-directory gateway, and a participant named PartnerTwo with a DUNS ID of 987654321 and an HTTP gateway), this section describes how to add support for:

Creating an FTP target

The FTP target receives files and passes them to the Document Manager for processing. As described in Preparing to configure the hub, before you can create an FTP target, you must have an FTP server installed, and you must have created an FTP directory and configured your FTP server.

In this example, it is assumed that the FTP server has been configured for Partner Two and that the root directory is c:/ftproot.

  1. Click Hub Admin > Hub Configuration > Targets.
  2. Click Create.
  3. Enter the following information:
    1. Target Name: FTP_Receiver
    2. Transport: FTP Directory
    3. FTP Root Directory: C:/ftproot
  4. Click Save.

Setting up the hub to receive binary files

This section covers the steps required to configure the hub to receive binary documents that Partner Two wants to send to Partner One.

Creating a valid interaction for binary documents

By default, WebSphere Business Integration Connect does not have a binary-to-binary document interaction configured. In this section, you will create the required interaction to allow binary documents to pass through the system.

  1. Click Hub Admin > Hub Configuration > Document Flow Definition.
  2. Click Manage Interactions.
  3. Click Create Interaction.
  4. From Source select: Package: None Protocol: Binary (1.0) Document Flow: Binary (1.0).
  5. From Target select: Package: None Protocol: Binary (1.0) Document Flow: Binary (1.0).
  6. From Action select Pass Through.
  7. Click Save.

Updating the B2B capabilities for Partner One

This section shows how to configure Partner One to be able to accept binary documents.

  1. Click Account Admin > Profiles > Community Participant.
  2. Click Search.
  3. Click the magnifying glass icon next to Partner One.
  4. Click B2B Capabilities.
  5. Click the activate icon underneath Set Source for Package: None to enable it.
  6. Click the activate icon underneath Set Target for Package: None to enable it.
  7. Click the folder icon next to Package: None.
  8. Click the activate icon for Protocol: Binary (1.0) for both source and target.
  9. Click the folder icon next to Protocol: Binary (1.0).
  10. Finally, click the activate icon for Document Flow: Binary (1.0) for both source and target.

Updating the B2B capabilities for Partner Two

This section shows how to configure Partner Two to be able to send binary documents.

  1. Click Account Admin > Profiles > Community Participant.
  2. Click Search.
  3. Click the magnifying glass icon next to Partner Two.
  4. Click B2B Capabilities.
  5. Click the activate icon underneath Set Source for Package: None to enable.
  6. Click the activate icon underneath Set Target for Package: None to enable.
  7. Click the folder icon next to Package: None.
  8. Click the activate icon for Protocol: Binary (1.0) for both source and target.
  9. Click the folder icon next to Protocol: Binary (1.0).
  10. Finally, click the activate icon for Document Flow: Binary (1.0) for both source and target.

Creating a new participant connection

This section shows how to configure a new participant connection between Partner One and Partner Two for binary documents.

  1. Click Account Admin > Participant Connections.
  2. Select Partner Two from the Source list.
  3. Select Partner One from the Target list.
  4. Click Search.
  5. Locate the None (N/A), Binary (1.0), Binary (1.0) to None (N/A), Binary (1.0), Binary (1.0) connection and click Activate to activate it.

Setting up the hub for custom XML documents

As described in Configuring the hub, you must configure the hub to be able to route XML Files. This section covers the steps required to configure the Document Manager to be able to route the following XML document:

<?xml version="1.0" encoding="UTF-8"?> 
       <!DOCTYPE Tester> 
         <Tester> 
        <From>987654321</From> 
       <To>123456789</To> 
   </Tester> 

The Document Manager uses the RootTag to identify the type of XML document. It then extracts the values from the From and To fields to identify the From Participant Name and To Participant Name.

Creating the CustomXML protocol definition format

The first step is to create a new protocol for the Custom XML you are going to exchange.

  1. Click Hub Admin > Hub Configuration > Document Flow Definition.
  2. Click Create Document Flow Definition.
  3. Enter the following information:
    1. Document flow type: Protocol
    2. Code: CustomXML
    3. Version: 1.0
    4. Description: CustomXML
  4. Set Document Level to No.
  5. Set Status to Enabled.
  6. Set Visibility: Community Operator to Yes.
  7. Set Visibility: Community Manager to Yes.
  8. Set Visibility: Community Participant to Yes.
  9. Select:
    1. Package: AS
    2. Package: None
    3. Package: Backend Integration.
  10. Click Save.

Creating the Tester_XML document definition

The second step is to create a document flow definition for the new protocol.

  1. Click Hub Admin > Hub Configuration > Document Flow Definition.
  2. Click Create Document Flow Definition.
  3. Enter the following information:
    1. Document flow type: Document Flow
    2. Code: XML_Tester
    3. Version: 1.0
    4. Description: XML_Tester
  4. Set Document Level to Yes.
  5. Set Status to Enabled.
  6. Set Visibility: Community Operator to Yes.
  7. Set Visibility: Community Manager to Yes.
  8. Set Visibility: Community Participant to Yes.
  9. Click the folder icon next to Package: AS and select Protocol: CustomXML.
  10. Click the folder icon next to Package: None and select Protocol: CustomXML.
  11. Click the folder icon next to Package: Backend Integration and select Protocol: CustomXML.
  12. Click Save.

Creating the Tester_XML XML Format

Finally, you create the XML format associated with the new protocol.

  1. Click Hub Admin > Hub Configuration > XML Formats.
  2. Click Create XML Format.
  3. Enter the following information:
    1. Routing Format: CustomXML 1.0
    2. File Type: XML
    3. Identifier Type: Root Tag
    4. Identifier Type Value: Tester
    5. Source Business Id: Element Path
    6. Source Business Id Value: /Tester/From
    7. Target Business Id: Element Path
    8. Target Business Id Value: Tester/To
    9. Source Document Flow: Constant
    10. Source Document Flow Value: XML_Tester
    11. Source Document Flow Version: Constant
    12. Source Document Flow Version Value: 1.0
  4. Click Save.

Creating a valid interaction for XML_Tester XML documents

You now have a new protocol and document flow with which to set up a valid interaction.

  1. Click Hub Admin > Hub Configuration > Document Flow Definition.
  2. Click Manage Interactions.
  3. Click Create Interaction.
  4. From Source, select:
    1. Package: None
    2. Protocol: CustomXML (1.0)
    3. Document Flow: XML_Tester (1.0).
  5. From Target select:
    1. Package: None
    2. Protocol: CustomXML (1.0)
    3. Document Flow: XML_Tester (1.0).
  6. From Action, select Pass Through.
  7. Click Save.

Updating the B2B capabilities for partnerOne

To enable the exchange of the custom XML document, you must update the B2B capabilities of the participants.

  1. Click Account Admin > Profiles > Community Participant.
  2. Click Search.
  3. Click the magnifying glass icon next to Partner One.
  4. Click B2B Capabilities.
  5. Click the activate icon underneath Set Source for Package: None to enable it.
  6. Click the activate icon underneath Set Target for Package: None to enable it.
  7. Click the folder icon next to Package: None.
  8. Click the activate icon for Protocol: CustomXML (1.0) for both source and target.
  9. Click the folder icon next to Protocol: CustomXML (1.0).
  10. Finally, click the activate icon for Document Flow: XML_Tester (1.0) for both source and target.

Updating the B2B capabilities for partnerTwo

You update the B2B capabilities of Partner Two to enable the exchange of the new custom XML format.

  1. Click Account Admin > Profiles> Community Participant.
  2. Click Search.
  3. Click the magnifying glass icon next to Partner Two.
  4. Click B2B Capabilities.
  5. Click the activate icon underneath Set Source for Package: None to enable it.
  6. Click the activate icon underneath Set Target for Package: None to enable it.
  7. Click the folder icon next to Package: None.
  8. Click the activate icon for Protocol: CustomXML (1.0) for both source and target.
  9. Click the folder icon next to Protocol: CustomXML (1.0).
  10. Finally, click the activate icon for Document Flow: XML_Tester (1.0) for both source and target.

Creating a new participant connection

Finally, create a new participant connection.

  1. Click Account Admin > Participant Connections.
  2. Select Partner Two from the Source list.
  3. Select Partner One from the Target list.
  4. Click Search.
  5. Locate the None (N/A), Binary (1.0), Binary (1.0) to None (N/A), Binary (1.0), Binary (1.0) connection and click Activate to activate it.

Copyright IBM Corp. 2003, 2004