Download M2M AD301 User guide

Glossary
CIFS share
A directory or file that has been exported (shared) from the Avaki data catalog. A CIFS share can be
mapped into a Windows file system like a network drive. When you browse the Windows file system,
CIFS shares look like—and can be accessed like—other files and directories. CIFS shares are created
through a data grid access server. Contrast with Avaki share.
client
Avaki supports several types of client: Avaki Studio, CIFS clients, command clients, JDBC/ODBC clients, NFS clients, web clients, and WS clients.
command client
A machine that can issue Avaki commands but does not contribute resources to the Avaki domain.
connect port
The connect port on a grid domain controller, grid server, data grid access server, proxy server, or
share server accesses the JNDI naming service or RMI registry for the underlying application server.
The connect port is one of many ports that a GDC or server uses to communicate with other Avaki
objects. You must supply the connect port number of a target grid server or GDC whenever you connect a new object (another server, a copy of Avaki Studio, or a command client, for example) to an
Avaki domain. When you interconnect two Avaki domains, you must supply each domain’s connect
port number to the other one.
data catalog
A hierarchical structure similar to a file system that encompasses all objects in an Avaki domain. The
data catalog contains Avaki directories and files, Avaki shares, Avaki servers, SQL views, database
operations and data services, and other objects.
data grid access server
(DGAS) An Avaki server that makes Avaki directories and their contents available to CIFS clients and
NFS clients.
178
Data Integration with Sybase Avaki Studio