IBM Tivoli Directory Integrator 5.2: Readme

Transcription

1 IBM Tioli Directory Integrator 5.2: Readme GI

2

3 IBM Tioli Directory Integrator 5.2: Readme GI

4 ii IBM Tioli Directory Integrator 5.2: Readme

5 Contents New for IBM Tioli Directory Integrator Config Editor enhancements Online help information Logging New Connectors Actie Directory Changelog Connector....1 Exchange Changelog Connector RDBMS Change Connector New EentHandlers SNMP EentHandler Actie Directory Changelog EentHandler...2 Exchange Changelog EentHandler LDAP Serer EentHandler Updates to Connectors HTTP Client Connector JDBC Connector JMS Connector changes JNDI Connector LDAP Connector changes Script Connector Sandbox Hooks AssemblyLine Hooks Connector Hooks Starting AssemblyLines with startal() Secure Sockets Layer Support Jaa VM Precompiling JaaScript Code AMC Windows Serices (MS Management Console) Support System store User Property Store Delta compare updates Checkpoint/Restart Jaadocs iii

6 i IBM Tioli Directory Integrator 5.2: Readme

7 New for IBM Tioli Directory Integrator 5.2 Config Editor enhancements New Connectors The following information describes new or changed functionality for IBM Tioli Directory Integrator 5.2: For this release, the term GUI (Graphical User Interface) is supplanted by the new term, Config Editor. The following features were added to the Config Editor in this release: Online help information Online help information is aailable in the Config Editor. This is new for IBM Tioli Directory Integrator 5.2. All panels in the Config Editor include a help button. Logging Configuration of the logging for the serer is done in tree-iew pane. Configuration of the EentHandlers and AssemblyLines logging is done in a separate tab for both EentHandlers and AssemblyLines. In a log configuration window, 0 (zero) or more log-schemes can be added. The following are the log schemes for this release: IDIFileRoller Console File Syslog NT Eentlog DailyRollingFile MOBJ Note: The MOBJ Appender is used to customize logging. This is compatible with preious logging schemes. The following Connectors are new to IBM Tioli Directory Integrator 5.2: Actie Directory Changelog Connector The Actie Directory Changelog Connector is a specialized instance of the LDAP Connector. This Connector contains logic to poll Actie Directory for changed objects using the usnchanged mechanism. The Actie Directory Changelog Connector operates in Iterator mode. 1

8 The Actie Directory Changelog Connector functionality is new for 5.2. See Actie Directory Changelog Connector in IBM Tioli Directory Integrator 5.2: Reference Guide. Exchange Changelog Connector The Exchange Changelog Connector is a specialized instance of the LDAP Connector. The Exchange Connector contains logic to poll Exchange for changed objects using the usnchanged mechanism. The Exchange Changelog Connector operates in Iterator mode. The Exchange Changelog Connector functionality is new for 5.2. See Exchange Changelog Connector in IBM Tioli Directory Integrator 5.2: Reference Guide. RDBMS Change Connector The RDBMS Connector uses JDBC to connect to a specific RDBMS table. New EentHandlers The RDBMS Connector only operates in Iterator mode. The Connector reads specific fields to determine new changes in the change table. The RDBMS Connector reads the next change table record, or discoers the first change table record. The RDBMS Change Connector functionality is new for 5.2. See RDBMS Change Connector in IBM Tioli Directory Integrator 5.2: Reference Guide. The following EentHandlers are new to IBM Tioli Directory Integrator 5.2: SNMP EentHandler SNMP is a standard wire-leel protocol used to query and set published attributes in remote systems. Typically, it is used by a monitoring console to configure and get status information from a wide range of SNMP-compliant systems. The SNMP EentHandler receies UDP packages on a specified port, and returns an appropriately formatted response to the originator. The implementation is non-blocking by default, meaning the SNMP EentHandler spawns a copy of itself to perform the work while the main thread returns to listen for further packets (the main thread can be set to blocking as well). The SNMP EentHandler functionality is new for 5.2. See SNMP EentHandler in IBM Tioli Directory Integrator 5.2: Reference Guide. Actie Directory Changelog EentHandler The Actie Directory Changelog EentHandler detects and sends notification of changes that occur in Actie Directory. It reports changed Actie Directory objects so that other data sources can be synchronized with Actie Directory. The LDAP protocol is used both for registering for change notification and retrieing changed objects. This implementation of the Actie Directory Changelog EentHandler functionality is new for 5.2. See Actie Directory Changelog EentHandler in IBM Tioli Directory Integrator 5.2: Reference Guide. 2 IBM Tioli Directory Integrator 5.2: Readme

9 Exchange Changelog EentHandler The Exchange Changelog EentHandler detects changes that occur in Exchange Directory Serice and notifies a user about these changes. It reports changed Exchange objects so that other data sources can be synchronized with Exchange. The LDAP protocol is used for retrieing changed objects. This implementation of the Exchange Changelog EentHandler functionality is new for 5.2. See Exchange Changelog EentHandler in IBM Tioli Directory Integrator 5.2: Reference Guide. LDAP Serer EentHandler The LDAP Serer EentHandler accepts an LDAP connection request from an LDAP client. The LDAP Serer EentHandler generates a copy of itself to take care of this connection until the connection is closed by the LDAP client. The LDAP Serer EentHandler only terminates when the TCP connection is closed. Each LDAP message receied on the connection dries one cycle of the LDAP Serer EentHandler logic. Updates to Connectors The LDAP Serer EentHandler functionality is new for 5.2. See LDAP Serer EentHandler in IBM Tioli Directory Integrator 5.2: Reference Guide. The following are Connector updates and changes for IBM Tioli Directory Integrator 5.2: HTTP Client Connector For IBM Directory Integrator 5.2, there are two new parameters added to the HTTP Client Connector: File from Response HTTP Body The full path of the file. The body of the response HTTP message is copied to the file. File to HTTP Body The full path of the file. The file contents are copied as HTTP body in the HTTP message. JDBC Connector ODBC, by means of the standard Jaa2 JDBC-ODBC bridge, is supported on Windows systems only. Commercial ODBC/JDBC bridges are aailable. If you need an ODBC/JDBC bridge, consider purchasing a commercially aailable bridge. A new parameter, Commit, is included with the JDBC Connector. This parameter controls when database transactions are committed. Options are: After eery database operation On Connector close Manual Manual means user must call commit() method of the JDBC Connector. See JDBC Connector in IBM Tioli Directory Integrator 5.2: Reference Guide. New for IBM Tioli Directory Integrator 5.2 3

10 JMS Connector changes There is a new method added to the JMS Connector: acknowledge() This new method acknowledges all consumed messages of the session. The method acknowledge() is used to explicitly acknowledge the JMS session s consumed messages when Auto Acknowledge is unchecked. By inoking acknowledge() of the JMS Connector, the JMS Connector acknowledges all messages consumed by the session to which the message was deliered. Calls to acknowledge() are ignored when Auto Acknowledge is checked. For more detailed information about the acknowledge() method, see JMS Connector in IBM Tioli Directory Integrator 5.2: Reference Guide. Also new for this release, the JMS Connector can now be used on OS/390 with pre-mq 5.2 releases. JNDI Connector JNDI connector has a way to set a modify operation alue when the connector is in Modify mode. You can also use the simple connector interface to directly add, remoe or replace attribute alues and attributes instead of setting modify operation. There is no Config Editor proided to set the modify operation. You must manually add the operation alue to each attribute in the work entry of the JNDI connector in Modify mode using the following interface: di.com.ibm.di.entry.attribute.setoper(char operation) operation di.com.ibm.di.entry.attribute.attribute_delete This constant deletes the specified attribute alues from the attribute. The resulting attribute has the set difference of its prior alue set and the specified alue set. If no alues are specified, it deletes the entire attribute. If the attribute does not exist, or if some or all members of the specified alue set do not exist, this absence might be ignored and the operation succeeds, or an Exception might be thrown to indicate the absence. Remoal of the last alue might remoe the attribute if the attribute is required to hae at least one alue. di.com.ibm.di.entry.attribute. ATTRIBUTE_REPLACE This constant replaces an attribute with specified alues. If the attribute already exists, this constant replaces all existing alues with new specified alues. If the attribute does not exist, this constant creates it. If no alue is specified, this constant deletes all the alues of the attribute. Remoal of the last alue might remoe the attribute if the attribute is required to hae at least one alue. This is the default modify operation. di.com.ibm.di.entry.attribute. ATTRIBUTE_ADD This constant adds an attribute with the specified alues. If the attribute does not exist, this constant creates the attribute. The resulting attribute has a union of the specified alue set and the prior alue set. 4 IBM Tioli Directory Integrator 5.2: Readme

11 Sandbox Hooks For more detailed information about setting the modify operation, see JNDI Connector in IBM Tioli Directory Integrator 5.2: Reference Guide. LDAP Connector changes The LDAP Connector includes functionality to compare and modify attributes. You can do the following to an LDAP attribute: LDAP compare Add a alue to an attribute Replace an attribute alue Remoe an attribute alue Remoe all attribute alues There is also a new flag in the Config Editor for the default action for attribute add or replace. In the LDAP Connector Config Editor there is a new checkbox named Add Attributes (instead of replace). This option changes the default behaior of the LDAP Connector when it modifies an entry. Connect to an actie non-ldap port, and the application freezes as it waits for the TCP timeout to occur (this timeframe is ariable depending on the operating system). This problem is not eident in JVM Instead, a MalformedURL exception is thrown. This is because the JNDI proider in JVM checks the LDAP URL to ensure that you are not attempting to connect to a known, non-ldap port (such as a Notes port, or ftp port, and so forth). The JVM does not use this check, because it is possible and alid to hae an LDAP serer running on any gien port number. See LDAP Connector in IBM Tioli Directory Integrator 5.2: Reference Guide. Script Connector For IBM Tioli Directory Integrator 5.2, the Script Connector now supports the following Connector modes: Call/Reply This new feature of the IBM Tioli Directory Integrator enables the user to record AssemblyLine operations for later playback, without any of the data sources being present. The Sandbox functionality is new for 5.2. See Sandbox in IBM Tioli Directory Integrator 5.2: Users Guide. The following hooks are new for IBM Tioli Directory Integrator 5.2: AssemblyLine Hooks AssemblyLines hae the following new hooks for IBM Tioli Directory Integrator 5.2: Epilog - After Close This script is run after all Connectors are closed and their Epilog Hooks hae completed. New for IBM Tioli Directory Integrator 5.2 5

12 Also new for IBM Tioli Directory Integrator 5.2, the Prolog - Init Hook is referred to as the Prolog - Before Initialization Hook. Connector Hooks Connectors in Iterator mode hae an End Of Data Hook. It is called when the end of the data-stream is reached (possibly due to a timeout for Connectors supporting a timeout mechanism). For Connectors in Iterator mode with Delta enabled, End Of Data Hook is called after that the Delete entries hae been processed. Connectors in Update mode hae the following new hooks: Before Lookup After Lookup Connectors in Delete mode hae the following new hooks: Before Lookup After Lookup Starting AssemblyLines with startal() Secure Sockets Layer Support The function main.startal( al. tcb) starts the AssemblyLine (al) with the Task Call Block (TCB) tcb. The TCB property assemblyline.runmode can be normal, record and playback to drie the Sandbox mode (record/playback). The TCB property assemblyline.resetcheckpoint (default:false) corresponds to the ibmdisr Z command line option. It causes the checkpoint tables to be cleared, and thus runs the AssemblyLine normally, not in restart mode. The IBM Tioli Directory Integrator Serer has the ability to hae secure communication with those directories supporting Secure Sockets Layer (SSL) security protocol. The following Connectors and EentHandlers support SSL with properly configured IBM Tioli Directory Integrator Serers: Connectors JMS Connector LDAP Connector Netscape/iPlanet LDAP ChangeLog Connector IBM Directory Serer ChangeLog Connector Actie Directory ChangeLog Connector Lotus Notes Connector EentHandlers Actie Directory ChangeLog EentHandler DSML2 EentHandler Exchange ChangeLog EentHandler HTTP EentHandler LDAP EentHandler IBM Directory Serer EentHandler Web Serice EentHandler 6 IBM Tioli Directory Integrator 5.2: Readme

13 zos LDAP EentHandler For more information, see Connectors and EentHandlers in the IBM Tioli Directory Integrator 5.2: Reference Guide and IBM Tioli Directory Integrator Secure Sockets Layer Support in the IBM Tioli Directory Integrator 5.2: Users Guide. Jaa VM Precompiling JaaScript Code AMC IBM Tioli Directory Integrator 5.2 is dependent on Jaa The precompile function sorts under Optimization. The function com.ibm.di.scriptengine.precompile can be set in global.properties to turn precompiling of JaaScript on or off. Default is on. Users with user role can access all AMC screens from the main menu, but they cannot perform any actions: Cannot start and stop AssemblyLines or EentHandlers Cannot update the IBM Tioli Directory Integrator configuration Cannot iew logs and details for components such as parameters and statistics AMC only reports logs generated by MOBJ on AssemblyLines and EentHandlers. See log4j default parameters in IBM Tioli Directory Integrator 5.2: Administrator Guide. Windows Serices (MS Management Console) Support System store The IBM Tioli Directory Integrator serice logs all messages (error, info and debug) in the Application Windows system log. You can iew these messages with the Windows Eent Viewer. The IBM Tioli Directory Integrator serice automatically starts the IBM Tioli Directory Integrator at system boot. The Windows Serices (MS Management Console) Support functionality is new for 5.2. See IBM Tioli Directory Integrator as Windows Serice in IBM Tioli Directory Integrator 5.2: Administrator Guide. The System Store addresses the arious needs of IBM Tioli Directory Integrator for persistent storage and uses the DB2Jaa (CloudScape) RDBMS as its underlying storage technology. The System Store can be shared by multiple instances of IBM Tioli Directory Integrator serers if the CloudScape database runs as a serer. If CloudScape runs embedded in an IBM Tioli Directory Integrator serer, it cannot be shared simultaneously with other serers. The system store implements three types of persistent stores for IBM Tioli Directory Integrator components: The User Property Store New for IBM Tioli Directory Integrator 5.2 7

14 User Property Store The Delta Tables Delta compare updates The Checkpoint Tables Each store offers its own set of features and built-in behaior, as well as a callable interface that users can access from their scripts, for example, to persist their own data and state information. For more information about the System Store, see System Store in IBM Tioli Directory Integrator 5.2: Users Guide. For information about migrating an IBM Tioli Directory Integrator system, including the System Store, see Migrating from IBM Tioli Directory Integrator to IBM Tioli Directory Integrator 5.2 in IBM Tioli Directory Integrator 5.2: Administrators Guide. This is a new functionality in Change Connectors for IBM Tioli Directory Integrator 5.2. These Connectors now use the new User Property Store mechanism to remember the last change read, making it simpler and easier to implement synchronization solutions. The process of computing changes in a data source inoles the use of a local store (System Store) in which the delta process stores information about each entry read from a Connector. Each time the delta process is run, a sequence counter increments. Each entry read from the Connector is stored in a table along with the current sequence number. The purpose of the sequence number is to be able to detect entries no longer part of the source data set. This is accomplished by comparing the sequence numbers after a completed iteration oer the source data set. For this release of IBM Tioli Directory Integrator, the Delta function has been increased. The following are some of the new or changed items addressed in this release: Delta process The process of computing changes in a data source inoles the use of a local store in which the Delta process stores information about each entry read from a Connector. Each time the delta process is run, a sequence counter increments. Each entry read from the Connector is stored in a Delta table along with the current sequence number. The purpose of the sequence number is to be able to detect entries no longer part of the source data set. This is accomplished by comparing the sequence numbers after a completed iteration oer the source data set. Unique attribute In order for the Delta mechanism to be able to uniquely identify each entry, you must specify a unique attribute to use as the Delta key. This is done in the Connector s Delta tab by entering (or selecting) an attribute name in the Unique Attribute Name parameter. This attribute must be found in the Input Map of your Iterator, and can either be an attribute read from the connected system or a computed attribute (Adanced Attribute 8 IBM Tioli Directory Integrator 5.2: Readme

15 Checkpoint/Restart Map). Each attribute must hae a alue that can be represented as a string (that is, it must implement the tostring() function), and the resulting string alue cannot be null or blank. If a designated unique attribute has more than one alue, then an error is thrown. Delta table structures The tables used by the Delta store consist of the Delta Systable (DS) that contains information about each Delta Table currently in use in the delta store. The Delta Table (DT) contains information about each entry that has been read and processed by the Delta function in a Connector. See Deltas and Delta Store in IBM Tioli Directory Integrator 5.2: Users Guide for more information about the expanded Delta functionality. IBM Tioli Directory Integrator enables the user to checkpoint the operation of AssemblyLines and restart them from the point where they were interrupted by either a controlled or uncontrolled shutdown. The Checkpoint/Restart framework stores state information and other parameters in a database at arious points during AssemblyLine execution, which enables the serer to reinstate the running enironment of the AssemblyLine so that it can be restarted in a controlled way. This can be on the original serer, but potentially can also be on a different machine. Note: The purpose of the Checkpoint/Restart functionality is to facilitate the recoery of IBM Tioli Directory Integrator 5.2 from a crash. For the following Parsers, Checkpoint/Restart is not supported in AddOnly mode: XML Parser Checkpoint/Restart is not supported by the XML Parser in AddOnly mode with Sae Connector Info enabled. DSML Parser Checkpoint/Restart is not supported by the DSML Parser in AddOnly mode for Connectors that do not generate the full XML document for each entry. SOAP Parser Checkpoint/Restart is not supported by the SOAP Parser in AddOnly mode for Connectors that do not generate the full XML document for each entry. A new ibmdisr command line option: Z causes the serer to clear the checkpoint tables for the AssemblyLines specified, and thus causes the AssemblyLines to run in normal mode, not in restart mode. The Checkpoint/Restart functionality is new for 5.2. See Checkpoint/Restart in IBM Tioli Directory Integrator 5.2: Users Guide. Jaadocs The Jaadocs information for IBM Directory Integrator 5.2 is increased. All classes and their methods are part of the Jaadocs. See install_directory\docs\api to iew the Jaadocs. New for IBM Tioli Directory Integrator 5.2 9

16 10 IBM Tioli Directory Integrator 5.2: Readme

17

18 Printed in USA GI