The Handle Reply is the start of the mediation reply path for handling reply messages created by any Generate Reply task on the input path.
A Handle Reply task appears automatically in the output path when a Generate Reply task is placed on the input path. Handle Reply tasks do not appear in the palette, and you cannot add these tasks
manually.
See Replying to Messages for more information about the Handle Reply task.
General Tab
Use the General tab to specify a name and description for the task. This tab is useful for providing documentation for tasks in your mediation flows.
Field Description
Name Assign a name to the task, to identify the task in
the mediation flow. This name appears in the tooltip that opens when you hovers the cursor over the task icon in the mediation flow.
Description Describe the task briefly. This description
appears in the tooltip that opens when you hover the cursor over the task icon in the mediation flow.
Invoke Operation
The Invoke Operation task enables you to invoke an operation of an interface in the target interface list during processing of an input, output, or fault path. The operation can be one-way or request-reply. If the operation is request-reply, the reply message is stored in the mediation exchange for use by subsequent tasks in the mediation path.
General Tab
See Invoking an Operation for more information about the Invoke Operation task.
Use the General tab to specify a name and description for the task. This tab is useful for providing documentation for tasks in your mediation flows.
Field Description
Name Assign a name to the task, to identify the task in the mediation flow. This name appears in the tooltip that opens when you hover the cursor over the task icon in the mediation flow.
Description Describe the task briefly. This description appears in the tooltip that opens when you hover the cursor over the task icon in the mediation flow.
Field Description
Target Operation The operation to invoke. The drop-down list is populated with all operations from the interfaces in the target interface list of the mediation flow.
Input Tab
The Input tab is a mapping panel for mapping data from the mediation exchange to the input fields of this task. See Transforming Tasks for more information about using a mapping panel.
Field Description
Task Input A complex element containing the input message for the invoked operation. The structure of the sub-elements depends on the structure of the input message for the operation.
You can also can input the required value for fields directly into the input schema.
Output Tab
The Output tab contains a static tree representation of the reply message schema for the invoked operation. Subsequent tasks in the mediation flow will have access to the reply message. The reply message is stored in an element within the mediation exchange whose root is named the same as the Invoke Operation task name specified on the General tab.
Subsequent tasks also have access to the message context properties in the reply message. See Working with Message Context Properties.
If the message exchange pattern for the operation is one-way, the output is null.
Log
The Log task sends information from the mediation flow context to the log. The Log task can be placed on an input, output, or fault path.
General Tab
For more information about the Log task, see Logging Mediation Exchange Information. For information about configuring the log, see Configuring a Log Task.
Use the General tab to specify a name and description for the task. This tab is useful for providing documentation for tasks in your mediation flows.
Field Description
Name Assign a name to the task, to identify the task in the mediation flow. This name appears in the tooltip that opens when you hover the cursor over the task icon in the mediation flow.
Description Describe the task briefly. This description appears in the tooltip that opens when you hover the cursor over the task icon in the mediation flow.
Field Description
Log Role Select the role for log messages—INFO, WARN, DEBUG, or ERROR. Each is handled separately, and each has its own log.
Use Transform Data Select this option to display the Log tab as a mapping panel that shows the schema with the elements message, messageID, and role, so that you can build custom log messages. See Information for Custom Log Messages.
If this option is not set, the Log tab displays information from the
mediation exchange for you to specify which information to send to the log file. See Information for Standard Log Messages.
The Use Transform Data option is cleared by default.
Log Tab
The appearance of the Log tab depends on whether the option Use Transform Data is selected on the General tab.
● If Use Transform Data is clear (the default), the Log tab shows top-level message information, from which you choose the information to log. See Information for Standard Log Messages.
● If Use Transform Data is selected, the Log tab appears as a mapping panel so that you can build custom log messages. See Information for Custom Log Messages.
Information for Standard Log Messages
If the Use Transform Data option is not selected in the General tab, you use the Log tab to specify what top-level information from the mediation exchange to send to the log file.
Item Description
Log All Items Selects all sub-items on this tab and sends all information in the mediation flow context to the log.
Mediation Flow Properties The properties defined for the mediation flow. These properties can be defined on the Properties tab of the mediation flow.
You can select the parent item to send all mediation flow properties to the log, or you can select individual properties to send the properties to the log.
Mediation Flow Context Logs message context such as component and mediation flow name information, if the Mediation Flow Context option is set on the Advanced tab of the mediation operation Properties view.
See Working with Message Context Properties for information about the Mediation Flow Context option.
Message Context Logs all message context information. The message context includes information about the transport used for the message and the security context for the message.
You can optionally select either the transport or security information if you do not want the entire message context sent to the log.
Item Description
Message Data The content of the message.
Contributed Data Some mediation tasks, such as Transform or custom tasks, can contribute additional data items to the mediation exchange. Each contributed data item is named for the task that contributes the data.
You can send any contributed data item to the log.
Exchange Variable You can send exchange variable information to the log if you have specified an exchange variable on the mediation operation, and have set it using the Set Exchange Variable task.
Information for Custom Log Messages
If the Use Transform Data option is selected on the General tab, the Log tab is a mapping panel, where you can map mediation information to build custom log tasks.
Field Description
message Specify the data from the mediation exchange to log.
You can log any data available in the mapper—the message element allows logging of a simple message, and also allows mapping XML documents in a serialized text form.
If the Mediation Flow Context option is set on the Advanced tab of the mediation operation’s Properties view, you can map message context information to the message element. See Working with Message Context Properties for information about the Mediation Flow Context option.
messageID Optionally specify a message ID value to be included as part of the message that is being logged. The message ID consists of two elements, name and code. The name element is a string type and the code element is integer type.
At run-time, the value in the name element and the value in the code element are combined to form a message ID that has the syntax
name-code. For example, if the name element contains the value Mail and the code element contains the value 1000 then the message ID will be
Mail-1000. However, if you only provide the value for the name
element, a default value of 0 will be used for the code element. Similarly, if you only provide the value for code element, the default value for the name element will be AMSB.LogTask.
role Optionally specify a logging-level role for run-time.
Values can be info, warn, debug, or error. Values are not case-sensitive.
If you map to this role, the value you give its property overrides the Log Role setting in the General tab.