You can dynamically override values in the local environment in the same way as setting values in other elements of a message.
Other local environment overrides are available for WS-Addressing. See WS-Addressing with the SOAPRequest node.
Setting | Description |
---|---|
Operation | Overrides the Operation property
on the node. For example:
|
TransportType | Overrides the Transport property
on the node to switch transport. For example, if the node is configured
to use the JMS transport, use the following to switch to HTTP transport:
To
switch to JMS transport:
This
overrides the request and response transport for this message. |
UserContext | You can store BLOB context data in the following
location in the local environment. The SOAPAsyncResponse node can
later retrieve this data.
Data
stored in the UserContext must be in BLOB format. This field is included
in the message bitstream, and therefore increases the message size.This setting applies only to the SOAPAsyncRequest node and is ignored by a SOAPRequest node. |
Setting | Description |
---|---|
Compression | Overrides the Use compression property
on the node. For example:
To
set a minimum size (in bytes) at which compression is applied, use
the following override:
|
Enable CRL checking | Overrides the Enable
Certificate Revocation List checking property on the node.
For example:
|
HTTPVersion | Overrides the HTTPVersion.
For example:
|
Method | Overrides the Method. For example:
|
ProxyConnectHeaders | Specifies
additional headers that are used if the outbound request is an SSL
connection through a proxy. These additional headers are sent with
the initial CONNECT request to the proxy. For example, you can send
proxy authentication information to a proxy server when you are using
SSL. You can send multiple headers but each one must be separated
by a carriage return and a line feed (ASCII 0x0D 0x0A), in accordance
with RFC2616; for example:
This setting is
used only if the request is an SSL request through a proxy server.
To send proxy authentication information for a non-SSL request, specify
the individual headers in the HTTPRequestHeader folder, as shown in
the following example:
|
ProxyURL | Overrides the HTTP(S)
proxy location property on the node. For example:
|
RequestURI | Overrides the RequestURI, which
is the path after the URL and port. For example:
|
SSL authentication alias | Overrides the SSL
authentication alias for the client-side of a SOAP connection
on the node. For example:
|
SSLCiphers | Overrides the Allowed
SSL Ciphers (if using SSL) property on the node. For example:
|
SSLProtocol | Overrides the SSLProtocol property on the node. For example:
Valid values are: SSL, SSLv3, TLS, TLSv1, TLSv1.1, TLSv1.2, SSL_TLS, and SSL_TLSv2 |
Timeout | Overrides the Request
timeout (in seconds) property on the node. For example:
|
TimeoutMillis | Overrides the Request
timeout (in seconds) property on the node. For example:
This
property defines the timeout in milliseconds. The value of TimeoutMillis
overrides the value for Timeout if both values are set. |
WebServiceURL | Overrides the Web
service URL property on the node. For example:
|
ServicePrincipalName | Specifies the Service Principal Name (SPN) to
use when the broker negotiates
the Kerberos security protocol. For example:
|
You can set the following JMS properties in the SOAPRequest node under LocalEnvironment.Destination.SOAP.Request.Transport.JMS. These properties apply only when using JMS transport. You can switch between HTTP and JMS transport using the TransportType override, or the WS-Addressing To field; see WS-Addressing information in the local environment.
Some JMS local environment overrides for the SOAPRequest node have equivalent properties in the JMSTransport header. If you specify a local environment override, it takes precedence over any equivalent property set in the JMSTransport header.
Setting | Description |
---|---|
BindingsLocation | Overrides the JNDI
URL bindings location property on the node. For example:
|
ConnectionFactoryName | Overrides the Connection
factory name property on the node. For example:
|
ContextParameters | Specify JNDI context parameters in addition
to the JNDI context parameters defined on the node. You can define
specific JNDI context parameters, for example:
|
CorrelationID | Sets the request message CorrelID. For example:
|
CorrelationPattern | Sets the request message correlation pattern.
For example:
The allowed values are the integers 1 and 2:
|
DeliveryMode | Overrides the DeliveryMode property
on the node. For example:
Allowed values for this property are PERSISTENT and NON_PERSISTENT. If the UriFormat is ibm, 1 and 0 are additional allowed values
for DeliveryMode. |
Destination | Overrides the Destination property
on the node. For example:
|
DestinationURI | You can override multiple JMS properties at
the same time in the local environment using the DestinationURI setting.
Properties that you set in this way can be overridden by setting local
environment overrides for individual JMS properties as shown in the
following tables.
This local environment override can
be set with either a W3C-style or IBM-style URI format. For more information,
see WSDL URI formats for JMS. |
Expiration | Overrides the Expiration property
on the node. This property is specified in milliseconds. For example,
to set an expiration of 100 milliseconds:
|
InitialContextFactory | Overrides the Initial
context factory property on the node. For example:
|
MessagePriority | Overrides the MessagePriority property
on the node. For example:
|
MessageType | Overrides the MessageType property
on the node. For example:
Allowed values for this property are textand bytes. |
ProviderName | Overrides the JMS
provider name property on the node. For example:
|
ReplyToDestination | Overrides the ReplyToDestination property
on the node. For example:
|
TargetService | Overrides the TargetService property
on the node. For example:
|
Timeout | Overrides the Timeout property
on the node. This value is specified in seconds. For example, to set
a timeout value of 30 seconds:
|
TransactionMode | Overrides the Transaction
mode property on the node. For example:
Allowable
values for this property are Yes, No and ForceLocal.
|
UriFormat | Overrides the UriFormat property
on the node. For example:
Allowable values for this property are w3c and ibm. |
UserProperties | Specify user context parameters in addition
to the user context parameters defined on the node. You can define
specific user context parameters, for example:
|
Setting | Description |
---|---|
OneWay | In gateway mode, instructs the node that the outbound message is a one-way
message and that no reply message is expected. For
example:
If the message is sent over the HTTP transport, the node waits for an acknowledgment HTTP 202 response message from the remote server. If the message is sent over the JMS transport, no response is expected, the outbound message has no Reply-To queue, and the node does not wait for a response. For more information, see One-way messages in Gateway mode. |