ibm tivoli directory integrator 5.2: reference...
TRANSCRIPT
-
IBM
Tivoli
Directory
Integrator
5.2:
Reference
Guide
SC32-1377-00
���
-
IBM
Tivoli
Directory
Integrator
5.2:
Reference
Guide
SC32-1377-00
���
-
Note
Before
using
this
information
and
the
product
it
supports,
read
the
general
information
under
Appendix
D,
“Notices,”
on
page
191.
First
Edition
(November
2003)
This
edition
applies
to
version
5,
release
2,
of
The
IBM
Tivoli
Directory
Integrator
and
to
all
subsequent
releases
and
modifications
until
otherwise
indicated
in
new
editions.
©
Copyright
International
Business
Machines
Corporation
2002,
2003.
All
rights
reserved.
US
Government
Users
Restricted
Rights
–
Use,
duplication
or
disclosure
restricted
by
GSA
ADP
Schedule
Contract
with
IBM
Corp.
-
Preface
This
document
contains
the
information
that
you
need
to
administer
the
IBM®
Tivoli®
Directory
Integrator.
Who
should
read
this
book
This
book
is
intended
for
system
administrators.
Publications
Read
the
descriptions
of
the
IBM
Tivoli
Directory
Integrator
library
to
determine
which
publications
you
might
find
helpful.
After
you
determine
the
publications
you
need,
refer
to
the
instructions
for
accessing
publications
online.
IBM
Tivoli
Directory
Integrator
library
The
publications
in
the
IBM
Tivoli
Directory
Integrator
library
are:
IBM
Tivoli
Directory
Integrator
5.2:
Readme
Contains
last-minute
information
about
IBM
Tivoli
Directory
Integrator
5.2.
IBM
Tivoli
Directory
Integrator
5.2:
Getting
Started
Guide
A
brief
tutorial
and
introduction
to
IBM
Tivoli
Directory
Integrator
5.2.
IBM
Tivoli
Directory
Integrator
5.2:
Administrator
Guide
Includes
complete
information
for
installing
the
IBM
Tivoli
Directory
Integrator.
Includes
information
about
migrating
from
a
previous
version
of
IBM
Tivoli
Directory
Integrator.
Includes
information
about
configuring
the
logging
functionality
of
IBM
Tivoli
Directory
Integrator.
IBM
Tivoli
Directory
Integrator
5.2:
Users
Guide
Contains
information
about
using
the
IBM
Tivoli
Directory
Integrator
5.2
tool.
Contains
instructions
for
designing
solutions
using
the
IBM
Tivoli
Directory
Integrator
tool
(ibmditk)
or
running
the
ready-made
solutions
from
the
command
line
(ibmdisrv).
Also
provides
information
about
interfaces,
concepts
and
AssemblyLine/EventHandler
creation
and
management.
Includes
examples
to
create
interaction
and
hands-on
learning
of
IBM
Tivoli
Directory
Integrator
5.2.
IBM
Tivoli
Directory
Integrator
5.2:
Reference
Guide
Contains
detailed
information
about
the
individual
components
of
IBM
Tivoli
Directory
Integrator
5.2
AssemblyLine
(Connectors,
EventHandlers,
Parsers,
Plug-ins,
and
so
forth).
Related
publications
Information
related
to
the
IBM
Tivoli
Directory
Integrator
is
available
in
the
following
publications:
v
The
IBM
Tivoli
Directory
Integrator
5.2
uses
the
JNDI
client
from
Sun
Microsystems.
For
information
about
the
JNDI
client,
refer
to
the
Java™
Naming
and
Directory
Interface™
1.2.1
Specification
on
the
Sun
Microsystems
Web
site
at
http://java.sun.com/products/jndi/1.2/javadoc/index.html.
v
The
Tivoli
Software
Library
provides
a
variety
of
Tivoli
publications
such
as
white
papers,
datasheets,
demonstrations,
redbooks,
and
announcement
letters.
©
Copyright
IBM
Corp.
2002,
2003
iii
http://java.sun.com/products/jndi/1.2/javadoc/index.html
-
The
Tivoli
Software
Library
is
available
on
the
Web
at:
http://www.ibm.com/software/tivoli/library/
v
The
Tivoli
Software
Glossary
includes
definitions
for
many
of
the
technical
terms
related
to
Tivoli
software.
The
Tivoli
Software
Glossary
is
available,
in
English
only,
from
the
Glossary
link
on
the
left
side
of
the
Tivoli
Software
Library
Web
page
http://www.ibm.com/software/tivoli/library/
Accessing
publications
online
The
publications
for
this
product
are
available
online
in
Portable
Document
Format
(PDF)
or
Hypertext
Markup
Language
(HTML)
format,
or
both
in
the
Tivoli
software
library:
http://www.ibm.com/software/tivoli/library.
To
locate
product
publications
in
the
library,
click
the
Product
manuals
link
on
the
left
side
of
the
Library
page.
Then,
locate
and
click
the
name
of
the
product
on
the
Tivoli
software
information
center
page.
Information
is
organized
by
product
and
includes
READMEs,
installation
guides,
user’s
guides,
administrator’s
guides,
and
developer’s
references
as
necessary.
Note:
To
ensure
proper
printing
of
PDF
publications,
select
the
Fit
to
page
check
box
in
the
Adobe
Acrobat
Print
window
(which
is
available
when
you
click
File->Print).
Accessibility
Accessibility
features
help
a
user
who
has
a
physical
disability,
such
as
restricted
mobility
or
limited
vision,
to
use
software
products
successfully.
With
this
product,
you
can
use
assistive
technologies
to
hear
and
navigate
the
interface.
After
installation
you
also
can
use
the
keyboard
instead
of
the
mouse
to
operate
all
features
of
the
graphical
user
interface.
Contacting
software
support
Before
contacting
IBM
Tivoli
Software
support
with
a
problem,
refer
to
IBM
System
Management
and
Tivoli
software
Web
site
at:
http://www.ibm.com/software/sysmgmt/products/support/
If
you
need
additional
help,
contact
software
support
by
using
the
methods
described
in
the
IBM
Software
Support
Guide
at
the
following
Web
site:
http://techsupport.services.ibm.com/guides/handbook.html
The
guide
provides
the
following
information:
v
Registration
and
eligibility
requirements
for
receiving
support
v
Telephone
numbers
and
e-mail
addresses,
depending
on
the
country
in
which
you
are
located
v
A
list
of
information
you
must
gather
before
contacting
customer
support
iv
IBM
Tivoli
Directory
Integrator
5.2:
Reference
Guide
http://www.ibm.com/software/tivoli/library/http://www.ibm.com/software/tivoli/library/http://www.ibm.com/software/tivoli/library/http://www.ibm.com/software/sysmgmt/products/support/http://techsupport.services.ibm.com/guides/handbook.html
-
Contents
Preface
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. iii
Who
should
read
this
book
.
.
.
.
.
.
.
.
. iii
Publications
.
.
.
.
.
.
.
.
.
.
.
.
.
. iii
IBM
Tivoli
Directory
Integrator
library
.
.
.
. iii
Related
publications
.
.
.
.
.
.
.
.
.
. iii
Accessing
publications
online
.
.
.
.
.
.
. iv
Accessibility
.
.
.
.
.
.
.
.
.
.
.
.
.
. iv
Contacting
software
support
.
.
.
.
.
.
.
.
. iv
Chapter
1.
Introduction
.
.
.
.
.
.
.
. 1
Chapter
2.
Connectors
.
.
.
.
.
.
.
. 3
Connector
availability
and
reference
.
.
.
.
.
. 3
Raw
Connectors
.
.
.
.
.
.
.
.
.
.
.
. 3
Script-based
Connectors
.
.
.
.
.
.
.
.
. 5
Configurations
.
.
.
.
.
.
.
.
.
.
.
.
. 5
Btree
Object
DB
Connector
.
.
.
.
.
.
.
.
.
. 5
Configuration
.
.
.
.
.
.
.
.
.
.
.
.
. 5
Btree
object
.
.
.
.
.
.
.
.
.
.
.
.
.
. 6
Command
line
Connector
.
.
.
.
.
.
.
.
.
. 6
Configuration
.
.
.
.
.
.
.
.
.
.
.
.
. 6
Examples
.
.
.
.
.
.
.
.
.
.
.
.
.
. 6
Direct
TCP
/URL
scripting
.
.
.
.
.
.
.
.
. 7
TCP
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 7
URL
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 7
Domino
Users
Connector
.
.
.
.
.
.
.
.
.
. 7
Deployment
and
connection
to
Domino
server
.
. 8
Configuration
.
.
.
.
.
.
.
.
.
.
.
.
. 9
Security
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 9
Using
the
Domino
Connector
.
.
.
.
.
.
. 10
List
of
Domino
user
attributes
(or
Person
document
items)
.
.
.
.
.
.
.
.
.
.
.
. 17
Domino
Server
6.0
for
AIX/Linux/Solaris
.
.
. 19
Examples
.
.
.
.
.
.
.
.
.
.
.
.
.
. 19
See
also
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 19
File
system
Connector
.
.
.
.
.
.
.
.
.
.
. 20
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 20
See
also
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 20
FTP
Client
Connector
.
.
.
.
.
.
.
.
.
.
. 20
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 20
See
also
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 21
Old
HTTP
Client
Connector
.
.
.
.
.
.
.
.
. 21
Modes
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 21
Special
attributes
.
.
.
.
.
.
.
.
.
.
. 22
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 23
Examples
.
.
.
.
.
.
.
.
.
.
.
.
.
. 23
See
also
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 23
HTTP
Client
Connector
.
.
.
.
.
.
.
.
.
. 23
Modes
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 24
Special
attributes
.
.
.
.
.
.
.
.
.
.
. 24
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 25
Examples
.
.
.
.
.
.
.
.
.
.
.
.
.
. 26
See
also
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 26
Old
HTTP
Server
Connector
.
.
.
.
.
.
.
.
. 26
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 27
See
also
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 27
HTTP
Server
Connector
.
.
.
.
.
.
.
.
.
. 27
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 28
See
also
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 28
JDBC
Connector
.
.
.
.
.
.
.
.
.
.
.
.
. 28
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 29
Link
Criteria
.
.
.
.
.
.
.
.
.
.
.
.
. 30
Other
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 30
Timestamp
.
.
.
.
.
.
.
.
.
.
.
.
. 30
SQL
Databases:
column
names
with
special
characters
.
.
.
.
.
.
.
.
.
.
.
.
.
. 30
Using
prepared
statements
.
.
.
.
.
.
.
. 30
On
Multiple
Entries
.
.
.
.
.
.
.
.
.
. 31
ODBC–specifying
database
paths
directly
.
.
. 31
JMS
Connector
.
.
.
.
.
.
.
.
.
.
.
.
. 31
JMS
message
flow
.
.
.
.
.
.
.
.
.
.
. 32
JMS
message
types
.
.
.
.
.
.
.
.
.
.
. 32
Iterator
mode
.
.
.
.
.
.
.
.
.
.
.
.
. 34
Call/Reply
mode
.
.
.
.
.
.
.
.
.
.
. 34
Lookup
mode
.
.
.
.
.
.
.
.
.
.
.
. 34
JMS
headers
and
properties
.
.
.
.
.
.
.
. 35
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 37
Examples
.
.
.
.
.
.
.
.
.
.
.
.
.
. 38
Specific
topics
.
.
.
.
.
.
.
.
.
.
.
. 38
Enabling
SSL
.
.
.
.
.
.
.
.
.
.
.
.
. 39
JNDI
Connector
.
.
.
.
.
.
.
.
.
.
.
.
. 39
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 39
Setting
the
Modify
operation
.
.
.
.
.
.
. 40
See
also
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 42
LDAP
Connector
.
.
.
.
.
.
.
.
.
.
.
. 42
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 44
Handling
memory
problems
in
the
LDAP
Connector
.
.
.
.
.
.
.
.
.
.
.
.
.
. 46
LDAP
Connector
updates
.
.
.
.
.
.
.
.
. 47
Problem
when
connecting
to
an
active
non-LDAP
port
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 49
See
also
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 49
IBM
Directory
Changelog
Connector
.
.
.
.
. 49
Netscape/iPlanet
Changelog
Connector
.
.
.
. 50
Active
Directory
Changelog
Connector
.
.
.
. 51
Exchange
Changelog
Connector
.
.
.
.
.
. 56
Lotus
Notes
Connector
.
.
.
.
.
.
.
.
.
. 62
Known
limitations
.
.
.
.
.
.
.
.
.
.
. 63
Session
types
.
.
.
.
.
.
.
.
.
.
.
.
. 63
Connecting
.
.
.
.
.
.
.
.
.
.
.
.
. 64
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 64
Security
.
.
.
.
.
.
.
.
.
.
.
.
.
. 65
Mailbox
Connector
.
.
.
.
.
.
.
.
.
.
.
. 66
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 66
Predefined
properties
and
attributes
.
.
.
.
. 66
See
also
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 67
Memory
Stream
Connector
.
.
.
.
.
.
.
.
. 67
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 68
MQe
Password
Store
Connector
.
.
.
.
.
.
. 68
MQe
Password
Store
Connector
Entry
structure
69
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 69
©
Copyright
IBM
Corp.
2002,
2003
v
-
NT4
Connector
.
.
.
.
.
.
.
.
.
.
.
.
. 70
Preconditions
.
.
.
.
.
.
.
.
.
.
.
.
. 70
Character
sets
.
.
.
.
.
.
.
.
.
.
.
. 73
Examples
.
.
.
.
.
.
.
.
.
.
.
.
.
. 73
NT4
Connector
functional
specifications
and
software
requirements
.
.
.
.
.
.
.
.
.
. 73
RDBMS
Changelog
Connector
.
.
.
.
.
.
.
. 74
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 75
Change
table
format
.
.
.
.
.
.
.
.
.
. 76
Creating
change
tables
in
DB2
.
.
.
.
.
.
. 76
Creating
change
tables
in
Oracle
.
.
.
.
.
. 77
runtime-provided
Connector
.
.
.
.
.
.
.
.
. 78
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 78
See
also
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 78
Script
Connector
.
.
.
.
.
.
.
.
.
.
.
.
. 78
Predefined
script
objects
.
.
.
.
.
.
.
.
. 79
Functions
.
.
.
.
.
.
.
.
.
.
.
.
.
. 79
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 80
Examples
.
.
.
.
.
.
.
.
.
.
.
.
.
. 80
See
also
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 80
SNMP
Connector
.
.
.
.
.
.
.
.
.
.
.
. 80
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 81
Examples
.
.
.
.
.
.
.
.
.
.
.
.
.
. 81
TCP
Connector
.
.
.
.
.
.
.
.
.
.
.
.
. 81
Iterator
Mode
.
.
.
.
.
.
.
.
.
.
.
.
. 81
AddOnly
Mode
.
.
.
.
.
.
.
.
.
.
.
. 82
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 82
See
also
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 82
URL
Connector
.
.
.
.
.
.
.
.
.
.
.
.
. 83
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 83
Supported
URL
protocol
.
.
.
.
.
.
.
.
. 83
See
also
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 83
Web
Service
Connector
.
.
.
.
.
.
.
.
.
. 83
Using
the
Web
Service
Connector
.
.
.
.
.
. 83
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 85
The
On
Error
hook
.
.
.
.
.
.
.
.
.
.
. 85
Schema/namespaces
types
support
.
.
.
.
. 85
Chapter
3.
EventHandlers
.
.
.
.
.
.
. 87
EventHandler
types
.
.
.
.
.
.
.
.
.
.
. 87
When
are
they
started?
.
.
.
.
.
.
.
.
.
. 87
What
do
they
do?
.
.
.
.
.
.
.
.
.
.
.
. 87
Data
flow
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 88
Passing
input/output
file
names
to
an
AssemblyLine
.
.
.
.
.
.
.
.
.
.
.
.
. 88
EventHandler
availability
.
.
.
.
.
.
.
.
.
. 88
Active
Directory
Changelog
EventHandler
.
.
.
. 89
Behavior
.
.
.
.
.
.
.
.
.
.
.
.
.
. 89
Access
to
the
USN
synchronization
values
in
the
User
Property
Store
.
.
.
.
.
.
.
.
.
.
. 89
Access
to
the
runtime
EventHandler’s
USN
synchronization
values
.
.
.
.
.
.
.
.
. 90
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 91
Connector
EventHandler
.
.
.
.
.
.
.
.
.
. 92
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 92
Objects/properties/attributes
.
.
.
.
.
.
. 92
See
also
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 92
DSMLv2
EventHandler
.
.
.
.
.
.
.
.
.
. 93
Transportation
(binding)
.
.
.
.
.
.
.
.
. 93
Operations
.
.
.
.
.
.
.
.
.
.
.
.
. 93
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 95
Exchange
Changelog
EventHandler
.
.
.
.
.
. 98
Behavior
.
.
.
.
.
.
.
.
.
.
.
.
.
. 98
Access
to
the
USN
synchronization
values
in
the
User
Property
Store
.
.
.
.
.
.
.
.
.
.
. 99
Access
to
the
runtime
EventHandler’s
USN
synchronization
values
.
.
.
.
.
.
.
.
. 100
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 100
HTTP
EventHandler
.
.
.
.
.
.
.
.
.
.
. 101
Example
.
.
.
.
.
.
.
.
.
.
.
.
.
. 102
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 102
See
also
.
.
.
.
.
.
.
.
.
.
.
.
.
. 103
IBM
Directory
Server
EventHandler
.
.
.
.
.
. 103
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 104
See
also
.
.
.
.
.
.
.
.
.
.
.
.
.
. 105
JMX
EventHandler
.
.
.
.
.
.
.
.
.
.
. 105
Behavior
description
.
.
.
.
.
.
.
.
.
. 105
Using
the
EventHandler
.
.
.
.
.
.
.
.
. 106
IBM
Tivoli
Directory
Integrator
notification
types
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 107
JMX
system
notification
types
.
.
.
.
.
.
. 107
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 107
Dynamic
addition/removal
of
notification
types
108
LDAP
EventHandler
.
.
.
.
.
.
.
.
.
.
. 109
Object
Added
(_objAdded)
.
.
.
.
.
.
.
. 110
Object
Rename
(_objRenamed)
.
.
.
.
.
.
. 110
Object
Modified
(_objModified)
.
.
.
.
.
. 110
Object
Removed
(_objRemoved)
.
.
.
.
.
. 110
Error
Encountered
(_handleError)
.
.
.
.
.
. 111
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 111
See
also
.
.
.
.
.
.
.
.
.
.
.
.
.
. 112
LDAP
Server
EventHandler
.
.
.
.
.
.
.
. 112
Scripting
.
.
.
.
.
.
.
.
.
.
.
.
.
. 113
Returning
the
LDAP
message
returned
values
113
Error
handling
.
.
.
.
.
.
.
.
.
.
.
. 113
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 113
Mailbox
EventHandler
.
.
.
.
.
.
.
.
.
. 114
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 114
Objects/properties/attributes
.
.
.
.
.
.
. 114
Examples
.
.
.
.
.
.
.
.
.
.
.
.
.
. 115
See
also
.
.
.
.
.
.
.
.
.
.
.
.
.
. 115
SNMP
EventHandler
.
.
.
.
.
.
.
.
.
.
. 115
Scripting
the
desired
action
.
.
.
.
.
.
.
. 116
Error
handling
.
.
.
.
.
.
.
.
.
.
.
. 116
Returning
the
SNMP
packet
returned
values
.
. 116
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 117
TCP
Port
EventHandler
.
.
.
.
.
.
.
.
.
. 117
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 117
Objects/properties/attributes
.
.
.
.
.
.
. 117
Examples
.
.
.
.
.
.
.
.
.
.
.
.
.
. 118
See
also
.
.
.
.
.
.
.
.
.
.
.
.
.
. 118
Generic
thread
(primitive
EventHandler)
.
.
.
. 118
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 118
See
also
.
.
.
.
.
.
.
.
.
.
.
.
.
. 118
Timer
EventHandler
(primitive
EventHandler)
.
. 118
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 118
Examples
.
.
.
.
.
.
.
.
.
.
.
.
.
. 119
Web
Service
EventHandler
.
.
.
.
.
.
.
.
. 120
AssemblyLines-WSDL
mapping
.
.
.
.
.
. 120
Using
the
EventHandler
.
.
.
.
.
.
.
.
. 122
Web
Service
EventHandler
Processing
Sequence
122
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 124
vi
IBM
Tivoli
Directory
Integrator
5.2:
Reference
Guide
-
Hosting
WSDL
.
.
.
.
.
.
.
.
.
.
.
. 124
Automatic
WSDL
Generation
.
.
.
.
.
.
. 125
zOS
LDAP
Changelog
EventHandler
.
.
.
.
. 126
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 126
Polling
logic
.
.
.
.
.
.
.
.
.
.
.
.
. 127
Chapter
4.
Parsers
.
.
.
.
.
.
.
.
. 129
Base
Parsers
.
.
.
.
.
.
.
.
.
.
.
.
.
. 129
Character
Encoding
conversion
.
.
.
.
.
.
. 129
Availability
.
.
.
.
.
.
.
.
.
.
.
.
. 129
CSV
Parser
.
.
.
.
.
.
.
.
.
.
.
.
.
. 129
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 130
DSML
Parser
.
.
.
.
.
.
.
.
.
.
.
.
. 130
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 131
Examples
.
.
.
.
.
.
.
.
.
.
.
.
.
. 131
See
also
.
.
.
.
.
.
.
.
.
.
.
.
.
. 131
Fixed
Parser
.
.
.
.
.
.
.
.
.
.
.
.
.
. 132
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 132
HTTP
Parser
.
.
.
.
.
.
.
.
.
.
.
.
. 132
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 132
Attributes
or
properties
.
.
.
.
.
.
.
.
. 132
See
also
.
.
.
.
.
.
.
.
.
.
.
.
.
. 134
LDIF
Parser
.
.
.
.
.
.
.
.
.
.
.
.
.
. 134
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 134
See
also
.
.
.
.
.
.
.
.
.
.
.
.
.
. 135
Line
Reader
Parser
.
.
.
.
.
.
.
.
.
.
. 135
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 135
Script
Parser
.
.
.
.
.
.
.
.
.
.
.
.
.
. 135
Objects
.
.
.
.
.
.
.
.
.
.
.
.
.
. 136
Functions
.
.
.
.
.
.
.
.
.
.
.
.
.
. 137
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 137
Example
.
.
.
.
.
.
.
.
.
.
.
.
.
. 137
See
also
.
.
.
.
.
.
.
.
.
.
.
.
.
. 137
Simple
Parser
.
.
.
.
.
.
.
.
.
.
.
.
. 138
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 138
SOAP
Parser
.
.
.
.
.
.
.
.
.
.
.
.
. 138
Example
Entry
.
.
.
.
.
.
.
.
.
.
.
. 138
Example
SOAP
document
.
.
.
.
.
.
.
. 138
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 139
Parser-specific
calls
.
.
.
.
.
.
.
.
.
. 139
Examples
.
.
.
.
.
.
.
.
.
.
.
.
.
. 139
XML
Parser
.
.
.
.
.
.
.
.
.
.
.
.
.
. 140
Configuration
.
.
.
.
.
.
.
.
.
.
.
. 141
Examples
.
.
.
.
.
.
.
.
.
.
.
.
.
. 141
Examples
.
.
.
.
.
.
.
.
.
.
.
.
.
. 143
See
also
.
.
.
.
.
.
.
.
.
.
.
.
.
. 143
User-defined
parsers
.
.
.
.
.
.
.
.
.
.
. 143
Chapter
5.
Script
languages
.
.
.
.
. 145
BSF-based
script
languages
.
.
.
.
.
.
.
.
. 145
WSH-based
script
languages
.
.
.
.
.
.
.
. 145
BeanShell
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 145
PerlScript
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 145
PerlScript
example
.
.
.
.
.
.
.
.
.
. 146
VB
Script
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 147
JavaScript
.
.
.
.
.
.
.
.
.
.
.
.
.
. 147
Java
and
JavaScript
.
.
.
.
.
.
.
.
.
.
. 147
Chapter
6.
Objects
.
.
.
.
.
.
.
.
. 149
The
AssemblyLine
Connector
object
.
.
.
.
.
. 149
The
attribute
object
.
.
.
.
.
.
.
.
.
.
. 149
Examples
.
.
.
.
.
.
.
.
.
.
.
.
.
. 149
See
also
.
.
.
.
.
.
.
.
.
.
.
.
.
. 150
The
Raw
Connector
object
.
.
.
.
.
.
.
.
. 150
Methods
.
.
.
.
.
.
.
.
.
.
.
.
.
. 150
The
Entry
object
.
.
.
.
.
.
.
.
.
.
.
. 151
Global
Entry
instances
available
in
scripting
.
. 151
See
also
.
.
.
.
.
.
.
.
.
.
.
.
.
. 151
The
FTP
object
.
.
.
.
.
.
.
.
.
.
.
.
. 152
Example
.
.
.
.
.
.
.
.
.
.
.
.
.
. 152
Main
object
.
.
.
.
.
.
.
.
.
.
.
.
.
. 152
The
Search
(criteria)
object
.
.
.
.
.
.
.
.
. 152
Operands
.
.
.
.
.
.
.
.
.
.
.
.
.
. 152
Example
.
.
.
.
.
.
.
.
.
.
.
.
.
. 153
The
shellCommand
object
.
.
.
.
.
.
.
.
. 153
The
status
object
.
.
.
.
.
.
.
.
.
.
.
. 153
The
system
object
.
.
.
.
.
.
.
.
.
.
.
. 153
The
task
object
.
.
.
.
.
.
.
.
.
.
.
.
. 153
Appendix
A.
Password
Synchronization
Plug-ins
.
.
.
.
.
. 155
Appendix
B.
AssemblyLine
and
Connector
mode
flowcharts
.
.
.
.
. 159
AssemblyLine
flow
.
.
.
.
.
.
.
.
.
.
. 160
Connector
initialization
.
.
.
.
.
.
.
.
. 163
Close
flow
.
.
.
.
.
.
.
.
.
.
.
.
. 164
AddOnly
mode
.
.
.
.
.
.
.
.
.
.
.
.
. 164
Call/Reply
mode
.
.
.
.
.
.
.
.
.
.
.
. 166
Delete
mode
.
.
.
.
.
.
.
.
.
.
.
.
.
. 168
On
Multiple
Entries
.
.
.
.
.
.
.
.
.
. 168
Iterator
mode
.
.
.
.
.
.
.
.
.
.
.
.
. 173
Lookup
mode
.
.
.
.
.
.
.
.
.
.
.
.
. 175
On
Multiple
Entries
.
.
.
.
.
.
.
.
.
. 175
Update
mode
.
.
.
.
.
.
.
.
.
.
.
.
. 178
On
Multiple
Entries
.
.
.
.
.
.
.
.
.
. 179
End-of-flow
for
all
modes
.
.
.
.
.
.
.
.
. 185
End-of-flow
.
.
.
.
.
.
.
.
.
.
.
.
. 185
Error
Handling
.
.
.
.
.
.
.
.
.
.
.
. 185
Appendix
C.
MOBJ
management
engine
.
.
.
.
.
.
.
.
.
.
.
.
.
. 189
The
JMX
MBean
Server
object
.
.
.
.
.
.
.
. 189
The
MOBJ
object
.
.
.
.
.
.
.
.
.
.
.
. 189
Appendix
D.
Notices
.
.
.
.
.
.
.
. 191
Third-party
component
statements
.
.
.
.
.
. 193
Apache
statement
.
.
.
.
.
.
.
.
.
.
. 193
Rhino
statement
.
.
.
.
.
.
.
.
.
.
. 194
Trademarks
.
.
.
.
.
.
.
.
.
.
.
.
.
. 194
Contents
vii
-
viii
IBM
Tivoli
Directory
Integrator
5.2:
Reference
Guide
-
Chapter
1.
Introduction
To
work
with
examples
complementing
this
manual,
you
must
refer
back
to
the
installation
package
to
download
the
necessary
files.
To
access
these
example
files,
go
to
the
root_directory/examples
directory
in
the
installation
directories.
©
Copyright
IBM
Corp.
2002,
2003
1
-
2
IBM
Tivoli
Directory
Integrator
5.2:
Reference
Guide
-
Chapter
2.
Connectors
Connector
availability
and
reference
The
following
is
a
list
of
all
Raw
Connectors
(and
AssemblyLine
Connectors)
included
with
the
IBM
Tivoli
Directory
Integrator.
You
can
also
make
your
own
Raw
Connectors
if
needed
(the
AssemblyLine
wraps
them
so
they
are
available
as
AssemblyLine
Connectors).
All
following
AssemblyLine
Connectors
have
access
to
the
methods
described
in
the
com.ibm.di.server.AssemblyLineComponent
in
addition
to
the
methods
and
properties
of
the
Raw
Connector.
Raw
Connectors
For
a
list
of
Supported
Modes,
see
“Legend
for
the
Supported
Mode
columns”
on
page
4.
For
each
Raw
Connector
listed,
see
the
documentation
outlined
in
this
chapter.
“Btree
Object
DB
Connector”
on
page
5
A
D
I
L
U
“Command
line
Connector”
on
page
6
A
I
“Direct
TCP
/URL
scripting”
on
page
7
?????
“Domino
Users
Connector”
on
page
7
A
D
I
L
U
“File
system
Connector”
on
page
20
A
I
“FTP
Client
Connector”
on
page
20
A
I
“Old
HTTP
Client
Connector”
on
page
21
A
D
I
L
U
C
“HTTP
Client
Connector”
on
page
23
A
I
L
C
“Old
HTTP
Server
Connector”
on
page
26
A
D
I
L
U
C
“HTTP
Server
Connector”
on
page
27
A
I
“JDBC
Connector”
on
page
28
A
D
I
L
U
“JMS
Connector”
on
page
31
A
I
L
C
“JNDI
Connector”
on
page
39
A
D
I
L
U
©
Copyright
IBM
Corp.
2002,
2003
3
-
“LDAP
Connector”
on
page
42
A
D
I
L
U
“IBM
Directory
Changelog
Connector”
on
page
49
I
“Netscape/iPlanet
Changelog
Connector”
on
page
50
I
“Active
Directory
Changelog
Connector”
on
page
51
I
“Exchange
Changelog
Connector”
on
page
56
I
“Lotus
Notes
Connector”
on
page
62
A
D
I
L
U
“Mailbox
Connector”
on
page
66
I
L
D
“Memory
Stream
Connector”
on
page
67
A
I
“MQe
Password
Store
Connector”
on
page
68
I
“NT4
Connector”
on
page
70
A
D
I
L
U
“RDBMS
Changelog
Connector”
on
page
74
I
“runtime-provided
Connector”
on
page
78
?
?
?
?
?
A
runtime
provided
Connector
is
a
Connector
sent
to
the
AssemblyLine
as
a
parameter
when
the
AssemblyLine
is
started.
We
cannot
say
what
modes
that
Connector
supports.
See
“runtime-provided
Connector”
on
page
78.
“Script
Connector”
on
page
78
A
D
I
L
U
C
You
write
the
Script
Connector
yourself,
and
it
provides
the
modes
you
write
into
it.
“SNMP
Connector”
on
page
80
I
A
L
“TCP
Connector”
on
page
81
I
A
“URL
Connector”
on
page
83
I
A
“Web
Service
Connector”
on
page
83
C
Legend
for
the
Supported
Mode
columns
v
A–AddOnly
v
D–Delete
v
I–Iterator
v
L–Lookup
v
U–Update
4
IBM
Tivoli
Directory
Integrator
5.2:
Reference
Guide
-
v
C–Call/Reply
v
?–Conditionally
supported,
see
documentation
v
+–Newer
version
support
exists
Script-based
Connectors
Another
source
of
problems
can
appear
if
you
use
the
same
libraries
as
IBM
Tivoli
Directory
Integrator.
A
new
version
of
IBM
Tivoli
Directory
Integrator
might
have
updated
libraries,
or
you
might
have
upgraded
your
libraries
since
the
last
time
you
compiled
your
Connector.
For
a
list
of
Supported
Modes,
see
“Legend
for
the
Supported
Mode
columns”
on
page
4.
Generic
Connector
?
?
?
?
?
You
write
the
Script
Connector
yourself,
and
it
provides
the
modes
you
write
into
it.
See
″JavaScript™
Connector″
in
IBM
Tivoli
Directory
Integrator
5.2:
Users
Guide.
Configurations
For
a
list
of
Supported
Modes,
see
“Legend
for
the
Supported
Mode
columns”
on
page
4.
Btree
Object
DB
Connector
The
Btree
Connector
is
a
simple
database
capable
of
storing
Java
objects.
Each
object
is
uniquely
identified
by
a
value
called
the
key.
The
Connector
uses
an
underlying
Btree
implementation
to
store
AssemblyLine
Entry
objects.
This
enables
the
user
to
store
the
conn
and
work
entries
using
a
unique
key.
This
Connector
is
also
used
by
the
AssemblyLine’s
Delta
feature,
although
in
version
5.2
and
later
of
the
product
the
usage
of
the
System
Store
is
recommended
for
this
purpose.
If
you
want
to
use
the
Btree
implementation
directly
to
store
a
Java
object
other
than
AssemblyLine
entries
you
must
first
get
the
Btree
object
and
then
use
its
methods
directly.
Notes:
1.
The
Btree
Connector
creates
a
new
Btree
database
if
one
does
not
exist.
However,
if
you
iterate
on
a
non-existing
database,
it
is
created
and
the
Iterator
returns
no
values.
2.
The
Btree
Connector
excels
at
small,
quick
jobs,
but
because
the
Btree
Connector
does
not
automatically
balance
its
data
structures,
it
breaks
down
when
sorted
lists
are
entered
containing
a
few
thousand
entries.
For
randomly-ordered
data
sets
the
limits
are
somewhat
higher.
For
larger
data
sets,
consider
the
CloudScape™
database
(see
″Using
CloudScape
database″
in
IBM
Tivoli
Directory
Integrator
5.2:
Users
Guide).
Configuration
The
Connector
needs
the
following
parameters:
DB
Filename
The
file
path
where
the
Btree
data
is
stored.
Key
Attribute
Name
The
attribute
name
giving
the
unique
value
for
the
entry.
Chapter
2.
Connectors
5
-
Selection
Mode
Specify
All,
Existing
or
Deleted.
In
order
to
use
the
Existing
and
Deleted
keywords,
the
Connector
(database)
must
have
been
used
by
an
AssemblyLine
with
the
delta
enabled.
When
Delta
is
enabled
on
an
Iterator
using
the
Btree
method,
the
AssemblyLine
stores
a
sequence
property
in
the
database
and
also
adds
a
sequence
number
to
each
entry
read
from
the
source.
Detailed
Log
If
this
field
is
checked,
an
additional
log
message
is
generated.
Btree
object
The
getDatabase()
method
returns
the
underlying
Btree
object.
This
object
can
be
used
to
store
other
Java
objects
than
AssemblyLine
entries.
The
following
snippet
shows
how
you
can
insert,
search
and
replace
objects
in
the
database:
var
bt
=
system.getConnector("btreedb");
bt.initialze
(null);
var
db
=
bt.getDatabase();
db.insert
("my
key",
new
java.lang.String("my
value"));
var
value
=
db.search
("my
key");
value
=
value
+
"
-
modified";
db.replace
("my
key",
value);
Note:
The
BTree
Connector
lets
you
Lookup
or
Update
on
the
keyAttribute
only.
Also,
the
BTree
Connector
does
not
support
the
Advanced
Link
Criteria
(see
″Advanced
link
criteria″
in
IBM
Tivoli
Directory
Integrator
5.2:
Users
Guide).
Command
line
Connector
The
command
line
Connector
enables
you
to
read
the
output
from
a
command
line
or
pipe
data
to
a
command
line’s
standard
input.
Every
command
argument
is
separated
by
a
space
character,
and
quotes
are
ignored.
Note:
You
do
not
get
a
separate
shell,
so
redirection
characters
(
|
>
and
so
forth)
do
not
work.
To
use
redirection,
make
a
shell-script
(UNIX®)
or
batch
command
(DOS)
with
a
suitable
set
of
parameters.
For
example,
on
a
Windows®
system,
type
cmd
/c
dir
to
list
the
contents
of
a
directory.
Configuration
The
Connector
needs
the
following
parameters:
Command
Line
The
command
line
to
run.
Detailed
Log
If
this
field
is
checked,
an
additional
log
message
is
generated.
Parser
The
Parser
responsible
for
interpreting
or
generating
entries.
Examples
Go
to
the
root_directory/examples/commandLine_connector
directory
of
your
IBM
Tivoli
Directory
Integrator
installation.
6
IBM
Tivoli
Directory
Integrator
5.2:
Reference
Guide
-
Direct
TCP
/URL
scripting
You
might
want
to
access
URL
objects
or
TCP
ports
directly,
not
using
the
Connectors.
The
following
is
example
code
that
can
be
put
in
your
Prolog:
TCP
//
This
example
creates
a
TCP
connection
to
www.example_page_only.com
and
asks
for
a
bad
page
var
tcp
=
new
java.net.Socket
(
"www.example_page_only.com",
80
);
var
inp
=
new
java.io.BufferedReader
(
new
java.io.InputStreamReader
(
tcp.getInputStream()
)
);
var
out
=
new
java.io.BufferedWriter
(
new
java.io.OutputStreamWriter
(
tcp.getOutputStream()
)
);
task.logmsg
("Connected
to
server");
//
Ask
for
a
bad
page
out.write
("GET
/smucky\r\n");
out.write
("\r\n");
//
When
using
buffered
writers
always
call
flush
to
make
sure
data
is
sent
on
connection
out.flush
();
task.logmsg
("Wait
for
response");
var
response
=
inp.readLine
();
task.logmsg
(
"Server
said:
"
+
response
);
URL
//
This
example
uses
the
java.net.URL
object
instead
of
the
raw
TCP
socket
object
var
url
=
new
java.net.URL("http://www.example_page_only.com");
var
obj
=
url.getContent();
var
inp
=
new
java.io.BufferedReader
(
new
java.io.InputStreamReader
(
obj
)
);
while
(
(
str
=
inp.readLine()
)
!=
null
)
{
task.logmsg
(
str
);
}
Domino
Users
Connector
The
Domino™
Users
Connector
provides
access
to
Lotus®
Domino
user
accounts
and
means
for
managing
them.
It
operates
in
Iterator,
Lookup,
AddOnly,
Update
and
Delete
modes
and
enables
the
following
operations
to
be
performed:
Iterator
Iterate
over
all
(or
a
filtered
subset
of)
Person
documents
from
the
Name
and
Address
Book.
Lookup
Search
for
and
retrieve
Person
documents
that
match
some
criteria.
AddOnly
Register
new
users
in
Domino
Server
and
create
their
Person
documents.
Update
Modify
users’
Person
documents;
Enable/disable
users;
Register
existing
(internet)
users.
Chapter
2.
Connectors
7
-
Delete
Post
requests
for
user
deletion
in
the
Domino
Server
Administration
Requests
Database.
Note:
Domino
Users
Connector
requires
Lotus
Notes®
to
be
release
5.0.8
or
higher.
Deployment
and
connection
to
Domino
server
The
Domino
Users
Connector
must
be
used
with
Lotus
Domino
Server
version
5.0.8
or
above.
IBM
Tivoli
Directory
Integrator
must
be
installed
and
run
from
the
machine
where
the
Domino
Server
is
installed
for
the
Domino
Users
Connector
to
function.
Add
the
pathname
of
Notes.jar
to
the
myclasspath
variable
in
both
the
ibmdisrv.bat
and
ibmditk.bat
files
(or
the
MYCLASSPATH
variable
in
both
the
ibmdisrv
and
ibmditk
files
if
you
are
not
operating
on
a
Windows
platform).
It
provides
interfaces
to
native
calls
that
access
the
Domino
Server.
This
library
is
provided
by
Lotus
and
can
be
found
in
the
folder
where
the
Domino
Server
is
installed
(for
example,
C:\Lotus\Domino).
The
file
ncso.jar
must
be
removed
from
the
root_directory/jars
folder.
Also,
remove
the
string
jars/ncso.jar;
from
the
myclasspath
variable
in
both
ibmdisrv.bat
and
ibmditk.bat
files
(or
the
MYCLASSPATH
variable
in
both
the
ibmdisrv
and
ibmditk
files
if
you
are
not
operating
on
a
Windows
platform).
Finally,
add
the
path
to
the
local
Domino
binaries
(for
example,
C:\Lotus\Domino)
to
the
PATH
environment
variable
inside
ibmditk
and
ibmdisrv.
Solaris-specific
settings
Edit
the
ibmditk
and
ibmdisrv
files
and
add
the
following
line
to
the
java
command
line:
-Djava.library.path=$PATH
This
enables
the
JVM
(and
therefore
the
Domino
Users
Connector)
to
find
the
required
Domino
libraries.
The
following
is
an
example
of
the
java
command
line:
/opt/IBM/IBMDirectoryIntegrator/_jvm/bin/java
\
-cp
$MYCLASSPATH
-Djava.library.path=$PATH
\
-Dcom.ibm.di.installdir=/opt/IBM/IBMDirectoryIntegrator
\
com.ibm.di.loader.IDILoader
com.ibm.di.admin.miadmin
"$@"
On
certain
versions
of
Domino
(at
least
5.0.8),
an
additional
change
to
the
java
command
line
is
required.
The
Domino
library
is
expecting
the
Java
property
os.name
to
be
SOLARIS,
when
in
fact
Java
1.3.1
returns
SunOS
as
the
value.
To
remedy
the
situation,
edit
ibmditk
and
ibmdisrv
and
add
the
following
line
to
the
java
command:
-Dos.name=SOLARIS
Here’s
an
example
line
with
all
of
the
previous
information:
/opt/IBM/IBMDirectoryIntegrator/_jvm/bin/java
\
-cp
$MYCLASSPATH
-Djava.library.path=$PATH
\
-Dos.name=SOLARIS
-Dcom.ibm.di.installdir=/opt/IBM/IBMDirectoryIntegrator
\
com.ibm.di.loader.IDILoader
com.ibm.di.admin.miadmin
"$@"
Linux
specific
settings
When
running
on
Linux,
you
must
make
the
java.library.path
changes
as
previously
mentioned.
The
following
is
an
example
of
the
Linux
startup
script:
8
IBM
Tivoli
Directory
Integrator
5.2:
Reference
Guide
-
/opt/IBM/IBMDirectoryIntegrator/_jvm/bin/java
\
-Xquickstart
-Xms16m
-cp
$MYCLASSPATH
-Djava.library.path=$PATH
\
-Dcom.ibm.di.installdir=/opt/IBM/IBMDirectoryIntegrator
\
com.ibm.di.loader.IDILoader
com.ibm.di.admin.miadmin
"$@"
To
authenticate
the
local
server
connection,
Domino
requires
the
user’s
short
name
and
internet
password
(these
are
Connector’s
parameters).
Configuration
The
Connector
needs
the
following
parameters:
Username
The
user
name
used
for
log
in
or
authentication
to
the
Domino
Server.
Password
The
password
for
the
Username.
Name
and
Address
Book
Database
The
name
of
the
Name
and
Address
Book
database
to
use.
Default
value
is
names.nsf.
Use
full-text
search
If
checked,
the
Connector
accesses
user
documents
through
the
People
view
and
full-text
searches.
If
not
checked,
the
Connector
uses
regular
database
searches.
In
this
case
the
Connector
automatically
narrows
the
database
search
to
user
documents
only,
by
accessing
only
documents
for
which
Form
item
value
is
Person.
This
parameter
affects
the
Iterator
and
Lookup
modes
only.
Full-text
filter
This
value
is
taken
into
account
only
when
Use
full-text
search
is
enabled.
This
parameter
contains
full-text
query
that
filters
the
user
documents
returned
by
the
Connector
in
Iterator
mode.
If
null
or
empty
string,
no
filtering
is
performed.
Default
value
is
″
″.
Formula
filter
This
value
is
taken
into
account
only
when
Use
full-text
search
is
not
enabled.
This
parameter
contains
a
formula
that
filters
the
users
returned
by
the
Connector
in
Iterator
mode.
The
Connector
automatically
adds
the
following
to
this
formula:
"&
Form
=
"Person""
which
limits
the
search
to
user
documents
only.
Default
value
is
″
″.
Detailed
Log
If
this
field
is
checked,
an
additional
log
message
is
generated.
Security
To
have
the
IBM
Tivoli
Directory
Integrator
access
the
Domino
Server,
you
might
have
to
enable
it
through
Domino
Administrator
->
Configuration
->
Current
Server
Document
->
Security
->
Java/COM
Restrictions.
The
user
account
you
have
configured
the
IBM
Tivoli
Directory
Integrator
to
use
must
belong
to
a
group
listed
under
Run
restricted
Java/Javascript/COM
and
Run
unrestricted
Java/Javascript/COM.
Chapter
2.
Connectors
9
-
Using
the
Domino
Connector
Iterator
mode
The
Connector
iterates
through
the
Person
documents
of
the
Name
and
Address
Book
database.
All
Person
documents
(matching
the
filter,
if
filter
is
set)
are
delivered
as
Entry
objects,
and
all
document
items,
except
attachments,
are
transformed
into
Entry
attributes.
Along
with
the
attributes
corresponding
to
the
Person
document
items,
the
Entry
returned
by
the
Connector
contains
some
extra
(derived)
attributes
for
which
values
are
calculated
by
the
Connector.
Here
is
the
list
of
the
derived
attributes:
DER_IsEnabled
(Boolean)
Specifies
whether
the
user
is
enabled/disabled:
v
true
-
if
the
user
does
not
belong
to
a
Deny
List
only
group
v
false
-
if
the
user
belongs
to
at
least
one
Deny
List
only
group
Lookup
mode
In
Lookup
mode,
the
Connector
performs
searches
for
user
documents,
and
the
type
of
search
depends
on
the
value
of
the
Use
full-text
search
parameter:
v
Use
full-text
search
=
true:
The
Connector
performs
a
full-text
search
in
the
People
view.
Full-text
searches
work
both
with
full-text
indexed
and
not
full-text
indexed
databases.
However,
the
search
is
less
efficient
if
the
database
is
not
full-text
indexed.
It
is
also
possible
that
the
database
full-text
index
is
not
updated,
in
which
case
the
search
results
do
not
match
the
actual
database
content.
v
Use
full-text
search
=
false:
The
Connector
performs
a
regular
database
search
using
Lotus
formula.
The
element
(Form
=
″Person″)
is
automatically
added
to
the
formula
by
the
Connector,
so
the
search
is
limited
to
user
documents
only.
When
simple
link
criteria
is
used,
you
can
use
both
canonical
(CN=UserName/O=Org)
and
abbreviated
(UserName/Org)
name
values
to
specify
the
user’s
FullName.
The
Connector
automatically
processes
and
converts
the
value
you
specified,
if
necessary.
When
advanced
link
criteria
is
used,
you
must
be
careful
and
specify
the
user’s
FullName
in
the
correct
format,
which
is:
v
for
full-text
search:
use
abbreviated
names
(UserName/Org)
v
for
regular
database
search:
use
canonical
names
(CN=UserName/O=Org)
AddOnly
mode
The
AddOnly
mode
always
adds
a
new
Person
document
in
the
Name
and
Address
Book
database.
The
add
process
accepts
whatever
attributes
are
provided
by
the
Attribute
Mapping,
however
to
have
correct
user
processing
by
Domino,
the
attribute
names
must
match
the
Item
names
Domino
operates
with.
As
the
Connector
operates
with
users
only,
it
always
sets
the
attributes
Type
and
Form
to
the
value
of
Person,
thus
overriding
any
values
set
to
these
attributes
during
the
Attribute
Mapping
process.
The
LastName
Domino
user
attribute
is
required
for
successful
creation
of
a
Person
document.
The
HTTPPassword
attribute
is
not
required,
but
if
present
its
value
is
automatically
hashed
by
the
Connector.
Depending
on
a
fixed
schema
of
attributes,
the
Connector
can
register
the
new
user.
The
table
below
specifies
these
attributes
and
the
Connector
behavior
according
to
their
presence
or
absence
in
the
conn
Entry,
and
their
values:
10
IBM
Tivoli
Directory
Integrator
5.2:
Reference
Guide
-
Attribute
name
Type
Required
for
registration?
Value
REG_Perform
Boolean
Yes
If
set
to
true
the
Connector
performs
user
registration.
If
this
attribute
is
missing,
or
its
value
is
false,
the
Connector
does
not
perform
user
registration,
regardless
of
the
presence
and
the
values
of
the
other
REG_
Attributes.
REG_IdFile
String
Yes
Contains
the
full
path
of
the
ID
file
to
be
registered.
For
example,
c:\\newuserdata
\\newuser.id
REG_UserPw
String
Yes
The
user’s
password.
REG_CertifierIDFile
String
Yes
The
full
file
path
to
the
certifier
ID
file.
REG_CertPassword
String
Yes
The
password
for
the
certifier
ID
file.
Note:
If
the
certifier
password
is
wrong
when
registering
users,
a
popup
window
is
displayed.
Ensure
that
the
Certifier
password
is
correctly
specified.
REG_Server
String
No
The
name
of
the
server
containing
the
user’s
mail
file.
If
this
attribute
is
missing,
the
value
is
obtained
from
the
Connector’s
Domino
Session
object.
REG_CreateMailDb
Boolean/String
No
true
-
Creates
a
mail
database
false
-
Does
not
create
a
mail
database;
it
is
created
during
setup.
If
this
attribute
is
missing,
a
default
value
of
false
is
assumed.
If
this
attribute
is
true,
the
MailFile
attribute
must
be
mapped
to
a
valid
path.
Chapter
2.
Connectors
11
-
REG_Expiration
Date
No
The
expiration
date
to
use
when
creating
the
ID
file.
If
the
attribute
is
missing,
or
its
value
is
null,
a
default
value
of
the
current
date
+
2
years
is
used.
REG_IDType
Integer/String
No
The
type
of
ID
file
to
create:
0
-
create
a
flat
ID
1
-
create
a
hierarchical
ID
2
-
create
an
ID
that
depends
on
whether
the
certifier
ID
is
flat
or
hierarchical.
If
the
attribute
is
missing,
a
default
value
of
2
is
used.
REG_Is
NorthAmerican
Boolean/String
No
true
-
the
ID
file
is
North
American
false
-
the
ID
file
is
not
North
American.
If
this
attribute
is
missing,
a
default
value
of
true
is
used.
REG_OrgUnit
String
No
The
organizational
unit
to
use
when
creating
the
ID
file.
If
this
attribute
is
missing,
a
default
value
of
″
″
is
used.
REG_RegistrationLog
String
No
The
log
file
to
use
when
creating
the
ID
file.
If
this
attribute
is
missing,
a
default
value
of
″
″
is
used.
REG_StoreID
InAddressBook
Boolean/String
No
true
-
stores
the
ID
file
in
the
server’s
Domino
Directory
false
-
does
not
store
the
ID
file
in
the
server’s
Domino
Directory.
If
this
attribute
is
missing,
a
default
value
of
false
is
used.
REG_Registration
Server
String
No
The
server
to
use
when
creating
the
ID
file.
This
attribute
is
used
only
when
the
created
ID
is
stored
in
the
server
Domino
Directory,
or
when
a
mail
database
is
created
for
the
new
user.
12
IBM
Tivoli
Directory
Integrator
5.2:
Reference
Guide
-
REG_MinPassword
Length
Integer/String
No
The
RE