@jpd:ebxml Annotation

Specifies annotations for participant business processes involved in exchanging ebXML business messages.

Syntax

@jpd:ebxml

protocol-name="ebXML"

ebxml-service-name="serviceName"

ebxml-action-mode="default" | "non-default"

Attributes

protocol-name

The protocol name, which is always ebXML.

ebxml-service-name

The name of the ebXML service associated with this business process and defined in the TPM repository. Defaults to the name of the business process file. The name specified here must match the service name specified on the initiator side (for example, in the ebxml-service-name annotation on the ebXML control in the initiator business process). You provide this service name to your trading partners.

Note: This service name corresponds to the eb:Service entry in the ebXML message envelope.

ebxml-action-mode

Action mode for this business process. Determines the value specified in the eb:Action element in the message header of the ebXML message, which becomes important in cases where multiple message exchanges occur within the same conversation. One of the following values:

default—Sets the eb:Action element to SendMessage (default name).
non-default—Sets the eb:Action element to the name of the method (on the ebXML control) that sends the message in the initiator business process. For one-way conversations, this name must match the method name of the Client Request node in the corresponding participant business process. For round trip conversations, the method name in the callback interface for the Client Callback node in the participant business process must match the method name (on the ebXML control) in the control callback interface in the initiator business process. Using non-default is recommended to ensure recovery and high availability.

Note: If unspecified, the ebxml-action-mode is set to non-default.

Remarks

None.