IBM Lotus Enterprise Integrator for Domino (LEI) Release 7.0 January 10, 2006 A) What's New in LEI Release 7.0 B) System Requirements C) Installation Considerations D) Installing LEI - General Instructions E) Uninstalling LEI F) Operational Considerations G) What's Been Fixed in LEI Release 7.0 H) Documentation Errata I) Troubleshooting and Additional Support _______________________________________________________________________________ A) What's New in LEI Release 7.0 For the latest information about Enterprise Integration offerings, visit the http://www.lotus.com/ei Web site or the Lotus Documentation site http://www.lotus.com/doc. LEI Release 7.0 contains the following new features and enhancements. - Memory management LEI, DECS, and LC LSX now use Domino memory management. If you wish to use operating system calls for memory allocations, you can set EIUseOSMemory=1 in the notes.ini file and then restart your Domino server or Notes client. - Lotus Connectors Several Lotus Connectors changes have been made in LEI 7.0. - Updated database version support See the first chapter in the LEI installation guide for the current list of supported database versions relative to the supplied connector types. This list is also in the Lotus Connectors and Connectivity Guide in the "Supported Lotus Connector Versions" section. - DataDirect driver availability The Lotus-branded DataDirect drivers are available for download on IBM Passport Advantage for licensed LEI users at the following Web address: http://www-306.ibm.com/software/howtobuy/passportadvantage/ - Lotus Connector for Sybase LEI release 7.0 supports the Sybase 12.5 client; it no longer supports the Sybase 11.x drivers. - Lotus Connector for Oracle The Lotus Connector for Oracle 7 is being retired in LEI 7.0. The Lotus Connector for Oracle supports Oracle 8.1.7, 9 (9.0.1), 9.2, and 10g. The Lotus Connector for Oracle now supports calling procedures that are contained in Oracle packages. - LEI Administrator user interface Enhancements have been made to the LEI user interface to improve the user experience. Enhancements are listed below. - The field mapping area is now wider to accommodate long field names. - If a field entry does not pass validation and it is contained in a tabbed table, the cursor moves to that field so that it can be modified. - Field mapping presents fields names in the order they appear in the connector, not alphabetically. - A ruled field mapping area helps visually distinguish which fields are mapped together. - The name of the Domino server on which the LEI Administrator resides now appears in the main LEI screen. - The Notes connection document has been streamlined by combining all selection options (document, field, view) under one tab called Selection Options. - The ODBC connection document provides a new function which allows the user to browse ODBC data sources that are available on the server. - The credentials database allows selection from the Domino directory. - Screen space is now better used. - Sametime awareness has been added. - The following analysis tools have been added: - Unused connections report lists all connections in the administrator that are not used. - Invalid link report lists all activities and connection documents that refer to another activity and connection document that no longer exist. - Activity structure report analyzes selected activity documents and displays the connections they employ (traced down to the base connection) and the dependent activities that they reference. - Additional safeguards have been added to avoid errors when creating connection and activity documents - Connection documents now contain a Test Connection action which allows the user to test the connection before putting it into use. If the connection succeeds, the LEI Administrator displays the connection properties. If the connection fails, an error message appears. - A "Connections Used" option has been added to the Scripted Activity document. - A "Notes ID file path" option has been added to the data management type activity documents. This allows you to designate a different Notes ID for Notes connections. in an activity. A "Notes password" option is also available. - The Actions menu has additional report and failover view tools. - Enhanced troubleshooting tools - SYM files are now available for troubleshooting on Windows. - DCTEST connectivity results can now be captured in a text file that includes connection and client library information. - Update and delete synchronization The Virtual Documents activity now enables you to choose when to synchronize the activity document with the data in the external system database to which it refers. This synchronizes the activity document with the data when that data has been updated or deleted by some means other than through the activity document's front-end. You can synchronize for updates and deletes separately or together on a configurable frequency using the activity document's new options. - Enterprise fail-over for data management activities LEI now supports a failover mode of operation that lets data management activities run on one of a designated set of servers. In this mode, the LEI Administrator database must be cluster-replicated to servers in a Domino cluster. Each LEI instance uses its local replica; there is no master LEI server. This prevents failure of the entire cluster if one Domino server crashes. All activity documents that support failover contain a field for the administrator to list zero or more failover server names. Each server in a cluster periodically polls these servers to check if they are down, based on the servers' "heartbeats" in their server documents. When a server detects that another server is down, it searches for that server's eligible activities and then runs them as a failover. To prevent conflicts, failover servers are responsible for running an activity in the order in which are listed in that activity. The first active server in the list runs the activity. You can activate cluster support without also activating failover. When running LEI in failover mode, if you want to shut down the Domino server, shut down the LEI server first. This allows time for the exit status of each running activity to replicate to the other servers in the cluster. This enhancement requires pre-installation server configuration. To enable this new feature for your data management activities, you must perform the following tasks prior to running LEI. 1. Ensure that cluster replication is enabled (on the Domino server) for the LEI database decsadm.nsf. 2. Activate cluster mode and optionally failover mode using the LEI Administrator's configuration document. The four applicable fields are as below: -- Clustering checkbox to enable cluster mode -- Failover checkbox to enable failover mode -- Status Broadcast interval set as the frequency of the server's "heartbeat"; it may take at least this long for other the servers to notice a crash. -- Synchronization delay to set the set the time (in seconds) expected for replication from one LEI Administrator database to all others in the cluster to occur. Tip: This value must include an adjustment for difference in server clocks and a safety margin. For example, if the fastest server clock can be 50 seconds ahead of the slowest, and Domino cluster replication updates all servers within 10 seconds, AND you want to allow a 15 second margin for safety, then set this value to 75. This value adds to the amount of time used to notice a server crash. Too small a value risks servers mistakenly thinking other servers have crashed; running their activities when they should not. 3. Ensure that all servers in the LEI cluster contain a replica of the LEI Administrator (descadm.nsf) and the LEI log (leilog.nsf). 4. Ensure that the EIAdminServer variable in the notes.ini on each server in the LEI cluster points to itself. This is a significant change from how this variable was set in LEI 3 and 6 for LEI clustering. For example, if servers A, B, and C are to be part of the same cluster, the notes.ini EIAdminServer variable for server A should be set to "A", on server B, the notes.ini variable would be "B" and so on. - LEI now uses Domino memory management tools. Benefits of the switch include enhanced performance and simplified troubleshooting. - Accessibility in the LEI installer The LEI installer now uses InstallShield multi-platform (ISMP 5.0.2) tools and is compliant with IBM Corporate Instruction 162 for accessibility. - Dependent activity execution option You can now specify when to execute a dependent activity or activities using the choices Always, Upon success, or Upon failure in the Dependent Activity(s) field on the parent activity document. - i5/OS LEI installer The LEI installer now checks which OS400 version is installed on your system. If you are running i5/OS V5R3, it uses a slightly modified installation procedure. See the LEI installation guide for details. You can use the WRKPTFGRP command on i5/OS V5R3 systems to determine what PTF groups are installed, specifically the Java PTF Group. - i5/OS installer product ID requirement (5799PTL): Before you can install LEI on a i5/OS platform, the product ID 5799-PTL must be installed. You can download that product from the "IBM eServer i5/OS Tools for Developers" (5799-PTL) Web site at the following address: http://www-1.ibm.com/servers/enable/site/porting/tools. - i5/OS PTF requirements The Java PTF group number requirements are listed below: -- SF99269 is the required PTF group for V5R3 installations. - Japanese documentation set The LEI documentation set is available in the Japanese language in the IntlDoc subdirectory. If you wish to use the Japanese translation, back up the English version .nsf documentation files (typically located in the Lotus\Domino\Data\Help directory) and copy the Japanese language .nsf documentation files into the Help directory. The Japanese-version documentation is also available at the IBM Lotus Documentation site http://www.lotus.com/doc. - Support for the LEI migration tool, previously supported for LEI 6.x users for migrating their LEI administrator and script vault databases from LEI 3.x to LEI 6.x, is not supported for LEI 7.x. Users who wish to migrate from LEI 3.x must first upgrade to LEI 6.x and Domino 6.x before upgrading to LEI 7 and Domino 7. For more information on upgrading and migrating from Domino 5.x and LEI 3.x to Domino 6.x and LEI 6.x, see the LEI 6.5.2 installation guide at http://www.lotus.com/doc. - Documentation file name changes The Lotus Connectors and Connectivity Guide file name is now lccon.nsf. The Lotus Connector LotusScript Extensions Guide file name is now lsxlc.nsf. Both continue to be installed with Domino and also available on the Web. B) System Requirements *Hardware Requirements* - 40MB disk space on Win32 - 80MB disk space on UNIX and i5/OS - 90MB temp space on Win32 - required by i5/OS LEI Installer - 15MB temp space on Win32 - required by LEI installer - 90MB temp space on UNIX - required by LEI installer *Operating Systems and Versions* LEI is supported on the following platforms: - Windows 2000 Server and Advanced Server - Windows 2003 Server and Server Enterprise Edition - AIX 5.2 and 5.3 - Solaris 9.0 - RedHat Enterprise Linux (RHEL) 2.1 and 3.0 and NOVELL SUSE LINUX Enterprise Server 1.0 - OS/400 V5R3 Read all Domino documentation regarding the specific patches Domino requires for its server. The patch level required by Domino is a prerequisite for successful LEI installation. Patch requirements are updated periodically. See the Domino documentation for details. For example, the correct Solaris patch cluster is required. *Software Requirements* LEI 7.0 requires Notes/Domino 7.0. - Notes 7 client to administer the LEI Administrator database and run the LEI server if LEI is installed on a Notes client - Domino 7.0 server to manage the LEI Administrator database and run the LEI server if LEI is installed on a Domino server - Client libraries of the external systems to be accessed must be installed on the LEI server and the Domino server. When running activities, if the LEI server and the Domino server are on separate machines, the client libraries must be installed on both machines. - For UNIX - X Window system server environment - For UNIX - X Window system client libraries Verify that all of your database software is current with all available maintenance releases and/or fix packs. *Current supported data drivers list* Supported Lotus Connector data driver versions are listed below. Note: DataDirect ODBC drivers can be used with the Lotus Connector for ODBC. These include the Data Direct Sybase, Oracle, Informix, DB2, and SQL Server ODBC wire protocols. LEI and DECS support the supplied Lotus- branded DataDirect ODBC driver. LEI recommends using the Lotus-branded DataDirect ODBC Wire Prototol Drivers Release 5.0. Win NT4, 2000, Win2003 Oracle 8i, 9i, 10g DB2 8.x Sybase 12.5 MS SQL Server 2000 Data Direct ODBC 5.0 AIX 5.1, 5.2, 5.3 Oracle 8i, 9i, 10g DB2 8.x Sybase 12.5 Data Direct ODBC 5.0 Solaris 8, 9 Oracle 8i, 9i, 10g DB2 8.x Sybase 12.5 Data Direct ODBC 5.0 RedHat Enterprise Linux (RHEL) 2.1 and 3.0 and NOVELL SUSE LINUX Enterprise Server 1.0 Oracle 8i, 9i, 10g DB2 8.x Data Direct ODBC 5.0 i5/OS V5R1, V5R2, V5R3 DB2 8.x Data Direct ODBC 5.0 *Testing Connectivity* - The supplied DCTEST program tests connectivity from the system on which the LEI server is installed to external data sources. The LEI server acts as a client to your external data server. - Run the appropriate connectivity test program from the Domino server before running LEI. The program names are listed below by platform: Issue the following command for Windows: ndctest Issue the following command for UNIX: dctest Issue the following command for i5/OS: RUNDOMCMD SERVER(your_dom_server) CMD(CALL PGM(QDOMINOxxx/DCTEST)) BATCH(*NO) where xxx is the Domino release (650 for Domino 6.50 or 603 for Domino 6.0.3) A command window help menu provides information for using the connectivity test program. C) Installation Considerations See the Installation Guide (leiig.nsf) supplied with LEI and also available as both a .nsf file and an HTML browseable at the Lotus Documentation site (http://www.lotus.com/doc) on the Enterprise Integrator product page for complete LEI installation instructions. See below for related considerations. Installation Considerations - When installing LEI as an NT service for use with a local Domino server or a local Notes client, be sure that the service starts with the same NT login credentials as Domino. For both cases set the following notes.ini parameter as specified below: EIUseOSMemory=1 - The user ID of the user who is installing LEI must be resident in the Domino Directory group LocalDomainAdmins or the LEI installation will fail. - The Domino server must be running during LEI installation. For the UNIX platforms, the installer does not error out if Domino is not running. You must verify that the Domino server is running before installing LEI. - DECS, if installed, must not be running during LEI installation. - The LEI installation utility does not inform you that you must make changes to your Domino Directory in order to support the server-side browsing method used by LEI. See the LEI Installation Guide (leiig.nsf) for details. - The LEI server must be installed on a machine where a Notes client or a Domino server is installed. Only one LEI server can be installed on any single non-partitioned machine. On a partitioned machine, an LEI server can be installed on each partition. The LEI server version and the Notes/Domino version must match, for example Domino 7.0 with LEI 7.0. - On UNIX, do not use the following characters in an LEI server name: ", ', &, ;, :, / D) Installing LEI - General Instructions The LEI install process is explained fully in the IBM Lotus Enterprise Integrator for Domino (LEI) Installation Guide (leiig.nsf) supplied with this release and at http://www.lotus.com/doc. Before installing to a UNIX platform, you must do the following: - Set the correct access controls in the names.nsf file on the Domino server. - Establish the correct access rights in the Notes ID file. - Ensure that all needed environment variable are set and exported. - Ensure that you have loaded and configured X Window system software. If you will be installing LEI to a Notes client, set the Notes ID to share its password with other Notes-based systems, as documented in the LEI installation guide. To avoid multiple prompting for password, ensure that your Notes client is running during LEI install. E) Uninstalling LEI The LEI uninstall process is documented in the IBM Lotus Enterprise Integrator for Domino (LEI) Installation Guide (leiig.nsf) supplied with this release and also available at the Lotus Documentation site (http://www.lotus.com/doc). F) Operational Considerations Current LEI Tech Notes and other user information can be found at http://www-3.ibm.com/software/lotus/support/integration/support.html. The Lotus Connector LotusScript Extensions Guide (lsxlc.nsf) and Lotus Connectors and Connectivity Guide (lccon.nsf) are supplied with Domino, not LEI. You can also obtain these guides at the Lotus Documentation site (http://www.lotus.com/doc) for this release. - DECS and LEI RealTime activities (Virtual Fields, Virtual Documents, and Virtual agents) do not support DB2 enabled Notes databases. LEI data management activities such as replication and direct transfer do support DB2 enabled Notes databases. - Although LEI does not write to the keyfilename field in the notes.ini file, it does access it. For LEI to work correctly, the ID name specified in the keyfilename field MUST be of a relative path. Using an absolute path, or fully-qualified name, for the sever.id or user.id value in that field is not supported. For example, this is a valid name for LEI use: keyfilename = server.id This is not a valid name for LEI use: keyfilename = /opt/lotus/notesdata/server.id - LEI now uses Domino memory management by default. This may cause memory allocation errors with the Lotus Connector for SAP or the Order Metaconnector. Messages include the following: AllocMemHandle: OUT OF PRIVATE HANDLES! -- pid 00000734 Handles used so far 64, Maximum handles = 147455, error = 0x107 Unable to allocate memory. To correct this, add the following line to the notes.ini file: EIUseOSMemory=1 - The Lotus Connector for Notes option Fetch View Column Data on the Field Selection tab is not operational. A workaround is as below: 1. Click the Field Selections tab and select Fetch Document Items. 2. Click the Data Transformation tab and use @formulas to modify the values as you would in the view column. For example, for a field fullname containing Doe, John type: select @all; FIELD fname := @right(lname; ","); FIELD lname := @left(lname; ","); This would correspond to the following: column fname with a column formula of @right(lname; ",") column lname with a formula @left(lname; ",") - DB2 Personal Edition is limited to a single workstation and single DB connection. - Failover and virtual activities with save and replication conflicts LEI servers running in cluster mode may have replication conflicts when starting virtual activities. The new LEI feature of failover for data management activities running in an LEI cluster can cause save and replication conflicts for Virtual Documents and Virtual Fields activities. Until this issue is resolved by Lotus development, the workaround is as follows: Ensure that the server clocks are not set to the same time, but rather are spaced minimally the length of the polling interval time plus ten seconds. Support also has an alternative workaround that involves manually starting a virtual activity with a customized view action from the LEI Administrator -- contact support for details. - i5/OS Considerations - On the i5/OS platform, when transferring data from Notes to Japanese EBCDIC DB2, the Japanese single byte yen character (0x5c in LMBCS) is replaced with the backslash character. - On i5/OS, the LCFieldList.Copy method of LC LSX drops the source LCStream object property values for Stream Flags and Max Length. As a result, they are not set in the target FieldList object. LCFieldList.MaxLength is a read-only property based on the LCStream type: LCTYPE_TEXT or LCTYPE_BINARY. You can manually set the LCFieldList.Flags property when copying, obtaining the property values from the source object. - Use the native Lotus Connector for DB2 to access the IBM DB2 UDB and IBM DB2 on i5/OS. For the latest information about the i5/OS platform, visit the http://www-1.ibm.com/servers/eserver Web site: For the latest information about Enterprise Integration offerings, visit the http://www.lotus.com/ei Web site. G) What's Been Fixed in LEI Release 7.0 The following issues have been corrected in LEI 7.0 and are no longer problematic or dysfunctional. All listed issues have been resolved. General: - The LC LSX Open Event formula causes DBlock memory integrity errors. A data integrity check yields a damaged block trailer. - Upon crash and restart, LEI performs a cleanup routine and then exits. The user must then restart LEI manually. - When an activity has run too long or when Domino is shut down, LEI cannot kill any activity running in UNIX. - When Domino crashes and restarts, LEI does not always restart and once started may experience problems running RealTime activities. One error that may appear is "Unable to reach control store manager". This has been resolved using consistency checks for decsadm.nsf, leilog.nsf, and the .nsf databases serviced by LEI RealTime activities. - When LEI is started as add-in task and then Domino is shut down, there is no entry in the log.nsf database indicating that LEI was shut down. - When adding an LEI cluster to an existing Domino/LEI cluster, the administrator of the subsequent cluster is not added to the LEI server configuration file. - On i5/OS an uninitialized memory error occasionally causes LEI to fail. Connectors: - DB2 Connector performance degrades when using a large number of text fields. The DB2 Connector LCXFetch routine requires excessive memory heap allocation and causes performance degradation. This and DB2 Connector memory leaks have been corrected. - The LCTYPE_TEXT LCLSX code for the Text Connector fails at the following line when the property is "Condition": Set propStrm = connect.GetPropertyStream (tokenId, LCSTREAMFMT_NATIVE) - A Notes connection that contains computed subforms cannot be used as a target connection in an LEI activity. - An Oracle connection cannot call an Oracle package using any of the selection types on the Oracle Connector form. - The Notes Connector erroneously returns the following error when a view name is specified in the Notes connection document and the "Allow view creation/overwrite" selection option is checked: Error: Invalid document handle or ID - The user interface does not allow the user to manually add field value parameters to a Sybase connection document. The user can only select from an existing list of possible values. This is problematic when specifying Sybase stored procedures on the form. - In a Notes connection, fields from the Computed Subforms option do not show up on a check list of fields to use. - When creating a Collapse/Expand metaconnection document, you can save it without specifying any grouping keys. However, the metaconnection is not usable without this information. - A connection document password cannot be encrypted until the document has been saved. To simplify the process, the user is now prompted to save the document when she clicks the password encryption button. - On non-Windows platforms, the LC LSX LCDateTime SetConstant method, used with a Wildcard, fails because the wildcard does not match the date and time specified. Sample code is shown below: Dim clock9 As New LCDateTime(1998,1,25,08,50,00,00,-5,True) Dim Match As New LCDatetime - On i5/OS, a scripted activity using an ODBC and Sybase connection fails to create a table. - On i5/OS, using the statement "Execute ODBCAgent" in a Command activity using a Notes connection fails to create a table or to run. - On i5/OS, using an Archive activity with a Notes source and a DB2 target fails. Virtual activities: - Virtual Documents activities terminate with an error when the mail server is not the same as the LEI server. This occurs when the "MailServer" entry in the notes.ini file does not match the LEI server. - When using the Virtual Documents form to create an external key table, the EINOTEPROPS size parameter is always set to 1024 bytes, regardless of its actual size or of the value manually entered. - The EINOTEPROPS field for DB2 external key tables is created as a BLOB type field instead of as a VARCHAR. - LEI does not create an external key table when using an Oracle connection if the table contains a timestamp field. - With a DB2 connection in a Virtual Documents activity, the user can create an external key table manually, not using the menu option in the activity document, without specifying a schema. This can cause issues later. The solution is for the code to force an external key table name to contain a schema. - In a Virtual Fields or Virtual Documents activity with integrated credentials enabled, LEI is unable to open a virtual attachment. - A Domino crash caused when using an ODBC SQL Server connection in a Virtual Documents activity where the Create/Update Stored Procedures option is enabled has been resolved. - When using a Virtual activity in conjunction with the Reader or No Access authority (ACL) and with the Write public documents option enabled, the activity cannot create, edit, or delete a public document. - When running a Virtual Documents activity, if the DB2 server to which the activity is connected shuts down, the activity will continue running but will cause Domino to crash. - On i5/OS, LEI is unable to save large (for example 900K) attachments even when the attachment table is set to accept larger (for example 100MB) attachments. Data management activities: - Because of the way the New method of LCConnection is implemented, using a non-scripted activity in LotusScript the user can specify either a connector name or connection document name to initialize the connection. The LEI Scripted activity does not support this functionality, requiring use of a connection document. This forces developers to code around the issue by initializing a connection from a connection document and then changing every property. This has been resolved. - Sort order issues within the Replication activity have been resolved. - Improvements have been made to the activity scheduling options. The user can now sets the restrict field as needed and then enable or disable the schedule. This prevents the Restrict to Schedule setting from being overwritten by the Schedule Disabled setting. - The dependent activities list does not contain the names of LEI activities that are currently selected. - An LEI Replication activity that contains a 'space' as its value replicates every time instead of just the first time. - A command activity scheduling issue involving the Run at Times and Run at Days of the Week options has been resolved. Scheduling issues involving the Start at Time and End at Time options have also been resolved. - The Replication activity does not adjust the timestamp prior to performing a comparison; this causes unnecessary updates. - When replicating from Notes to ODBC DB2 that contains a date/time field, LEI does not update the date and time field in the DB2 table. - In a replication activity that contains a source Notes connection and a target ODBC SQL server connection, mapping the date and Time fields in the source to the Datetime field in the target causes the activity to end in error when only the time is specified in the source. - Copying LEI activities using the shortcuts and and renaming the duplicate, yields a Notes error. - A browsing issue in the Polling activity relative to browsing in the timestamp field has been resolved. - A display issue on the Purge-log activity form has been resolved. - An inability to create an ODBC SQL Server index using a source of either ODBC SQL Server or Notes to a target ODBC SQL Server has been resolved. - The following replication activity problems have been resolved: -- Timestamp replication checking using a source and target timestamp is not functioning. -- Replication using any back-end with Notes as the source or target results in Error: Data is formatted incorrectly. -- Replication activities ends with the following error: Error overflow in field" when transferring data between DB2 and Notes. H) Documentation Errata - The readme.txt file kitted with the release should have contained the following statement in section B -- revised January 10, 2006: DataDirect ODBC drivers can be used with the Lotus Connector for ODBC. These include the Data Direct Sybase, Oracle, Informix, DB2, and SQL Server ODBC wire protocols. LEI and DECS support the supplied Lotus- branded DataDirect ODBC driver. LEI recommends using the Lotus-branded DataDirect ODBC Wire Prototol Drivers Release 5.0. - Any mention of DataDirect 4.2 drivers in the documentation should be 5.0. - Any mention of the iSeries name in the documentation should be i5/OS. - The flyover text for the Stored Procedure Output Mapping section of the Virtual Documents activity form is incorrect, as it reads below. Define the Fields from the Lotus connection which contain the stored procedure output. These fields must exist in the field mapping above. The flyover text should instead read as shown below: Define the Fields from the Lotus connection which contain the stored procedure output. These fields must not be specified in the mapping section of the activity document. - The following entry in the LC LSX Guide LCFieldList section for Lookup method and return value description should be changed as below: Change from: Value - field Description - LCField. The field whose name in this list is fieldName. If no such field exists, nothing is returned. Change to: Value - field Description - LCField. The field whose name in this list is fieldName. If no such field exists, the message "Error: Invalid Field" is returned. I) Troubleshooting and Additional Support For the latest LEI technical information, including Tech Notes, visit the following Web page: http://www-3.ibm.com/software/lotus/support/integration/support.html Support is also available for LEI at the following Web page: http://www-3.ibm.com/software/lotus/support ***************************************************************************** Under the copyright laws, neither the documentation nor the software may be copied, photocopied, reproduced, translated, or reduced to any electronic medium or machine-readable form, in whole or in part, without the prior written consent of IBM Corporation, except in the manner described in the documentation or the applicable licensing agreement governing the use of the software. Domino, Notes, IBM Lotus Enterprise Integrator for Domino (LEI), LotusScript, Lotus Connectors, and Domino Enterprise Connection Services (DECS) are trademarks of Lotus Software, IBM Software Group. AIX, DB2/2, DB2, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks are held by their respective owners. Copyright IBM Corporation 1985-2005 Lotus Software, IBM Software Group One Rogers Street Cambridge, MA 02142 All Rights Reserved. *****************************************************************************