User guide

Glossary
182 Data Integration with Sybase Avaki Studio
grid server
An Avaki server that maintains a portion of the Avaki domain’s namespace, runs Avaki services such
as shares, execution services, caches, and searches, and allows you to run Avaki’s web UI and execute
Avaki commands.
group
See Avaki group.
hard link
Provides an alternate name for an item in the data catalog. Changes to the object’s other names have
no effect on the hard link: you can move or change a file’s original name and the hard link will still
know where to find the file. To delete a hard-linked object, you must remove its original name. Con-
trast with soft link.
interconnect
To create a unidirectional link from one Avaki domain to another. Interconnecting lets an Avaki
domain make its data catalog visible to users in another domain (subject to Avaki access controls).
JDBC driver
JDBC (Java Database Connectivity) drivers allows application programmers to access database data
shared in the data catalog. When a JDBC driver accesses data, it returns a JDBC result set that’s
immediately available to your program. JDBC drivers can:
• Call any data service in the data catalog
• Call any database operation in the data catalog
• Perform SQL select operations against SQL views in the data catalog
Sybase offers three JDBC drivers for use with Avaki EII software:
• The included Avaki JDBC driver
• jConnect, Sybase’s standard JDBC driver
• An XA-capable driver for use with database connectors that support distributed transactions
link
See hard link and soft link.
local cache
A cache service that runs on the same grid server as a database operation or a data service that gen-
erates cachable data. The local cache stores results produced by local database operations and data
services so they don’t have to execute for every new request. See also remote cache.