User guide

Glossary
180 Data Integration with Sybase Avaki Studio
DGAS
See data grid access server.
distributed transaction
A set of related operations (typically SQL operations such as SELECT, INSERT, UPDATE, DELETE,
and CALL) that
• involve one or more databases, and
• might lead to unwanted results (such as leaving participating databases in an inconsistent state
or producing inconsistent reads) if some of the operations complete and others do not, and there-
fore
• must all be executed at once, as a single transaction.
The individual operations that make up a distributed transaction are performed by database opera-
tions that use database connectors configured with XA-capable JDBC drivers; all the database opera-
tions are executed, using the two-phase commit protocol, by a specially configured data service. The
two-phase commit protocol is designed to ensure that the participating databases will be left in a con-
sistent state—that is, that all the operations in the distributed transaction will be completed, or none of
them will.
domain name
A unique alphanumeric identifier for an Avaki domain. The domain name is assigned by the Avaki
administrator when the Avaki domain is initialized. The domain name has a maximum length of 30
characters.
enterprise information integration
(EII) A software system that
• enables applications and users to access, without replication, both raw and integrated data from
multiple heterogeneous distributed data sources while hiding the complexity of the data sources,
and
• provides tools enabling users and data owners to further integrate and transform data.
exclusion
See schedule exclusion.
execution service
Execution services execute data services. There is an execution service on every grid server, and you
can configure a pool of execution services for load-sharing. When a pool is in place, a data service
can be run by any execution service in its grid server’s pool.