Disabling Test Connection to a JDBC Resource

  • By default, testing connection to a JDBC resource is enabled in ActiveMatrix Administrator. To disable the feature set the Java property com.tibco.admin.jdbc.disable.validate.connection.oninit to true in the ActiveMatrix System Node’s TRA file. System Node’s TRA file is located at CONFIG_HOME\tibcohost\<instance_name>\data_3.2.x\nodes\SystemNode\bin\ directory. 
    java.property.com.tibco.admin.jdbc.disable.validate.connection.oninit=true
    The default value of this property is false.
  • Alternatively, when creating the resource template, set the attribute disableValidateConnectionOnInit to true in the <CONFIG_HOME>\admin\amxadmin\samples\resourcetemplate_data.xml file.

    Sample resourcetemplate_data.xml: 

    <ResourceTemplate
        xsi:type="amxdata:JdbcResourceTemplate"
        name="cliJdbcNonXaNoTx"
        description="jdbc non xa no tx"
        maxConnections="8888"
		disableValidateConnectionOnInit="true">
        <Direct
            xsi:type="amxdata:Direct"
            dbUrl="jdbc:hsqldb:hsql://localhost:1234/jdbcRtDb"
            jdbcDriver="org.hsqldb.jdbcDriver"
            isTransactional="false"
            loginTimeOut="2"/>
        <connection-property xsi:type="amxdata:Property" name="Property1" value="propertyValue1"/>
        <connection-property xsi:type="amxdata:Property" name="Property2" value="propertyValue2"/>
        <connection-property xsi:type="amxdata:Property" name="Property3" value="propertyValue3"/>
        <hostTypeProperties xsi:type="amxdata:Properties">
            <Property xsi:type="amxdata:Property" name="hostProp1" value="val1"/>
            <Property xsi:type="amxdata:Property" name="hostProp2" value="val2"/>
        </hostTypeProperties>
        <InlineCredentials username="cliJdbc" password="cliTiger"/>
    </ResourceTemplate>
If the resource template and resource instance are already created and if you disable the test connection to JDBC resource feature, the feature is not disabled for existing resource template and resource instance. If the JDBC configuration is invalid for the resource instance, installing the resource instance will fail.

If the test connection to JDBC resource feature is disabled when creating resource template and if you enable it when creating the resource instance, the feature is not enabled for the resource template, which is already created. The feature is enabled for the resource template and resource instance created after enabling the feature.