ISOENTITIES(5)

NAME
isoentities - ISODE entities database

DESCRIPTION
The isoentities file contains information regarding the known application-entity titles (AETs). This file is used by the stub-directory service in ISODE.

NB : Use of this database is deprecated. Consult the ISODE User's Manual for further information.

Entries are separated by blank lines (or the end-of-file). Items are separated by any number of blanks and/or tab characters, though double-quotes may be used to prevent separation between arguments. The character `#' at the beginning of a line indicates a comment line.

Each entry consists of four items: the first two, the designator and qualifier, for the object descriptor of the application-entity information (the distinguished designator “default” is used for a template entry); the third item is the object identifier of application-entity information in dot-notation (if no application-entity information is desired the string “NULL” should be used instead); and the fourth item is the entire presentation address expressed using the ISODE string format. Note that since double-quotes are often used in the new string format, it is very important to quote them correctly in the isoentities file. Usually preceeding the first character of the address with single backslash is adequate.

It is suggested for readability purposes that a blank line should seperate entries.

Note that this database is used by the stub-directory service in ISODE. A real directory uses an entirely different mechanism for resolving lookups. The stub-directory mechanism in ISODE transforms the internal AET notion (the object identifiers) into one which appears to have come from a real directory (i.e., application-entity information).

RFC1085 SUPPORT
Since applications using RFC1085 (the lightweight presentation protocol) usually demultiplex on the basis of TCP or UDP port, a further definition for the qualifier is placed in /etc/services, one of:

qualifier    portno/lpp
qualifier    portno/tcp
qualifier    portno/udp

The first alternative says that the service lives on both TCP and UD; the second alternative says that the service lives on TCP only; and, the third alternative says that the service lives on UDP only.

FILES
isoentities	ISODE entities database

SEE ALSO
isobjects(5), isoservices(5),
The ISO Development Environment: User's Manual, Volume 1: Application Services, “The ISODE Entities Database”.

AUTHOR
Marshall T. Rose
with design conceptualization by Stephen E. Kille, University College London.