Sybase ASE Requirements - DSS 6 | Data Source Solutions Documentation
Documentation: Sybase ASE Requirements - DSS 6 | Data Source Solutions Documentation
Sybase ASE Requirements
This section describes the requirements, access privileges, and other features of Data Source Solutions DSS when using Sybase Adaptive Server Enterprise (ASE) for replication.
Supported Platforms
- Learn about the Sybase ASE versions compatible with DSS on our Platform Support Matrix page (6.1.0, 6.1.5, 6.2.0, and 6.2.5).
Supported Capabilities
- Discover what DSS offers for Sybase ASE on our Capabilities for Sybase ASE page (6.1.0, 6.1.5, 6.2.0, and 6.2.5).
Data Management
-
Learn how DSS maps data types between source and target DBMSes or file systems on the Data Type Mapping page. For the list of the supported Sybase ASE data types and their mapping, see Data Type Mapping for Sybase ASE.
-
Understand the character encodings DSS supports for Sybase ASE on the Supported Character Encodings page.
Supported Editions
DSS supports the following Sybase ASE editions:
- Developer Edition
- Enterprise Edition
- Express Edition
Kerberos Authentication
Before you configure DSS for Kerberos authentication with Sybase ASE, refer to the Sybase ASE documentation for information about how to configure Kerberos for Sybase ASE.
DSS supports two ways for Kerberos authentication:
-
Accessing the kerberized Sybase ASE server with the User and Key Tab parameters supplied. In this case, DSS will run kinit to authenticate itself. To use a keytab file with DSS, enter the details in the User and Key Tab fields of the Location Connection dialog.
Additionally, the following action must be defined for a Sybase ASE location:
Group Table Action Parameter(s) Sybase ASE * Environment Name=KRB5_CONFIG Value=full path to the krb5.conf file -
Accessing the kerberized Sybase ASE server without supplying the User and Key Tab parameters. In this case, the DSS Agent Listener (in case of a remote DSS Agent connecting to Sybase ASE) or the Scheduler (in case of a local DSS connecting to Sybase ASE) should be started from an already Kerberos-authenticated environment.