whole_message placeholder

The SQL statement action supports a whole_message placeholder that represents a whole message.

In the Database Outbound Protocol Properties dialog box, there is a Use cached pre-xlate message as whole message check box. This is used to define whether the current thread uses the cached pre-xlate message or the outbound message as the whole message.

By default, the check box is cleared. When selected, the Database Outbound protocol driver attempts to extract the cached pre-xlate message from the message driver control. Then, it decodes it with base64 decoding, if waiting to be used.

Use the whole_message placeholder to insert/update a table column with the cached pre-xlate message. After this, the engine replaces the whole_message placeholder with the retrieved pre-xlate message if it exists at runtime.

You can directly specify the whole_message placeholder into the SQL statement action. You can also click Configure to open the Outbound SQL Statement Configurator dialog box in which to compose a SQL statement with the placeholder.

Outbound SQL Statement Configurator dialog box

In this dialog box, clicking Select next to the Column field opens the Select Column dialog box. The table component lists all the selected columns, and the Whole Message check box represents whether the column must be inserted/updated with a whole message.

For the selected columns, their values are replaced with whole_message. For example:

INSERT INTO callback(callback.THREADNAME, callback.PROCESS) 
VALUES (whole_message, callback.PROCESS)

In the Outbound SQL Statement Configurator dialog box, after opening the Select Column dialog box, clicking Add opens the Column List dialog box. This uses a table component to display columns. After making a selection, clicking Apply closes the Column List dialog box and applies the selected columns to the Select Column dialog box. If required, then at this point you can change the check box status on the Select Column dialog box.

Network Configurator

In the Route Messages or Route Replies tab of Network Configurator, double-clicking a route name opens the Route dialog box.

For the Store original message in metadata for downstream processing option, the pre-xlate message is cached in route details. This is used in the Database Outbound Protocol Properties dialog box and database outbound protocol engine thread.

When this option is selected, the engine thread caches the pre-xlate message at runtime. By default, this is cleared. The engine’s xlate thread encodes the pre-xlate message. Then, it caches it into the current message’s metadata driver control field before sending it to the destination thread. After this, the destination thread that is defined in the Route Details dialog box can use the cached message.