Binary documents

Binary document are passed through the hub as is, and, therefore, exchanging binary documents between a community participant and a Community Manager back-end application is a straightforward process. The binary protocol is already available for the AS, None, and Backend Integration packages; therefore, Step 1: Make sure the document flow definition is available is already done.

Note: You can add attributes at any level (Package, Protocol, or Document Flow) to modify default processing by clicking the Edit Attribute Values icon. No attributes are associated by default with the binary protocol or document flow.

Similarly, four interactions involving binary documents are already provided by default, and for those interactions, it is not necessary for you to perform Step 2: Create interactions. Interactions are supplied for the following exchanges:

Table 4. System-supplied interactions
Source Package/Protocol/Document flow Target Package/Protocol/Document flow
AS/Binary/Binary Backend Integration/Binary/Binary
Backend Integration/Binary/Binary AS/Binary/Binary
AS/Binary/Binary None/Binary/Binary
None/Binary/Binary AS/Binary/Binary

For the exchange of binary documents, you still have to perform:

Copyright IBM Corp. 2003, 2005