Required Directory Service Information

Review the required directory service information when using JNDI with jConnect.

JNDI must return this information for the target database server:

A host name and port number to connect to
The name of the database to use
Any connection properties that individual applications are not allowed to set on their own

Stores this information 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.

Note: You can use the alias name to reference the attribute instead of the OID.

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	sybaseVersion	1.3.6.1.4.1.897.4.2.1
Server name	sybaseServer	1.3.6.1.4.1.897.4.2.2
Service	sybaseService	1.3.6.1.4.1.897.4.2.3
Status	sybaseStatus	1.3.6.1.4.1.897.4.2.4
(Required)Address	sybaseAddress	1.3.6.1.4.1.897.4.2.5
Security mechanism	sybaseSecurity	1.3.6.1.4.1.897.4.2.6
Retry count	sybaseRetryCount	1.3.6.1.4.1.897.4.2.7
Loop delay	sybaseRetryDelay	1.3.6.1.4.1.897.4.2.8
(Required)jConnect connection protocol	sybaseJconnectProtocol	1.3.6.1.4.1.897.4.2.9
(Required)jConnect connection property	sybaseJconnectProperty	1.3.6.1.4.1.897.4.2.10
(Required)Database name	sybaseDatabasename	1.3.6.1.4.1.897.4.2.11
High availability failover servername	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

These examples show connection information entered for the database server “SYBASE11” under an LDAP directory service. You can use either the OID or the alias.

Example 1 – uses the attribute OID:

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 – uses the attribute alias, which is not case sensitive:
```
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 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”.