Required directory service information

When you use JNDI with jConnect, JNDI needs to return the following information for the target database server:

This information needs to be stored according to a fixed format in any directory service used for providing connection information. The required format consists of a numerical object identifier (OID), which identifies the type of information being provided (for example, the destination database), followed by the formatted information (see “Example 1” on page 23).

NoteYou can use the alias name to reference the attribute instead of the OID. See “Example 2” on page 24.

Table 2-3 shows the required formatting.

Table 2-3: Directory service information for JNDI

Attribute description

Alias

OID (object_id)

Interfaces entry replacement in LDAP directory services

sybaseServer

1.3.6.1.4.1.897.4.1.1

Collection point for sybaseServer LDAP attributes

sybaseServer

1.3.6.1.4.1.897.4.2

Version Attribute

sybaseVersion

1.3.6.1.4.1.897.4.2.1

Servername Attribute

sybaseServer

1.3.6.1.4.1.897.4.2.2

Service Attribute

sybaseService

1.3.6.1.4.1.897.4.2.3

Status Attribute

sybaseStatus

1.3.6.1.4.1.897.4.2.4

Address Attribute

sybaseAddress

1.3.6.1.4.1.897.4.2.5

Security Mechanism Attribute

sybaseSecurity

1.3.6.1.4.1.897.4.2.6

Retry Count Attribute

sybaseRetryCount

1.3.6.1.4.1.897.4.2.7

Loop Delay Attribute

sybaseRetryDelay

1.3.6.1.4.1.897.4.2.8

jConnect Connection Protocol

sybaseJconnectProtocol

1.3.6.1.4.1.897.4.2.9

jConnect Connection Property

sybaseJconnectProperty

1.3.6.1.4.1.897.4.2.10

Database Name

sybaseDatabasename

1.3.6.1.4.1.897.4.2.11

High Availability Failover Servername Attribute

sybaseHAservername

1.3.6.1.4.1.897.4.2.15

ResourceManager Name

sybaseResourceManagerName

1.3.6.1.4.1.897.4.2.16

ResourceManager Type

sybaseResourceManagerType

1.3.6.1.4.1.897.4.2.17

JDBCDataSource Interface

sybaseJdbcDataSource- Interface

1.3.6.1.4.1.897.4.2.18

ServerType

sybaseServerType

1.3.6.1.4.1.897.4.2.19

NoteAttributes in italics are required.

The following examples show connection information entered for the database server “SYBASE11” under an LDAP directory service. Example 1 uses the attribute OID. Example 2 uses the attribute alias, which is not case-sensitive. You can use either the OID or the alias.

Example 1

dn: servername=SYBASE11,o=MyCompany,c=US
 servername:SYBASE11
 1.3.6.1.4.1.897.4.2.5:TCP#1#giotto 1266
 1.3.6.1.4.1.897.4.2.5:TCP#1#giotto 1337
 1.3.6.1.4.1.897.4.2.5:TCP#1#standby1 4444
 1.3.6.1.4.1.897.4.2.10:REPEAT_READ=false&PACKETSIZE=1024
 1.3.6.1.4.1.897.4.2.10:CONNECTION_FAILOVER=true
 1.3.6.1.4.1.897.4.2.11:pubs2
 1.3.6.1.4.1.897.4.2.9:Tds

Example 2

dn: servername=SYBASE11,o=MyCompany,c=US
 servername:SYBASE11
 sybaseAddress:TCP#1#giotto 1266
 sybaseAddress:TCP#1#giotto 1337
 sybaseAddress:TCP#1#standby1 4444
 sybaseJconnectProperty:REPEAT_READ=false&PACKETSIZE=1024
 sybaseJconnectProperty:CONNECTION_FAILOVER=true
 sybaseDatabasename:pubs2
 sybaseJconnectProtocol:Tds

In these examples, SYBASE11 can be accessed through either port 1266 or port 1337 on host “giotto,” and it can be accessed through port 4444 on host “standby1.” Two connection properties, REPEAT_READ and PACKETSIZE, are set within one entry. The CONNECTION_FAILOVER connection property is set as a separate entry. Applications connecting to SYBASE11 are initially connected with the pubs2 database. You do not need to specify a connection protocol, but if you do, you must enter the attribute as “Tds”, not “TDS”.