### Configuring a Reply

A global Reply is generated automatically whenever you create a new Split-Join. The purpose of the global Reply is to send a response back to the invoking ALSB message flow. However, you may also create a local Reply to an Error Handler. Configuring the Reply can include the following tasks:

- View the Operation
- Define the Reply Variable
- Add General Information

Related Topics

- Split-Join Properties View - Reply Page

#### Viewing the Operation

The operation is based upon the initial WSDL selection for the overall Split-Join. It is displayed in the Properties view for reference.

#### Defining the Reply Variable

The Reply can either send a Response or a Fault back to the client depending on how you configure the variable. The Fault options available vary depending upon whether the Reply is global or local.

- A global Reply (that is, a Reply at the end of a Split-Join) can never have a SOAP Fault but can have a WSDL Fault. This is why the SOAP Fault option is always disabled.
- A local Reply (that is, a Reply attached to an Error Handler) can have either a WSDL Fault or a SOAP Fault. WSDL Faults will be available only if they were defined in the WSDL upon which the Split-Join is based. The SOAP Fault option will always be available provided one has been previously defined in the Error Handler.

Note: | Switching back and forth between the Response and Fault buttons will clear either configuration. For instance, if you have previously selected "Propagate SOAP Fault" for Fault configuration and you then switch to the "Response" configuration, "Propagate SOAP Fault" will be deselected.

Given the available options as outlined above, select either a Response or a Fault for your Reply Variable.

If you select Response, you must define the Message Variable the Response will be assigned to. This can be done in two ways:

1. Select a pre-existing variable from the Message Variable menu.
2. Create a new Message Variable (following steps).

Note: | If there are no available Message Variables associated with the previously chosen operation, you must create a new Message Variable.

To create a new Message Variable, select Create Message Variable from the Message Variable menu. The Create Message Variable Dialog appears:

1. Provide a name for the variable.
2. Click OK.

Note that Message Type Namespace and Message Type are displayed automatically in the Properties view once the variable is defined.

If you select Fault, you must specify either a WSDL Fault or propagate a SOAP Fault.

Note: | In some circumstances, no Faults or only a SOAP Fault will be available. See previous notes.

If you select a WSDL Fault, you must specify the Fault by name and define the Message Variable that it will be assigned to.

1. Select WSDL Fault Name and choose a name from those available.

Note: | There may only be one name available in which case no choice is necessary.

2. Define a Message Variable. This can be done in two ways:

1. Select a pre-existing variable from the Message Variable menu.
2. Create a new Message Variable (following steps).

Note: | If there are no available Message Variables associated with the previously chosen operation, you must create a new Message Variable.

To create a new Message Variable, select "Create Message Variable" from the Message Variable menu. The Create Message Variable Dialog opens:

1. Provide a name for the variable.
2. Click OK.

Note that Message Type Namespace and Message Type are displayed automatically on the properties page once a variable is defined.

If you select Propagate SOAP Fault, the SOAP Fault specified in the parent Error Handler will automatically be propagated in the Reply. There is nothing else to be configured

#### Adding General Information

General information is useful for making a node more legible. It includes the ability to add a unique identifier, or Label, to the node and to supplement it with notes, or Documentation. General information is optional.

1. To add a Label to a node, open the Properties view and enter a unique, identifying string in the Label field. The Label that you enter appears underneath the node in the Canvas area. Alternatively, you can simply double-click the string under the icon and edit.
2. To add Documentation to a node, open the Properties view and enter any notes that you think are important in the Documentation field.