UAKGQuery is a CORBA service which proviades CORBA API for access to relational database. This release supports Oracle as relational database.
Using UAKGQuery is possible to organize effective and uniform data access from different sources in heterogene computing environment.
If you want to use transactional features of UAKGQuery, ORBacus
Transaction service and OOC 1 ORBacus ORB is needed.
Note: transactional features are absent subject to UAKGQuery
has been compiled for Windows NT.
env_inc.nt.mak and set next varibles in it:
\CosQuery.1
--with-ots - if you want to use CORBA Transaction Service.
--with-ob-xa - if you want to use XA extensions of CORBA Transaction Service .
--toolbox=<path-to-toolbox> - if you installation directory of
GradSoft C++ toolbox differs from installation directory of UAKGQuery
(default is /usr/local)
./configure --help to see list of all possible options.
After installation next files will be installed into INSTALL_DIR
directory (which is defined as variable INSTALL_DIR in NT Makefile
or as configuration parameter prefix for UNIX)
<install-dir>/idl
You must set network port for requests listening in Server configuration parameters.
The way of doing this is ORB-depended, it can be done from server command line or from ORB configuration file: consult with your ORB manual for details.
Below is list of such options for common object request brokers:
-OAport <port> or property ooc.iiop.port in
configuration file.
-ORBpoa_iiop_port <port>
-ORBport <port>
-ORBEndPoint iiop://:<port>
Another precondition for succesfull service start is existance of installed Oracle8 client in working environment.
UAKGQuery use standart UNIX syslog interface for logging. So, consult with you operation system documentation for details, next example will work with most of supported UNIX systems:
!UAKGQueryService *.* /var/log/UAKGQuery.log # in addition call administrator on fatals. *.fatal |mail -s "UAKGQuery fatal" admin@his.cell.phone.kiev.ua
/var/log/UAKGQuery.log
In addition you can dup log output to file of to stderr by setting options of UAKGQueryService.
--ior-file-UAKGQueryService <fname> - write ior of UAKGQueryService to file with name fname.
--ior-stdout - output QueryService IOR to standart program output
--with-naming - register UAKGQueryService in CORBA Naming Service (note, that CosNaming initialization parameters must be aviable to ORB) .
--config <fname> - read configuration from file with name fname.
--ORACLE_XA <xa_string> - use Oracle XA transaction Oracle.
This option is aviable only for UNIX in the case of server was compiled with XA support.
--log-to-file <fname> - dup log output to file <fname>
--log-to-strerr - dup log output to UAKGQuery stderr.
--log-sql - log processed SQL sentences.
--no-syslog - does not use syslog for logging.
When you start ordinary UQAKGQuery client, which receive reference on UAKGQuery via resolving of initial references, you can use next command line parameters for client ORB:
-ORBInitRef UAKGQueryService=\
corbaloc::srv-host-name:port/UAKGQueryService
where: