Network Router User Manual

196 GINA V4.0 System Administrator Guide – September 2000

Starting and stopping GINA applications

8.3 Starting and stopping GINA applications

8.3.1 Environment variables

Please note that certain environment variables must be set so that GINA applications can

run. These variables are explained in section 3.3.5 on page 21.

8.3.2 Transaction-monitored applications

A GINA application which is based on the T-ORB service is made available by a start pro-

cess. This means that authorized partners can connect to the application following a suc-

cessful start in order to use its functions. The start process itself is implemented by the shell

script utmstart.multi. The script is created during the production process of an applica-

tion with the aid of the conﬁguration generator. Setting the -r option creates the kdcdf

script, whose execution then results in the creation of the start script.

An application is terminated using the administration (see section 8.4 on page 199).

Before a GINA application is started, the database instance with which the application

works must be available. With INFORMIX, this can be achieved using the interactive pro-

gram onmonitor or the program oninit. These programs and the necessary environ-

ment variables are described in [21].

8.3.3 Non-transaction-monitored applications

When using a database with NLS functionality, you must ensure that the appropriate envi-

ronment variables (DBNLS, LANG) are set. A description can be found in [18].

Event Handler

The DomsEventHandler (contained in the bin directory of the GINA installation) must be

available as a daemon process/NT service for all machines running non-transaction-moni-

tored applications. We recommend that this daemon process be started in the boot script.

The DomsEventHandler is required for local communication to the T-ORB/Client applica-

tion; the daemon process informs this application that a message has arrived at the GINA

application. A description of the interoperation of the participating partners can be found in

the Developer Manual [13]. Communication via the Event Handler is based on the TCP/IP

protocol and thus requires one of corresponding entries in the system ﬁle