VERIFIED SOLUTION i

Preventing the loss of Database connectivity that causes NA-Batch to fail in EngageOne

Product Feature: Administration

Operating System: Windows

Database: MsSQL

Configuration: Not stated
 
Locate the datasource file for JBoss and open it. Locate the connector for MSSQL and add the sections in Blue to the config. Once done, restart JBoss to make the changes take effect.

<subsystem xmlns="urn:jboss:domain:datasources:1.1">
            <datasources><datasource enabled="true" jndi-name="java:/ocm-nonjta" jta="false" pool-name="ocm-nonjta" spy="false" use-ccm="true" use-java-context="true">
                    <connection-url>jdbc:sqlserver://UKCSGMP-EO3111:1433;databaseName=eo3111_b20</connection-url>
                    <driver>sqljdbc</driver>
                    <transaction-isolation>TRANSACTION_NONE</transaction-isolation>
                    <pool>
                        <min-pool-size>10</min-pool-size>
                        <max-pool-size>200</max-pool-size>
                        <prefill>false</prefill>
                        <use-strict-min>false</use-strict-min>
                        <flush-strategy>EntirePool</flush-strategy>
                    </pool>
                    <security>
                        <security-domain>EncryptDBPassword</security-domain>
                    </security>
                    <validation>
                        <check-valid-connection-sql>SELECT 1</check-valid-connection-sql>
                        <validate-on-match>true</validate-on-match>
                         <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.mssql.MSSQLValidConnectionChecker"/>
                        <background-validation>true</background-validation>
                        <use-fast-fail>true</use-fast-fail>
                    </validation>
                </datasource><datasource enabled="true" jndi-name="java:/ocm" jta="true" pool-name="ocm" spy="false" use-ccm="true" use-java-context="true">
                    <connection-url>jdbc:sqlserver://UKCSGMP-EO3111:1433;databaseName=eo3111_b20</connection-url>
                    <driver>sqljdbc</driver>
                    <transaction-isolation>TRANSACTION_NONE</transaction-isolation>
                    <pool>
                        <min-pool-size>10</min-pool-size>
                        <max-pool-size>200</max-pool-size>
                        <prefill>false</prefill>
                        <use-strict-min>false</use-strict-min>
                        <flush-strategy>EntirePool</flush-strategy>
                    </pool>
                    <security>
                        <security-domain>EncryptDBPassword</security-domain>
                    </security>
                    <validation>
                        <check-valid-connection-sql>SELECT 1</check-valid-connection-sql>
                        <validate-on-match>true</validate-on-match>
                         <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.mssql.MSSQLValidConnectionChecker"/>
                        <background-validation>true</background-validation>
                        <use-fast-fail>true</use-fast-fail>
                    </validation>
                </datasource>
                <datasource enabled="true" jndi-name="java:jboss/datasources/ExampleDS" pool-name="ExampleDS" use-java-context="true">
                    <connection-url>jdbc:h2:mem:test;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE</connection-url>
                    <driver>h2</driver>
                    <security>
                        <user-name>sa</user-name>
                        <password>sa</password>
                    </security>
                </datasource>
                <drivers><driver module="com.microsoft.sqlserver.jdbc" name="sqljdbc">
                        <driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>
                    </driver>
                    <driver module="com.h2database.h2" name="h2">
                        <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class>
                    </driver>
                </drivers>
            </datasources>
        </subsystem>
 
UPDATED:  April 6, 2017