IBM Tivoli Directory Integrator 6.0: Release...

IBM Tivoli Directory Integrator 6.0:

Release Notes

December 14, 2004

Tivoli®

IBM Tivoli Directory Integrator 6.0:

Release Notes

��

Note

Before using this information and the product it supports, read the general information under “Notices,” on page 13.

Contents

Chapter 1. Additional components . . . 1

Chapter 2. Last-minute changes,

limitations and errata . . . . . . . . . 3

Documentation issues . . . . . . . . . . . 3

Config Editor issues . . . . . . . . . . . . 4

Server/Components issues . . . . . . . . . 7

Appendix. Notices . . . . . . . . . . 13

Third-party component statements . . . . . . 15

Apache statement . . . . . . . . . . . 15

Rhino statement . . . . . . . . . . . . 16

Additional attributions . . . . . . . . . 16

Trademarks . . . . . . . . . . . . . . 16

© Copyright IBM Corp. 2004 iii

iv IBM Tivoli Directory Integrator 6.0: Release Notes

Chapter 1. Additional components

In conjunction with the release of IBM® Tivoli® Directory Integrator 6.0, a number

of new, unbundled products have been released as well. These are:

v SAP Connector

v PeopleSoft Connector

v Siebel ERP Connector

More information, and instructions as to how to download and install these

components, can be found on the TDI Support site1.

1. The TDI support site can be found at http://www-306.ibm.com/software/sysmgmt/products/support/IBMDirectoryIntegrator.html

© Copyright IBM Corp. 2004 1

http://www-306.ibm.com/software/sysmgmt/products/support/IBMDirectoryIntegrator.html

2 IBM Tivoli Directory Integrator 6.0: Release Notes

Chapter 2. Last-minute changes, limitations and errata

This section will attempt to list problems and limitations in either the

documentation or the actual product that have been uncovered within the IBM

Tivoli Directory Integrator 6.0 product after it was released to Manufacturing but

before General Availability.

These issues will be addressed in future versions of IBM Tivoli Directory Integrator

6.0, either by means of a Fixpack or in a new version of the product.

Documentation issues

Table 1. Documentation issues

Manual Issue

Administrator

Guide

z/OS environment Support: The DSMLv2 Parser is supported on z/OS

but was omitted from the list.

Administrator

Guide

z/OS environment Support: The list of supported components should

have listed ″CSV Parser″, not ″CVS Parser″.

Administrator

Guide

z/OS environment Support: The list of supported components should

have listed ″Timer Connector″, not ″Timer Server Connector″.

Users Guide Branching: The documentation on exitBranch claims that there are the

following reserved names: ″Branch″, ″Loop″, ″Flow″ or ″AssemblyLine″.

This is almost correct.

The actual reserved exitBranch() names are:

v Cycle - same as system.skipEntry();

v Flow - Jumps to Response section. If no response section, same as

system.skipEntry().

v Response - same as system.skipEntry() (e.g. called from inside a

Response component)

v AssemblyLine - Jumps to Epilog.

Users Guide,

JavaDocs

The documentation on the COMProxy Object fails to document the

limitations of the current implementation—refer to the

Server/Components section for more information.

Administrator

Guide

Installing local Help: This section claims that you can download a set of

plugins from the Tivoli Documentation Library named

com.ibm.IBMDI.doc_6.0.zip. In reality, the name of the file to download is

com.ibm.IBMDI.doc_download.zip, and it only contains the

com.ibm.IBMDI.doc plugin.

Administrator

Guide

Supported platforms: a subset of IBM Tivoli Directory Integrator 6.0 is

available in the native z/OS environment. In the section on z/OS

environment support, this is listed as z/OS version 1.4, but subsequent

testing has enabled support for z/OS version 1.5 and 1.6 as well.


Table 1. Documentation issues (continued)

Manual Issue

Users Guide Appendix A, in the section about Connectors: new Connector modes, the

documentation erroneously states that ″AssemblyLines can now be

configured for automatic launching when the Server starts up by

including them in the new Config->Startup list of the Config Browser.″

This particular element in the Config Browser is in fact called AutoStart,

so the sentence should read: ″Furthermore, AssemblyLines can now be

configured for automatic launching when the Server starts up by

including them in the new Config->AutoStart list of the Config

Browser.″

Config Editor issues

Table 2. Config Editor issues

Component Issue

Config Browser:

NLS

When using the Config Editor, the left pane of the window shows the

configuration tree. The names of the folders are not translated, they

appear as Config, AssemblyLines, Connectors, Functions, Parsers,

AtributeMaps, Scripts, EventHandlers, Includes, ExternalProperties,

JavaLibraries, JavaProperties. Note that these English names are used in

log messages anyway, so in a sense it is advantageous to get used to the

English names.

NLS When using the Config Editor, some text may appear in italics (e.g.

inherited attributes). This looks ugly in Taiwan Chinese.

Workaround

Try to change font to a font without italics, if possible. Use File -> Edit

Preferences, set Appearance->Look&Feel to Metal, and change the fonts

under Theme Settings.

CE Usage When using the IBM Directory Integrator Config Editor for an extended

period of time, e.g. several days, it may become sluggish or even crash

due to lack of memory. This may cause work to be lost.

Workaround

Try to save your work regularly, e.g. every hour. Also, when doing so,

exit and restart the Config Editor. Remember that while it is possible to

run AssemblyLines and EventHandlers from the Config Editor, this is

only meant as a way of testing your configuration. For production work,

you should start the IBM Directory Integrator server as a separate

process, specifying the correct command line switches.

JVM:NLS The IBM Directory Integrator Config Editor may not start properly on a

HP-UX computer with locale zh_TW.utf8, you get a JVM error and core

dump.

WorkaroundEdit your configuration file on another computer, or use a

different locale.


Table 2. Config Editor issues (continued)

Component Issue

JDBC When trying different JDBC drivers using the IBM Directory Integrator

Config Editor, you should be aware that once you have tried a driver

that makes a connection, that driver will be used even if you later

specify an invalid driver.

Workaround

If you believe this to be the case, restart the IBM Directory Integrator

Config Editor.

External editor When you launch an external editor to look at a script or a hook, even if

you make no changes, the script is marked as changed, and therefore it

is no longer considered inherited.

Workaround

Reestablish the inheritance if necessary. You may also want to edit

preferences, and disable the ″Wait and Paste from External Editor″

checkbox under ″Editor Settings″.

CE Usage Sometimes drop-downs are not updated when new components are

added, e.g. if you copy/paste a Script from one configuration file to

another, the drop-down for new scripts will not show the new

component.

WorkaroundClose the AssemblyLine screen and reopen it.

CE Usage The Link Criteria Attribute drop-down is empty after quick discovery.

This could be related to the previous problem, as drop-downs are

generally not populated on the fly, but when they are created.

Workaround

Close the AssemblyLine screen and reopen it.

Ext Props External Props GUI is misbehaving; however, this problem has been

difficult to reproduce. Under certain circumstances, the Ext Props GUI

does not work consistently, especially when editing Config files

originally edited on another machine (where file paths may be different).

Schema set-up Connect/read next/query schema not working if reused connection: If

you are reusing a connector in an AssemblyLine, the connect/read

next/quick discovery of schema buttons do not work.

Workaround

Use the original connector to discover/establish the schema.

CE Usage The auto-numbering of AL component names is in conflict with

convention. The CE auto-numbers components in an AL with ″-x″ where

″x″ is a sequential count whenever you attempt to drag in a component

with a name that already exists in the AL.

This feature actually breaks with the naming convention for AL

components, since these will be declared as scripting variables. As a

result, any disabled auto numbered components result in the warning

Problem when declaring "<comp name>-1", possibly illegal name

Workaround

Give the component a proper name, especially if you will be referencing

it in scripts.

Chapter 2. Last-minute changes, limitations and errata 5


Component Issue

Configuration

Report

When using the Object->Configuration Report command, if your

solution directory is not the same as your installation directory, the file

browser to choose a configuration template will open in the wrong

directory.

Workaround

Use the file browser to navigate to the installation directory, then choose

the templates folder, and then the AL folder.

Remote CE You can get an unmarshall exception when you try to save a local config

file as remote, with default params.

Workaround

While saving to the remote machine, you would not necessarily know

the kind of file system or path, so it is advisable to save relative, i.e.

without specifying the absolute path. This would save the Config file in

the Solutions directory. In other words, remove any path information

from the File field of the Save As... remote dialog.

Remote CE Similar to the above problem, you cannot manipulate external proporties

from the Remote CE. The path specified for the external properties file

must exist on both remote and local machines.

Workaround

Only use relative path specifications for External Properties files.

Remote CE User cannot run AL/EH if property api.remote.ssl.on = false on the

remote server (java.net.SocketException).

Workaround

The remote server needs to have the api.remote.ssl.on = false

property set to true; SSL is a prerequisite for the Remote Server API.

Remote CE

Usage

If you use the ’tabbed browser’ view for the Config Browser, the

filename displayed on the tab for a ″saved as″ file is a temporary file

name instead of the defined format.

Workaround

Use the tree view for the Remote CE.

Remote CE Whenever you add a new component(Connector/Parser/FC etc.), the list

of System components displayed is the one installed on the local

machine and the chosen component may or may not exist on the remote

machine.

Workaround

You can confirm whether the component exists from the list of installed

components on the remote machine from the Help Menu: Help -> About

Remote IBM Tivoli Directory Integrator Components

Remote CE

Usage

After adding a new AL, you have to save the config before running it for

changes to be reflected on the remote machine.

Shortcuts The ToolTips for the Save Config button claims Alt+S is the shortcut,

instead of Ctrl+S.

Inheritance The Reconnect button is missing from the Inheritance dialog.



Component Issue

Copy/Paste Drag-drop of ALs between Configs does not copy over dependent

components the way Copy/Paste does.

Workaround

Use Copy/Paste to move Components.

Branch/Loop Disabling a Branch or Loop Component inside a Branch or Loop

Component can cause problems. If the Branch Component evaluates to

false, or when the Loop Component exits, the flow continues at the

wrong point (it skips too far ahead; the amount of skipping depends on

the number of components inside the disabled Component).

Workaround

Move the disabled Branch or Loop Component outside the Branch or

Loop Component it is inside of, e.g. to the end of the AssemblyLine.

Server/Components issues

Table 3. Server/Components issues

Component Issue

LDAP

Connector

The version of the LDAP Connector included in TDI 6.0 may hang while

trying to Add/Update an entry with a invalid Distinguished Name (DN)

containing a backslash (or escape character ’\’). This is because of a bug

in the Java Virtual Machine bundled with this release. This bug has been

reported to the IBM Java support team and is currently being worked

on.

The TDI Team will try to address this bug along with the next Java

upgrade pack for TDI 6.0.

LDAP Server

EH

An LDAP client might go into a infinite wait state if it tries to use SSL

when connecting to an LDAP Server EH which is running in non-SSL

mode. The client may not understand the error sent by the ServerSocket

class.

Workaround

If the client is trying to connect with SSL on, ensure that the LDAP

Server EH is running with SSL on.

File Connector There is a maximum file size limit of 2GB for files accessed through the

File Connector, both for input as well as output.

JavaScript For legal reasons, the version of Rhino in IBM Tivoli Directory Integrator

6.0 had to be downgraded from 1.5R4 to 1.5R2. This may cause some

performance degradation, but could also cause scripts to malfunction,

especially if they use the string replace (regexp) methods in JavaScript.

If you believe this to be a problem, replace jars/js.jar in the installation

folder for TDI 6.0 with a version obtained from The Mozilla

Organization. There are multiple versions available, however 1.5R4 is the

one which has been tested.

Server API /

AMC2

On Windows the system (Server API) log files of running AssemblyLines

and EventHandlers are locked by the operating system. That is why the

Server API and AMC2 functions for cleaning up log files would not be

able to delete log files currently in use.


http://www.mozilla.org/rhino/download.html

http://www.mozilla.org/rhino/download.html

Table 3. Server/Components issues (continued)

Component Issue

DSMLv2 Parser The DSMLv2 Parser does not support some optional DSMLv2 schema

attributes (among them the ″requestID″ attribute).

Server Even though the global.properties file might be read only (for example

on z/OS), if it contains properties for encryption, the Server will try to

overwrite it on startup. This operation will fail and will result in a

message ″error writing to file″ logged on the console. No workaround is

necessary, because if the user has made the global.properties file read

only, he would not like it to be modified.

Plugins on

Solaris

The idicryptokeys.sh shell script bundled with the Password

Synchronizers on Solaris contains a wrong path to the Java keytool

utility. As a result of that this shell script fails.

Workaround

Instead of running the idicryptokeys.sh script users can run the

following two commands in this order:

1. ./_jvm/bin/keytool -genkey -alias idicryptotest -keypass secret

-storepass secret -keystore idicryptotest.jks -storetype JKS -keyalg

RSA

2. ./_jvm/bin/keytool -list -v -alias idicryptotest -keystore

idicryptotest.jks -storepass secret -storetype JKS

Web Services

tutorial example

The Web Services Tutorial sample SSL certificates have expired.

Workaround

You can create new SSL certificates and can use these new certificates to

run the SSL examples.

Here is how you can create an SSL certificate to use with the web service

components using the standard Java utility keytool:

1. keytool -genkey -dname cn=localhost -validity 18263 -keystore

server.jks -storepass secret -keypass secret

2. keytool -export -alias mykey -file server.cer -keystore server.jks

-storepass secret

3. keytool -import -trustcacerts -file server.cer -keystore server.jks

-storepass secret -alias mytrustedkey

Answer ″yes″ and press Enter to the ″Certificate already exists in

keystore under alias <mykey> Do you still want to add it? [no]:″

question.

After these steps are executed a server.jks keystore file is created which

contains a key for the server. This file is also a truststore which contains

the server public key, i.e. trusts the server key. In this way this server.jks

file can be used as both the server keystore and client truststore file.

Note: An SSL server certificate for use with the web service components

must contain a key whose distinguished name (dname) must match the

name of the host on which the server AssemblyLine runs. For this

example we have chosen to use ″cn=localhost″, which means that only

requests from the local machine are allowed.



Component Issue

IDS and

SunONE

plugins

installation on

Windows

IDS Plugin: Wrong default paths in idspwconfigWin.props

If during installation of the IDS or Sun ONE Password Synchronizer

under Windows, you choose a directory different than the default one

suggested by the installer, the Password Synchronizer configuration file

(idspwconfigWin.props for IDS, sunpwsync.props for Sun ONE) will

contain a few properties with the default install path (for example

″C:\IDSPWSync″ instead of the path chosen by the user on installation).

If the plugin is started with the these property values, it will fail.

Workaround

If you do specify an install folder different from the default, you will

need to do the following after the install completes and before running

the plugin: edit the configuration file manually (idspwconfigWin.props

for IDS, sunpwsync.props for Sun ONE) and set the correct install file

path.

JVM When running the IBM Tivoli Directory Integrator Server, the logfile

created should contain a line like this: 2004-11-10 11:02:43,254 INFO

[/home/jens/6.0/cmvc-update.xml] - Java Runtime : IBM Corporation,

1.4.2 On some OS’s, e.g. Solaris and HP-Ux, the message may not specify

IBM as the vendor of the Java Runtime.

Workaround

If running on Solaris or HP-UX, assume that IBM is the vendor of the

Java Runtime.

Mailbox EH The mailbox EventHandler may crash when used with a Domino server

as IMAP server.

Logging The Error log does not show the name of an AttrributeMap component.

Errors from Attribute Map Components do not show the name of the

Attribute Map Component, only the name of the AssemblyLine, and

often (depending on the error), the name of the attribute being mapped.

Workaround

The message will often contain the name of the attribute that is mapped,

which should give you a hint as to which Attribute Map it is that fails.

Attribute Map

Component

If you create an AssemblyLine with the new AttributeMap Component,

you will always get the message that the AssemblyLine failed when

running it, even if there were no problems.

Workaround

Read the log carefully, and if there does not seem to be a problem with

the AssemblyLine, ignore the message.

Installer The Installer assumes C: as install disk and does not let you start if not

enough room on that disk, even if you install on another disk.

Workaround

Temporarily move some files off the C: disk, then after installation, move

them back again.

HTTP Server

Connector

There is no SSL support in the HTTP Server Connector.



Component Issue

HTTP Server

Connector

When running an AL containing the HTTP Server Connector from the

CE, closing the Execute window without first explicitly stopping the AL

does not always release the TCP/IP port it used.

Workaround

Either always stop the AL first before closing the Execute window, or

stop and restart the CE to free the port.

FTP Connector The FTP Client Connector does not work with IPv6. The reason is that

the PORT command assumes a 32 bit address, while IPv6 uses 128 bit

addresses. There is currently no workaround for this problem.

API The API call system.copyFile() does not work across platforms. This is

because it is using the corresponding Java method, which has the same

problem.

Memory Queue

(MemQ)

MemQ does not provide persistance. The database support is used just

as an extra store if the memory available or allocated is insufficient. The

table is deleted after use.

Memory Queue

(MemQ)

The default name given to all MemQ’s created from CE is always

<stdin> whereas those created by the server will have the thread name

as the default name, though you can specify any name.

Fail-Over

Service (FOS)

The FoS has to be restarted after every change in FoS Configuration.

Workaround

This is a current limitation of FoS. AMC2.0 is the only way you could

configure FoS. FoS reads this configuration at startup and configures the

fail over service. If you change the FoS Configuration then you need to

restart the FoS.

Fail-Over

Service (FOS)

FoS can only be run with servers where the Server API RMI runs over

SSL. (Note that this is a requirement for the Remote CE as well.)

AMC 2.0 AMC 2.0 relies upon Tomcat, a Java-based application server. Tomcat has

problems with RMI when it is installed in a path with spaces in it so

you therefore may have to install amc (and therefore TDI) in a directory

that does not have any spaces in it. (See also

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4543)

AMC 2.0 The Config Editor provides a way to encrypt External Properties files.

Also there are options for which cipher to use and password. However,

AMC2 can display/edit/add/remove the default External Properties file

only.

AMC 2.0 On ″Manage -> Users″ screen (and certain others) an AMC admin can

only enter English characters.

This is currently a limitation with displaying entered multibyte

characters.

AMC 2.0 For Connectors, Parsers and EventHandlers, the user can only edit the

properties that have not been inherited and ones that do not have

default values. (These parameters are not returned from the server.)



Component Issue

COMProxy You cannot use early binding that is calling functions directly using

VTBL. You can call the functions directly but internally it would always

use late binding i.e. use the invoke method of IDispatch. Functions can

only be called using the ″call″ method of the COMProxy Object as

COMProxy.call(<IDispatch object>,<method name>,<params>)

Workaround

Use enumMethods to get the signature of all methods and properties

supported by an interface.

COMProxy You can’t launch host ActiveX controls or applications from TDI.

COMProxy You cannot create a component object in one thread and call it from

another thread. The COMProxy object does not support various

threading models.

COMProxy You need to call Release() on the component after use, otherwise there

will be a resource leak.

COMProxy COMProxy cannot communicate with managed code, unless the .Net

component has registered itself for interoperability with COM.


Appendix. Notices

This information was developed for products and services offered in the U.S.A.

IBM might not offer the products, services, or features discussed in this document

in other countries. Consult your local IBM representative for information on the

products and services currently available in your area. Any reference to an IBM

product, program, or service is not intended to state or imply that only that IBM

product, program, or service may be used. Any functionally equivalent product,

program, or service that does not infringe any IBM intellectual property right may

be used instead. However, it is the user’s responsibility to evaluate and verify the

operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter in

this document. The furnishing of this document does not give you any license to

these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation

North Castle Drive

Armonk, NY 10504-1785

U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM

Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation Licensing

2-31 Roppongi 3-chome, Minato-ku

Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other

country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS

PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER

EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED

WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS

FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or

implied warranties in certain transactions, therefore, this statement may not apply

to you.

This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be

incorporated in new editions of the information. IBM may make improvements

and/or changes in the product(s) and/or the program(s) described in this

information at any time without notice.

Any references in this information to non-IBM Web sites are provided for

convenience only and do not in any manner serve as an endorsement of those Web

sites. The materials at those Web sites are not part of the materials for this IBM

product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it

believes appropriate without incurring any obligation to you.


Licensees of this program who wish to have information about it for the purpose

of enabling: (i) the exchange of information between independently created

programs and other programs (including this one) and (ii) the mutual use of the

information which has been exchanged, should contact:

IBM Corporation

Department MU5A46

11301 Burnet Road

Austin, TX 78758

U.S.A.

Such information may be available, subject to appropriate terms and conditions,

including in some cases, payment of a fee.

The licensed program described in this document and all licensed material

available for it are provided by IBM under terms of the IBM Customer Agreement,

IBM International Program License Agreement, or any equivalent agreement

between us.

Any performance data contained herein was determined in a controlled

environment. Therefore, the results obtained in other operating environments may

vary significantly. Some measurements may have been made on development-level

systems and there is no guarantee that these measurements will be the same on

generally available systems. Furthermore, some measurement may have been

estimated through extrapolation. Actual results may vary. Users of this document

should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of

those products, their published announcements or other publicly available sources.

IBM has not tested those products and cannot confirm the accuracy of

performance, compatibility or any other claims related to non-IBM products.

Questions on the capabilities of non-IBM products should be addressed to the

suppliers of those products.

This information contains examples of data and reports used in daily business

operations. To illustrate them as completely as possible, the examples include the

names of individuals, companies, brands, and products. All of these names are

fictitious and any similarity to the names and addresses used by an actual business

enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which

illustrate programming techniques on various operating platforms. You may copy,

modify, and distribute these sample programs in any form without payment to

IBM, for the purposes of developing, using, marketing or distributing application

programs conforming to the application programming interface for the operating

platform for which the sample programs are written. These examples have not

been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or

imply reliability, serviceability, or function of these programs. You may copy,

modify, and distribute these sample programs in any form without payment to

IBM for the purposes of developing, using, marketing, or distributing application

programs conforming to IBM’s application programming interfaces.

Each copy or any portion of these sample programs or any derivative work, must

include a copyright notice as follows:


© (your company name) (year). Portions of this code are derived from IBM Corp.

Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rights

reserved.

If you are viewing this information softcopy, the photographs and color

illustrations may not appear.

Third-party component statements

Apache statement

This product includes software developed by the Apache Software Foundation

(http://www.apache.org/). The Apache components may include the Xerces,

Xalan, XML4J, and Log4J libraries, and these are provided in object code form. This

object code was obtained from the Apache web site and is unmodified.

Apache license

The Apache Software License, Version 1.1

Copyright (c) 1999-2002 The Apache Software Foundation. All rights reserved.

Redistribution and use in source and binary forms, with or without modification,

are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list

of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this

list of conditions and the following disclaimer in the documentation and/or

other materials provided with the distribution.

3. The end-user documentation included with the redistribution, if any, must

include the following acknowledgment: ″This product includes software

developed by the Apache Software Foundation (http://www.apache.org/).″

Alternately, this acknowledgment may appear in the software itself, if and

wherever such third-party acknowledgments normally appear.

4. The names ″Xerces″, ″Xalan″, ″log4j″, ″mx4j″ and ″Apache Software Foundation″

must not be used to endorse or promote products derived from this software

without prior written permission. For written permission, please contact

[email protected].

5. Products derived from this software may not be called ″Apache″, nor may

″Apache″ appear in their name, without prior written permission of the Apache

Software Foundation.

THIS SOFTWARE IS PROVIDED ″AS IS″ AND ANY EXPRESSED OR IMPLIED

WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED

WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR

PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE

FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT,

INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL

DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF

SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR

BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF

LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT

(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF

THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF

SUCH DAMAGE.

Appendix. Notices 15

This software consists of voluntary contributions made by many individuals on

behalf of the Apache Software Foundation. For more information on the Apache

Software Foundation, please see http://www.apache.org

Rhino statement

The IBM Tivoli Directory Integrator uses Rhino (JavaScript™ for Java™) object code.

The source code for Rhino is located at

http://www.mozilla.org/rhino/download.html and is available under the terms of

the Netscape Public License 1.1 (http://www.mozilla.org/MPL/NPL-1.1.html). The

Rhino source code found on the Mozilla Web site was not modified in generating

the object code used in IBM Tivoli Directory Integrator.

Additional attributions

IBM Tivoli Directory Integrator uses ANTLR developed by jGuru.com; see

http://www.ANTLR.org and http://www.jGuru.com

IBM Tivoli Directory Integrator uses Castor developed by the ExoLab Project; see

http://www.exolab.org/

IBM Tivoli Directory Integrator includes software developed by the MX4J project.

Trademarks

The following terms are trademarks of International Business Machines

Corporation in the United States, or other countries, or both:

IBM Tivoli AIX® Lotus®

Notes® pSeries® DB2® WebSphere®

OS/390® Domino® iNotes CloudScape

Java, JavaScript and all Java-based trademarks and logos are trademarks or

registered trademarks of Sun Microsystems, Inc. in the United States and other

countries.

Microsoft®, Windows NT® and Windows® are registered trademarks of Microsoft

Corporation.

Intel™ is a trademark of Intel Corporation in the United States, other countries, or

both.

UNIX® is a registered trademark of The Open Group in the United States and

other countries.

This product includes software developed by the Apache Software Foundation

(http://www.apache.org/).

Other company, product, and service names may be trademarks or service marks

of others.


http://www.antlr.org/

http://www.jguru.org/

http://www.exolab.org/

��

Printed in USA

IBM Tivoli Directory Integrator 6.0: Release...

Documents

Transcript of IBM Tivoli Directory Integrator 6.0: Release...