Configuring IBM App Connect Enterprise to connect to SQL server: Part 1

The following task demonstrates the initial setup of the odbc.ini and krb5.conf files.

1. Configure the Linux® or UNIX client machine to connect to the SQL server by adding the following entry to your odbc.ini file:

   [TESTDB]
   Driver=/opt/IBM/mqsi/11.0.0.n/server/ODBC/drivers/lib/UKsqls95.so
   Description=DataDirect SQL Server Wire Protocol
   Database=TESTDB
   HostName=sqlserver.domain.company.com
   PortNumber=1433
   AnsiNPW=1
   LoginTimeout=0
   QueryTimeout=0
   ;# To specify a named instance of SQLServer replace the HostName and PortNumber lines with
   ;#HostName=sqlserver.domain.company.com\named_instance
   ;# To use Integrated Windows Authentication uncomment the following lines.
   ;#AuthenticationMethod=9
   ;#Domain=domain.company.com

   In this example:

   • TESTDB is the name of a database.
   • sqlserver.domain.company.com is the address of your SQL server.
   • 1433 is the port number of your SQL server.

     To use a named instance instead of a port number, comment out the PortNumber property and change HostName to HostName=sqlserver.domain.company.com\named_instance

   If your SQL server host uses Integrated Windows Authentication, uncomment and configure the final 2 lines in the example.

2. If you have not already done so, join the SQL server host machine to the Windows Active Directory domain.
3. Create a sample message flow that connects to the database and set up the mqsicredentials command parameters and associated permissions in the SQL server as you would a normal ODBC connection. You can, alternatively, use the mqsisetdbparms command to set up the parameters and permissions. Now test that this initial setup works correctly.