Web Service Sender

This destination connector connects to a SOAP endpoint via JAX-WS and invokes a defined operation. When configuring this connector you can automatically fetch the WSDL from the remote server, and all the services / endpoints / operations will be filled out and modifiable from drop-down menus. Automatic generation of a sample SOAP envelope is supported too. Custom headers and MTOM attachments can be added to each request as well.

Supported property groups:

Destination Settings

Item	Name	Default Value	Description
A	WSDL URL		The URL to the WSDL describing the web service and available operations. Select Get Operations after entering the WSDL to automatically fill out the Service, Port, Location URI, and available Operations.
B	Service		The service name for the WSDL defined above. This field is filled in automatically when the Get Operations button is selected and does not usually need to be changed, unless multiple services are defined in the WSDL.
C	Port / Endpoint		The port / endpoint name for the service defined above. This field is filled in automatically when the Get Operations button is selected and does not usually need to be changed, unless multiple endpoints are defined for the currently selected service in the WSDL.
D	Location URI		The dispatch location for the port / endpoint defined above. This field is filled in automatically when the Get Operations button is selected and does not usually need to be changed. If left blank, the default URI defined in the WSDL will be used.
E	Socket Timeout (ms)	30000	Sets the connection and socket timeout (SO_TIMEOUT) in milliseconds to be used when invoking the web service. A timeout value of zero is interpreted as an infinite timeout.
F	Authentication	No	Turning on authentication uses a username and password to get the WSDL, if necessary, and uses the username and password binding provider properties when calling the web service.
G	Username		The username used to get the WSDL and call the web service.
H	Password		The password used to get the WSDL and call the web service.
I	Invocation Type	Two-Way	Determines how to invoke the operation selected below. Two-Way: Invoke the operation using the standard two-way invocation function. This will wait for some response or acknowledgement to be returned. One-Way: Invoke the operation using the one-way invocation function. This will not wait for any response, and should only be used if the operation is defined as a one-way operation.
J	Operation		The web service operation to be called. This is used to generate the envelope along with the Generate Envelope button.
K	SOAP Action		The SOAPAction HTTP request header field can be used to indicate the intent of the SOAP HTTP request. This field is optional for most web services, and may be auto-populated when you select an operation.
L	SOAP Envelope		The actual SOAP envelope to send to the remote web service. Use the Generate Envelope button above to generate a sample skeleton XML document that you can then fill out using Velocity Variable Replacement. For more complex schemas, this button may produce an incomplete SOAP envelope. Please refer to your vendors to ensure you're sending the correct SOAP envelopes in your outgoing messages. Note: This is an XML SOAP document, so any variables used here may need to be properly entity-encoded. You can do this by dragging the XML Entity Encoder over from the Destination Mappings list first, and then dragging the map variable inside the "XmlUtil.encode()" function call.
M	Headers		Use Table: The table below will be used to populate headers. Use Map: The Java map specified by the following variable will be used to populate headers. The map must have String keys and either String or List<String> values. When using the User Table option above, entries in this table will be added to the request as HTTP headers. Multiple headers with the same name are supported.
N	Use MTOM	No	Enables MTOM on the SOAP Binding. If enabled, attachments can be added to the table below and referenced from within the envelope.
O	Attachments		Use Table: The table below will be used to populate attachments. Use List: The Java list specified by the following variable will be used to populate attachments. The List must have AttachmentEntry values. The AttachmentEntry class is available in JavaScript scripts and is documented in The User API (Javadoc). When using the Use Table option above, entries in this table will be added as MTOM attachments along with the request. The following columns are configurable: ID: A unique ID for the attachment which can be referenced from within the SOAP envelope. Content: The Base64-encoded content of the attachment. You can also use a message attachment replacement token here. MIME Type: The MIME type of the attachment (e.g. "image/png").

Web Service Sender

Supported property groups:

Destination Settings

Item	Name	Default Value	Description
A	WSDL URL		The URL to the WSDL describing the web service and available operations. Select Get Operations after entering the WSDL to automatically fill out the Service, Port, Location URI, and available Operations.
B	Service		The service name for the WSDL defined above. This field is filled in automatically when the Get Operations button is selected and does not usually need to be changed, unless multiple services are defined in the WSDL.
C	Port / Endpoint		The port / endpoint name for the service defined above. This field is filled in automatically when the Get Operations button is selected and does not usually need to be changed, unless multiple endpoints are defined for the currently selected service in the WSDL.
D	Location URI		The dispatch location for the port / endpoint defined above. This field is filled in automatically when the Get Operations button is selected and does not usually need to be changed. If left blank, the default URI defined in the WSDL will be used.
E	Socket Timeout (ms)	30000	Sets the connection and socket timeout (SO_TIMEOUT) in milliseconds to be used when invoking the web service. A timeout value of zero is interpreted as an infinite timeout.
F	Authentication	No	Turning on authentication uses a username and password to get the WSDL, if necessary, and uses the username and password binding provider properties when calling the web service.
G	Username		The username used to get the WSDL and call the web service.
H	Password		The password used to get the WSDL and call the web service.
I	Invocation Type	Two-Way	Determines how to invoke the operation selected below. Two-Way: Invoke the operation using the standard two-way invocation function. This will wait for some response or acknowledgement to be returned. One-Way: Invoke the operation using the one-way invocation function. This will not wait for any response, and should only be used if the operation is defined as a one-way operation.
J	Operation		The web service operation to be called. This is used to generate the envelope along with the Generate Envelope button.
K	SOAP Action		The SOAPAction HTTP request header field can be used to indicate the intent of the SOAP HTTP request. This field is optional for most web services, and may be auto-populated when you select an operation.
L	SOAP Envelope		The actual SOAP envelope to send to the remote web service. Use the Generate Envelope button above to generate a sample skeleton XML document that you can then fill out using Velocity Variable Replacement. For more complex schemas, this button may produce an incomplete SOAP envelope. Please refer to your vendors to ensure you're sending the correct SOAP envelopes in your outgoing messages. Note: This is an XML SOAP document, so any variables used here may need to be properly entity-encoded. You can do this by dragging the XML Entity Encoder over from the Destination Mappings list first, and then dragging the map variable inside the "XmlUtil.encode()" function call.
M	Headers		Use Table: The table below will be used to populate headers. Use Map: The Java map specified by the following variable will be used to populate headers. The map must have String keys and either String or List<String> values. When using the User Table option above, entries in this table will be added to the request as HTTP headers. Multiple headers with the same name are supported.
N	Use MTOM	No	Enables MTOM on the SOAP Binding. If enabled, attachments can be added to the table below and referenced from within the envelope.
O	Attachments		Use Table: The table below will be used to populate attachments. Use List: The Java list specified by the following variable will be used to populate attachments. The List must have AttachmentEntry values. The AttachmentEntry class is available in JavaScript scripts and is documented in The User API (Javadoc). When using the Use Table option above, entries in this table will be added as MTOM attachments along with the request. The following columns are configurable: ID: A unique ID for the attachment which can be referenced from within the SOAP envelope. Content: The Base64-encoded content of the attachment. You can also use a message attachment replacement token here. MIME Type: The MIME type of the attachment (e.g. "image/png").

Web Service Sender

Recommendations

SMTP Sender

DICOM Sender

JMS Sender

TCP Sender

HTTP Sender

File Writer

Web Service Sender

SMTP Sender

DICOM Sender

JMS Sender

TCP Sender

HTTP Sender

File Writer