ToPartner Transport

These parameters allow you to supply information needed to transport data to the TP. Find these parameters under the ToPartner Transport subtab.

For a complete description of how to enter these parameters for both ToPartner Transport and FromPartner Transport parameters, seeXDC Parameters.

All Purpose End Point

Description

An endpoint specifies the logical address of where messages can be received. The all- purpose end point is used to designate the receipt address of all ebXML messages.

Values

A valid URL, according to the syntax given under XDC Parameters; required.

Default

None

Use Synchronous Channel

Description

Specifies whether the communication between the message service handler (MSH) servers is synchronous or asynchronous. When set to true, the MSH response message is returned on the same HTTP connection as the inbound request, with an appropriate HTTP response code.

This parameter is not required and is not used in the current release of ebXML Protocol Manager. However, it is provided for compatibility with previous releases.

Ext Attribute SyncReplyMode replaces this parameter in the current release, since ebXML requires a string (for example, None or mshSignalsOnly) and not a Boolean value.

Values

Select true, false, or None; not required.

Default

false

Track for Auditing

Description

Specifies whether the message is tracked using Enterprise Manager’s Message Tracker. Choosing true enables the Message Tracker.

Values

Select true, false, or None; not required.

Default

false

Destination URL

Description

Allows you to enter the destination URL for the current TP.

Values

A valid URL according to the syntax given under XDC Parameters; required.

Default

None

Header Names/Values

Description

Allows you to enter any needed message headers and/or values that may be required by the current TP to reach its destination.

Values

Valid message header names and/or values; not required.

Default

None