XACI Command Reference Manual

Chapter 1. Overview of XACI Command Reference
Prev Next
Chapter 1. Overview of XACI Command
Reference
Architecture Overview
General Features and Functionalities
Architecture Overview
The basic purpose of the XABroker Command Line Interface (XACI) is to process the commands that
administer the XABroker. These commands manipulate the XABroker and its transactions for
administrative needs. The target usage of XABroker will be through users of the MXCS. For example,
ODBC/MX, DataDirect SequeLink, and NonStop JDBC Type 4 driver clients. In most usages, the
distributed transaction request is made by an external Transaction Manager (TM) to fulfill the need of an
application that requires to access two different databases under the same logical transaction. Therefore,
the TM is expected to create a transaction context that will be used as an identifier on all subsequent
communications on the connection to the database. Using this transaction identifier (XID), the TM can
commit or rollback all its operations that are bound in the same logical transaction by following the
distributed transaction semantics.
General Features and Functionalities
The important features and functionality of XACI are:
Provides an interactive interface, several scripting interfaces, and an optional log file support.1.
Uses the Config client library to communicate administrative requests to the XABroker product
(does what we need in an easy-to-use way, and it hides some of the implementation which could
change).
2.
Displays the XABroker configuration to an administrator as four separate objects to be managed:
XABroker, XADef, XATrans, and XASession.
3.
Supports administrative actions on the above objects: INFO, ADD, DELETE, KILL, RESOLVE,
RUN, and ALTER.
4.
Prev Up Next
About This Guide
Home Chapter 2. Command Summary
Part Number 543716-002
Legal Notices