Java Connection Management  JDBC 2.0 extension/JTA drivers

Chapter 7: Load Balancing, Failover, and Component Availability

JDBC 1.0 and 2.0

Set up jConnect to access LDAP and JNDI with JDBC 1.0 and JDBC 2.0 connections by:


Configuring LDAP

To configure LDAP, run your server with JDK 1.3 and use your LDAP software to set up an LDAP entry of this form. In this example, primary_server is the name of the high availability (HA) primary server, secondary_server is its secondary server, and host and port are the host name and port number of the machine on which the database server runs.

dn: sybaseServername=primary_server, dc=sybase, dc=com
sybaseServername: primary_server
sybaseAddress: TCP#1#host port
sybaseHAservername: sybaseServername=secondary_server
sybaseJconnectProperty: REQUEST_HA_SESSION=true
sybaseJconnectProperty: Tds
objectclass: sybaseServer

dn: sybaseServername=secondary_server, dc=sybase, dc=com
sybaseServername: secondary_server
sybaseAddress: TCP#1#host port
objectclass: sybaseServer

Configuring a connection cache

Use EAServer Manager to configure the connection cache with these values for the specified properties:

To specify additional properties that EAServer uses for LDAP server configuration, create a <cache_name>.props file in the $JAGUAR/Repository/ConnCache directory, and set these property values:

java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory
java.naming.factory.object=com.sybase.jdbc2.jdbc.SybObjectFactory
java.naming.provider.url=ldap://duplo:389/dc=sybase,dc=com

where duplo:389 is the port where the LDAP server is running. The values listed for the first two properties are the defaults used by EAServer.





Copyright © 2005. Sybase Inc. All rights reserved. JDBC 2.0 extension/JTA drivers

View this book as PDF