WebSphere Message Brokers
File: ac04730_
Writer: Terry Cowling

Reference topic

This build: July 31, 2007 21:17:35

Warehouse node

Purpose

Use the Warehouse node to interact with a database in the specified ODBC data source. The Warehouse node is a specialized form of the Database node that stores the entire message, parts of the message, or both, in a table within the database. You define what is stored by creating mappings that use the data from the input message to identify the action that is required.

You can use the Warehouse node:

  • To maintain an audit trail of messages that are passing through the broker
  • For offline or batch processing of messages that have passed through the broker (data mining)
  • As a source from which to reprocess selected messages in the broker

Use standard database query and mining techniques to retrieve messages that you have stored in the warehouse. (No explicit support is provided by WebSphere Message Broker.)

You must have created or identified the following items:

  • Input data in the form of a message set and message
  • An ODBC connection to the database
  • A database and database table to store the message
  • At least two columns in the table: one for the binary object (the message), and one for the timestamp

The Warehouse node is represented in the workbench by the following icon:

Warehouse node icon

Using this node in a message flow

When you use the Warehouse node, you can choose to store the following elements in the database that is associated with the node:
  • The entire message, optionally with an associated timestamp. The message is stored as a binary object, with the timestamp in a separate column. There are two advantages to this option:
    • You do not need to decide beforehand how you will use the warehoused data; because you have stored it all, you can retrieve all the data and apply data mining tools to it later.
    • You do not need to define a specific database schema for every type of message that might pass through the broker. In a complex system, many different message types might be processed, and the overhead of defining a unique schema for each message type can become prohibitive. You can precede each Warehouse node with a Compute node that converts each message into a canonical warehouse format with a common schema, or you can store the whole message as a binary object.
  • Selected parts of the message, optionally with an associated timestamp, which requires a defined database schema for that message type. The message is mapped to true type so, for example, a character string in the message is stored as a character string in the database.

Configuring the Warehouse node

When you have put an instance of the Warehouse node into a message flow, you can configure it. To display its properties, right-click the node and click Properties. (If you double-click a Warehouse node, you open the New Message Map dialog box.)

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 Warehouse node as follows:

  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. Specify in Data Source the name by which the appropriate database is known on the system on which this message flow is to execute. The broker connects to this database with user ID and password information that you have specified on the mqsicreatebroker, mqsichangebroker, or mqsisetdbparms command.

      z/OS platform On z/OS systems, the broker uses the broker started task ID, or the user ID and password that were specified on the mqsisetdbparms command JCL, BIPSDBP in the customization data set <hlq>.SBIPPROC.

    2. In Field Mapping, identify the mapping routine that is to be executed in this node. By default, the name that is assigned to the mapping routine is identical to the name of the mappings file in which the routine is defined, and the default name for the file is the name of the message flow concatenated with the name of the node when you include it in the message flow (for example, MFlow1_Warehouse.mfmap for the first Warehouse node in message flow MFlow1). You cannot specify a value that includes spaces.

      If you click Browse next to this entry field, a dialog box is displayed that lists all available mapping routines that can be accessed by this node. Select the routine that you want and click OK; the routine name is set in Field Mapping.

      To work with the mapping routine that is associated with this node, double-click the node, or right-click the node and select Open Mappings. If the mapping routine does not exist, it is created for you with the default name in the default file. If the file exists already, you can also open file <flow_name>_<node_name>.mfmap in the Broker Development view.

      The content of the mapping routine determines what is stored in the database, and in what format. You can, for example, store all or just a part of each message. You can also store the data as binary data, or store each field in the same format as it is in the message (for example, a character field in the message is stored as character in the database).

      A mapping routine is specific to the type of node with which it is associated; you cannot use a mapping routine that you have developed for a Warehouse node with any other node that uses mappings (for example, a DataInsert node). If you create a mapping routine, you cannot call it from any other mapping routine, although you can call it from an ESQL routine.

      For more information about working with mapping files, and defining their content, see Developing message mappings.

    3. Select the Transaction setting from the drop-down menu:
      • If you select Automatic (the default), the message flow, of which the Warehouse node is a part, is committed if it is successful; that is, the actions that you define in the mappings are taken and the message continues through the message flow. If the message flow fails, it is rolled back. Therefore, choosing Automatic means that the ability to commit or roll back the action of the Warehouse node on the database depends on the success or failure of the entire message flow.
      • If you select Commit, any uncommitted actions that are taken in this message flow are committed on the database that is connected to this node, irrespective of the success or failure of the message flow as a whole. The changes to the database are committed even if the message flow itself fails.
    4. For database warning messages to be treated as errors, and the node to propagate the output message to the Failure terminal, select Treat Warnings as Errors. The check box is cleared initially.

      When you select the check box, the node handles all positive return codes from the database as errors and generates exceptions in the same way as it does for the negative, or more serious, errors.

      If you do not select the check box, the node treats warnings as normal return codes, and does not raise any exceptions. The most significant warning raised is not found, which can be handled as a normal return code safely in most circumstances.

    5. For the broker to generate an exception when a database error is detected, select Throw Exception on Database Errors. The check box is selected initially.

      If you clear the check box, you must handle the error in the message flow to ensure the integrity of the broker and the database; the error is ignored if you do not handle it through your own processing, because you have chosen not to invoke the default error handling by the broker; for example, you could connect the Failure terminal to an error processing subroutine.

Terminals and properties

The Terminals of the Warehouse node 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 input message is propagated if a failure is detected during the computation. If you have selected Treat Warnings as Errors, the node propagates the message to this terminal even if the processing completes successfully.
Out The output terminal that outputs the message following the execution of the database statement.

The following tables describe the node properties. The column headed M indicates whether the property is mandatory (marked with an asterisk 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 Description properties of the Warehouse node are described in the following table.

Property M C Default Description
Node name No No The node type 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 Warehouse node Basic properties are described in the following table.

Property M C Default Description
Data Source No Yes   The ODBC data source name of the database that contains the tables to which you refer in the mappings that are associated with this node (identified by the Field Mapping property).
Field Mapping Yes No Warehouse The name of the mapping routine that contains the statements that are to be executed against the database or the message tree. The routine is unique to this type of node.
Transaction Yes No Automatic The transaction mode for the node. Valid values are Automatic and Commit.
Treat Warnings as Errors Yes No Cleared If you select this check box, database SQL warnings are treated as errors.
Throw Exception on Database Error Yes No Selected If you select the check box, database errors cause the broker to throw an exception.
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:17:35

ac04730_ This topic's URL is: