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:
- The FTP transport
- Custom XML documents
- Binary files (with no packaging)
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.
- Click Hub Admin > Hub Configuration > Targets.
- Click Create.
- Enter the following information:
- Target Name: FTP_Receiver
- Transport: FTP Directory
- FTP Root Directory: C:/ftproot
- 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.
- Click Hub Admin > Hub Configuration > Document Flow Definition.
- Click Manage Interactions.
- Click Create Interaction.
- From Source select: Package: None
Protocol: Binary (1.0) Document Flow: Binary (1.0).
- From Target select: Package: None
Protocol: Binary (1.0) Document Flow: Binary (1.0).
- From Action select Pass Through.
- Click Save.
Updating the B2B capabilities for Partner One
This section shows how to configure Partner One to be
able to accept binary documents.
- Click Account Admin > Profiles > Community Participant.
- Click Search.
- Click the magnifying glass icon next to Partner One.
- Click B2B Capabilities.
- Click the activate icon underneath Set Source for Package: None to
enable it.
- Click the activate icon underneath Set Target for Package: None to
enable it.
- Click the folder icon next to Package: None.
- Click the activate icon for Protocol: Binary (1.0) for
both source and target.
- Click the folder icon next to Protocol: Binary (1.0).
- 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.
- Click Account Admin > Profiles > Community Participant.
- Click Search.
- Click the magnifying glass icon next to Partner Two.
- Click B2B Capabilities.
- Click the activate icon underneath Set Source for Package: None to
enable.
- Click the activate icon underneath Set Target for Package: None to
enable.
- Click the folder icon next to Package: None.
- Click the activate icon for Protocol: Binary (1.0) for
both source and target.
- Click the folder icon next to Protocol: Binary (1.0).
- 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.
- Click Account Admin > Participant Connections.
- Select Partner Two from the Source list.
- Select Partner One from the Target list.
- Click Search.
- 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.
- Click Hub Admin > Hub Configuration > Document Flow Definition.
- Click Create Document Flow Definition.
- Enter the following information:
- Document flow type: Protocol
- Code: CustomXML
- Version: 1.0
- Description: CustomXML
- Set Document Level to No.
- Set Status to Enabled.
- Set Visibility: Community Operator to Yes.
- Set Visibility: Community Manager to Yes.
- Set Visibility: Community Participant to Yes.
- Select:
- Package: AS
- Package: None
- Package: Backend Integration.
- Click Save.
Creating the Tester_XML document definition
The second step is to create a document flow definition
for the new protocol.
- Click Hub Admin > Hub Configuration > Document Flow Definition.
- Click Create Document Flow Definition.
- Enter the following information:
- Document flow type: Document Flow
- Code: XML_Tester
- Version: 1.0
- Description: XML_Tester
- Set Document Level to Yes.
- Set Status to Enabled.
- Set Visibility: Community Operator to Yes.
- Set Visibility: Community Manager to Yes.
- Set Visibility: Community Participant to Yes.
- Click the folder icon next to Package: AS and select Protocol: CustomXML.
- Click the folder icon next to Package: None and select Protocol: CustomXML.
- Click the folder icon next to Package: Backend Integration and
select Protocol: CustomXML.
- Click Save.
Creating the Tester_XML XML Format
Finally, you create the XML format associated with the
new protocol.
- Click Hub Admin > Hub Configuration > XML Formats.
- Click Create XML Format.
- Enter the following information:
- Routing Format: CustomXML 1.0
- File Type: XML
- Identifier Type: Root Tag
- Identifier Type Value: Tester
- Source Business Id: Element Path
- Source Business Id Value: /Tester/From
- Target Business Id: Element Path
- Target Business Id Value: Tester/To
- Source Document Flow: Constant
- Source Document Flow Value: XML_Tester
- Source Document Flow Version: Constant
- Source Document Flow Version Value: 1.0
- 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.
- Click Hub Admin > Hub Configuration > Document Flow Definition.
- Click Manage Interactions.
- Click Create Interaction.
- From Source, select:
- Package: None
- Protocol: CustomXML (1.0)
- Document Flow: XML_Tester (1.0).
- From Target select:
- Package: None
- Protocol: CustomXML (1.0)
- Document Flow: XML_Tester (1.0).
- From Action, select Pass Through.
- 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.
- Click Account Admin > Profiles > Community Participant.
- Click Search.
- Click the magnifying glass icon next to Partner One.
- Click B2B Capabilities.
- Click the activate icon underneath Set Source for
Package: None to enable it.
- Click the activate icon underneath Set Target for
Package: None to enable it.
- Click the folder icon next to Package: None.
- Click the activate icon for Protocol: CustomXML (1.0) for both
source and target.
- Click the folder icon next to Protocol: CustomXML (1.0).
- 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.
- Click Account Admin > Profiles> Community Participant.
- Click Search.
- Click the magnifying glass icon next to Partner Two.
- Click B2B Capabilities.
- Click the activate icon underneath Set Source for
Package: None to enable it.
- Click the activate icon underneath Set Target for
Package: None to enable it.
- Click the folder icon next to Package: None.
- Click the activate icon for Protocol: CustomXML (1.0) for both
source and target.
- Click the folder icon next to Protocol: CustomXML (1.0).
- 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.
- Click Account Admin > Participant Connections.
- Select Partner Two from the Source list.
- Select Partner One from the Target list.
- Click Search.
- 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.
