Copyright © Cloud Software Group, Inc. All Rights Reserved

SOAP Send Reply

Activity

The SOAP Send Reply activity sends a reply to an application that sent a SOAP request. This activity is primarily used in process definitions that implement web services. When a SOAP Event Source is used as the process starter, the SOAP Send Reply activity is used to send the reply to the request that starts the process instance.

This activity cannot be used if the SOAP request is one way.

Configuration

The Configuration tab has the following fields.

Field	Global Var?	Description
Name	No	The name to appear as the label for the activity in the process definition.
Description	No	Short description of the activity.
Reply To	No	The SOAP Event Source process starter that received the request.

Transport

The Transport tab has the following fields.

Field	Global Var?	Description
JMS Transport
Delivery Mode	No	The delivery mode of the message. Can be one of the following: • PERSISTENT: signifies the messages are stored and forwarded. • NON-PERSISTENT: messages are not stored and may be lost due to failures in transmission. • TIBCO EMS Reliable : this mode is only available when using TIBCO Enterprise Message Service. See the TIBCO Enterprise Message Service documentation for more information about this mode.
JMS Application Properties	No	Any application-specific message properties that are part of the message. This is specified by the JMS Application Properties shared configuration resource.

Input

See TIBCO ActiveMatrix BusinessWorks Process Design for more information about mapping and transforming input data.

The input for the activity is the following.

Input Item	Datatype	Description
outputMessage or <operationName>		The output schema of the operation for the selected SOAP request. Each of the schema elements are available in this dialog for mapping.
Header.<headerPart>	complex	Headers can contain multiple parts. The headers element contains all header parts required in a SOAP reply. These parts are specified on the Output Headers tab of the SOAP Event Source activity. The header parts are stored in an element named Header.<partName> where <schema-name> is the name of the schema specified on the Output Headers tab. Each Header.<partName> element also contains an item named @mustUnderstand. This boolean value is set to true in the outgoing reply if you require that the client must understand the header part.
mimeEnvelopeElement	complex	This element contains the reply message attachments when mime attachments are used. This element contains a repeating element named mimePart that contains each mime attachment.
_configData	complex	This element is available only for a JMS transport. Specifies the values to use to override transport-specific configuration values, if desired. The content of the _configData element depends upon the type of transport used.

Output

The activity has no output.

Error Output

The Error Output tab lists the possible exceptions that can be thrown by this activity. See TIBCO ActiveMatrix BusinessWorks Error Codes for more information about error codes and corrective action to take.

Exception	Thrown When...
HTTP Transport
ServerException	An error occurred and the reply could not be sent to the client.
JMS Transport
JMSMessageCreateException	The JMS message could not be created.
JMSSessionCreateException	The JMS session could not be created.
JMSSendException	The JMS send operation failed.

Copyright © Cloud Software Group, Inc. All Rights Reserved