Creating an SXD file

The MessageIN Event that retrieves data via the JDBC input connector must use the appropriate SXD file to be able to handle the data. This SXD file must include one field element for each column in the database table from which data is retrieved.

You can let the JDBC input connector retrieve the table information, and create this SXD file for you. You can create a separate Project for this purpose. This Project must contain a JDBC input connector, a MessageIN Event, and any Process and output connector. For example a PageOUT Process containing a dummy text field and a Null output connector.

When you run the Project, the SXD file is created in the path you specify in the connector settings. You must then import the SXD file to the appropriate resource set, and connect it to the MessageIN Event in the real Project.

JDBC input connector configuration

When you configure the connector to create an SXD file, you must specify the connection settings (JDBC driver, Connection URL, User name, and Password) to connect to the database with the table from which to retrieve the information. You can use the same connection settings as in the real Project, but if you need to you can connect to another database that contains a table with identical columns as the one you will use in the real Project.

To create the SXD file, you must also specify the following:

SQL file or SQL command	The SQL query must select all columns in the database table. For example, to select all columns in the table CustomerData you can use the following SQL command: SELECT * FROM CustomerData
Event name	The same Event name as in the real Project.
Mode	Select Copy (no delete). This will make sure no data is removed from the database table.
Row level	The same row level as in the real Project. The row level affects the output in the SXD file. For example, if you select row level Output as blocks, block elements will be included in the SXD file.
Create SXD	The path to the SXD file.

MessageIN Event configuration

The name of the MessageIN Event must be the same as Event name specified in the JDBC input connector. Since the Event does not use any SXD file in this case, you must specify a pattern for the Event (open the Event tool and enter the Pattern). For example, if Event name is CustomerData you can also use CustomerData as Pattern.