IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Request nodes

If you want to make a request, in the middle of your flow, to an external system, and put the result into the message tree, use a request node.

MQGet node

Use an MQGet node to retrieve a message from a WebSphere® MQ queue, if you want to get the message later in the message flow.

HTTPRequest node

Use an HTTPRequest node if your message flow interacts with a web service after it has started.

FileRead node

Use the FileRead node to read a file from the middle of a message flow. The node can:

Read the entire contents of the file.
Read a single record.
Rename or delete the file without reading any data.

JMSReceive node

Use the JMSReceive node to consume or browse messages from a JMS queue in the middle of a message flow. The node can augment the input message with result data from the received message.

WebSphere Adapters nodes

Use the WebSphere Adapters nodes to interact with Enterprise Information Systems (EIS) such as SAP, Siebel, and PeopleSoft. The following request nodes are available:

SAPRequest node
SiebelRequest node
PeopleSoftRequest node
JDEdwardsRequest node
TwineballRequest node

SOAP nodes

Use the SOAP nodes to process client SOAP messages and to configure the message flow to behave like a SOAP web Services provider:

SOAPRequest
SOAPAsyncRequest
SOAPAsyncResponse

WebSphere Service Registry and Repository (WSRR) nodes

Use the WebSphere Service Registry and Repository nodes to retrieve web services information:

Use the EndpointLookup node to retrieve service endpoint information held in the WebSphere Service Registry and Repository.
Use the RegistryLookup node to retrieve any type of entity held in the WebSphere Service Registry and Repository.

IMSRequest node

Use the IMSRequest node to send a request to run a transaction on a local or remote IBM® Information Management System (IMS™) system, and wait for a response. IMS Connect must be configured and running on the IMS system.

CORBARequest node

Use the CORBARequest node to call an external CORBA application over Internet Inter-Orb Protocol (IIOP). You can create a message flow that contains a CORBARequest node, which calls a CORBA server. The message flow uses an IDL file to call methods on a remote CORBA object. You can then give existing CORBA applications a new external interface; for example, a SOAP interface.

CICSRequest node

Use the CICSRequest node to call an external CICS® Transaction Server for z/OS® application over TCP/IP-based IP InterCommunications (IPIC) protocol. You can create a message flow that contains a CICSRequest node, which calls an application on CICS. By using the CICS support that is provided in IBM Integration Bus you can deploy CICS applications into a service-oriented architecture (SOA).

Database node

Use the Database node to interact with a database that is identified by the node properties. The Database node handles both predefined and self-defining messages. Use the ESQL editor to code ESQL functions to update database content from the message, insert new information into the database, and delete information from the database, using information in the message. Do not use the ESQL code that you develop for use in a Database node in any other type of node.

This node provides a flexible interface with a wide range of functions. It also has properties that you can use to control the way in which the interaction participates in transactions.

You can control the way in which the database is accessed by this node by specifying user and password information for the data source that you specify in the node properties. Use the mqsisetdbparms command to initialize and maintain these values.

You can update only databases from this node; you cannot update message content. If you want to update message content, use the Compute or Mapping node.

DatabaseRetrieve node

Use the DatabaseRetrieve node to ensure that information in a message is up to date. Use the node to modify a message using information from a database. For example, you can add information to a message using a key, such as an account number, that is contained in a message. Use the DatabaseRetrieve node to implement message routing with minimal programming logic. For more advanced routing scenarios, use a Compute node or a JavaCompute node.

SCARequest, SCAAsyncRequest, and SCAAsyncResponse nodes

The SCARequest node is used to send a request to WebSphere Process Server. The node is configured using a Broker SCA Definition (.outsca) file; depending on the contents of the .outsca file, requests are either:
- Two-way, synchronous; the node sends the request, then blocks until it receives a response, or the timeout period is exceeded.
- One-way; the node sends a request only.
The SCAAsyncRequest and SCAAsyncResponse nodes are used to construct a pair of message flows that call a WebSphere Process Server service component asynchronously.
The SCAAsyncRequest node sends an SCA outbound request to a service component that runs in WebSphere Process Server.

The SCAAsyncResponse node receives the response from a business process that is running in WebSphere Process Server and to which the previous asynchronous request was made. The SCAAsyncResponse node can be in the same message flow or in a separate message flow.

Calling a WebSphere Process Server service component asynchronously means that the SCAAsyncRequest node sends a request but does not wait for the associated response to be received, although it might wait for an acknowledgment of the request.

The nodes are used as a pair, and correlate responses and requests. See SCAAsyncRequest node and SCAAsyncResponse node.

ac34057_.htm |

Last updated Friday, 21 July 2017