This topic contains the following sections:
If you include an HTTPInput node in a message flow, you must either include an HTTPReply node in the same flow, or pass the message to another flow that includes an HTTPReply node (for example, through an MQOutput node to a second flow that starts with an MQInput node). In the latter case, the request from, and reply to, the client are coordinated by the request identifier stored in the LocalEnvironment (described below).
The HTTPInput node handles messages in the following message domains:
When the HTTPInput node receives a message from a Web service client, it invokes the appropriate parsers to interpret the headers and the body of the message, and to create the message tree that is used internally by the message flow. The node creates a unique identifier for the input message and stores it as a binary array of 24 bytes in the LocalEnvironment tree at LocalEnvironment.Destination.HTTP.RequestIdentifer. This value is used by the HTTPReply node and must not be modified in any way.
HTTP messages are always non-persistent, and have no associated order.
If you include an output node in a message flow that starts with an HTTPInput node, it can be any of the supported output nodes (including user-defined output nodes). You can create a message flow that receives messages from Web service clients and generates messages for clients that use all supported transports to connect to the broker, because you can configure the message flow to request the broker to provide any conversion that is necessary.
If you create a message flow to use as a subflow, you cannot use a standard input node; you must use an instance of the Input node as the first node to create an in terminal for the subflow.
If your message flow does not receive Web service requests, you can choose one of these other input nodes:
The HTTPInput node is represented in the workbench by the following icon:
You can use this node in two different scenarios:
The Web service client generates a Web service request. This is directed to the HTTPInput node of a message flow running in the broker. You design the message flow to process the message in some way, and to generate a response that is in the format of a Web service response. The broker sends the response to the Web service client through the HTTPReply node of the message flow.
For example, you have Web service clients that interact with a Web service that provides specific information on a given subject (stock prices or exchange rates, for example). You replace this service with an inhouse database lookup solution, but want to make no changes to your client applications. You design a message flow including an HTTPInput node that receives requests from your clients. This node connects to a Compute node that retrieves the required information from the database and generates a new output message, in the form of a Web service response including this new data. The Compute node passes the message on to the HTTPReply node, which generates the response for the Web service client.
The Web service client generates a Web service request. This is directed to the HTTPInput node of a message flow running in the broker. You design the message flow to process the message in some way, and to interact with the Web service to which the client application believes it is connected. You include an HTTPRequest node in the message flow to send a request to the Web service and to receive the response. The message flow also generates a response to the client, based in full or in part on the response received in the HTTPRequest node, in the format of a Web service response. The broker sends the response to the Web service client through the HTTPReply node of the message flow.
For example, you have a client application that interacts with a Web service that sends information to another application requiring the information in another format. You design a new message flow that includes an HTTPInput node, an HTTPRequest node, and an HTTPReply node. The HTTPInput node receives the input from the Web service client, and passes the message to the HTTPRequest node, which interacts with the Web service.
When the response is received, the HTTPRequest node propagates the message to a Compute node, which creates an output message in legacy format from the content of the Web service response. The message flow ends with an MQOutput node, which delivers the transformed message to the legacy application, followed by an HTTPReply node that provides the appropriate response to the Web service client.
In a second example, your clients interact with a Web service, and you want to retain information about the requests to the Web service for audit purposes. You design a message flow that includes an HTTPInput node connected to a Warehouse node. The input message received from the Web service client is stored in the database, and the Warehouse node passes the message on to an HTTPRequest node, which interacts with the Web service. When the response is received, the HTTPRequest node propagates the response to the HTTPReply node, which generates the response for the Web service client.
When you have put an instance of the HTTPInput node into a message flow, you can configure it. Right-click the node in the editor view and click Properties. The node's basic properties are displayed in the properties dialog.
All mandatory properties for which you must enter a value (those that do not have a default value defined) are marked with an asterisk on the properties dialog.
Configure the HTTPInput node as follows:
Leave Message Set blank for XML, XMLNS, JMS, , and BLOB parsers.
Leave Message Type blank for XML, XMLNS, JMS, and BLOB parsers.
Leave Message Format blank for XML, XMLNS, JMS, and BLOB parsers.
Click Cancel to close the dialog and discard all the changes that you have made to the properties.
HTTPInput routes each message that it retrieves successfully to the out terminal. If message validation fails, the message is routed to the failure terminal; you can connect nodes to this terminal to handle this condition. If you have not connected the failure terminal, the message is discarded, the Maximum client wait time expires, and the TCP/IP listener returns an error to the client. The are no other situations in which the message is routed to the failure terminal.
If the message is caught by this node after an exception has been thrown further on in the message flow, the message is routed to the catch terminal. If you have not connected the catch terminal, the message is discarded, the Maximum client wait time expires, and the TCP/IP listener returns an error to the client.
The HTTPInput node terminals are described in the following table.
Terminal | Description |
---|---|
Failure | The output terminal to which the message is routed if an error occurs. |
Out | The output terminal to which the message is routed if it is successfully retrieved. |
Catch | The output terminal to which the message is routed if an exception is thrown downstream and caught by this node. |
The following tables describe the node properties; the column headed M indicates whether the property is mandatory (marked with an asterisk on the properties dialog 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 bar file to deploy it).
The HTTPInput node Basic properties are described in the following table.
Property | M | C | Default | Description |
---|---|---|---|---|
URL Selector | Yes | Yes | Identifies the location from where Web service requests are retrieved. If the URL that you want is http://<hostname>[:<port>]/[<path>], specify either /<path> or /<path fragment>/* where * is a wild card that you can use to mean match any. | |
Maximum Client Wait Time | Yes | No | 180 | How long the listener waits, in seconds, before sending an error message back to the client. The valid range is zero (which means an indefinite wait) to (231)-1. |
Fault Format | No | Yes | SOAP 1.1 | The property value can be SOAP
1.1, SOAP 1.2 or ![]() ![]() |
Use HTTPS | No | Yes | no | Identifies whether the node is to accept secure HTTP. |
The HTTPInput node Default 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 incoming message. | |
Message Set | No | No | The name or identifier of the message set in which the incoming message is defined. | |
Message Type | No | No | The name of the incoming message. | |
Message Format | No | No | The name of the physical format of the incoming message. |
The HTTPInput node Description properties are described in the following table.
Property | M | C | Default | Description |
---|---|---|---|---|
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. |
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac04565_ |