Chapter 4. Developing applications with ESQL
SET I = I + 1;
CREATE PROCEDURE CopyEntireMessage() BEGIN
SET OutputRoot = InputRoot;
The Compute node can now parse the line that instructs the Compute node to
copy the header and content of the input message (InputRoot) to the output
message (OutputRoot). The message that the MQOutput node,
ESQL_SIMPLE_OUT, puts on the ESQL_SIMPLE_OUT queue has the same
content as the message that the MQInput node, ESQL_SIMPLE_IN, got from
the ESQL_SIMPLE_IN queue.
2. Save ESQL_Simple.esql and ESQL_Simple.msgflow.
The next section describes how to deploy the ESQL_Simple message flow so
that you can test it.
4.2.4 Deploying and testing the ESQL_Simple message flow
Before you can test the ESQL_Simple message flow, you must deploy it to the
broker. Then, when you put the test input message on the ESQL_SIMPLE_IN
queue, the broker processes the message using the deployed message flow.
Deploying the ESQL_Simple message flow
To deploy a message flow to the broker, package it in a message broker archive
(bar) file. 7.4.2, “Deploying resources to a remote broker” on page 226 provides
more information about deployment. This chapter just explains what you need to
do to deploy the message flow applications that you create so that you can test
Attention: Ignore any warning messages about unresolvable database table
references that are also displayed in the Problems view when you save the
message flow. These messages are displayed because the Message Brokers
Toolkit does not have access to the database fields that the ESQL in the
message flow refers to. It is possible to connect to the database from the
Message Brokers Toolkit, but it is unnecessary for the exercises in this
chapter (“Creating the Create_Customer_Account message flow” on
page 181 describes how to connect to a database from the Message Brokers