You can dynamically override set 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 SOAPReply node.
Setting | Description |
---|---|
HTTPVersion | Overrides the HTTPVersion. For example:
|
Method | Overrides the reply message 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 reply message HTTP(S) proxy location. For example:
|
RequestURI | Overrides the reply message RequestURI, which is the path after the URL and port. For example:
|
SSLCiphers | Overrides the reply message Allowed SSL Ciphers (if using SSL). For example:
|
SSLProtocol | Overrides the reply message SSLProtocol. For example:
Valid values are SSL, SSLv3, and TLS. |
Timeout | Overrides the reply message Request timeout (in seconds). For example:
|
WebServiceURL | Overrides the reply message Web service URL. For example:
|
You can set the following certificate revocation list (CRL) property in the SOAPReply node under LocalEnvironment.Destination.SOAP.Request.Transport.
Setting | Description |
---|---|
EnableCRLCheck | Sets CRL checking on (TRUE)
or off (FALSE) . For example:
|
Setting | Description |
---|---|
BindingsLocation | Overrides the reply message JNDI URL bindings location. For
example:
|
ConnectionFactoryName | Overrides the reply message Connection factory name. For example:
|
ContextParameters | Overrides the reply message JNDI context parameters. You can
override specific JNDI context parameters, for example:
|
CorrelationID | Sets the reply message CorrelID. For example:
|
Destination | Overrides the reply message Destination. For example:
|
DeliveryMode | Overrides the reply message DeliveryMode. 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. |
Expiration | Overrides the reply message Expiration. This property is specified
in milliseconds. For example, to set an expiration of 100 milliseconds:
|
InitialContextFactory | Overrides the reply message Initial context factory. For example:
|
MessagePriority | Overrides the reply message MessagePriority. For example:
|
MessageType | Overrides the reply message MessageType. For example:
Allowed values for this property are text and bytes. |
ProviderName | Overrides the reply message JMS provider name. For example:
|
TransactionMode | Overrides the Transaction
mode property on the node. For example:
Allowable
values for this property are Yes, No and ForceLocal.
|
UriFormat | Overrides the reply message UriFormat. For example:
Allowable values for this property are w3c and ibm. |
UserProperties | Overrides the User
Context Parameters on the node. You can override specific
user context parameters, for example:
|
Setting | Description |
---|---|
OneWay | Instructs the node that the inbound message
was a one-way message. The node resources are cleared because no reply
message is needed. For example:
Additionally,
if the inbound message used HTTP transport, the node sends an acknowledgment
HTTP 202 message. For more information, see One-way messages in Gateway mode. |