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 Comm Man, 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 Configuring the FTP server for receiving documents, 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 Target.
  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 the Community Manager.

Creating an interaction for binary documents

By default, WebSphere Partner Gateway provides four interactions involving binary documents. It does not, however, provide an interaction for binary documents packaged as None going to a participant with the document also packaged as None. 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 the Action list, select Pass Through.
  7. Click Save.

Updating the B2B capabilities for the Community Manager

This section shows how to configure the Community Manager to be able to accept binary documents.

  1. Click Account Admin > Profiles > Community Participant.
  2. Click Search.
  3. Click the View details icon next to Comm Man.
  4. Click B2B Capabilities.
  5. Click the Role is not active icon under Set Target for Package: None to enable it.
  6. Click the Expand icon next to Package: None.
  7. Click the Role is not active icon for Protocol: Binary (1.0) under Set Target.
  8. Click the Expand icon next to Protocol: Binary (1.0).
  9. Finally, click the Role is not active icon for Document Flow: Binary (1.0) under Set 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 View details icon next to Partner Two.
  4. Click B2B Capabilities.
  5. Click the Role is not active icon under Set Source for Package: None to enable it.
  6. Click the Expand icon next to Package: None.
  7. Click the Role is not active icon for Protocol: Binary (1.0) under Set Source.
  8. Click the Expand icon next to Protocol: Binary (1.0).
  9. Finally, click the Role is not active icon for Document Flow: Binary (1.0) under Set Source.

Creating a new participant connection

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

  1. Click Account Admin > Participant Connections.
  2. Select Partner Two from the Source list.
  3. Select Comm Man 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 Custom XML documents, you must configure the hub to be able to route custom 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. Select Protocol from the Document flow type list.
  4. Enter the following information:
    1. Code: CustomXML
    2. Version: 1.0
    3. Description: CustomXML
  5. Set Document Level to No.
  6. Set Status to Enabled.
  7. Set Visibility: Community Operator to Yes.
  8. Set Visibility: Community Manager to Yes.
  9. Set Visibility: Community Participant to Yes.
  10. Select:
    1. Package: AS
    2. Package: None
    3. Package: Backend Integration.
  11. 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. Select Document Flow from the Document flow type list.
  4. Enter the following information:
    1. Code: XML_Tester
    2. Version: 1.0
    3. Description: XML_Tester
  5. Set Document Level to Yes.
  6. Set Status to Enabled.
  7. Set Visibility: Community Operator to Yes.
  8. Set Visibility: Community Manager to Yes.
  9. Set Visibility: Community Participant to Yes.
  10. Click the Expand icon next to Package: AS and select Protocol: CustomXML.
  11. Click the Expand icon next to Package: None and select Protocol: CustomXML.
  12. Click the Expand icon next to Package: Backend Integration and select Protocol: CustomXML.
  13. 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. Select CustomXML 1.0 from the Routing Format list.
  4. Select XML from the File Type list.
  5. Select Root Tag from the Identifier Type list, and type Tester for the value.
  6. Select Element Path from the Source Business Id list, and type /Tester/From for the value.
  7. Select Element Path from the Target Business Id list, and type /Tester/To for the value.
  8. Select Constant from the Source Document Flow list, and type XML_Tester for the value.
  9. Select Constant for the Source Document Flow Version, and type 1.0 for the value.
  10. Click Save.

Creating an interaction for XML_Tester XML documents

You now have a new protocol and document flow with which to set up an 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 the Action list, select Pass Through.
  7. Click Save.

Updating the B2B capabilities for the Community Manager

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 View details icon next to Comm Man.
  4. Click B2B Capabilities.
  5. Click the Role is not active icon under Set Target for Package: None to enable it.
  6. Click the Expand icon next to Package: None.
  7. Click the Role is not active icon for Protocol: CustomXML (1.0) for Set Target.
  8. Click the Expand icon next to Protocol: CustomXML (1.0).
  9. Finally, click the Role is not active icon for Document Flow: XML_Tester (1.0) for Set 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 View details icon next to Partner Two.
  4. Click B2B Capabilities.
  5. Click the Role is not active icon under Set Source for Package: None to enable it.
  6. Click the Expand icon next to Package: None.
  7. Click the Role is not active icon for Protocol: CustomXML (1.0) for Set Source.
  8. Click the Expand icon next to Protocol: CustomXML (1.0).
  9. Finally, click the Role is not active icon for Document Flow: XML_Tester (1.0) for Set Source.

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 Comm Man from the Target list.
  4. Click Search.
  5. Locate the None (N/A), CustomXML (1.0), XML_Tester(1.0) to None (N/A), CustomXML(1.0), XML_Tester (1.0) connection and click Activate to activate it.

Copyright IBM Corp. 2003, 2005