|
|
1.1 root 1: .TH ISOENTITIES 5 "31 May 1988"
2: .\" $Header: /f/osi/support/RCS/isoentities.5,v 7.0 89/11/23 22:27:31 mrose Rel $
3: .\"
4: .\"
5: .\" $Log: isoentities.5,v $
6: .\" Revision 7.0 89/11/23 22:27:31 mrose
7: .\" Release 6.0
8: .\"
9: .SH NAME
10: .B isoentities
11: \- ISODE entities database
12: .SH DESCRIPTION
13: The \fIisoentities\fR file contains information regarding the known
14: application-entity titles (AETs).
15: This file is used by the stub\-directory service in ISODE.
16: .PP
17: Entries are separated by blank lines (or the end\-of\-file).
18: Items are separated by any number of blanks and/or tab characters,
19: though double\-quotes may be used to prevent separation between arguments.
20: The character `#' at the beginning of a line indicates a comment line.
21: .PP
22: Each entry consists of four items:
23: the first two,
24: the designator and qualifier,
25: for the object descriptor of the application-entity information
26: (the distinguished designator \*(lqdefault\*(rq is used for a template entry);
27: the third item is the object identifier of application-entity
28: information in dot-notation
29: (if no application-entity information is desired the string
30: \*(lqNULL\*(rq should be used instead);
31: and the fourth item is the entire presentation address expressed using
32: the ISODE string format.
33: Note that since double-quotes are often used in the new string format,
34: it is \fBvery\fR important to quote them correctly in the
35: \fIisoentities\fR file.
36: Usually preceeding the first character of the address with single backslash
37: is adequate.
38: .PP
39: It is suggested for readability purposes that a blank line should
40: seperate entries.
41: .PP
42: Note that this database is used by the stub-directory service in ISODE.
43: A real directory uses an entirely different mechanism for resolving lookups.
44: The stub-directory mechanism in ISODE transforms the internal AET
45: notion (the object identifiers) into one which appears to have come
46: from a real directory (i.e., application-entity information).
47: .SH "RFC1085 SUPPORT"
48: Since applications using RFC1085 (the lightweight presentation protocol)
49: usually demultiplex on the basis of TCP or UDP port,
50: a further definition for the qualifier is placed in
51: \fI/etc/services\fR,
52: one of:
53: .sp
54: .in +.5i
55: .nf
56: qualifier portno/lpp
57: qualifier portno/tcp
58: qualifier portno/udp
59: .fi
60: .in -.5i
61: .sp
62: The first alternative says that the service lives on both TCP and UD;
63: the second alternative says that the service lives on TCP only;
64: and,
65: the third alternative says that the service lives on UDP only.
66: .SH FILES
67: .nf
68: .ta \w'\*(EDisoentities 'u
69: \*(EDisoentities ISODE entities database
70: .re
71: .fi
72: .SH "SEE ALSO"
73: isobjects(5), isoservices(5),
74: .br
75: \fIThe ISO Development Environment: User's Manual, Volume 1:
76: Application Services\fR, \*(lqThe ISODE Entities Database\*(rq.
77: .SH AUTHOR
78: Marshall T. Rose
79: .br
80: with design conceptualization by Stephen E. Kille, University College London.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.