Inserting a whole message using the whole_message placeholder
The SQL statement action supports a whole_message placeholder that represents a whole message.
- Open the Site Preferences dialog box and on the Database Configurations tab configure a database connection. Or, open a previously created database connection.
-
Define the database schema format to use in the Database Outbound protocol. To
do this:
- Open the Database Schema Configurator.
- Import table schema by clicking the Import button.
- Click OK.
- In the Network Configurator Database Outbound Protocol Properties dialog box, click the Table Schema button and select a table schema from the Select Table Schema dialog box.
- Select SQL Statement option and click Configure.
-
Select a Table/View.
Click Select to open the Table Selection dialog box. Select from the list of all tables in the current database connection.
- For Column, click Select to select one or more columns for the selected table/view.
-
After selecting a column, click Whole Message for the selected columns.
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.
- If required, then click the Configure for the Condition field.
-
Click OK to close the Outbound SQL
Statement Configurator dialog box.
This inserts whole_message into the Value pane.For example:
INSERT INTO callback(callback.PROCESS, callback.CONTEXT) VALUES (<callback.PROCESS>, whole_message)
-
If required, then select the Use cached pre-xlate message as whole
message check box. This defines 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 in base64 decoding, if it is waiting to be used.
-
In the Route Messages or Route Replies tab of Network Configurator,
double-click a route name to open the Route dialog box.
Select the Store original message in metadata for downstream processing option. The pre-xlate message is cached in route details and 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. Then, the destination thread that is defined in the Route Details dialog box can use the cached message.
-
Send messages to the Database Outbound protocol using the Testing
Tool.
Note: The Database Outbound protocol parses a message that is based on the defined table schema. To insert the entire message to one single column, the message must not include the field separator and termination characters.