Appendix B Repository Properties Reference
Connection
cache property names begin with com.sybase.jaguar.conncache
.
In Jaguar Manager, configure connection cache properties in the
Connection Cache Properties dialog box.
In addition to the properties described here, you can configure additional properties for JDBC and Client-Library caches. See "All Properties tab" for more information.
Specifies whether components can use this cache by specifying the cache name alone.
true
or false
.
The default is false
.
To access a cache from an aliased JNDI reference, this property must be true.
In Jaguar Manager, set this property using the Allow By-Name Access check box on the Cache tab in the Connection Cache Properties dialog box.
com.sybase.jaguar.component.resource-ref,
com.sybase.jaguar.webapplication.resource-ref
Specifies the number of connections kept open in the cache.
A positive integer.
The cache size specifies the number of connections kept open in the cache. At times, more connections may be open than the size allows if additional connections are required. However, excess connections are deallocated and not returned to the cache.
In Jaguar Manager, set this property in the Number of Connections in Cache field on the Cache tab in the Connection Properties dialog box.
Specifies the query to use when testing whether a connection is still useable.
The SQL query text. The default is:
select 1The default does not work on all databases. For example, for an Oracle database, you must set this property to:
select 1 from dual
To set this property in Jaguar Manager, use the All Properties tab in the Connection Cache Properties dialog box.
com.sybase.jaguar.conncache.checkallowed
Specifies whether the cache manager should test connections before returning them to the cache.
true
or false
.
The default is false
.
The query used to test the cache is specified by the com.sybase.jaguar.conncache.check property.
To set this property in Jaguar Manager, use the Enable connection sanity check option on the Cache tab in the Connection Cache Properties dialog box.
com.sybase.jaguar.conncache.check
Specifies the DLL, shared library, or JDBC driver class name used in the connection.
The syntax is the same as the DLL or Class Name field on the Driver tab in the Connection Cache Properties dialog box. See "Driver properties".
Specifies the type of connection cache.
Your choices for library type are:
| Value | To indicate |
|---|---|
| CTLIB_110 | Sybase Open Client Client-Library connections |
| ODBC | Connections using an open database connectivity driver |
| JDBC | Connections using Java Database Connectivity driver |
| OCI_7 | Connection using OCI 7.x |
| OCI_8 | Connections using OCI 8.x |
In Jaguar Manager, set this property on the Cache tab in the Connection Cache properties dialog box.
Specifies an optional text description of the cache.
desc
Where desc is the descriptive text.
In Jaguar Manager, set this property in the Description field on the General tab in the Connection Cache properties dialog box.
Specifies whether to use a high availability connection.
true
or false
.
The default is false
.
In Jaguar Manager, set this property on the Driver tab in the Connection Cache properties dialog box. The property is available only for Client Library 11.0 connections.
Specifies the cache name.
The cache name as displayed in Jaguar Manager.
Specifies the password for connections in the cache.
The password text. Values are encrypted in the repository.
In Jaguar Manager, set this property in the Password field on the General tab in the Connection Cache Properties dialog box.
com.sybase.jaguar.conncache.username
For JDBC caches that use Sybase jConnect for JDBC to connect to a Sybase DirectConnect gateway, specifies the back-end data server name that the DirectConnect gateway connects to.
This property is ignored for caches that use JDBC drivers other than jConnect.
The remote server name.
In Jaguar Manager, set this property using the Service Name field on the Cache tab in the Connection Cache Properties dialog box.
Enables set-proxy support for connections to databases that support this feature.
true
or false
.
The default is false
, which
disables set-proxy support.
Current versions of Adaptive Server Enterprise and Adaptive Server Anywhere allow a user to assume the identity and privileges of another user. Except for Oracle connections that use OCI, you can use this feature with any database that recognizes this command:
set session authorization "login-name"
When proxy support is enabled, connections retrieved from the cache are set to act as a proxy for the user name associated with the EAServer client. To set proxy to another user name, use the Java JCMCache.getProxyConnection() method or the C JagCmGetProxyConnection() routine in your component.
The user name specified in the cache properties (com.sybase.jaguar.conncache.username) must have set-proxy privileges in the database and/or server used by the cache.
In Jaguar Manager, set this property using the All Properties tab in the Connection Cache Properties dialog box.
com.sybase.jaguar.conncache.username
Specifies the user name for connections in the cache.
The user name.
In Jaguar Manager, set this property using the User name field on the General tab in the Connection Cache Properties dialog box.
com.sybase.jaguar.conncache.password.e
| Copyright © 2002 Sybase, Inc. All rights reserved. |
| |