Siemens GENERAL INTERFACE FOR NETWORK APPLICATIONS User Manual
Druck vom 24. 01.2001 17:00.14 umschlag
GINA V4.0
General Interface for Network Applications
System Administrator Guide
Comments
Suggestions
Corrections
The User Documentation
Department would like to know
your opinion on this manual.
Your feedback helps us to
optimize our documentation to
suit your individual needs.
Fax forms for sending us your
comments are included at the
back of the manual.
Order number of this manual:
GINA V4.0 System Administrator Guide – September 2000
Druck vom 24. 01.2001 17:00.15 titel
GINA V4.0
General Interface for Network Applications
System Administrator Guide
Edition September 2000
Copyright and Trademarks
GINA is a registered trademark of Siemens Business Services GmbH & Co OHG.
®
Copyright © Siemens Nixdorf Informationssysteme AG 1990.
SINIX
SINIX is the UNIX
®
Reliant
is a registered trademark of Pyramid Technology Corporation.
UNIX is a registered trademark in the United States and other countries, licensed exlusively through
X/Open Company Limited.
Base: OSF/Motif™, Copyright © Open Software Foundation, Inc.
X Window System™, Copyright © Massachusetts Institute of Technology.
OSF/Motif is a registered trademark of Open Software Foundation, Inc.
X Window System is a registered trademark of Massachusetts Institute of Technology.
Copyright © Siemens Business Services GmbH & Co OHG 2000.
All rights reserved.
Delivery subject to availability; right of technical modifications reserved.
All hardware and software names used are trademarks of their respective manufacturers.
®
System derivative of Siemens Nixdorf Informationssysteme AG.
Introduction
Changes since Version 3
Installation and deinstallation
Creating GINA applications
Configuring the Persistency Service
Configuring T-ORB for
Configuring T-ORB for BEATUXEDO
Operating GINA applications
Glossary
Abbreviations
open
UTM
Continued
Related publications
Index
Druck vom 24. 01.2001 17:00.16 verwivz.doc
Contents
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2 Changes since Version 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1 Interface cancelations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.2 Revisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3 Installation and deinstallation . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.2 Scope of supply and structure of GINA . . . . . . . . . . . . . . . . . . . . . . 11
3.2.1 Delivery package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.2.2 Licensing of GINA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.2.3 Directory structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.3.1 UNIX (Solaris, SINIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.3.2 UNIX / HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.3.3 Windows NT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.3.4 BS2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.3.5 Environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.4 Deinstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.4.1 UNIX (Solaris, SINIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.4.2 UNIX / HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.4.3 Windows NT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.5 Availability, restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4 Creating GINA applications . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.1 Application variants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.2 Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.3 The generators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.4 Makefiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5 Configuring the Persistency Service . . . . . . . . . . . . . . . . . . . . . . 31
5.1 Setting up the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
GINA V4.0 System Administrator Guide – September 2000
5.2 Customizing the database layout . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.2.1 The pfx file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.2.2 The tbl file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
5.2.3 Further options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
6 Configuring T-ORB for
open
UTM . . . . . . . . . . . . . . . . . . . . . . . . . 43
6.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
6.2 Configuration language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
6.2.1 Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
6.2.2 Lexical structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
6.2.3 Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
6.3 Revision generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
6.4 Sample configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
6.5 Call and options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
6.6 Generated files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
6.6.1 Generated files for UNIX hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
6.6.1.1 Development option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
6.6.1.2 Runtime option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
6.6.2 Generated files for WindowsNT hosts . . . . . . . . . . . . . . . . . . . . . . . 99
6.6.2.1 Development option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
6.6.2.2 Runtime option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
6.6.3 Generated files for BS2000/OSD hosts . . . . . . . . . . . . . . . . . . . . . . . 101
6.6.3.1 Development option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
6.6.3.2 Runtime option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
6.6.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
6.7 Creating a configuration file using WinConfig . . . . . . . . . . . . . . . . . . . 103
6.7.1 Calling WinConfig . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
6.7.2 Elements of the graphical user interface . . . . . . . . . . . . . . . . . . . . . . 105
6.7.2.1 Host edit window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
6.7.2.2 Application edit window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
6.7.2.3 WinConfig menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
6.7.3 Mouse key assignments and mouse actions . . . . . . . . . . . . . . . . . . . . 153
7 Configuring T-ORB for BEA T
UXEDO . . . . . . . . . . . . . . . . . . . . . . . 155
7.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
7.2 Configuration language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
7.2.1 Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
7.2.2 Lexical structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
7.2.3 Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
7.3 Revision generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
7.4 Sample configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
7.5 Call and options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
GINA V4.0 System Administrator Guide – September 2000
Druck vom 24. 01.2001 17:00.17 verwivz.doc
7.6 Generated files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
7.6.1 Generated files for UNIX hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
7.6.2 Generated files for WindowsNT hosts . . . . . . . . . . . . . . . . . . . . . . . 181
7.6.3 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
7.7 BEA TUXEDO domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
7.7.1 Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
7.7.2 Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
7.7.3 Example of a configuration file with domains . . . . . . . . . . . . . . . . . . . . 188
7.7.4 Generated files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
7.7.5 Special points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
8 Operating GINA applications . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
8.1 Communication administration . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
8.1.1 Communication structure of a server application . . . . . . . . . . . . . . . . . . 193
8.1.2 Communication structure of a client application . . . . . . . . . . . . . . . . . . 193
8.2 DB administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
8.2.1 Security management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
8.2.2 Data backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
8.2.3 Logging database errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
8.3 Starting and stopping GINA applications . . . . . . . . . . . . . . . . . . . . . . 196
8.3.1 Environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
8.3.2 Transaction-monitored applications . . . . . . . . . . . . . . . . . . . . . . . . 196
8.3.3 Non-transaction-monitored applications . . . . . . . . . . . . . . . . . . . . . . 196
8.4 Administering GINA applications . . . . . . . . . . . . . . . . . . . . . . . . . . 199
8.4.1 TP monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
8.4.2 Cyclical timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
8.4.3 Monitoring alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
8.4.4 Cyclical tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
GINA V4.0 System Administrator Guide – September 2000
GINA V4.0 System Administrator Guide – September 2000
Druck vom 24. 01.2001 17:00.18 einleit
1 Introduction
GINA (General Interfacefor Network Applications) provides a framework for the implementation and operation of object-oriented, transaction-oriented client/server applications. The
GINA-API is an object-oriented solution forthe mixed,distributed applicationswhich are encountered everywhere in modern business life.
GINA is suitable for use in many types of client/server environment– for systems which
place high demands on the criteria of data consistency and reliability (business-critical applications) as well as for the rightsizing of mainframe-based systems for decentralized online transaction processing (OLTP).
GINAis based onstandardsand can adaptto individual circumstances.Theobject-oriented
paradigmsavesprogrammingtime andmakessystem structures clearer.Modifications and
corrections are easier. GINA is a high-performance development environment for distributed and persistent objects.
GINA is an open system and provides connectivity to external OLTP systems in a variety of
environments such as the BS2000 or MVS environments.
About this manual
This manual is intended for system administrators who need to install GINA or applications
used by GINA. It describes how the communications system and GINA applications are
configured.
This manual also deals with the operation of GINA applications in client/server environments.
Developers and programmers of GINA applications may also want to refer to this manual
on occasions.
For more information, please contact us at the address below:
Siemens Nixdorf Informationssysteme AG
SBS MPM CPI
Otto-Hahn-Ring 6
81739 München
Fax (089) 636-48 303
E-Mail gina.service@mch20.sbs.de
GINA V4.0 System Administrator Guide – September 2000 1
Structure of this manual
Chapter 1 describes the structure and contents of this manual as well as other docu-
mentation on GINA.
Chapter 2 contains a listing of the essential changes since the last version of this man-
ual as well as a brief description of each.
Chapter 3 Installation and deinstallation
describes the installation of GINA, including prerequisites.
Chapter 4 Creating GINA applications
describes the necessary steps in creating GINA applications.
Chapters 5 ... 8
describe the configuration and administration of GINA applications:
Chapter 5 Configuring the Persistency Service
Chapter 6 Configuring T-ORB for openUTM
Chapter 7 Configuring T-ORB for BEA TUXEDO
Chapter 8 Operating GINA applications
The Glossary and Abbreviations chapters explain important technical terms and abbreviations.
The Related publications section contains a list of manuals and secondary literature.
The table of contents and index simplify the task of finding information.
Documentation on GINA
GINA Introductory Guide
This manual provides a brief summary of the performance characteristics and underlying philosophy of GINA. It also presents the various
components which make up GINA.
GINA
Introductory Guide
It is aimed at decision-makers who want to assess the possible usefulness of GINA or users who intend to work with GINA and want to become familiar with its structure.
2 GINA V4.0 System Administrator Guide – September 2000
Druck vom 24. 01.2001 17:00.18 einleit
G
G
GINA
Developer
Manual
GINA
Reference
Manual
Persist. Service
GINA Developer Manual
This manual is intended for developersof GINA applications. It provides
a detailed description of GINA concepts and gives practical instructions
and assistance for use.You should read this manual first as it describes
the theory and principles on which GINA is based.
Application developers should be familiar with the fundamentals of the
object-oriented paradigm; knowledge of C++ is essential.
INA Reference Manual Persistency Service
This is the manualfor GINA application programmers.It contains formal
descriptions of Persistency Service interfaces set out in alphabetical
order.
It also contains descriptions of the associated tools.
Programmers must be familiar with object-oriented programming and
must be able to program in C++.
They must be familiar with the concepts of the PersistencyService and
Support components which are described in the Developer Manual
INA Reference Manual T-ORB
This is the manualfor GINA application programmers.It contains formal
descriptions of T-ORB interfaces set out in alphabetical order.
GINA
Reference
Manual
T-ORB
It also contains descriptions of the associated tools.
Programmers must be familiar with object-oriented programming and
must be able to program in C++.
They must be familiar with the concepts of the T-ORB and Support
components which are described in the Developer Manual.
The Related publications sections of the manuals listed above also provide references to
related topics.
Ordering manuals
If you would like to order these manuals please contact your local Siemens office.
GINA V4.0 System Administrator Guide – September 2000 3
Notational conventions used in this manual
Thischaracter drawsyourattention to special features orpoints ofinterest; youwill also find
useful or secondary information there. ❍❍●
Particular attention must be paid to the information indicated by this symbol. ❍❍●
Terms that are explained in the text are highlighted in bold.
Program code, messages, keywords or class names are indicated by typewriter text.
Italic typewriter text
Text parts that are to be emphasized are represented by italics.
[1] Numbers in square brackets refer to the Related publications section.
◊ Rhombuses introduce processing statements.
indicates variables for parameters that you must enter.
4 GINA V4.0 System Administrator Guide – September 2000
Druck vom 24. 01.2001 17:00.19 aender
2 Changes since Version 3
2.1 Interface cancelations
The interfaceslisted in the following section werechanged in Version 4.0 of GINA. This version contains the new variant. Each section indicates the GINA version as of which the relevant interface or its old variant is no longer supported.
G_Exception eliminated
In earlier versions, GINA used the exception handling simulation of the Generic++ class
library [11] on some platforms. To facilitate this, the GINA exception classes were derived
internally from the Generic class G_Exception. This derivation process has had to be
eliminated because of a compiler problem.
The message and name methods derivedfrom G_Exception described in the Reference
Manual are omitted from GINA Version 4.0 and later.
OQL
Version 3.0 of GINA sees the introduction ofa new,improvedinterface for databasequeries
which is a subset of ODMG-OQL. Up to this version, the new OQL existed in parallel to the
old one and the user can decide the variant to be used.
Access via the old OQL will be eliminated as of GINA Version 4.0.
Entering special options in the mgen2 and mdiff generators
As of Version 3.3, special options (e.g. noansi, nohinfo) for the mgen2 and mdiff generators can be defined in a file, i.e. you no longer need to specify them individually in the
call. Instead, you reference an existing file using the -k option when you call a generator.
All of the special options can be specified in this file.
As of Version 3.3, special options were supported both as call options and via a special option file. As of Version 4, however, special options will only be read from a file.
GINA V4.0 System Administrator Guide – September 2000 5
Interface cancelations
Changing the names of the iterator methods max/min to maxValue/minValue
The methods max and min in the iterator classes PMibs::MibsFilterIt,
P
Mibs::MibsSeqIt, and VIEWITERATOR(P) were renamed maxValue and minValue
respectively in Version 3.0 of GINA in order to prevent conflicts with the max and min
macros defined in some environments.
The old API containing the method names max and min was supported as a transitional
aid. These methods are inline methods which call the methods maxValue and minValue
respectively. You can suppress these methods explicitly using the GINA_WITHOUT_MINMAX
compiler switch in order to prevent conflicts with macros of the same name.
The method names max and min will be omitted from GINA Version 4.0 and later.
mgen2: Column aliases (mnemonics for SQL) and PS-DB-API
The algorithm for defining the names of the column aliases as well as the parameters for
the functions in the PS-DB-API will be changed as of GINA V5.0.
To avoid name clashes, underscores contained in the names of the specialist attributes will
be doubled. In terms of the PS-DB-API, this change will not affect the GINA user as it is the
datatype of the individual attributes that is the decisive factor there. In terms of column
aliases, this change will affect all SQL queries where a search is to be performed for attributeswith an underscore in theirnames. Theunderscores in the relevantattribute names
must then simply be doubled.
C runtime libraries under WindowsNT
Version 4.0 and above will be shipped with multithreaded libraries only.
6 GINA V4.0 System Administrator Guide – September 2000
2.2 Revisions
Revisions
Druck vom 24. 01.2001 17:00.19 aender
Replacement of idlgen by idlgen1
The idlgen1 generates two definitions from an interface definition (x.idl) specified in
CORBA-IDL (Revision 2.2): x.hi which defines the data members to be encoded and
decoded and x.hd which defines the methods to be exported. The interim format x.hi
serves as input for the MIO generator miogen2. The interim format x.hd serves as input
for the T-ORB generator dogen2.
GINA V4.0 System Administrator Guide – September 2000 7
Revisions
8 GINA V4.0 System Administrator Guide – September 2000
Druck vom 24. 01.2001 17:00.19 install
3 Installation and deinstallation
This chapter describes how to install and deinstall GINA. Some of the technical information
given here is for the purposes of example only, e.g. it may vary partially depending on the
details of the operating system.
The current version of GINA can run under:
– UNIX-SVR4
– BS2000/OSD (under special release)
– WindowsNT
– Windows95/98
Further information on your respective system base can be found in the Release Notice
supplied with GINA. Please read this Release Notice carefully. ❍❍●
GINA V4.0 System Administrator Guide – September 2000 9
Requirements
3.1 Requirements
The following third-party products are required to implement the GINA components.
Please note that the products listed may be based on other products, which must then likewise be installed. Up-to-date information on the products required can be found in the Release Notice included in the delivery. ❍❍●
● Generic++ V2.5 [11]
GINA requires the class library Generic++ V2.5, which is contained in the GINA scope
of supply and is installed under the name libsupport2.
●
open
For communication and transaction monitoring, the T-ORB server uses the TP monitor
UTM. GINA Version 4.0 requires UTM Version
V5.0 or later [29].
To connect non-transaction-monitored applications (T-ORB client) to a transactionmonitored server, the CPIC interface is used.
This requires the product
UTM V5.0 and
open
UTM-Client V5.0
open
open
UTM (UNIX, NT, BS2000/OSD)
UTM-Client (UNIX, NT) V5.0A or later [36].
The software component UTM-D is also required when using GINA with BS2000.
● INFORMIX Dynamic Server 2000 (IDS.2000) V9.2
The Persistency Service in GINA V3.3 uses INFORMIX as the data storage system.
INFORMIXDynamic Server2000 [19] (UNIX & NT)and Client SDK 2.40 (UNIXand NT)
are required.
The XA interface[5] is required forthe integrated useof T-ORB and the PersistencyService. This interface is only integrated under UNIX in V9.2. Detailed information on coupling T-ORB and the Persistency Service under WindowsNT can be found in chapter 6,
Compiling and linking, of the Developer Manual [13].
10 GINA V4.0 System Administrator Guide – September 2000
Scope of supply and structure of GINA
3.2 Scope of supply and structure of GINA
Druck vom 24. 01.2001 17:00.20 install
This section describes the delivery packages and the general delivery structure of GINA
Version 4.0.
3.2.1 Delivery package
GINAV4.0 is supplied as a full-feature version (UNIX, NT) and as a partial version (WindowsNT only). The full-feature version contains the following GINA components:
● Persistency Service development, runtime system and PS browser
The development system of the PersistencyService comprises the generators mgen1,
mgen2, mgendb, mspgen2 and mdiff, the runtime system comprises the libraries of
the Persistency Service and the Persistency Service/client.
The PS browser comprises the components bruno and cuno.
● T-ORB development and runtime system
The development system of T-ORB comprises the generators config, miogen1,
miogen2, dogen1, dogen2 and idlgen, the runtime system comprises the libraries
of T-ORB and T-ORB/client.
● Support runtime system
The runtime system of the Support component comprises two libraries, one of which
contains support functions for T-ORB and the Persistency Service and the other of
which makes available the valid Generic++ class library.
The partial version under WindowsNT contains only the runtime environment (RT version)
for a T-ORB client. It is also prepared for use under Windows95 and Windows98. More detailed information can be found in the Release Notice included with the relevant version of
GINA.
The delivery medium is a CD.
GINA V4.0 System Administrator Guide – September 2000 11
Scope of supply and structure of GINA
3.2.2 Licensing of GINA
The tool FLEXlm from the company GLOBE
erators and the GINA runtime system are protected by licenses.
Before GINA can be used, the GINA Competence Center must generate the licenses for
the machine you require (processor ID) and convey them to you.
If you require an evaluation license, refer to the Release Notice for a template which you
must return completed to the GINA Competence Center.
Installing licenses
Store the license entries received from the Competence Center in the file
GinaLicense.dat. This file isa textfile. All machines where GINA is installedmust be able
to access this file. The environment variable LM_LICENSE_FILE must be set on each of
these machines. This variable contains the path and the name of the license file.
trotter
is used to license GINA. Both the gen-
Example (UNIX, csh)
setenv LM_LICENSE_FILE /home/usr/license/Ginalicense.dat
If the file already existson your machine, insert in file license.dat the lines of relevance
to GINA.
You can also specify several license files:
Example (UNIX, csh)
setenv LM_LICENSE_FILE /home0/GinaLicense.dat:/home1/GinaLicense.dat
12 GINA V4.0 System Administrator Guide – September 2000
Structure of the license file
Scope of supply and structure of GINA
Druck vom 24. 01.2001 17:00.20 install
The license file has the following structure:
Keyword License DaemonVer- Valid N License Proces- License-
sion code sor ID name
Example
FEATURE GinaDEV ginad 1.000 1-jan-0 0 C2348347 2387823 "Gina license"
Keyword Keyword for FLEX
License Type of license used
(GinaDEV, GinaRTS, TorbDEV, TorbRTS, PsDEV, PsRTS,
TorbClient, PsClient)
Daemon Name of the license daemon
Version Version number
Valid Date until which the license is valid
N Number of licenses (0 = unrestricted license)
License code 20-digit license code
Processor ID Processor ID which is assigned to the license code
License name Name of the license
lm
GINA V4.0 System Administrator Guide – September 2000 13
Scope of supply and structure of GINA
3.2.3 Directory structure
bin
doc
include
java
lib
template
Generators of the PS development system
Generators of the T-ORB development system
text
psbrowser
Release notice
Online documentation of the PS browser
doms
mibs
psc
support
support2
trace
usr
directory for the PS browser
Libraries of the PSund PS /client runtime system and PS browser
Libraries of the T-ORB runtime system
Libraries of the Support runtime system
comment
scr
Note
comment is a directory containing code templates
used by the generators dogen2 and idlgen1.
src contains code templates for the user outputs of
the T-ORB
The illustration shows the GINA default directory structure. The actual structure may differ
from that shown above.
You should thereforestudy the Release Notice, whichcan also be found under the file name
readme.
Version
in the doc directory. ❍❍●
14 GINA V4.0 System Administrator Guide – September 2000
Druck vom 24. 01.2001 17:00.21 install
Installation
3.3 Installation
The installation procedures depend on the system base. The variants described here are
examples only.
You must always perform installation and deinstallation in accordance with the description
of your system base or the information in the Release Notice. ❍❍●
GINA is shipped as a package which is created using a system-specific packet assembly
procedure (package under UNIX, setup under NT). The full-feature version of GINA V4.0
under UNIX is divided up into subpackages so that you do not have to install the entire product folder. The functional scope of a full-feature version can only be achieved by installing
all of the subpackages.
The names and contents of the subpackages as well as the order in which they must be
installed can be found in the Release Notice.
Depending on the selected variant, GINA builds on standard products (
open
UTM, INFORMIX).These mustbe installed usingtheir owninstallation procedures andare notdescribed
here.
If the GINA package is stored on the delivery CD as a file in compressed format, it must be
copied to an intermediate directory and unpacked prior to installation (refer to the description for the relevant platform).
Thefollowingactions, for example, must be carried out to install GINA itself on theplatforms
listed below.
GINA V4.0 System Administrator Guide – September 2000 15
Installation
3.3.1 UNIX (Solaris, SINIX)
Start the installation under UNIX using the command pkgadd.
The installation directory in which GINA is to be installed may not exist before the pkgadd
command is called. ❍❍●
1. Log in as root.
2. Set up a new user group
3. Set up a new user
4. Create a new directory e.g. /opt/gina for GINA:
mkdir -p /opt/gina
chmod 775 /opt/gina
chown gina:tmns /opt/gina
5a. Insert the GINA delivery CD in the CD drive and install the uncompressed GINA pack-
age using the following command:
pkgadd -d <
You are then prompted to do the following:
◊ Select the GINA subpackage to be installed.
◊ Specify the directory in which GINA is to be installed,
e.g. /opt/gina/
◊ Define users for this and the directories below:
e.g.
e.g.
◊ Specify the source directory from which GINA is installed.
<
CD drive directory
CD drive directory
gina
tmns
as userid (default: root)
as groupid (default: root)
gina
GINA
tmns
.
>
.
>/<
gina package file name
>
The GINA package is then installed under /opt/gina/
created and the structure filled with the files.
16 GINA V4.0 System Administrator Guide – September 2000
GINA
, the directory structure
Druck vom 24. 01.2001 17:00.21 install
Installation
5b. The following steps are required if the GINA package is stored on the delivery CD in
compressed format:
◊ Copy the GINA package from the CD to an intermediate directory
cp <
CD drive directory
directory name
>
◊ Unpack the file in the intermediate directory using gunzip.
◊ Install the unpacked GINA package
>/<
gina package file name
>.gz <
intermediate
pkgadd -d <
You are then prompted to do the following:
◊ Select the GINA package to be installed.
◊ Specify the directory in which GINA is to be installed,
e.g. /opt/gina/
◊ Define users for this and the directories below:
e.g.
gina
e.g.
tmns
◊ Specify the source directory from which GINA is installed.
<
intermediate directory name
The GINA package is then installed under /opt/gina/
created and the structure filled with the files.
3.3.2 UNIX / HP-UX
See UNIX (Solaris, SINIX) on page 16 for steps 1 through 4.
5. Insert the GINA delivery CD into the CD drive and install the uncompressed GINA pack-
age using the following command:
intermediate directory name
GINA
as userid (default: root)
as groupid (default: root)
>/<
gina package file name
>/<
gina package file name
>
GINA
, the directory structure
>
swinstall
The swinstall command opens a menu interface via which the aforementioned information is queried.
The GINA package is then installed, the directory structure created and the structure
filled with the files.
GINA V4.0 System Administrator Guide – September 2000 17
Installation
3.3.3 Windows NT
Installationof the full-featureorpartialversion(RTversion) under WindowsNTis performed
using the setup command, the installation tool is included in the GINA package on the
delivery CD.
1. Log in as administrator.
2. Create a new directory for GINA.
3. Insert the GINA delivery CD in the CD drive andstart thegraphical installation interface
using the command
<
drive
The dialog box which is displayed queries the path of the installation directory and the
components to be installed.
The GINA package is then installed, the directory structure created and the structure
filled with the files.
If, during installation, you selected GINA packages containing the services
DomsEventHandler and DomsDynConnectHandler, they will be automatically activated
the next time the system starts (under WindowsNT only).
Further information on this can be foundin the DeveloperManual [13] in thesection entitled
Compiling and linking, Special features under Windows NT. ❍❍●
>:\setup
If you intend to run GINA on a machine without a network link, you must set the
LM_NO_NETWORK environment variable in order to avoid the wait times resulting from futile
attempts to access a license server. ❍❍●
Special points in relation to the operation of the GINA PS browser
Beforethe GINA PS browseris called (on UNIX platforms), the directory in which the GINA
phases were installed must be included in the PATH environment variable.
Example for csh
sentenev PATH <gina_install_dir>/:$PATH
Furthermore, the environment variable LD_LIBRARY_PATH (for Solaris, SINIX) or
SHLIB_PATH (for HP-UX) must contain the file in which the GINA library is located.
18 GINA V4.0 System Administrator Guide – September 2000
Loading...