> # Product Requirements

> This section lists the product requirements for:

> - SequeLink Server
> - SequeLink Client for ODBC
> - SequeLink Client for ADO
> - SequeLink Client for JDBC
> - SequeLink Client for .NET
> - SequeLink Manager Snap-in

> For the latest information about the operating system platforms supported for each SequeLink component, go to the following Web URLs:

> For SequeLink Servers:

> http://www.datadirect.com/products/sequelink/matrix/slwebmatrixosvendorview.htm

> For SequeLink Clients:

> http://www.datadirect.com/products/sequelink/matrix/slwebmatrixclients.htm

> ### SequeLink® Server

> The following sections describe the requirements for installing SequeLink Server.

> ####

> #### Windows Server platforms

> - DVD-ROM drive on your Windows server, or a Windows server machine with a DVD-ROM drive and file transfer capability to a supported Windows server.
> - Minimum of 100 MB of free disk space.
> - MMC 1.2 or higher (you can download this software from the Microsoft Web site).

> Table 1-1 lists the databases supported by SequeLink Server on Windows and their requirements.

> Table 1-1. Requirements of Databases Supported by SequeLink Server on Windows
> Database | Database Requirements
> --- | ---
> DB2 UDB v8.x, v9.x | The DB2 CLI client must be installed. Although an earlier version of a client can access a later version of a database, for example, client 8.2 to server 9.1, to insure that you have access to all of the features of a particular database, you should use the client that matches the database version, for example, client 9.1 to server 9.1. All components of the DB2 client software must be installed; otherwise, the driver will not operate properly. The appropriate DLLs and objects must be on your path.
> Informix Dynamic Server 10 | Informix Client SDK 2.90 must be installed. To determine if it has been installed, check the version of the Informix Client SDK in the following file: INFORMIXDIR/release/en_us/0333/ CLIENTREL.TXT where INFORMIXDIR is the INFORMIXDIR environment variable. If this file exists, the Informix Client SDK has been installed.
> JDBC Socket | MDAC 2.7 Service Pack 1 or higher and a configured JDBC driver of your choice.
> Oracle 9i, 10g R2 | By default, SequeLink Server for Oracle uses the Oracle Bequeath protocol to communicate to the Oracle database engine. However, we strongly recommend that you configure the SequeLink Oracle service to use the Oracle Net Service (IPC or TCP protocol) instead. For more information, refer to the SequeLink Administrator's Guide.
> Microsoft SQL Server 2000 and 2005 | MDAC 2.7 Service Pack 1 or higher (32-bit platforms) or MDAC 2.8 or higher (64-bit platforms).
> ODBC Socket | MDAC 2.7 Service Pack 1 or higher (32-bit platforms) or MDAC 2.8 or higher (64-bit platforms). In addition, SequeLink Server for ODBC Socket requires a properly configured ODBC driver that implements the ODBC functions described in "Backend Driver Requirements for SequeLink® Server for ODBC Socket".
> Sybase Adaptive Server 12.5.x and Sybase 15 | MDAC 2.7 Service Pack 1 or higher (32-bit platforms) or MDAC 2.8 or higher (64-bit platforms).

> NOTE: MDAC 2.7 Service Pack 1 is shipped with SequeLink on the DataDirect DVD and can be found in the sqlnk60\mdac\win32 subdirectory.

> #### UNIX Platforms

> - DVD-ROM drive on your UNIX server, or a Windows server machine with a DVD-ROM drive and file transfer capability to a supported UNIX server.
> - TCP/IP.
> - Korn shell. This requirement applies to Linux, which by default is not shipped with a Korn shell.

> Table 1-2 lists the databases supported by SequeLink Server on UNIX and their requirements.

> Table 1-2. Requirements of Databases Supported by SequeLink Server on Linux and UNIX
> Database | Database Requirements
> --- | ---
> DB2 UDB v8.x, v9.x | The DB2 CLI client must be installed. Although an earlier version of a client can access a later version of a database, for example, client 8.2 to server 9.1, to insure that you have access to all of the features of a particular database, you should use the client that matches the database version, for example, client 9.1 to server 9.1. You must have all components of the DB2 client software installed; otherwise, the driver will not operate properly. The appropriate shared libraries and objects must be on your path.
> Informix Dynamic Server 10 | Informix Client SDK 2.90 must be installed. To determine if it has been installed, check the version of the Informix Client SDK in the following file: INFORMIXDIR/release/en_us/0333/ CLIENTREL.TXT where INFORMIXDIR is the INFORMIXDIR environment variable. If this file exists, the Informix Client SDK has been installed.
> JDBC Socket | A configured JDBC driver of your choice.
> ODBC Socket | A configured ODBC driver of your choice. SequeLink Server for ODBC Socket requires a properly configured ODBC driver that implements the ODBC functions described in "Backend Driver Requirements for SequeLink® Server for ODBC Socket". The driver must work correctly with the DataDirect Technologies ODBC Driver Manager.
> Oracle 9i, 10g R2 | By default, SequeLink Server for Oracle uses the Oracle Bequeath protocol to communicate to the Oracle database engine. However, we strongly recommend that you configure the SequeLink Oracle service to use the Oracle Net Service (IPC or TCP protocol) instead. For more information, refer to the SequeLink Administrator's Guide.
> Sybase Adaptive Server 12.5.x and Sybase 15 | None.

> #### z/OS UNIX System Services Platform

> This section lists product requirements specific to SequeLink Server for JDBC Socket for z/OS USS.

> NOTE: If you choose to use and install the JDBC driver from IBM DB2® WebSphere® Classic Federation for z/OS, formerly known as eXadas from CrossAccess, ensure the following maintenance packages are applied: PTF UN08293 and APAR PN13696.

> - A minimum of 1500 tracks for a 3390 device (or equivalent). The amount of disk space required depends on the disk type.
> - IBM z/OS Communications Server.
> - Full z/OS USS support.
> - Any SAF-compliant security system product, such as:
> - IBM RACF V2R1 or higher
> - Computer Associates CA-ACF2 6.0 or higher
> - Computer Associates CA-TOP SECRET
> - A minimum region size of 128 MB.
> - Java SDK 1.4. You can download the Java SDK from the IBM website:

> http://www-1.ibm.com/servers/eserver/zseries/software/java/getsdk14.html

> On the IBM Web site, carefully review the prerequisites.

> #### Backend Driver Requirements for SequeLink® Server for ODBC Socket

> SequeLink Server for ODBC Socket allows ODBC, ADO, JDBC, and .NET applications to connect to any database for which an ODBC 2.0 or 3.0-compliant driver is available.

> In addition to the requirements provided in "SequeLink® Server", SequeLink Server for ODBC Socket requires a properly configured ODBC driver that implements the ODBC functions listed in Table 1-3. On Windows, the ODBC driver must work correctly with the Microsoft ODBC Driver Manager; on UNIX, the driver must work correctly with the DataDirect Technologies ODBC Driver Manager.

> Table 1-3. Required ODBC Function Support for the Third-party ODBC Driver

> SQLAllocHandle SQLBindCol SQLBindParameter SQLBulkOperations SQLCancel SQLColAttribute SQLColumnPrivileges SQLColumns SQLDescribeParam (optional) SQLDisconnect SQLDriverConnect SQLEndTran SQLExecDirect SQLExecute | SQLFetch SQLFetchScroll (optional) SQLForeignKeys SQLFreeHandle SQLFreeStmt SQLGetConnectAttr SQLGetData SQLGetDiagRec SQLGetFunctions SQLGetInfo SQLGetTypeInfo SQLMoreResults SQLNumParams SQLNumResultCols | SQLParamData SQLPrepare SQLPrimaryKeys SQLProcedureColumns SQLProcedures SQLPutData SQLRowCount SQLSetConnectAttr SQLSetEnvAttr SQLSetStmtAttr SQLSpecialColumns SQLStatistics SQLTablePrivileges SQLTables

> #### Checking Your Third-Party JDBC Driver for SequeLink® Server for JDBC Socket

> The ivcheckjdbcdriver utility is unpackaged after you extract the contents of the .tar file. The SequeLink administrator can use the ivcheckjdbcdriver utility to check the third-party JDBC driver environment that will be used behind the SequeLink Server for JDBC Socket.

> Use this utility before configuring the SequeLink Server for JDBC Socket. You must enter the following configuration information:

> - The JRE installation directory
> - The JDBC Driver classpath
> - The driver classname
> - The connection URL of your backend JDBC driver

> When the ivcheckjdbcdriver script has verified these settings and successfully made a connection, you can use these settings for the configuration of your SequeLink Server for JDBC Socket. The utility returns a driver-specific note with information for your environment.

> NOTE: For some drivers, SequeLink provides a wrapper driver with its own Driver name and Connection URL. This wrapper driver fixes incorrect JDBC behavior, provides workarounds for driver deficiencies and optimizes code paths. For the following third-party drivers we strongly advise you to use these wrappers:

> - Websphere Information Integrator Classic Federation for z/OS (also known as CrossAccess or DB2 II Classic Federation)

> Driver name: com.ddtek.jdbc.crossaccess30.CrossAccessDriver

> Connection url: jdbc:dd-crossaccess30:<datasource>:
> tcp/<host>/<port>:CODEPAGE=USS

> - Apache Derby 10 (also known as Cloudscape)

> Driver name: com.ddtek.jdbc.derby10.DerbyDriver

> Connection url: jdbc:dd-derby10

> For more information on the ivcheckjdbcdriver utility, refer to the SequeLink Troubleshooting Guide and Reference.

> ### SequeLink® Client for ODBC

> Windows Client 32-bit platforms:

> Microsoft Data Access Components (MDAC), version 2.7 Service Pack 1 or higher. You can download a utility from the following Microsoft Web site that will report your installed MDAC version:

> http://msdn.microsoft.com/data/downloads/default.aspx

> MDAC 2.7 Service Pack 1 is shipped with SequeLink and can be found in the sqlnk60\mdac\win32 subdirectory (32-bit) on the DataDirect DVD. Alternatively, you can download the appropriate version of MDAC from the Microsoft Web site.

> Windows Client 64-bit platforms:

> Microsoft Data Access Components (MDAC), version 2.8 (64-bit) or higher.

> UNIX:

> No product-specific requirements.

> ### SequeLink® Client for ADO

> Windows Client platforms:

> Microsoft Data Access Components (MDAC) 2.7 Service Pack 1 or higher. You can download a utility from the following Microsoft Web site that will report your installed MDAC version:

> http://msdn.microsoft.com/data/downloads/default.aspx

> MDAC 2.7 Service Pack 1 is shipped with SequeLink and can be found in the sqlnk60\mdac\win32 subdirectory (32-bit) on the DataDirect DVD. Alternatively, you can download the appropriate version of MDAC from the Microsoft Web site.

> ### SequeLink® Client for JDBC

> You can develop applications for SequeLink Client for JDBC using J2SE 1.4.2 or higher and the following APIs, which are supplied with SequeLink Client for JDBC:

> - JDBC 2.0 Optional Package
> - JNDI 1.2
> - JTA 1.0.1

> Table 1-4 lists the product requirements for using SequeLink Client for JDBC.

> Table 1-4. Product Requirements for SequeLink Client for JDBC
> For Applications Using... | Minimum Product Requirements
> --- | ---
> JDBC 3.0 API | J2SE 1.4.2 or higher
> J2EE Connector Architecture | J2SE 1.4.2 or higher
> JSR 114 Rowsets | J2SE 1.4.2 or higher
> JDBC 2.0 Core API | J2SE 1.4.2 or higher
> JDBC 2.0 Optional Package Note that some components have specific requirements: XADataSource DataSource, ConnectionPoolDataSource | J2SE 1.4.2 or higher J2SE 1.4.2 or higher and minimum J2EE 1.2 JNDI 1.2

> NOTE: Standard installations of J2SE on some platforms do not include the jar file containing the extended encoding set that is required to support some of the less common database code pages. To verify whether your J2SE version provides extended code page support, check that charsets.jar is installed in the lib subdirectory of your J2SE installation directory.

> If you do not have the required file, re-install J2SE, making sure that you install the international version of J2SE.

> ### SequeLink® Client for .NET

> Microsoft .NET Framework Redistributable 1.x, available for download on the Microsoft Web site.

> All components should be compatible with .NET applications built to run on the Windows versions listed.

> If you want to use distributed transactions, you must install COM+ Services, which include the Microsoft Distributed Transaction Coordinator (MS DTC).

> ### SequeLink® Manager Snap-in

> The following list describes the product requirements for the SequeLink Manager Snap-in:

> MMC 1.2 or higher (you can download this software from the Microsoft Web site)