Connect to an SSL-Enabled Microsoft SQL Server Database from PowerCenter on UNIX/Linux

(1)

© 2013 Informatica Corporation. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. All other company and product names may be trade names or trademarks of their respective owners and/or copyrighted materials of such owners.

Connect to an SSL-Enabled

Microsoft SQL Server Database

from PowerCenter on UNIX/Linux

(2)

2

Abstract

Because Microsoft SQL Server databases have no native connectivity from UNIX/Linux

environments, you must set up ODBC connectivity from Linux to run the Informatica services on a UNIX/Linux server. You can use the DataDirect ODBC drivers that are installed with the

Informatica services. However, if SSL is enabled for a Microsoft SQL Server database, then the DataDirect drivers are not sufficient. This article provides guidelines for installing and configuring ODBC connectivity to Microsoft SQL Server when SSL is enabled.

Supported Versions

 PowerCenter

Overview

When working in an environment with an SSL-enabled Microsoft SQL Server database, you must use DataDirect SequeLink ODBC Socket to resolve SSL encryption issues. SequeLink ODBC Socket provides a connection from the UNIX/Linux ODBC client to the middle tier, instead of directly to SQL Server.

Contact Informatica Global Customer Support to get a download link for the following items:

 A PDF file that contains instructions for installing the software

 A tar file (closed_sl_60_linux64.tar) to install on Linux

 A zip file (sl600socket.zip) to install on the Windows machine where the Microsoft SQL Server database resides

Follow the instructions in the PDF document in conjunction with the information in this article.

Install and Configure DataDirect ODBC on Linux

1. Install the Informatica services, which include the DataDirect ODBC drivers, on Linux.

2. Set the ODBCHOME environment variable to the location where the drivers have been installed:

export ODBCHOME=$INFA_HOME/ODBC6.0

3. Set the library path variable to include $ODBCHOME/lib.

4. Set the ODBCINI environment variable in the .profile to the location of the final version of .odbc.ini:

(3)

3

export ODBCINI=$ODBCHOME/odbc.ini

5. Add the ODBC/bin directory to the PATH environment variable.

You can find the library name in the odbc.ini file.

6. Add the data sources to the .odbc.ini file that is specified in the $ODBCINI environment variable.

7. Restart the Informatica services.

To use these ODBC connections in PowerCenter sessions, configure ODBC relational connections in the Workflow Manager.

Configuration on Linux

1. Use the following command to untar the ODBC Socket file:

tar –xvf closed_sl_60_linux64.tar The following figure shows the tar file:

The following figure shows the extracted contents from the tar file:

2. Make changes to the .profile file and run the following commands for the SequeLink drivers:

export

SQLNK_ODBC_HOME=/opt/app/informatica/SequeLink/closed_sl_60_linux64/lib64 export SHLIB_PATH=$SQLNK_ODBC_HOME/lib64:”$SHLIB_PATH”

LD_LIBRARY_PATH=.:$ODBCHOME/lib:$SQLNK_ODBC_HOME:$LD_LIBRARY_PATH

3. Verify that the SQLNK_ODBC_HOME appears after ODBCHOME/lib because the first step is to use ODBC drivers provided by Informatica and, if the driver is not found, then go to next path search.

4. Define the data source in the odbc.ini file.

The following figure shows the data source details:

(4)

4

The host is the Windows machine where the Microsoft SQL Server database is installed.

The following figure shows the port under the Value tab in the General area of the Service Settings:

Configuration on Windows

To open ports 19995 and 19996 on the Windows machine that hosts the Microsoft SQL Server database, perform the following steps. The ports provide access to the Informatica services on Linux.

1. Copy the sl600socket.zip file to the machine that hosts the Microsoft SQL Server database.

2. You obtain the sl600socket.zip file from Informatica Global Customer Support.

3. Unzip the file.

The following image shows the extracted contents of the zip file:

(5)

5

4. Install the software.

Use the instructions in the PDF provided by Informatica Global Customer Support to install the software. After the installation completes, the new Windows services SLAgent60 and SLSocket60 are visible.

5. Stop the SLAgent60 and SLSocket60 services.

6. Right-click the SLAgent60 service and set up the appropriate user account name that will be allowed to administer the SequeLink Socket.

7. Right-click the SLSocket60 service and set up the appropriate user account name that will be allowed to administer the SequeLink Socket.

Note: For steps 5 and 6, the user name must match exactly what was entered during the installation of the server. If the user names do not match, you must reinstall the software.

8. Create a DSN on the server machine that connects to the Microsoft SQL Server database.

9. Start the Console Snap-In on the machine where the DSN has been created.

For example, click Programs > DataDirect SequeLink 6.0 Service for ODBC Socket >

SequeLink Management Console Snap-In.

The Console Snap-In appears.

10. Expand the Connected to SLAgent60 folder in the Console Snap-In.

11. Under the Value tab for DataSourceSOCODBCConnStr, enter “DSN=<name of DSN created earlier>.”

(6)

6

12. Enter “DSN=<name of DSN created earlier>” under the Value tab for DataSourceSOCODBCConnStr.

The Value tab for ServiceConnectInfo provides the host name and port number that needs to be entered in the odbc.ini file.

13. Save the settings.

14. Exit the Console Snap-In.

15. Log in to the Console Snap-In again to verify that the settings are saved.

Test the Connection to the Microsoft SQL Server Database

Run a test to verify that the machine can connect to the Microsoft SQL Server database.

The following is a test for SequeLink connectivity:

infad@infa-

server:/opt/app/informatica/SequeLink/closed_sl_60_linux64/example>

./example64

(7)

7

./example64 DataDirect Technologies, Inc. ODBC Example Application.

Enter the data source name : <Data Source name> as specified in ODBC.INI file

Enter the user name : <Username to connect to SQL Server>

Enter the password : <Password to connect to SQL Server>

Enter SQL statements (Press ENTER to QUIT) SQL>

If the test is successful, the server connects to Microsoft SQL Server and the SQL prompt appears.

Troubleshooting

Use the following tips to troubleshoot:

 If the user under which the services run changes, a log on error occurs when you start the Console Snap-In. To resolve, uninstall the software, restart the server, and then install the software again.

 Verify that there is no other DSN in the odbc.ini file with the same name as the DSN that is used to connect to the Microsoft SQL Server database.

The following errors might occur if there are duplicate names:

SQLSTATE = 08S01 NATIVE ERROR = 11

MSG = [Informatica][ODBC SQL Server Driver][libssclient24]General network error. Check your network documentation.

SQLSTATE = 01000 NATIVE ERROR = 11

MSG = [Informatica][ODBC SQL Server Driver][libssclient24]ConnectionRead (recv()).

 If you attempt to connect to the Microsoft SQL Server database from a machine other than the machine that hosts the database, the following errors might occur:

MSG = [DataDirect][ODBC 20101 driver][SequeLink Client]TCP/IP error, connection timed out

MSG = [DataDirect][ODBC 20101 driver]1221

Authors

Ajay Tawakley

Manager Technical Delivery, Professional Services

Connect to an SSL-Enabled Microsoft SQL Server Database from PowerCenter on UNIX/Linux