Hi All,

We are using the latest version of IBM ACE v12.0.12.2 and a policy file to establish a connection to an SQL Server Database. The SQL jar file path is set to /apps/JDBDrivers/SQLServer/. Below is our policy file. However, we are experiencing issues in establishing the connection to the database. When we place the SQL driver jar file in the shared classes directory of the Execution Group (e.g., /var/mqsi/config/Broker_Name/EG_Name/shared-classes), it starts working. It seems that the jar file path specified in the policy file is not being recognized.

Our Policy File
===========
<?xml version="1.1" encoding="UTF-8" standalone="yes"?>
<policies>
  <policy policyType="JDBCProviders" policyName="KrRouteDispatcherJDBC">
    <connectionUrlFormat>jdbc:sqlserver://[serverName]:[portNumber];DatabaseName=[databaseName];user=[user];password=[password];sslProtocol=TLSv1.2;encrypted=true;trustServerCertificate=true</connectionUrlFormat>
    <connectionUrlFormatAttr1></connectionUrlFormatAttr1>
    <connectionUrlFormatAttr2></connectionUrlFormatAttr2>
    <connectionUrlFormatAttr3></connectionUrlFormatAttr3>
    <connectionUrlFormatAttr4></connectionUrlFormatAttr4>
    <connectionUrlFormatAttr5></connectionUrlFormatAttr5>
    <databaseName>LOG_PNDATA_TEST</databaseName>
    <databaseSchemaNames>useProvidedSchemaNames</databaseSchemaNames>
    <databaseType>Microsoft_SQL_Server</databaseType>
    <databaseVersion></databaseVersion>
    <description></description>
    <environmentParms></environmentParms>
    <jarsURL>/intApps/JDBCDrivers/SQLSERVER/</jarsURL>
    <jdbcProviderXASupport>FALSE</jdbcProviderXASupport>
    <maxConnectionPoolSize>2</maxConnectionPoolSize>
    <portNumber>1675</portNumber>
    <securityIdentity>KrRouteDispatcherSecurityIdentity</securityIdentity>
    <serverName>N060PPNSQL401.kroger.com</serverName>
    <type4DatasourceClassName>com.microsoft.sqlserver.jdbc.SQLServerDataSource</type4DatasourceClassName>
    <type4DriverClassName>com.microsoft.sqlserver.jdbc.SQLServerDriver</type4DriverClassName>
    <useDeployedJars>FALSE</useDeployedJars>
  </policy>
</policies>

That would probably be because your path names do not match:

In the policy you have:  <jarsURL>/intApps/JDBCDrivers/SQLSERVER/</jarsURL>

In your description we see:                /apps/JDBDrivers/SQLServer/

So beside the start /intApps and /apps, there is also a missing C in JDBDrivers and the case difference for SQLServer vs SQLSERVER....

I'd say you're shooting yourself in the foot!

Sorry it was typo in description correct is /intApps/JDBCDrivers/SQLSERVER/ , hence path of jar in policy file is correct yet it is not working for DB2 it's working but for SQL server it is not working