Database Lookup Filter

<!-- Database Lookup Filter Configuration Template -->
<!--
This XML file is designed to help you configure the Rhapsody
Database Lookup filter. All element or attribute tags are case
insensitive, i.e., both 'config' and 'CONFIG' are valid tags.

Please refer the Rhapsody manual and tutorials for more information.


Please note that this file is not executable.
-->
<config>
    <!-- Main Database Standard JDBC Configuration -->
    <driver>enter driver name here</driver>
    <url>enter database url here</url>
    <username>enter database username here</username>
    <password>enter database password</password>

    <!-- Secondary Database Standard JDBC Configuration
    One or more secondary databases can be configured
    -->
    <database name="enter this database name">
        <driver>enter driver name here</driver>
        <url>enter database url here</url>
        <username>enter database username here</username>
        <password>enter database password</password>
    </database>

    <!--
    Database Connections' Auto-Commit Mode Configuration.
    By default, auto-commit mode is turned off, which means that
    transactions will be rolled back in case of failure when processing
    a message.
    The auto-commit mode option will be applied to all database connections.
    The property is required (if only SELECT statements are used, autoCommit
    may be turned on in order to enhance performance when processing messages).
    -->
    <!-- <autoCommit/> -->

    <!-- Convert null fields: an empty string("") is used to generate a sql 
    statement when the message field does not exists 
    -->
    <!--  <convertNullFields/>  --> 

    <!-- Statements Configuration -->
    <!--
    Root Statement Configuration
    Only one root statement can be configured:
    The 'name' attribute: name of the statement, the name will be used 
    to refer the statement in the Rhapsody log.
    The 'iterate' attribute: full path of a message element which is 
    repeating so that the statement can be iterated.
    The 'database' attribute: one of the secondary database names. If this 
    attribute is omitted, the main database will be used for the statement.
    The 'name', 'iterate' and 'database' attribute can be omitted.
    The 'test' attribute: test condition to decide whether the sql query 
    for the statement is executed.
    The 'maxResultRows' attribute: maximum Number of Rows Limit that Result .
    Set can hold for the statements: default 0 means no limit.
    -->
    <statement name="" iterate="" database="" test="" maxResultRows="0">
        <!--
        SQL or Stored Procedure for the statement, this element can be omitted 
        if this is the case
        -->
        <sql>enter sql query</sql>
        <!-- <procedure>enter stored procedure</procedure> -->

        <!--Communication Point In Input Mode
        Populating Message Field Configuration
        The 'name' attribute: a column name which is returned from the statement
        -->
        <substituteColumn name="">Enter a message field name to be populated</substituteColumn>

        <!--
        Child Statements Configuration:
        One or more child statements can be configured.
        A child statement can have one or more child statements.
        Attribute details are the same as for the root statement.
        -->

        <statement name="" iterate="" database="" test="" maxResultRows="0">
            <sql>enter sql query</sql>
            <!-- <procedure>enter stored procedure</procedure> -->
        </statement>

    </statement>

</config>