Chapter 7: Load Balancing, Failover, and Component Availability

JDBC 2.0 extension/JTA drivers

Set up JDBC 2.0 extension / JTA drivers by:

When failover occurs, EAServer supports XA transactions only if they are in the prepared state. XA transactions in any other state are lost. For information on transactions, see Chapter 2, “Understanding Transactions and Component Lifecycles,” in the EAServer Programmer’s Guide.

Configuring LDAP

Using your LDAP software, set up an LDAP entry of this form:

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

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

Configuring an XA resource

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

User Name – the database user name.
Password – the database password.
Connection URL (Server Name) – LDAPLOOKUP=sybaseServername=primary_xa_server.
Driver (DLL or Class Name) – com.sybase.jdbc2.jdbc.SybXADataSource.

Create a <cache_name>.props file in the $JAGUAR/Repository/ConnCache directory, and set this property value, where duplo:389 is the port where the LDAP server is running:

java.naming.provider.url=ldap://duplo:389/dc=sybase,dc=com

View this book as PDF