HTTPRequest node

Use the HTTPRequest node to interact with a Web service.

This topic contains the following sections:

Purpose

The HTTPRequest node interacts with a Web service, using all or part of the input message as the request that is sent to that service. You can also configure the node to create a new output message from the contents of the input message, augmented by the contents of the Web service response, before you propagate the message to subsequent nodes in the message flow.

Depending on the configuration, this node constructs an HTTP or an HTTP over SSL (HTTPS) request from the specified contents of the input message, and sends this request to the Web service. The node receives the response from the Web service, and parses the response for inclusion in the output tree. The node generates HTTP headers if these are required by your configuration.

You can use this node in a message flow that does or does not contain an HTTPInput or HTTPReply node.

The HTTPRequest node handles messages in the following message domains:

  • MRM
  • XML
  • XMLNS
  • XMLNSC
  • JMSMap
  • JMSStream
  • MIME
  • BLOB
  • IDOC

The HTTPRequest node is contained in the HTTP drawer of the palette, and is represented in the workbench by the following icon:

HTTPRequest node icon

Using the HTTPRequest node to issue a request to a Web service

An HTTP request has two parts:
  1. The URL of a service.
  2. A stream of data that the remote server processes, then sends back a response, which is often a SOAP or other Web service message in XML.

The URL is of the format http://<address>[:port]/<function>; for example, http://localhost:7080/request. This URL can be specified statically in the HTTPRequest node parameters as a field in the message itself, or as a field in the LocalEnvironment. The data to be sent to the Web service can be the whole, or a portion of, the message tree, as specified in the HTTPRequest node properties.

The data must be in CCSID 1208 format for most requests. The reply can replace the input message, or be inserted into the message tree; the location is specified in the HTTPRequest node parameters. The domain for the reply is XMLNS. If the request is successful, the HTTPResponse is inserted into the front of the message tree, the reply placed in the specified location in the tree, and the request propagated to the Out terminal. If the HTTPRequest node is not able to issue the request, an ExceptionList is inserted into the message tree and the tree is propagated to the Failure terminal.

If the request is sent successfully by the HTTPRequest node, but the Web service is not successful, the HTTPResponse is inserted into the message tree, and propagated to the Error terminal. The error message location parameter on the HTTPRequest node specifies where in the tree the response is placed, for example OutputRoot.XMLNS.error. You might need to use a Compute node to cast this response to an appropriate code page to be able to display the data, for example:
Set OutputRoot.XMLNS.error850 = CAST(InputRoot.XMLNS.error.BLOB as CHAR CCSID 850);
For information about HTTP, see Hypertext Transfer Protocol - HTTP/1.1. For more information about HTTP return codes, see HTTP Response codes.

You can specify a timeout interval, so that if the request takes longer than the specified duration, the request is propagated to the Error terminal with an appropriate message. For each request that the HTTPRequest node processes, it opens a connection, and then closes it when the response is returned. If the timeout interval is specified, the socket is closed after the interval. This closure ensures that a request gets only the correct response, and any response data for a request that has timed out is discarded.

You can use the HTTP proxy to route a request through an intermediate site. You can run tools as a proxy to see the request and the response, and therefore debug your flows. The HTTP destination is as seen by the proxy; if you specify the HTTP destination of localhost, and the HTTP proxy is running on a different computer, the request is routed to the remote proxy computer, not the computer from which the original request was issued.

Using the HTTPRequest node in a message flow

The HTTPRequest node can be used in any message flow that needs to send an HTTP request. The most common example of this is a message flow that calls a Web service.

For more information about Web service applications, see Working with Web service applications.

Handling errors

The node interacts directly with an external service using TCP/IP; it can, therefore, experience the following types of error:

  • Errors that are generated by TCP/IP, for example no route to host or connection refused.

    If the node detects these errors, it generates an exception, populates the exception list with the error information that is received, and routes the input message unchanged to the Failure terminal.

  • Errors that are returned by the Web server. These errors are represented by HTTP status codes that are outside the range 100 to 299. If the node detects these errors, it routes the reply to the Error terminal while following the properties specified on the Error tab.

    The reply is produced as a BLOB message because the node cannot determine in what format the reply will be. If you have not configured this node to handle redirection, messages with a redirection status code (3xx) are also handled in the same way.

HTTP Response Codes

The HTTPRequest node treats the 100 series status codes as a 'continue' response, discards the current response, and waits for another response from the Web server.

The 200 series status codes are treated as success, the settings on the various tabs on the node determine the format of the output message that is generated. and the response is routed to the Out terminal of the node.

The 300 series status codes are for redirection. If the Follow HTTP(s) Redirection property is selected, the node does not resend the request to the new destination that is specified in the response that is received. If the Follow HTTP(s) Redirection property is not selected, the codes are treated as an error, as described in Using the HTTPRequest node to issue a request to a Web service. For more information about HTTP return codes, see HTTP Response codes.

The 400 and 500 series status codes are errors, and are treated as described in Using the HTTPRequest node to issue a request to a Web service. For more information about HTTP return codes, see HTTP Response codes.

Manipulating headers

If you select Replace input message with web-service response or Replace input with error, the header for the input message (the header that belongs to the message when it arrives at the In terminal of the HTTPRequest node) is not propagated with the message that leaves the HTTPRequest node. However, if one of the properties that specifies a location in the message tree is specified, the input message's headers are propagated.

The HTTPResponse header, which contains the headers that are returned by the remote Web service, is the first header in the message (after Properties) that is propagated from the node. This action is taken regardless of the options that are chosen. Therefore, for the reply from the HTTPRequest node to be put to a WebSphere® MQ queue, manipulate the headers so that an MQMD is the first header (after Properties).

If you are replacing the input message with a response, you can copy the input message's MQMD to the Environment tree before the HTTPRequest node, and then copy it back into the message tree after the HTTPRequest node. If you are specifying a location for the response, in order to maintain existing input message headers, you must move or remove the HTTP Response header so that the MQMD is the first header.

The following example contains ESQL that removes the HTTPHeader:
SET OutputRoot = InputRoot;
SET OutputRoot.HTTPResponseHeader = NULL; 
The following example contains ESQL for moving the HTTPHeader, and therefore preserving the information that it provides:
SET OutputRoot = InputRoot;
DECLARE HTTPHeaderRef REFERENCE TO OutputRoot.HTTPResponseHeader;
DETACH HTTPHeaderRef;
ATTACH HTTPHeaderRef TO OutputRoot.MQMD AS NEXTSIBLING;

Configuring the HTTPRequest node

When you have put an instance of the HTTPRequest node into a message flow, you can configure the node; see Configuring a message flow node. The properties of the node are displayed in the Properties view. To display the properties of the node in the Properties dialog, either double-click the node, or right-click the node and click Properties.

All mandatory properties for which you must enter a value (those that do not have a default value defined) are marked with an asterisk.

Configure the HTTPRequest node:

  1. Optional: On the Description tab, enter a Short description, a Long description, or both. You can also rename the node on this tab.
  2. On the Basic tab:
    1. The HTTPRequest node determines the URL for the Web service to which it sends a request. Set one of the following three options; the node checks these in the order shown (that is, the first always overrides the second, the second overrides the third):
      1. X-Original-HTTP-URL in the HTTPRequest header in the input message
      2. LocalEnvironment.Destination.HTTP.RequestURL in the input message
      3. The Web service URL property

      The first two options provide dynamic methods to set a URL for each input message as it passes through the message flow. To use either of these options, include a Compute node in the message flow, before the HTTPRequest node, to create and initialize the required value.

      The third option provides a value that is fixed for every message that is received in this node. Set this property to contain a default setting that is used if the other fields have not been created, or contain a null value. If either field contains a value, the setting of this property is ignored. The Web service URL property must contain a valid URL or the deployment will fail. Ensure that the value that you set in X-Original-HTTP-URL or the LocalEnvironment.Destination.HTTP.RequestURL is also a valid URL; if it is not, the node uses the default setting from the Web service URL property.

      If a URL begins http://, the request node makes an HTTP request to the specified URL. If the URL begins https://, the request node makes an HTTP over SSL (HTTPS) request to the specified URL, using the parameters that are specified on the SSL tab for the node.

    2. Set the value of the Request timeout (sec) property, which is the length of time, in seconds, that the node waits for a response from the Web service. If a response is received within this time, the reply is propagated through the Out terminal to the rest of the message flow. If a response is not received within this time, the input message is propagated through the Failure terminal, if it is connected. If the Failure terminal is not connected, and a response is not received in this time, an exception is generated.
  3. On the HTTP Settings tab:
    1. In HTTP(S) proxy location, set the location of the proxy server to which requests are sent.
    2. Select Follow HTTP(S) redirection to specify how the node handles Web service responses that contain an HTTP status code of 300 to 399:
      • If you select the check box, the node follows the redirection that is provided in the response, and reissues the Web service request to the new URL (included in the message content).
      • If you clear the check box, the node does not follow the redirection provided. The response message is propagated to the Error terminal.
    3. Select one of the options for the HTTP version property. Valid values are: 1.0 or 1.1.

      If you select the HTTP version property value 1.1, you can also select Enable HTTP/1.1 keep-alive.

    4. Start of changeSelect one of the options for the HTTP method property. Valid values are: POST, GET, PUT, DELETE, and HEAD.End of change
  4. On the SSL tab, if you want to use HTTP over SSL (HTTPS) requests, set the values for HTTPS requests:
    1. Specify the Protocol property that you want to use to make the request. Both ends of an SSL connection must agree on the protocol to use, so the chosen protocol must be one that the remote server can accept. The following options are available:
      • SSL. This option is the default. This option tries to connect using the SSLv3 protocol first, but allows the handshake to fall back to the SSLv2 protocol where the SSLv2 protocol is supported by the underlying JSSE provider.
      • SSLv3. This option tries to connect with the SSLv3 protocol only. Fallback to SSLv2 is not allowed.
      • TLS. This option tries to connect with the TLS protocol only. Fallback to SSLv3 or SSLv2 is not allowed.
    2. Set the Allowed SSL ciphers property. Use this setting to specify a single cipher (such as SSL_RSA_FIPS_WITH_3DES_EDE_CBC_SHA) or a list of ciphers that are the only ones used by the connection. This set of ciphers must include one or more that are accepted by the remote server. A comma is used as a separator between the ciphers. The default value is an empty string, which enables the node to use any, or all, of the available ciphers during the SSL connection handshake. This method gives the greatest scope for making a successful SSL connection.
  5. On the Response Message Parsing tab, set values for the properties that describe the message domain, message set, message type, and message format that the node uses to determine how to parse the response message returned by the Web service. If an error message is returned by the Web service, the values of these properties are ignored, and the message is parsed by the BLOB parser.
    1. In Message domain, select the name of the parser that you are using from the list. Choose from the following options:
      • MRM
      • XML
      • XMLNS
      • XMLNSC
      • JMSMap
      • JMSStream
      • MIME
      • BLOB
      • IDOC
    2. If you are using the MRM or IDOC parser, select the relevant Message set from the list. This list is populated with available message sets when you select MRM or IDOC as the Message domain.

      Leave Message set blank for XML, XMLNS, XMLNSC, JMS, MIME, and BLOB parsers.

    3. If you are using the MRM parser, select the correct message from the list in Message type. This list is populated with messages that are defined in the Message set that you have selected.

      Leave Message type blank for XML, XMLNS, XMLNSC, JMS, MIME, BLOB, and IDOC parsers.

    4. If you are using the MRM or IDOC parser, select the format of the message from the list in Message format. This list includes all the physical formats that you have defined for this Message set.

      Leave Message format blank for XML, XMLNS, XMLNSC, JMS, MIME, and BLOB parsers.

  6. On the Parser Options tab, Parse timing is, by default, set to On Demand. This value causes validation to be delayed until it is parsed by partial parsing. If you change this value to Immediate, partial parsing is overridden and everything in the message is parsed and validated, except for those complex types with a composition of Choice or Message that cannot be resolved at the time. If you change this value to Complete, partial parsing is overridden and everything in the message is parsed and validated; complex types with a composition of Choice or Message that cannot be resolved at the time cause a validation failure.
  7. On the Error Handling tab, set values for the properties that determine how an error message returned by the Web service is handled:
    1. For the whole Web service error message to be propagated as the output message, leave Replace input with error selected (the default setting).

      For the Web service error message to be included in the output message with part of the input message content, clear Replace input with error and set the Error message location property. If you clear this property, the node copies the input message to the output message and writes the Web service error message over the output message content at the specified location (the input message itself is not modified).

    2. In the Error message location field, enter the start location (within the output message tree) at which the parsed elements from the Web service error message bit stream are stored. This property is required only if you have cleared Replace input with error.

      You can enter any valid ESQL field reference, including expressions within the reference and new field references (to create a new node in the message tree for the response). For example, enter:

      OutputRoot.XMLNSC.ABC.DEF
      or
      Environment.WSError

      If you select Replace input with error, this property is ignored.

  8. On the Advanced tab, set values for the Advanced properties that describe the structure and content of the Web service request and response:
    1. Specify the content of the request message that is sent to the Web service:
      • For the request message to be the whole input message body, leave Use whole input message as request selected (the default setting).

        For the request message to contain a subset of the input message, clear Use whole input message as request and set the Request message location in tree property.

      • In the Request message location in tree field, enter the start location from which the content of the input message tree is copied to the request message. This property is required only if you have cleared Use whole input message as request. The node creates a new request message and copies the specified parts of the input message (the input message itself is not modified).

        You can enter any valid ESQL field reference, including expressions within the reference. For example, enter:

        InputRoot.XMLNSC.ABC

        If you select Use whole input message as request, this property is ignored.

      When the appropriate message tree content is parsed to create a bit stream, the message properties (Message domain, Message set, Message type, and Message format) that are associated with the input message body and stored in the Properties folder are used.

    2. Specify the content of the output message that is propagated to the next node in the message flow:
      • For the whole Web service response message to be propagated as the output message, leave Replace input message with web-service response selected (the default setting).

        For the Web service response message to be included in the output message with part of the input message content, clear Replace input message with web-service response and set the Response message location in tree property. If you clear this property, the node copies the input message to the output message and writes the Web service response message over the output message content at the specified location (the input message itself is not modified).

      • In the Response message location in tree field, enter the start location (within the output message tree) at which the parsed elements from the Web service response message bit stream are stored. This property is required only if you have cleared Replace input message with web-service response.

        You can enter any valid ESQL field reference, including expressions within the reference, and including new field references (to create a new node in the message tree for the response). For example, enter:

        OutputRoot.XMLNSC.ABC.DEF
        or
        Environment.WSReply

        If you select Replace input message with web-service response, this property is ignored.

      When the response bit stream is parsed to create message tree contents, the message properties (Message domain, Message set, Message type, and Message format), that you have specified in the Response Message Parsing properties of the node, are used.

    3. For the node to generate an HTTPRequestHeader for the request message, leave Generate default HTTP headers from input selected (the default setting).

      If you do not want the node to generate an HTTPRequestHeader for the request message, clear Generate default HTTP headers from input. To control the contents of the HTTPRequestHeader that is included in the request message, include a Compute node that adds an HTTPRequestHeader to the input message before this HTTPRequest node in the message flow, and clear this check box.

      • If you have selected Generate default HTTP headers from input and the input message includes an HTTPRequestHeader, the HTTPRequest node extracts Web service headers from the input HTTPRequestHeader and adds any unique Web service headers, except Host (see the following table), that are present in an HTTPInputHeader, if one exists in the input message. (An HTTPInputHeader might be present if the input message has been received from a Web service by the HTTPInput node.)

        The HTTPRequest node also adds the Web service headers shown in the following table, with default values, if these are not present in the HTTPRequestHeader or the HTTPInputHeader.

        Header Default value
        SOAPAction "" (empty string)
        Content-Type text/xml; charset=utf-8
        Host The host name to which the request is to be sent.

        The HTTPRequest node also adds the optional header Content-Length with the correct calculated value, even if this value is not present in the HTTPRequestHeader or the HTTPInputHeader.

      • If you have selected Generate default HTTP headers from input and the input message does not include an HTTPRequestHeader, the HTTPRequest node extracts Web service headers, except Host, from the HTTPInputHeader (if it is present in the input message). The HTTPRequest node adds the required Web service headers with default values, if these values are not present in the HTTPInputHeader.
      • If you have cleared Generate default HTTP headers from input and the input message includes an HTTPRequestHeader, the node extracts all Web service headers present in the input HTTPRequestHeader. The node does not check for the presence of an HTTPInputHeader in the input message, and it does not add the required Web service headers if they are not supplied by the input HTTPRequestHeader.
      • If you have cleared Generate default HTTP headers from input and the input message does not include an HTTPRequestHeader, no Web service headers are generated. The HTTPRequest node does not check for the presence of an HTTPInputHeader in the input message and does not add any required Web service header. The request message is propagated to the Web service without an HTTPRequestHeader. This action typically causes an error to be generated by the Web service, unless the Web service is configured to handle the message contents.
  9. On the Validation tab, set Validation properties if you want the parser to validate the body of response messages against the Message set. (If a message is propagated to the Failure terminal of the node, it is not validated.) These properties do not cause the input message to be validated. It is expected that, if such validation is required, the validation has already been performed by the input node or a preceding validation node.

    For more details see Validating messages and Validation properties.

Connecting the output terminals to another node

Connect the Out, Error, or Failure terminal of this node to another node in this message flow to process the message further, to process errors, or to send the message to an additional destination. If you do not connect the Error terminal, the message is discarded. If you do not connect the Failure terminal, the broker provides default error processing, see Handling errors in message flows.

Terminals and properties

The HTTPRequest node terminals are described in the following table.

Terminal Description
In The input terminal that accepts a message for processing by the node.
Failure The output terminal to which the message is routed if a failure is detected during processing in the node.
Out The output terminal to which the message is routed if it represents successful completion of the Web service request, and if further processing is required within this message flow.
Error The output terminal to which messages that include an HTTP status code that is not in the range 200 through 299, including redirection codes (3xx) if you have not set the property Follow HTTP(s) redirection property, is routed.

The following tables describe the node properties. The column headed M indicates whether the property is mandatory (marked with an asterisk on the panel if you must enter a value when no default is defined); the column headed C indicates whether the property is configurable (you can change the value when you add the message flow to the broker archive file to deploy it).

The HTTPRequest node Description properties are described in the following table.

Property M C Default Description
Node name No No The node type, HTTPRequest The name of the node.
Short description No No   A brief description of the node.
Long description No No   Text that describes the purpose of the node in the message flow.

The HTTPRequest node Basic properties are described in the following table.

Property M C Default Description
Web service URL Yes Yes   The URL for the Web service. You must provide this in the form http://<hostname>[:<port>]/[<path>] where
  • http://<hostname> must be specified.
  • <port> has a default of 80. If you specify a value, you must include the : before the port number.
  • <path> has a default of /. If you specify a value, you must include the / before the path.
Request timeout (sec) Yes No 120 The time in seconds that the node waits for a response from the Web service. The valid range is 1 to (231)-1. You cannot enter a value that represents an unlimited wait.

The HTTPRequest node HTTP Settings properties are described in the following table.

Property M C Default Description
HTTP(S) proxy location No Yes   The proxy server to which requests are sent. This value must be in the form hostname:port.
Follow HTTP(S) redirection No No Cleared If you select the check box, redirections are followed. If you clear this check box, redirections are not followed.
HTTP version No Yes 1.0 The HTTP version to use for requests. Valid values are 1.0 and 1.1.
Enable HTTP/1.1 keep-alive No Yes Selected (if HTTP version is 1.1) Use HTTP/1.1 Keep-Alive.
HTTP method Start of changeNoEnd of change Start of changeNoEnd of change Start of changePOSTEnd of change Start of changeThe HTTP method. Valid values are POST, GET, PUT, DELETE, and HEAD. By default, the HTTPRequest node uses the HTTP POST method when it connects to the remote Web server. HEAD is used to determine whether a service is available - for example, by a network dispatcher trying to work out which servers are available - and sends back the correct headers (including content-length) but no body data. End of change

The HTTPRequest node SSL properties are described in the following table.

Property M C Default Description
Protocol No Yes SSL The SSL protocol to use when making an HTTPS request.
Allowed SSL ciphers No Yes   A comma-separated list of ciphers to use when making an SSL request. The default value of an empty string means use all available ciphers.

The HTTPRequest node Response Message Parsing properties are described in the following table.

Property M C Default Description
Message domain No No   The domain that will be used to parse the response message that is received from the Web service.
Message set No No   The name or identifier of the message set in which the response message is defined.
Message type No No   The name of the response message.
Message format No No   The name of the physical format of the response message.

The HTTPRequest node Parser Options properties are described in the following table.

Property M C Default Description
Parse timing No No On Demand This property controls when a response message is parsed. Valid values are On Demand, Immediate, and Complete.

For a full description of this property, see Parsing on demand.

Use XMLNSC compact parser for XMLNS domain No No Cleared This property controls whether the XMLNSC Compact Parser is used for messages in the XMLNS Domain. If you set this property, the response message data appears under XMLNSC in nodes that are connected to the output terminal when the input MQRFH2 header or Response Message Parsing properties Domain is XMLNS.
Retain mixed content No No Cleared This property controls whether the XMLNSC parser creates elements in the message tree when it encounters mixed text in a response message. If you select the check box, elements are created for mixed text. If you clear the check box, mixed text is ignored and no elements are created.
Retain comments No No Cleared This property controls whether the XMLNSC parser creates elements in the message tree when it encounters comments in a response message. If you select the check box, elements are created for comments. If you clear the check box, comments are ignored and no elements are created.
Retain processing instructions No No Cleared This property controls whether the XMLNSC parser creates elements in the message tree when it encounters processing instructions in a response message. If you select the check box, elements are created for processing instructions. If you clear the check box, processing instructions are ignored and no elements are created.

The HTTPRequest node Error Handling properties are described in the following table.

Property M C Default Description
Replace input with error No No Selected If you select this check box, the input message content is replaced by the error message content. If you clear this check box, you must specify Error message location.
Error message location Yes No OutputRoot The start location at which the parsed elements from the Web service error bit stream are stored. This property takes the form of an ESQL field reference.

The HTTPRequest node Advanced properties are described in the following table.

Property M C Default Description
Use whole input message as request No No Selected If you select this check box, the whole input message body is to be passed to the Web service. If you clear this check box, you must select Request message location in tree.
Request message location in tree Yes No InputRoot The start location from which the bit stream is created for sending to the Web service. This property takes the form of an ESQL field reference.
Replace input message with web-service response No No Selected If you select this check box, the Web service response message replaces the copy of the input message as the content of the output message that is created. If you clear this check box, you must select Response message location in tree.
Response message location in tree Yes No OutputRoot The start location at which the parsed elements from the Web service response bit stream are stored. This property takes the form of an ESQL field reference.
Generate default HTTP headers from input No No Selected If you select this check box, an HTTPRequestHeader is generated. If you clear this check box, a valid HTTPRequestHeader must exist in the input message.

The HTTPRequest node Validation properties are described in the following table.

For a full description of these properties see Validation properties.

Property M C Default Description
Validate No Yes None This property controls whether validation takes place. Valid values are None, Content and Value, Content, and Inherit.
Failure action No No Exception This property controls what happens if validation fails. You can set this property only if you set Validate to Content or Content and Value. Valid values are User Trace, Local Error Log, Exception, and Exception List.
Include all value constraints No No Selected This property cannot be edited. The default action, which is indicated by the check box being selected, is that basic value constraint checks are included in Content and Value validation.
Fix No No None This property cannot be edited.
Start of change

LocalEnvironment overrides

You can dynamically override set values in the LocalEnvironment in the same way as setting values in other elements of a message. The following values can be set under LocalEnvironment.Destination.HTTP.
Setting Description
RequestURL Overrides the Web service URL property on the node. For example:
SET OutputLocalEnvironment.Destination.HTTP.RequestURL = 'http://ibm.com/abc/';
Timeout Overrides the Request timeout (sec) property on the node. For example:
SET OutputLocalEnvironment.Destination.HTTP.Timeout = 42;
ProxyURL Overrides the HTTP(S) proxy location property on the node. For example:
SET OutputLocalEnvironment.Destination.HTTP.ProxyURL = 'my.proxy';
RequestLine.RequestURI Overrides the RequestURI, which is the path after the URL and port. For example:
SET OutputLocalEnvironment.Destination.HTTP.RequestLine.RequestURI = 
'/abc/def?x=y&g=h';
RequestLine.HTTPVersion Overrides the HTTP version property on the node. For example:
SET OutputLocalEnvironment.Destination.HTTP.RequestLine.HTTPVersion = 
'HTTP/1.1';
KeepAlive Overrides the Enable HTTP/1.1 keep-alive property on the node. For example:
SET OutputLocalEnvironment.Destination.HTTP.KeepAlive = TRUE;
RequestLine.Method Overrides the HTTP method property on the node. For example:
SET OutputLocalEnvironment.Destination.HTTP.RequestLine.Method = 'GET';
SSLProtocol Overrides the SSLProtocol. For example:
SET OutputLocalEnvironment.Destination.HTTP.SSLProtocol = 'TLS';

Valid values are: SSL, SSLv3, and TLS.

SSLCiphers Overrides the Allowed SSL Ciphers property on the node. For example:
SET OutputLocalEnvironment.Destination.HTTP.SSLCiphers = 
'SSL_RSA_FIPS_WITH_3DES_EDE_CBC_SHA';
ProxyConnectHeaders Start of changeSpecifies 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:
DECLARE CRLF CHAR CAST(X'0D0A' AS CHAR CCSID 1208);     
SET OutputLocalEnvironment.Destination.HTTP.ProxyConnectHeaders =
'Proxy-Authorization: Basic Zm5lcmJsZTpwYXNzd29yZA==' || CRLF || 
'Proxy-Connection: Keep-Alive' || CRLF;
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:
SET OutputRoot.HTTPRequestHeader."Proxy-Authorization" = 'Basic Zm5lcmJsZTpwYXNzd29yZA==';
SET OutputRoot.HTTPRequestHeader."Proxy-Connection" = 'Keep-Alive';
End of change
UseFolderMode Sets the UseFolderMode. Use for bitstream generation; for certain parsers this changes the output bitstream. For example:
SET OutputLocalEnvironment.Destination.HTTP.UseFolderMode = TRUE;

Working with WrittenDestination data

After the request has been made, the WrittenDestination folder in the LocalEnvironment is updated with the URI to which the request was sent. A WrittenDestination for an HTTPRequest node has the following format:
WrittenDestination = (
   HTTP  = (
      RequestURL = 'http://server:port/folder/page'
   )
)
End of change
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009.
Last updated : 2009-01-07 15:20:04

ac04595_