Figure 412 Creating a New Channel

The next screen in the wizard allows you to configure the source organization (or specify "open source"), and specify whether to expect or generate receipts, as shown in Figure 4.13.

Figure 4.13 Setting the Channel's Source Properties

Figure 4.13 Setting the Channel's Source Properties

Specifying an organization name and an associated identifier in this screen allows the channel to receive only those documents that contain that organization's identifier in the BizTalk header. If "Open source" is selected, then other, dynamic criteria are used to decide if this channel should accept a particular instance document. In addition, "Expect receipt" signifies that our BizTalk Server will request that the destination server reply to this document with a receipt.

Finally,"Generate receipt" should be selected only if the type of document handled by this channel requires a receipt to be generated. If so, the corresponding, preconfigured receipt channel should also be selected here.

The next screen (Figure 4.14) acquires information about the inbound document. The inbound document definition is specified in the first text box, and the inbound instance document is validated against any document specification referenced by this definition. In addition, for any channels that are configured as open source, this document definition is used in part to help decide whether this channel is an acceptable target for this instance document. If the instance document is properly validated by the document definition, then this channel can be an acceptable target for the document. In addition, several security-related options are given, to decrypt the document content or verify its digital signature. Finally, both tracking and filtering options are given, as explained in the previous sections.

Figure 4.14 Configuring the Channel's Inbound Document Type

Figure 4.14 Configuring the Channel's Inbound Document Type

Similar to the inbound document page of the wizard, the next screen contains information pertaining to the destination document format (Figure 4.15). The outbound document definition is specified here. If the outbound definition and the inbound definition are not identical, then a mapping must be made between the two schemas.The "Map inbound document to outbound document" check box selects this, and the "Map reference" text box then contains a mapping file generated by the BizTalk Mapper. Finally, a digital signature can be applied to the outbound document here from a certificate store. This information informs the channel how to parse and treat the inbound document.

Figure 4.15 Configuring the Channel's Outbound Document Type

Figure 4.15 Configuring the Channel's Outbound Document Type

Next, the wizard accepts logging configuration information (Figure 4.16). As mentioned in the channel filtering section, you can opt to have the inbound and/or outbound documents saved to the tracking database in either the native format, the intermediate XML format, or both.

Figure 4.16 Configuring the Channel's Document-Level Logging Options

Figure 4.16 Configuring the Channel's Document-Level Logging Options

The final screen of the wizard (Figure 4.17) configures advanced properties of the channel, including the X.12/EDIFACT-specific group number, the number of document delivery retry attempts, and the retry interval.

Figure 4.17 Configuring Advanced Channel Properties

Figure 4.17 Configuring Advanced Channel Properties

Note_

If your BizTalk Server is under load, and a particular channel is receiving and processing a large amount of traffic, you might receive a number of BizTalk Server errors when you try to update the channel. These errors are caused by aborted transactions in the configuration database. This can be remedied by disabling the receive function associated with this channel while editing the channel.

Was this article helpful?

0 0

Post a comment