Using SequeLink to Access Data

© 2010 Informatica Corporation

Abstract
If PowerExchange does not provide access for your database, you might be able to use the DataDirect SequeLink
Client and Server with the SequeLink ODBC drivers to access the data, depending on the database type. With the
SequeLink ODBC drivers, you can access data on a Windows machine from a UNIX or Linux machine that runs
PowerCenter Services.

Table of Contents
Overview ........................................................................................................................................................................... 2
How SequeLink Communicates with PowerCenter........................................................................................................... 3
Configuring SequeLink to Access data ............................................................................................................................. 4
Step 1. Downloading the SequeLink Software ............................................................................................................. 4
Step 2. Creating an ODBC Data Source ...................................................................................................................... 4
Step 3. Installing the SequeLink Server for ODBC Socket........................................................................................... 4
Step 4. Starting SequeLink ODBC Socket Services..................................................................................................... 7
Step 5. Configuring the SequeLink ODBC Socket Server............................................................................................ 8
Step 6. Installing the SequeLink ODBC Client ............................................................................................................. 9
Step 7. Configuring the SequeLink ODBC Client ......................................................................................................... 9
Setting the Environment Variables......................................................................................................................... 10
Configuring odbc.ini ............................................................................................................................................... 10
Restarting Informatica Services ............................................................................................................................. 10
Step 8: Configuring a PowerCenter Connection Object ............................................................................................. 11

Overview
PowerExchange provides access to most popular types of enterprise data sources and targets. If you need
PowerCenter sessions to access data on sources or targets for which PowerExchange does not provide access, you
might be able to use the DataDirect SequeLink Client and Server with the SequeLink ODBC drivers for data access.
SequeLink provides ODBC drivers for databases such as Microsoft Access, FileMaker, Progress, FoxPro, and dBase.
For a list databases that SequeLink supports, see the DataDirect SequeLink Support Matrix.
Important: Informatica does not support ODBC as a substitute for PowerExchange. PowerExchange provides better
performance and has unique capabilities, such as change data capture (CDC) and pushdown optimization, that the
ODBC drivers cannot exploit. Also, Informatica might not be able to certify all ODBC drivers prior to each release. For
more information, see the support statement about ODBC drivers with Informatica products, which is available from the
Informatica Support site at https://my-prod.informatica.com/portal/wps/myportal/us/Support#.
PowerCenter customers can download and use the SequeLink Client and SequeLink Server for ODBC Socket at no
cost. The SequeLink ODBC drivers that Informatica provides can only be used with PowerCenter. With SequeLink, you
can use a Windows ODBC driver to access data on a Windows machine from a UNIX or Linux machine that runs
PowerCenter Services.
To use SequeLink, install the SequeLink Client on the machine where the PowerCenter Integration Service runs and
install the SequeLink Server for ODBC socket on the machine where the data is stored. The SequeLink Server for
ODBC Socket includes the SequeLink Service and SequeLink Management Console Snap-in. Use the SequeLink
Management Console Snap-in to manage the SequeLink Service. The SequeLink Client includes the ODBC drivers,
driver manager, and odbc.ini.

2
How SequeLink Communicates with PowerCenter
The following figure provides an overview of how SequeLink communicates with PowerCenter:

In the example above, PowerCenter uses SequeLink software to read data from a Microsoft Access database. The
SequeLink Client components on the UNIX machine connect to the SequeLink Server on the Windows machine to
access the Microsoft Access database.
The data source names provide connectivity to the data that you want to access. You specify data source names when
you configure the connection object, SequeLink server data source, odbc.ini, and the System DSN.
The following figure shows the relationship between the data source names:

You configure a data source name in the following places:

y System DSN in the ODBC Data Source Administrator. When you create an ODBC data source, you specify an
ODBC data source name. You specify this name in the DataSourceSOCODBCConnStr attribute of the SequeLink
server data source. In the figure above, the data source name is CustData.
y Data source in the SequeLink Management Console Snap-in. When you configure a SequeLink server data
source, the DataSourceSOCODBCConnStr must contain the string with DSN=<data source name>. The DSN
value must match the data source name of the System DSN. In the figure above, the SequeLink server data source
is Access1 and the DataSourceSOCODBCConnStr attribute contains the string DSN=CustData.

3
y ODBC data source in odbc.ini. When you configure odbc.ini, you specify a name for the ODBC Data Source. The
data source name must match the connect string you provided in the connection object. If you have multiple
SequeLink server data sources, the ServerDataSource value in odbc.ini must match the SequeLink server data
source name in the SequeLink Management Console Snap-in. In the figure above, the ODBC Data Source is Test
and the ServerDataSource is Access1.
y Connect string in the connection object. When you create the ODBC Connection object in the Workflow
Manager, you specify a connect string. The connect string should contain the ODBC data source name that you
configure in odbc.ini. In the figure above, the connect string is Test.

Configuring SequeLink to Access data

To use SequeLink to connect to a database on Windows, verify that your environment meets the following
requirements:
y The PowerCenter license has the ODBC connectivity option.
y The required database drivers are installed on the Windows machine. You need the driver to create an ODBC data
source.
y The Windows and UNIX machines meet the SequeLink prerequisites. For more information about DataDirect
SequeLink prerequisites, see the DataDirect SequeLink documentation.
Complete the following steps to access data using SequeLink:
1. Download the SequeLink software.
2. Create an ODBC data source.
3. Install the SequeLink Server for ODBC Socket.
4. Start the SequeLink Service.
5. Configure the SequeLink OBDC Socket Server.
6. Install the SequeLink ODBC Client.
7. Configure the SequeLink ODBC Client.
8. Configure a PowerCenter connection object.

Step 1. Downloading the SequeLink Software

Contact Informatica Global Customer Support to get the SequeLink software. The SequeLink software is free to
Informatica customers.

Step 2. Creating an ODBC Data Source

When you create a data source, you provide a data source name that Sequelink uses to connect to the data. You
create the data source using the ODBC Data Source Administrator. The driver for the data source must be installed.

Step 3. Installing the SequeLink Server for ODBC Socket

1. Extract the installation files on the Windows machine where the data is stored.
2. Run the following command from the location where you extracted the installation files:
setup.exe /v"IPE=NO"

4
 The installation wizard appears.

3. Click Next.
4. Accept the License Agreement. Then, click Next.
The Custom Setup screen appears.

5. Verify that that following options are selected:

- SequeLink Manager
- SequeLink Server for ODBC socket

5
6. Click Next.

7. Review the values and click Next.

The default SequeLink Agent and SequeLink Server name and port numbers appear.
By default, the user that runs the installer is the user that is configured to administer the SequeLink Socket. The
user that administers the SequeLink Socket must have the Log on as a service right.
You can update the default values.

8. You can configure the data source name for the ODBC Connection String. Enter DSN=<Data Source Name>. The
DSN that you provide will be assigned to the Default SequeLink data source setting. Click Next to continue.
-or-

6
 You can configure the ODBC connect string with the SequeLink Management Console Snap-in after you install.
Click Next to continue.
For information about configuring the ODBC Connection String with the SequeLink Management Console
Snap-in, see “Configure the SequeLink OBDC Socket Server.”

9. Click Install.

10. Click Finish.

Step 4. Starting SequeLink ODBC Socket Services

1. Click Start > All Programs > DataDirect SequeLink 6.0 Service for ODBC Socket > SequeLink Management
Console Snap-in.

7
 The logon to SequeLink Service dialog box appears.

2. Enter the password for the user that administers the SequeLink Service. Then, click OK.

Step 5. Configuring the SequeLink ODBC Socket Server

SequeLink Services use the ODBC connection string to connect to the data source. The ODBC connection string is
configured within a SequeLink server data source. If you did not configure the ODBC connection string during the
installation, configure the ODBC connection string using the DataSourceSOCODBCCOnnStr attribute. The installer
creates a SequeLink server data source named Default. You can create multiple SequeLink server data sources.

To configure the ODBC connect string for the Default data source setting:
1. In the SequeLink Management Console Snap-in, navigate to the following location:
SequeLink Service > SLSocket60 > Configuration > Data Source Settings > Default > Advanced.

2. Double-click the Value field for the DataSourceSOCODBCCOnnStr attribute.

3. Set the value to DSN=<ODBC Data Source Name>.
For example, if you created a data source named Access, enter the following value: DSN=Access

To configure the additional SequeLink server data sources:

1. In the SequeLink Management Console Snap-in, navigate to the following location:
SequeLink Service> SLSocket60 >Configuration> Data Source Settings

8
2. Right-click on Data Source Settings and then select New > Data Source.

3. Enter a name for the data source.

4. If required, update the ODBC Connection String.
The DataSourceSOCODBCCOnnStr attribute defaults to the DSN value that you configured for the Default data
source setting.
To update the ODBC Connection String, select Advanced and double-click the DataSourceSOCODBCCOnnStr
attribute. Set the value to DSN=<Data Source Name>.
For more information about configuring the SequeLink Service, see the DataDirect SequeLink documentation.

Step 6. Installing the SequeLink ODBC Client

The SequeLink ODBC drivers that Informatica provides are branded drivers. These drivers can only be used with
PowerCenter.
To install the SequeLink ODBC client, complete the following steps:
1. Download The SequeLink ODBC client files.
For example, download slclient.tar
2. Extract the SequeLink client files to a directory on the UNIX machine where the Integration Service runs.
For example, you can enter tar –xvf slclient.tar
3. In the etc/tar directory within the directory where you extracted the slclient.tar, locate TAR file for your platform.
4. Extract the TAR file for your platform.
For example, you can enter tar –xvf ivslkHP-UX.tar
The directory that contains these extracted files is the SequeLink client directory. You will need to reference this
directory when you configure the SequeLink ODBC client.

Step 7. Configuring the SequeLink ODBC Client

To configure the SequeLink ODBC Client, complete the following steps:
1. Set environment variables.
2. Configure odbc.ini.
3. Restart Informatica Services.

9
Setting the Environment Variables
Set the following environment variables:
export SQLNK_ODBC_HOME=<SequeLink client directory>/lib
export ODBCINI=<SequeLink client directory>/lib/odbc.ini
export LD_LIBRARY_PATH=<SequeLink client directory>/lib:$LD_LIBRARY_PATH

The PowerCenter installation directory and the SequeLink client directory contain an odbc.ini file. You can choose to
configure the odbc.ini that is provided with PowerCenter. Set ODBCINI to the location of the odbc.ini that you want to
use.
Note: The name of the lib directory can be different for each platform. For example, the lib directory may be named
lib64.

Configuring odbc.ini
PowerCenter uses odbc.ini to connect to the SequeLink data source.
To configure odbc.ini, you need the following information:
y Data source name. The data source name that you provided when configuring the connect string for the ODBC
connection object in the Workflow Manager.
y Driver location. The driver is located in the lib folder of the SequeLink client installation location. The driver name
is dwslk22.xx or ivslk22.xx. The file name extension can be different for each platform.
y Host name and SequeLink Server port number. Host and port information is available on the Sequelink Socket
Server Services folder in the General area of the Service Settings.
y SequeLink server data source name. Optional. The name of the SequeLink server data source.
To update odbc.ini, create an entry for the date source under the ODBC Data Sources section and also create an entry
for the date source that specifies the connection information.
For example, if the Data Source name is Test and you created a SequeLink data source setting named Access1,
create an entry under the ODBC Data Sources section and also create an entry that includes the driver, description,
port, host, and server data source name.
[ODBC Data Sources]
Test = DataDirect 32-BIT SequeLink 6.0

[Test]
Driver= <SequeLink client directory>/lib/dwslk22.so
Description=DataDirect 32-BIT SequeLink 6.0
Host=<machine name that runs the SequeLink Service>
Port=<port number of the SequeLink Server>
UseLDAP=0
ServerDataSource=Access1

Note: The ServerDataSource is an optional field. If you do not specify the SequeLink server data source name in the
ServerDataSource field, the SequeLink Service uses the default SequeLink data source. Configure ServerDataSource
when you have multiple SequeLink data sources.

Restarting Informatica Services

Use the infaservice command to start and stop Informatica Services. By default, infaservice is installed in the
server/tomcat/bin directory in the PowerCenter Services installation directory.

To start or stop Informatica Services on UNIX:

1. At the command prompt, switch to the directory where the infaservice executable is located.
2. At the command prompt, enter the following command to start or stop the Service Manager:
infaservice [startup | shutdown]

10
Note: If you use a soft link to specify the location of infaservice, set the INFA_HOME environment variable to the
location of the PowerCenter Services installation directory.

Step 8: Configuring a PowerCenter Connection Object

Create an ODBC relational connection object to provide PowerCenter sessions a connection to the data source.
Enter the following information when you create the connection object:
Field Description
Username SequeLink Administrator username. Enter <Domain name>/ <Username>.
Password SequeLink Administrator password.
Connect String Name of the ODBC date source entry in odbc.ini.
For more information about creating a connection object, see the PowerCenter documentation.

Author
Padma Heid
Technical Writer

Acknowledgements
The author would like to thank Manigandan Paramasivan, Chaitanya (Chai) Pydimukkala, and Tim Kirwan (DataDirect
Technologies) for their contributions to this article.

11