[ver]
	4
[sty]
	
[files]
[charset]
	82
	ANSI (Windows, IBM CP 1252)
[revisions]
	0
[master]
	C:\SSPG\ch1toc.SAM
	
	0
	0
	0
[sequence]
	6
	0
	0
	0
	20
	8
	Numbered list
	0
	Bullet
	0
	Indnt bullet
	0
	Indnt caution
	0
	Indnt tip
	0
	Indnt note
	0
	Caution
	0
	Tip
	0
	Note
	0
	Browse
	0
	Keyword
	0
	Context
	0
	Title
	0
	Macros
	0
	Alink
	0
	Butnbar
	0
	Window
	0
	Win95 macros
	0
	Win31 macros
	0
	Build tag
[prn]
	Apple LaserWriter II NT
[port]
	LPT2:
[lang]
	1
[fldnames]
	Field1
	Field2
	Field3
	Field4
	Field5
	Field6
	Field7
	Field8
[desc]
	
	
	
	
	
	801442266
	22
	792458400
	1961
	8
	0
	0
	0
	0
	
	
	
	
	
	
	1
[fopts]
	0
	1
	0
	0
	
	
[lnopts]
	2
	Body Text
	1
[docopts]
	5
	2
[GramStyle]
	
[ParaNum]
	1
[tag]
	Body Text
	2
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		100
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Body Text
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Ahead
	3
	[fnt]
		Arial
		220
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		240
		4
		79
		0
		3
		100
	[brk]
		112
	[line]
		16
		2160
		3
		0
		1
		1
		1
		65
		10
		1
	[spec]
		0
		1
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		wr
	Body Text
	0
	0
[tag]
	Bhead title
	4
	[fnt]
		Arial
		200
		0
		16385
	[algn]
		1
		1
		0
		0
		0
	[spc]
		40
		220
		4
		79
		0
		3
		100
	[brk]
		80
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		2
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		wr
	Body Text
	0
	0
[tag]
	Chead title
	5
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		79
		0
		3
		100
	[brk]
		112
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		3
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		wr
	Body Text
	0
	0
[tag]
	Bhead
	6
	[fnt]
		Arial
		200
		0
		16385
	[algn]
		1
		1
		0
		0
		0
	[spc]
		40
		220
		4
		180
		0
		3
		100
	[brk]
		68
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		2
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Body Text
	0
	0
[tag]
	Chead
	7
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		100
		0
		3
		100
	[brk]
		68
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		3
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Body Text
	0
	0
[tag]
	Numbered list
	8
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		300
		300
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		5
		<*:>.
		0
		3
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Numbered list
	0
	0
[tag]
	1st lev para
	9
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		300
		0
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		68
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	1st lev para
	0
	0
[tag]
	Bullet
	11
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		120
		180
		180
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		</U>
		0
		3
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Bullet
	2
	1
	160
	1
	400
	0
[tag]
	Indnt bullet
	12
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		420
		180
		180
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		16
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		</U>
		0
		3
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Indnt bullet
	0
	0
[tag]
	2nd lev para
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		600
		0
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	2nd lev para
	0
	0
[tag]
	See also prnt
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	See also prnt
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Book art
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Book art
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Callout text
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Callout text
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Figure title
	0
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		40
		60
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Figure title
	0
	0
[tag]
	Chapter title
	0
	[fnt]
		Arial
		280
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		300
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Chapter title
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	1st pg foot
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	1st pg foot
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Right pg foot
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Right pg foot
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Left pg foot
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Left pg foot
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Table title
	0
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		60
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		7
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Table title
	0
	0
[tag]
	Table col hd
	0
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		100
		0
		3
		100
	[brk]
		4
	[line]
		10
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		6
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		256
		1
		0
		
		
		
	Table col hd
	0
	0
[tag]
	Table Text
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		1
		0
		0
		0
	[spc]
		40
		200
		4
		79
		0
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		256
		1
		0
		
		
		
	Table Text
	0
	0
[tag]
	See also hlp
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		40
		4
		180
		0
		3
		100
	[brk]
		96
	[line]
		9
		0
		3
		0
		1
		1
		1
		70
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	See also btn
	0
	120
[tag]
	See also btn
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		240
	[spc]
		24
		200
		4
		0
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	See also btn
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Crossref
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		513
		3
		0
		300
		600
	[spc]
		24
		200
		4
		19
		0
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Crossref
	0
	0
[tag]
	Indnt caution
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		300
		720
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Caution
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Indnt caution
	0
	0
[tag]
	Indnt tip
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		300
		324
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Tip
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Indnt tip
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Indnt note
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		300
		468
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Note
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Indnt note
	0
	0
[tag]
	Caution
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		720
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Caution
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Caution
	0
	0
[tag]
	Tip
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		324
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Tip
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Tip
	0
	0
[tag]
	Note
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		468
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Note
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Note
	0
	0
[tag]
	Mono
	0
	[fnt]
		Courier New
		180
		0
		32768
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		48
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Mono
	15
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	1
	2880
	1
	3360
	1
	3840
	1
	4320
	1
	4800
	1
	5280
	1
	5760
	1
	6240
	1
	6720
	1
	7200
	0
[tag]
	Indnt mono
	0
	[fnt]
		Courier New
		180
		0
		32768
	[algn]
		1
		3
		300
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		32
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Indnt mono
	15
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	1
	2880
	1
	3360
	1
	3840
	1
	4320
	1
	4800
	1
	5280
	1
	5760
	1
	6240
	1
	6720
	1
	7200
	0
[tag]
	Dhead
	0
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		100
		0
		3
		100
	[brk]
		68
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		4
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Body Text
	0
	0
[tag]
	Parameter
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		0
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Parameter
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Formula
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Formula
	0
	0
[tag]
	Browse
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		+
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Browse
	0
	0
[tag]
	Keyword
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		K
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Keyword
	0
	0
[tag]
	Context
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		#
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Context
	0
	0
[tag]
	Title
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		$
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Title
	0
	0
[tag]
	Macros
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		!
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Macros
	0
	0
[tag]
	Footnote
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		244
		0
	[spc]
		40
		2400
		3
		0
		0
		1
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		256
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Footnote
	0
	0
[tag]
	Alink
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		A
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Alink
	0
	0
[tag]
	Butnbar
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		0
		0
		3
		100
	[brk]
		48
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		\li-140 
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		wr
	Butnbar
	0
	0
[tag]
	Window
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		>
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Window
	0
	0
[tag]
	Win95 macros
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		W
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Win95 macros
	0
	0
[tag]
	Win31 macros
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		X
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Win31 macros
	0
	0
[tag]
	Build tag
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		*
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Build tag
	0
	0
[tag]
	_COND_IF
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	_COND_IF
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	_COND_ELSE
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	_COND_ELSE
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	_COND_ENDIF
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	_COND_ENDIF
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[lay]
	Standard
	3079
	[rght]
		12960
		10166
		1
		960
		1200
		3
		960
		720
		2
		1
		0
		1
		0
		2
		1
		960
		9446
		5
		1
		720
		1
		1440
		1
		2880
		1
		4320
		1
		5760
	[lft]
		12960
		10166
		1
		720
		1200
		3
		960
		960
		2
		1
		0
		1
		0
		2
		1
		720
		9206
		5
		1
		720
		1
		1440
		1
		2880
		1
		4320
		1
		5760
	[hlft]
	[lyfrm]
		1
		3008
		0
		0
		10166
		960
		0
		1
		3
		1 0 0 0 0 0 0
		0
		0
		1
	[frmlay]
		960
		10166
		1
		720
		180
		3
		0
		960
		0
		1
		0
		1
		1
		0
		1
		720
		9206
		0
	[txt]
>
	[hrght]
	[lyfrm]
		1
		11200
		0
		0
		10166
		960
		0
		1
		3
		1 0 0 0 0 0 0
		0
		0
		2
	[frmlay]
		960
		10166
		1
		960
		180
		3
		0
		720
		0
		1
		0
		1
		1
		0
		1
		960
		9446
		0
	[txt]
>
	[flft]
	[lyfrm]
		1
		5056
		0
		11760
		10166
		12960
		0
		1
		3
		1 0 0 0 0 0 0
		0
		0
		3
	[frmlay]
		12960
		10166
		1
		720
		480
		3
		11940
		960
		0
		1
		0
		1
		1
		0
		1
		720
		9206
		0
	[txt]
@Left pg foot@<:R1,1,3,8486,><:P19999,0,2 - >  Deployment Guide	Lotus Confidential

>
	[frght]
	[lyfrm]
		1
		13248
		0
		11760
		10166
		12960
		0
		1
		3
		1 0 0 0 0 0 0
		0
		0
		4
	[frmlay]
		12960
		10166
		1
		900
		480
		3
		11940
		780
		0
		1
		0
		1
		1
		0
		1
		900
		9386
		0
	[txt]
@1st pg foot@<:R1,1,3,8486,>Lotus Confidential	Deployment Guide <:P19999,0,2 - >

>
[elay]
[l1]
	0
[pg]
	8
	24 98 74 512 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	45 103 13 32 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	65 0 76 512 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	80 0 5 512 1 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	98 0 30 32 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	122 0 78 32 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	141 95 90 0 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	146 0 41 1025 1 0 0 240 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
[edoc]
@Chapter title@<:s><:#300,8486>Chapter 2  Understanding the Notes Environment

<:#600,8486><:f180,BArial,0,0,0>Lotus Notes is a client-server platform for developing and deploying groupware applications.  Lotus Notes allows people to access, track, share, and organize information in ways never before possible, even if they are only occasionally c
onnected to a network.<:f>

<:s><:#600,8486><:f180,BArial,0,0,0>To make the most of the collaborative power Notes offers your organization, planning your Notes deployment is essential. This guide offers information to assist in planning, installing, deploying, and maintaining Lotus Notes.  Additional
ly, it offers tips for maximizing capacity and improving performance.<:f>

<:#200,8486><+!><+"><[>This topic needs a rewrite.]<-"><-!>

@Ahead@<:s><:#240,8486><:f220,BArial,0,0,0>About Notes software<:f>

<:s><:#400,8486><:f180,BArial,0,0,0>Notes software consists of software for the <:f><:f180,BArial,0,0,0>end-user workstation 
<:f><:f180,BArial,0,0,0>and for the server, which is the central program for providing services to end-users.<:f>

<:s><:#1000,8486><:f180,BArial,0,0,0>Notes <:f><:f180,BArial,0,0,0>server software runs<:f><:f180,BArial,0,0,0> on a dedicated server machine that runs only Notes.  In addition to providing 
<:f><:f180,BArial,0,0,0>services that connect workstations, route mail, and control how databases are shared among users, the server also stores<:f><:f180,BArial,0,0,0> databases that Notes users share. A system administrator sets up, monitors, and secures 
all server operations. Most server operations are performed at the server machine, but some tasks, such as registering new users, must be performed<:f><:f180,BArial,0,0,0> from a workstation.

<:#600,8486><:f180,BArial,0,0,0>The Notes workstation <:f><:f180,BArial,0,0,0>software provides a graphical user interface to Notes. From their workstations, users have access to Notes mail services and to all authorized database services. Users may also store personal
 databases directly on their workstations.<:f>

@Ahead@<:s><:#240,8486><:f220,BArial,0,0,0>About the Notes server<:f>

<:#200,8486><:f180,BArial,0,0,0>A Notes deployment<:f><:f180,BArial,0,0,0> begins when you install the first server<:f><:f180,BArial,0,0,0>. The server controls:

@Bullet@<:s><:#200,8486><:f180,BArial,0,0,0>the Notes organization, including Notes domains, and Notes named networks

@Bullet@<:s><:#200,8486><:f180,BArial,0,0,0>mail routing and delivery

@Bullet@<:s><:#200,8486><:f180,BArial,0,0,0>database replication

@Bullet@<:s><:#200,8486><:f180,BArial,0,0,0>database s<:f>ecurity

@Bullet@<:s><:#200,8486><:f180,BArial,0,0,0>performance tuning<:f>

@Bullet@<:s><:#200,8486>mail and fax gateways

@Bullet@<:s><:#200,8486>add-in programs and custom server tasks

<:#400,8486>A Notes server also runs the Notes workstation software. You use the Notes workstation program to perform the initial server setup and subsequent server administration.

@Ahead@<:s><:#240,8486>About the Notes workstation

<:s><:#200,8486>A Notes workstation:

@Bullet@<:s><:#400,8486>provides users with the Notes interface for sending and receiving mail and for designing and using Notes applications

@Bullet@<:s><:#400,8486>can access local databases stored on its hard drive and replica databases stored on connected Notes servers

@Bullet@<:s><:#200,8486>can replicate changes from a local copy of a database to a replica database stored on a server

The privileges accorded to a Notes user depend on the type of license purchased for the user. The different types of Notes licenses are described______________________<:p<* >>

@Ahead@<:s><:#240,8486>About how Notes communicates

<:s><:#400,8486>Notes servers and workstations are connected via network. Server-to-server and workstation-to-server connections can take one of these forms:

@Bullet@<:s><:#200,8486>constantly connected local area network (LAN)

@Bullet@<:#200,8486>constantly connected wide area network (WAN) using routers and bridges

@Bullet@<:#200,8486>occasionally connected com port, which is used for remote/modem connections

@See also hlp@<:#110,8486>Network configurations are described in detail in the Network Configuration Guide.

@Ahead@<:s><:#240,8486>About Notes and file servers

<:s><:#400,8486>Although Notes runs on and takes advantage of network protocols, Notes is an application, not a network operating system. Notes relies on a file server to provide:

@Bullet@<:s><:#200,8486>network protocol, file, print, and non-Notes application services

@Bullet@<:#200,8486>bridges, routers, and bridging routers to pass data between LANs and WANs

@Bullet@<:s><:#200,8486>modems for remote/dial-in connections

<:s><:#600,8486>With some network operating systems, such as Microsoft LAN Manager, IBM LAN Server, NetWare, or Microsoft/Sybase SQL Server, Notes servers can run concurrently with the network file server. Some disadvantages of this plan include:

@Bullet@<:#600,8486>Security may be circumvented by network file server users if the Notes data directories are inadvertently shared. You should restrict all access to Notes data directories from network users. For more information about security in Notes see_________

@Bullet@<:s><:#400,8486>Performance of either the file server or the Notes server will suffer if one uses a lot of processing time.

@Bullet@<:#600,8486>Stability of the file server may be affected. If one of the file server's programs crashes or uses all available disk space, for example, and must be restarted, all other programs or processes, including Notes,  must be restarted too.

@Ahead@<:s><:#240,8486>About Notes named networks

<:#1200,8486>When you set up a new Notes server, Notes prompts you to enter a name for the Notes network.  A named network identifies a group of servers that are constantly connected (by either a LAN or bridged/routed WAN) and share a common protocol  so they can commun
icate directly, without requiring connection documents. The name you choose might reflect the location of the servers (for example Boston), or the location and network type (for example Boston Ethernet), or just the network type (for example, LANMAN)

<:s><:#1200,8486>You can group servers into named networks based on user function and need as well as physical connection and proximity. For example, all research and development people in an organization might be in the same named network. Grouping servers into named netwo
rks simplifies administrative tasks such as routing mail, and it also creates an easier to use environment for users, whose options in several dialog boxes depend on what named network they are in. For example, users on the same named network see the same l
ist of databases presented in the Open Database dialog box.

<:s><:#400,8486>Servers available only through occasionally-connected serial lines should be grouped in their own Notes named network.

@Bhead title@<:s><:#220,8486>Examples of Naming Networks

<:s><:#400,8486>Where your servers are located and what protocols they use will dictate how you name networks for your organization.

@Chead title@<:s><:#200,8486>Servers in one location with a single protocol

<:#600,8486>A single location, single protocol Notes named network called Boston_TCP might group several OS/2 and UNIX servers running on the same LAN with the protocol TCP/IP. Users choosing File Open Database would see databases on the OS/2 and the UNIX servers.

@Chead title@<:s><:#200,8486>Servers in multiple locations with a single protocol

<:s><:#400,8486>Although you could group all servers sharing a protocol on one named network, you may want to divide your servers into logical groupings to avoid user confusion.

<:s><:#1000,8486>With only one Notes named network, users throughout the organization might see several hundred servers in the File Open Database dialog box if the organization is a large one. By grouping servers into smaller named networks, a user sees only the servers in 
the same named network as his home server. The user can still access other servers by typing a server name into the Server text box in the Open Database dialog box.

@Chead@<:s><:#200,8486>Servers that run more than one protocol

<:#600,8486>A Notes server that runs more than one protocol can be part of a different Notes named network for each protocol it runs. For example, an OS/2 Notes server that supports three protocol can be part of three Notes named networks.

@Ahead@<:s><:#240,8486>About Notes domains

<:s><:#600,8486>A Notes domain is an organization of servers that allows for the centralized management of server administration and security.  Servers in a domain, unlike those in a Notes named network, do not need to share a common network protocol. Notes networks exist 
within a domain. 

<:#1000,8486>All servers in a domain share the same Public Name & Address book. The Public Name and Address book (PNAB) provides a domain-wide directory of Notes servers, users, certifiers, foreign domains, and groups and a manager for server-to-server communication and
 server programs. A Notes administrator with access to the Public Name & Address Book can manage administrative functions for an entire domain, even if it extends over a large geographic area.

<:s><:#1000,8486>By default, Notes assumes only one domain, but you might choose to create multiple domains for your organization. You might base your domains on geographical location of servers, or you might have several domains in the same location. As part of your site p
lanning, you must choose what strategy is best for your site. Changing domains after you register servers and users can require a lot of administrative work.

@Bhead title@<:s><:#220,8486>Choosing single or multiple domains 

<:s><:#200,8486>The advantages of keeping all servers in a single domain include: 

@Bullet@<:s><:#200,8486>simpler mail addressing

@Bullet@<:s><:#200,8486>optimal mail routing

@Bullet@<:s><:#200,8486>easier maintenance (you only need to maintain one Name & Address book)

<:s><:#200,8486>The advantages of organizing servers into multiple domains include: 

@Bullet@<:s><:#200,8486>faster lookup time because each Name & Address book is smaller

@Bullet@<:s><:#200,8486>more autonomy; each domain controls its own Name & Address book so problems can be localized

@Bullet@<:s>better use of server memory because each Name & Address book is smaller<:p<* >>

@Ahead@<:s><:#240,8486>About the Public Name & Address Book

<:#1000,8486>The Public Name & Address Book (PNAB) is the most important database in a Notes domain. The PNAB performs two critical roles. First, it provides a domain-wide directory of Notes servers, users, certifiers, foreign domains, and groups. Second, it contains do
cuments that manage server-to-server communication and server programs. Managing the PNAB for a domain is perhaps the most critical administration task for a Notes system.

@Bhead@<:s><:#220,8486>How the PNAB gets created

<:#800,8486>When you set up the first Notes server in your domain, Notes automatically creates a new PNAB with the filename NAMES.NSF. Each time you add servers to the domain, Notes automatically creates a replica of the same PNAB database for each server. Even if your
 site does not use Notes mail, you still need the PNAB to manage server-to-server communications.

@Bhead@<:s><:#220,8486>What the PNAB contains

<:s><:#1000,8486>The PNAB contains documents that manage the directory and server-to-server communication. Some of the documents in the PNAB appear automatically as a result of  tasks that you perform as a system administrator. For example, when you register a new user, Not
es automatically creates a new Person document; when you add a new server to the domain, Notes automatically creates a new Server document.

<:s><:#200,8486>The following documents may appear in the PNAB: <[>XREF to AG for each document type]

@Bullet@<:s><:#800,8486>Person documents identify individual users. The Person document identifies a user's home server, which is the server on which the user's mail file is stored. The document also contains the user's public key, which Notes uses to allow a user access to a serv
er and to encrypt and sign mail messages.

@Bullet@<:s><:#400,8486>Server documents identify individual servers in the domain. The Server document identifies a server's domain, which is critical information for mail routing.

@Bullet@<:#200,8486>Certifier and cross-certifier documents identify each certificate's ancestry.

@Bullet@<:#800,8486>Group documents contains lists of users, servers, or other groups within the domain.   The PNAB comes with two groups already established: LocalDomainServers and OtherDomainServers. 
<+!><[>Need to xref to some topic that covers creating group docs for efficient server administration. See the table on AG page 9-70 for info.]<-!>

@Bullet@<:#600,8486>Foreign domain documents identify domains that are non-Notes domains. When you want to route mail to a non-Notes domain, you must create a Foreign domain document. 
<+!><[>Need to xref some info on foreign mail systems, gateways, etc.]<-!>

@Bullet@<:s><:#800,8486>Connection documents establish server-to-server connections that manage replication and mail-routing. You create a Network Connection documents connect servers that are both on the same network and in the same domain. You create a Remote Connection document
 for servers that are on different networks or in different domains.

@Bullet@<:s><:#400,8486>Program documents identify Notes server tasks, API programs, or batch files that you want the server to start automatically. 
<+!><[>Need xref to something here.]<-!>  

@Ahead@<:s><:p<* >>About strategies for managing the PNAB

<:#600,8486>If you organize your servers into multiple domains, you need to plan how to manage the Public Name and Address Books for each domain. You can maintain separate PNABs for each domain or maintain a PNAB for each domain in addition to copies of all other domai
n PNABs.

@Bhead title@<:s><:#220,8486>Maintaining Separate Public Name & Address Book

<:#1200,8486>With this strategy, you maintain a unique Public Name & Address Book for each domain in the organization. A replica of the Public Name & Address Book (NAMES.NSF) is stored on each server in the domain. The advantage to this approach is that each domain admi
nistrator need only manage the unique Name & Address Book for that particular domain. The disadvantage is that a user sending mail to a user in a different domain must specify the domain name as part of the address, as in John Smith@ACMEWEST.

@Bhead title@<:s><:#220,8486>Maintaining cascading Public Name & Address Books

<:#1400,8486>Following a strategy for cascading Name & Address Books, every domain has its own primary Public Name & Address book, plus copies of Public Name & Address Books from every other domain in the organization. The advantage is that a user sending mail to a diff
erent domain does not need to specify the domain name because Notes will search through the cascading Name & Address Books to find the recipient. If Notes finds a match in an address book other than the primary address book for the domain, Notes appends the
 domain name to the address and continues with the mail routing and delivery process.

@Ahead@<:s><:#240,8486>About certifying servers and users

<:s><:#1200,8486>Certification is a key component of creating a secure Notes system. During server or user registration, each server and each user in a Notes system is issued a Notes User ID file that acts as their key to the system. To access a server database, a user or a
nother server must present a Notes ID and successfully pass an identity check, known as authentication. A Notes ID file is analogous to a driver's license that contains your name, some identifying information, and a stamp from the registrar attesting the va
lidity of the license. In Notes, the Certifier ID acts as the "registrar".

<:#400,8486>For an ID to be valid, it must contain one or more certificates created by a Certifier ID. The Certifier ID is created when you install the first server in a system and is stored in the file CERT.ID. 

@Ahead@<:s><:#240,8486>About how certification works

<:#800,8486>When you install the first server in a Notes system, Notes creates a Certifier, contained in the file CERT.ID. Thereafter, the person tasked with certifying IDs confirms that an ID belongs to the user or server presenting it, and stamps each  ID with a uniq
ue certificate created using the Certifier. A certifier needs at least Editor access in the Name & Address Book.

<:#400,8486>Because certification is an essential part of security for a Notes system, the Certifier ID should be password-protected and access to it should be limited to only a few people. 

@Bhead@<:s><:#220,8486>About Notes IDs

<:s><:#400,8486>A Notes ID is a unique binary file that identifies a legitimate Notes use or server. Each file contains the following information:

@Bullet@<:s><:#200,8486>The name of the ID owner

@1st lev para@<:s><:#200,8486>Identifies the user or server by name

@Bullet@<:s><:#200,8486>A Notes license number

@1st lev para@<:s><:#400,8486>Identifies a user as having legitimate use of Notes software. The license number is permanently associated with the User ID and cannot be changed.

@Bullet@<:s><:#200,8486>A public key and a private key

@1st lev para@<:s><:#400,8486>A string of numbers used during authentication and to decrypt mail messages. Notes also stores a copy of each user's public key in the Public Name & Address Book.

@Bullet@<:s><:#200,8486>One or more encryption keys

@1st lev para@<:s><:#400,8486>A string of numbers used to encrypt and decrypt fields in a document. Users distribute these keys to other user to ensure that only intended recipients can read a document.

@Bullet@<:s><:#200,8486>A password

@1st lev para@<:s><:#200,8486>An optional security feature to protect the ID from unauthorized use. 

@Bullet@<:s><:#200,8486>One or more certificates

@1st lev para@<:#400,8486>A certificate, provided by a Certifier ID, verifies that a Notes user or server is valid. A Notes server or user ID can have one or more certificates.

@Ahead@<:s><:#240,8486>About strategies for certifying users and servers

<:s><:#600,8486>For a user or server to access a Notes server, their ID must contain a certificate from a certifier that the server recognizes. How you certify servers in your organization is something you should plan as part of your overall deployment strategy. There are 
several strategies for issuing certificates in a Notes system:

@Bullet@<:s><:#200,8486>Hierarchical certificates

@1st lev para@<:s><:#600,8486>An organization uses multiple certifiers to stamp user and server IDs. One advantage of using hierarchical certificates is that the authority and responsibility for certifying users can be distributed, which improves the security of the system.  Hierarchica
l certification is the default.

@Bullet@<:s><:#200,8486>Flat certificates

@1st lev para@<:s><:#600,8486>All user and server IDs are stamped by the same Certifier ID. In order for a user or server to communicate with a user or server certified by a different Certifier ID<< cross certificates must be exchanged.

@1st lev para@<:s><:#200,8486>

@1st lev para@<:#200,8486><[>Need some art here to show different schemes]

@Bhead title@<:s><:#220,8486>About hierarchical certificates

<:s><:#1000,8486>Hierarchical certificates organize a Notes system in a pyramid configuration. At the top of the pyramid is an organizational certificate, which must be the common certificate in order for users and servers throughout the organization too have access to each
 other. Below the organizational certifier are organizational unit certifiers, which you can create along whatever logical lines suit the structure of your company.

<:s><:#1000,8486>If you issue hierarchical certificates, users and servers need to identify themselves using hierarchical names. This means that the user or server name is followed by a list of hierarchical certificates on the ID. For example, the name John Jones/Accounting
/Finance/Acme, lists the hierarchy of certificates on John Jones' ID, with the last certificate name, in this case ACME, identifying the organizational certificate.

@Chead title@<:s><:#200,8486>Advantages of using hierarchical certificates

@Bullet@<:s><:#200,8486>All users and servers can have unique names but still share a common certificate

@1st lev para@<:s><:#200,8486>John Smith/Ottawa/Acme/CA is easily differentiated from John Smith/Vancouver/Acme/CA

@1st lev para@<:s><:#400,8486>For servers, hierarchical naming can offer a clue as to the departmental hierarchy of an organization, for example:

@1st lev para@<:s><:#200,8486>ADMIN_1/F&A/Stardahl Hospital and ADMIN_1/Research/Stardahl Hospital 

@Bullet@<:s><:#200,8486>Hierarchical certificates allow for decentralized management of Certifier IDs.

@1st lev para@<:#600,8486>The organizational certifier can create organizational unit certifiers. These certifiers can be managed and kept secure at different sites. If the integrity of an organizational unit certifier is compromised, only the users and servers stamped with that cer
tificate need to be recertified.

@Note@<:s><:#200,8486>The organizational certifier ID should be stored on diskette and be locked in a safe.

@Chead title@<:s><:#200,8486>Disadvantages of using hierarchical certificates

<:s><:#400,8486>Organizing a Notes system with hierarchical certificates requires some planning.  Put some thought into devising a plan for meaningful organizational units.

<:#200,8486><[>NEED SOME CONCEPTUAL ART SHOWING ORG CERT AND ORG UNITS]

@Ahead@<:s><:#240,8486>About flat certificates

<:#1200,8486>If you choose to use flat certificates for your organization, this means that all of the authority for stamping user and server IDs rests in the hands of one administrator. This is the simplest strategy, because every user and server will share a common cer
tificate, but it may not be the most secure. For example, if the integrity of the certifier is compromised, perhaps by an employee who has access to the certifier ID leaving the company, you will need to immediately recertify all IDs.  Generally, hierarchic
al certification is preferable.

<:#400,8486><+!><+">yy Need to discuss disadvantages of Flat certificates. Also need either topics or pointers on Trusted and Non Trusted Certificates.<-"><-!> See Page 5-5 of AG

<+@><:I0,0,0,0><:#400,8486><+!><+">yy Need to discuss moving from flat to hierarchical certificate. 
<-!><-"><+!><+"> (Gregg Staiman)<-"><-!><+!><+"> x-ref to Upgraders Guide where Jill is handling this.<-!><-">

@Bhead@<+@><:s><:I0,0,0,0><:#220,8486>About Cross Certificates

<+@><:I0,0,0,0><:#1200,8486>The use of flat certificates require the use of cross certificates for a user or server to communicate with a user or server in a different domain. Cross certificates allow users or servers without common certificates to communicate with each other. Issuing
 cross certificates is analogous to a foreign country issuing you a visa so that you can travel in that country. Cross certificates are often exchanged between two organizations that need to communicate. Cross certificates must be stored in the Public Name 
& Address Book of each organization.

@Ahead@<:s><:#240,8486>About naming conventions and requirements

<:s><:#400,8486>As you develop your Notes deployment strategy, keep in mind the following naming conventions and guidelines.

@Bullet@<:s><:#400,8486>Domain names should be a single word or string (31 characters or fewer.  Do not use periods (.) in a domain name as they are a reserved character.

@Bullet@<:s><:#600,8486>Organization name is the name of the Certifier ID and is appended to all user and server names. Typically, the organization name is the same as the domain name, and there is only one organization per domain. The name can be up to 64 characters long.

@Bullet@<:#800,8486>Notes network names denote groups of servers that are physically connected and use the same network protocol. The name must be fewer than 31 characters long. It is helpful to use an identifier such as the location of the named network, the LAN type, or the 
protocol. For example, Boston_Novell, or NY_Ethernet are descriptive names.

@Bullet@<:s><:#600,8486>Notes server names are unique names that identify servers in a domain.  Server names can consist of one or more words (up to 79 characters) and can consist of any characters except: parentheses, at sign (@), slash and backslash (/ and \), equal sign (=), an
d plus sign (+)

@Bhead@<:s><:#220,8486>Guidelines for naming a Notes server

@Bullet@<:#400,8486>Choose a name you want to keep. Changing a server name involves recertifying the server ID and changing the name in the Server document, Group documents, ACLs, and Connection documents.

@Bullet@<:s><:#400,8486>Choose name without space. When you use server console commands, you must use quotation marks around a server name containing spaces.

@Bullet@<:s><:#600,8486>Keep in mind that replication and mail routing tasks are usually performed based on numeric then alphabetical order. For example, Notes routes mail to the server Accounting before routing to the server Research.

@Bullet@<:#600,8486>A server name can contain up to 79 characters, but in certain networks the first several characters must be unique for the network to identify the server. With NetBIOS, the first 15 characters must be unique; with AppleTalk, the first 32 must be unique; and
 with SPX, the first 47 must be unique.

@Ahead@<:s><:#240,8486>A Planning Checklist

@Ahead@<:#240,8486><[>Need a checklist here. See what IS uses]

>

[Embedded]
00047773
