Configuring Database Transliteration Settings

The following sections provide database-specific guidelines and configuration examples for determining and setting transliteration settings.

General Guidelines for Transliteration

The methods for configuring transliteration are database-specific. This section provides general guidelines for transliteration.

DB2

  1. Determine the code page of the DB2 database you want to connect to:

    2. db2 get database configuration for database name

    • If the database code page is 1208 (database code set is UTF-8), use the service template [SequeLink 6.0] DB2 for LUW service (enhanced code page support).
    • For all other database code pages, continue at Step 2.
  2. Use the service template: [SequeLink 6.0] DB2 for LUW service.
  3. If transliteration is required, set ServiceCodePage to OS. No additional configuration is required.

Microsoft SQL Server

Select either the SQL Server or SQL Server (enhanced code page) Service Template. See "Choosing a Service Template" for more information.

For example, use the [SequeLink 6.0] SQL Server (enhanced code page support) Service Template if you want to support national character set data types in your application.

No additional configuration is required.

Oracle

See "Setting Up a SequeLink® Service for Oracle" for an example of configuring an Oracle service.

To configure transliteration to support Unicode and national database character sets:

  1. Create a service using a service template with enhanced code page support. See "Choosing a Service Template" for more information.
  2. Determine the code page of your Oracle database. For example, execute SELECT parameter, value FROM nls_database_parameters where parameter='NLS_CHARACTERSET'.
  3. Set the value of the ServiceEnvironmentVariable service attribute to define the NLS_LANG environment variable to the code page of the Oracle database. For example, ServiceEnvironmentVariable=ITALIAN_WE8MSWIN1252.

Sybase

To configure transliteration in the Sybase environment, you must first identify the installed Sybase Server default character set (refer to the Sybase documentation for information about sp_default_charset). Then select the appropriate service template.

If the character set is...
And the platform is...
The service template is...
This information pertains to Windows.
Not Unicode
Windows/ Linux/UNIX
[SequeLink 6.0] Sybase service
This information pertains to Windows.
Unicode (UTF-8)
Windows
[SequeLink 6.0] Sybase service (enhanced code page support)
No additional configuration is required.
This information applies to Windows and UNIX.
Unicode (UTF-8)
Linux/UNIX
[SequeLink 6.0] Sybase service (enhanced code page support UTF-8)
No additional configuration is required.
This information applies to Windows and UNIX.
Not Unicode or UTF-8
Linux/UNIX
[SequeLink 6.0] Sybase service (enhanced code page support UTF-16)
No additional configuration is required.

If transliteration is required, set ServiceCodePage=OS and use the DataSourceSYBConnectOptions service attribute to specify the code page (see "DataSourceSybConnectOptions").

Transliteration Scenarios

This section provides scenarios for setting up transliteration on Unicode and non-Unicode databases:

Setting Up a SequeLink® Service for DB2 

In this scenario, we set up a SequeLink service to access a DB2 Unicode database on Windows:

  1. Check the database code page to confirm the database code set and database type:

    2. execute "get db cfg for accountdb"

    Database territory
    US
    Database code page
    1208
    Database code set
    UTF-8
    Database country/region code
    1

    The values for the database code set and code page indicate a DB2 Unicode database.

  2. To add a service to the SequeLink Server for DB2, use the [SequeLink 6.0] DB2 UDB LUW service (enhanced code page support).
  3. Start up the [SequeLink 6.0] DB2 UDB LUW service (enhanced code page support).

Setting Up a SequeLink® Service for Oracle

In this scenario, we set up a SequeLink service to access an Oracle9i Unicode database on Linux (en_US).

  1. Determine the code page of the Oracle database. Execute

    2. SELECT parameter, value FROM nls_database_parameters WHERE parameter='NLS_CHARACTERSET'

  2. Because our database is a Unicode database, add a service with service template [SequeLink 6.0]Oracle 10 service (enhanced code page support).
  3. Set the NLS_LANG environment variable to the code page of your Oracle database. For example:

    4. ServiceEnvironmentVariable NLS_LANG=ENGLISH_UNITED KINGDOM.UTF8

  4. Save the new settings in the SequeLink configuration file.
  5. Start the SequeLink service for Oracle.

Setting Up a SequeLink® Service for Microsoft SQL Server

In this scenario, we set up a SequeLink service for SQL Server on Windows with English (United States). Because client and server operating systems have the same regional settings, no transliteration is required.

Add a service with service template [SequeLink 6.0] SQL Server service. The service template sets the ServiceCodePage service attribute to Default, which disables transliteration.

Setting Up a SequeLink® Service for Sybase

In this scenario, we set up a SequeLink service for Sybase on a Solaris (en_US) to access a Greek, non-Unicode, database.

  1. Determine the installed Sybase server default character set (sp_default_charset). Execute:

    2. execute sp_default_charset

  2. Because this is not a Unicode database, add a service with service template [SequeLink 6.0] Sybase service.
  3. Set the ServiceCodePage service attribute to OS.
  4. Look up the Sybase default character set in Table D-11 "Values for DataSourceSybConnectOptions" to determine which DataSourceSYBConnectOptions values to use. For example:

    5. Sybase charset: iso88597

    codepage: ISO8859-7

    IANAAppCodePage: 10

    In this scenario, you add IANAAppCodePage=10 to the DataSourceSYBConnectOptions service attribute as follows:

    DataSourceSYBConnectOptions : IANAAppCodePage=10

  5. Save the new settings in the SequeLink configuration file.
  6. Start up the SequeLink Service for Sybase.