6.1.1-TIV-TDI-FP0003

+-----------------------------------------------------+
Fix pack 6.1.1-TIV-TDI-FP0003 README
IBM Tivoli Directory Integrator 6.1.1
Fix Pack 3
(All supported Platforms)
Date: March, 2008
+-----------------------------------------------------+




COPYRIGHT STATEMENT
====================

March 2008

References in this publication to IBM products, programs, or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM program product in this publication is not intended to state or imply that only IBM's program product may be used. Any functionally equivalent program may be used instead.IBM is a trademark of the International Business Machines Corporation.

Copyright International Business Machines Corporation 2008. All rights Reserved.



CONTENTS
=========
1. ABOUT THIS FIXPACK
2. FIXPACK CONTENT
2.1 Fixes also included in Fixpack 1
2.2 Fixes also included in Fixpack 2
2.3 Fixes included exclusively in Fixpack 3
2.4 Supported platforms
3. PREREQUISITES
4. INSTALLATION INSTRUCTIONS
4.1 Information about the Fixpack package
4.2 Steps to install fixpack for all Platforms (Except z/OS)
4.3 Installation instructions for zOS only.

5. UNINSTALLATION INSTRUCTIONS (not applicable to z/OS)
6. Documentation Update
7. CONTACTING CUSTOMER SUPPORT


1. ABOUT THIS FIXPACK
===================

This fixpack can be applied over, TDI 6.1.1 GA level on all supported platform for TDI 6.1.1 . Please note that this fixpack is applicable to the TDI Base (Server and CE) part only. It does not include any defect fixes for the Plug-in.
For details regarding actual contents, refer to Section "Fixpack Content".

2. FIXPACK CONTENT
==================

2.1 Fixes also included in Fixpack 1
====================================


APAR Description
----------------------------------------------------------------------------------------------------------------------
IO06949 A single click can cause AL components to disappear
IO06948 Open Remote dialog shows files mashed together
IO06193 Going in before applying changes hook when there are no changes
IO06966 AMC can not close an AL which has TCP connector
IO06965 AMC can not close AL containing IDS changelog conn
IO06950 Work Entry (work) not available in Prolog Hooks
IO06952 Problem with LoopComponent of type Connector
IO06218 Padding issue with JDBC Connector
IO06205 notes connector cannot retrieve type Numbers correctly
IO06953 Small debugging problem
IO06954 Expression editor does not show opentry (Input) Attributes
IO06956 Pasting to an Attribute Map gives Null pointer exception
IO08690 Init Option "when config changed" causes continues re-init
IO06961 Unable to clear TAM account group assignment on modify request
IO06205 Notes Connector returning Integer in scientific notation
IO06337 try catch block in TDI Script not catching Runtime Exception
IO06630 Running ibmdisrv in daemon mode ignoring -D cmd line option
IO06962 Re-use of AL Conn does not support non-standard modes.
IO06565 update autogen to include RecieverThread for JMS Conn
IO06628 increase iteration to check CS server up or not before AL Start
IO06963 Disabled AttMaps are still executed (script inside it, gets executed)
IO06639 LDIF Parser not able to parse multivalued attr's correctly
IO06579 fails on ldapmodify when changetype is modify and op is delete
IO06578 throws Null Pointer Exception when connect is pressed in attribute mapping GUI of MQE PWD Store connector.
IO06964 Remote Command Line FC doesn't clear the Input attr for each iteration
IO06645 TDI is trying to update the attributes which are no selected for update in Output map. Problem only in case of inherited output map.


2.2 Fixes also included in Fixpack 2
====================================
IO07770 611:RAC Conn: Iterator mode on Windows terminates AC on Linux
IO07786 611:RAC Conn: Iterator mode on zOS does not work
IO07792 If you disable a BP with Condition, it stays enabled
IO07793 IWE Attribute no longer shown onscreen
IO07794 Tooltips ("Information") for AL Init Parameters is not saved
IO07795 SAP IDOC Connector Log Init error
IO07796 'requireClientAuth' parameter is missing in old configurations.
IO06845 Failing to usr getParam/setParam methods for FC in script
IO07018 make parseEntry method Public of IDSChangelogConnector
IO07120 system.skipEntry() doenot work with maxread param in AL config
IO07020 Do not terminate connector if it has not been initialize
IO07017 ADChangelog v2 connector thows NPE while reconnect
IO06859 EmfSdoToXml FC:if we have annotation tags in xsd FC throws Exception
IO07113 EmfSdoToXml FC:throwing class cast exception while using enumeration in xsd
Io07772 Script Component should get disabled when checkbox disables
IO07117 change log conn pushes changes without using Compute Changes
Io07778 SysStore Connector creates fawlty WHERE CLAUSE from Link Crit
IO07378 Fix and remove some error messages (6.1.1)
IO06976 SAX parser removing spaces from values.
IO07135 shutdown request hook is not called when shutting down AL
IO07302 wrong prefix in log when reusing connector
IO07413 command param is not getting cleared when specified in config
IO07420 AL Connector throwing Null Pointer Exception while opening conf
IO06580 Problem with Colon : in property Stores name.
IO07308 DSMLV2SOap connector messing chinese chars.
IO07779 Feed and Flow section becomes null while renaming them
IO07780 Include SPMLv2 Parser
IO07294 Scripts are not getting published
IO07301 XSL BASED XML PARSER HAS PROBLEMS WITH UTF-8 BOM
IO07292 Failed to behave correctly when link criteria has time stamp
IO07303 COMMUNICATE REMOTE COMMANDLINE (FC) PARAMETERS TO EBCDIC
IO07521 Fatal Error on console when configs folder has non TDI xml file
IO07458 Reconnect for the LDAP Connector does not work
IO07293 Problem using (new) DSMLv2 connector with AD (6.1.1)
IO07505 Mail file title not set properly by Dom User Conn
IO07781 Compute changes does not work for SystemStore Connector
IO07756 DSMLV2 Parser throws Exception when having dsml.attributes
IO07110 EmfSdoToXml FC:synthesized name were not handleled
IO07782 CBE FC fails eventhough situation.CategoryName defined

2.3 Fixes included exclusively in Fixpack 3
===========================================
IO08360 Virtual List View parameter is missing its checkbox
IO07297 TDI Config Editor performs slowly.
IO08631 ReplaceUsersOnUpdate attribute does not work intuitively
IO08632 Not possible to specify Resource Type when creating a GSO Credentials
IO07555 The logger from within the AL seems not picking up the {2}
IO08633 AxisSoapToJava throws exception for mode parameter
IO08634 Server mode Connectors ignore param settings in the TCB.
IO07744 SAX Parser does not process 3rd level null value data correctly
IO08635 Apply SPMLv2 fixes from CVT 7.0 to 6.1.1
IO08643 Blank Iterator State Key is saved to the System Store
IO08645 Hardcode the label and the description of the parameter.
IO07803 XSLbasedXMLParser when used with URL connector throws Exception
IO07899 AL pooling:do not save connectors if not initialized
IO07833 Work is null in default_on_error of Connector loop comp
IO08627 Axis Easy WebServive Invoke function component is timing out
IO07800 Problem with null behavior
IO07832 TCPConnector: getWriter() gets null
IO08648 task.dumpEntry displays wrong Properties
IO08179 When Invalid command is executed, exit value is 0.
IO08007 JavaScript: STRING.MATCH & REGEXP.EXEC METHODS DO NOT RETURN GROUP PATTERNS
IO07802 JavaScript:TYPEOF DOES NOT WORK AS EXPECTED.
IO07798 JavaScript:CHANGE OF BEHAVIOR IN THE SPLIT METHOD
IO07797 JavaScript:STRING MATCH ISSUE
IO08212 SOAP Response is not correct when having zero output params
IO08231 Cannot inherit user property store connector config with File connector
IO08649 TAM Connector: modifying/deleting users/groups is a performance hit
IO08650 TAM Connector: Provide ability to perform filtered queries in the TAM Connector
IO08275 If CLOB attribute vaule is null,TDI Error: CTGDIS266E
IO08651 TAM Connector: Wrong results if ReplaceGroupsOnUpdate is set to true
IO08652 TAM Connector: Wrong results if ReplaceUsersOnUpdate is set to true
IO08653 TAM Connector:Modify SSO Credential error message
IO08335 FTPBean.cd returns true for existing and non existing directory
IO08273 Attribute inheritance issue when attribute case is changed.
IO08654 The documented RfcXmlInvoker class is missing.
IO08041 FC component initializes always at STARTUP.
IO08511 SCRIPT CONNECTOR INIT: "TASK" SCRIPT VARIABLE INCORRECT TYPE.


2.3 List of Supported platforms
===============================

Matrix describing the supported platforms can be found in the Technotes section on the IBM Tivoli Directory Support homepage :

http://www-01.ibm.com/support/docview.wss?uid=swg27008801


3.PREREQUISITES
===============

TDI 6.1.1 GA Level should be installed already.


4.INSTALLATION INSTRUCTIONS
===========================

4.1 Information about the Fixpack package:
==========================================


Files Included in package:

File Name - TDI_MAIN_IU.jar
Purpose - Used for installation of fixpack on all platforms except zOS.
Size - 8638850
md5 checksum - 3419c3db84f4144105e3bd019544af3a


File Name - Z611FP3.PTF
Purpose - PTF for z/OS
Size - 8234080
md5 checksum - d9061cc001f08d688fc02fbf0d992a1d


4.2 Steps to install fixpack for all Platforms, Except z/OS.
============================================================

1) Download the Fixpack and unzip the content in any preferred folder. You will find TDI_MAIN_IU.jar in the package, this is what you will need during installation.
2) To install this fixpack you need to launch update installer using GMI tool, Default location for GMI tools is like this:
- For Windows GMI tool is available in C:\Program Files\IBM\Common\ci\gmi\bin
- For Unix GMI tool is available in /usr/ibm/common/ci/gmi/bin
Start GMI tool from applicable location, using "gmi" command.
3) Click next on "Welcome to the Update Installer" screen.
4) Select "Install maintenance packages such as fixes, fix packs or refresh packs" and press next.
5) Then it will perform Offering query, let it go, it may take some time.
6) Select TDI 6.1.1 on the next screen and click next, you may have multiple instances of TDI 6.1.1 on same machine, select the one you want to apply the fixpack to. You can click on the Offering record in the list to check the details like installation directory etc.
7) You need to select the path where you have unzipped the Fixpack content. Press "edit" and add that path here. Also check the "include subdirectory" checkbox. This is the folder where GMI will be searching for applicable Fix or fixpack for selected Offering in earlier screen. Then press Next on this screen.
8) Next screen will be querying for the applicable fixpack in the search directory, and will list the applicable fixpack. Select Fixpack-3 on that screen and click Next.
9) Select "Install Maintenance on this computer" and click Next.
10) Next screen will show the summary, verify that everything looks ok and Click "Install" Button.
11) This should install the fixpack successfully.

NOTE:While installation user may see some Exceptions on GMI Console.user action is to ignore those Exceptions unless fixpack install fails.

4.3 Installation instructions for zOS only:
=======================================
In order to install this TDI PTF please follow the standard SMP/E process for applying a PTF.

The installation requisites for this PTF are the same as the installation requisites for TDI 6.1.1. That is why please see the TDI 6.1.1 Program Directory.


5. UNINSTALLATION INSTRUCTIONS (not applicable to z/OS)
=======================================================

You can uninstall the fixpack 3 for IBM TDI 6.1.1 using GMI tool only.

1) Launch update installer using GMI tool(for windows its available in C:\Program Files\IBM\Common\ci\gmi\bin,for unix platform its available in /usr/ibm/common/ci/gmi/bin ).
2) Select un-install option.
3) Select desired IBM TDI v6.1.1 from which you want to un-install fixpack package.
4) Next Panel will show list of IBM TDI v6.1.1 installed on different location along with the status of Fixpack 3 whether it is installed or not,select the desired IBM TDI v6.1.1.
5) Click next.
6) Click Un-install.
7) It will un-install Fixpack3 successfully.

NOTE:While uninstallation user may see some Exceptions on GMI Console.user action is to ignore those Exceptions unless fixpack uninstall fails.

6. Documentation Update
=======================

JDBC Connector:
----------------

API to disable or enable parameter substitution
In certain cases, your customized SQL can end up with substrings (starting with a "{" and ending with a "}") that will be acted upon by the parameter substitution mechanism, and should not. The JDBC Connector exposes an API so you can disable or enable the parameter substitution for the SQL statements that will be executed by the JDBC Connector.

/**
* set enableParamSubstitute parameter
*
*
*/
public void setParameterSubstitution(boolean val)
{
enableParamSubstitute = val;
}

/**
* Returns value of enableParamSubstitute parameter
*
*
*/
public boolean getParameterSubstitution()
{
return enableParamSubstitute ;
}
An alternative to using this API to avoid unwanted parameter substitution is using escape characters.

Avoid unwanted parameter substitution using Escape Character:

The escape character is a "\". If a "\" is encountered in the character directly preceding a {ArgumentIndex} and {TDIReference} (that is, \{ArgumentIndex}and \{TDIReference}), then the parameter substitution will not take place (will not be processed). Instead, the escape character will be removed and the parameter substitution will not occur. For example, \{TDIReference} would simply be {TDIReference} after being processed.

Remote Command Line Function Component:
---------------------------------------
"AS400ArgEncoding" new config parameter has been added in this function component.

Details
The character encoding to use for AS400 command line arguments. The default character encoding of the JVM is used if not specified. This configuration parameter is optional and only applies when the Run AS400 Program? parameter is set. Failure to set this value to the proper encoding of the target AS400 box can cause the command line parameter strings to be corrupted if the encoding of the JVM on the remote machine does not match the default encoding of the AS400 machine where the AS400 Program will be run.

Publishing Assembly Line:
-------------------------
Problem reported for APAR IO07294 is fixed in this fixpack, here is more documentation update on this functionality.For using published Assembly Lines along with global scripts in the different config we must include the published AL in its "include" section.


Logging:
--------
APAR IO07302 is fixed in this fix pack but still it has limitation which is permanent restriction for this release. if we reuse the connector or only connection and if we log message in hook of connector then it displays proper name of that connector while logging the message.But the debug messages from connectors and parsers always have same prefix(name of connector that is being used) in logs.


SPMLv2Parser:
-------------
SPMLv2Parser is now supported on Fixpack2 level and onwards.

Here is a technotes which will be helpful in using this Parser:

http://www-1.ibm.com/support/docview.wss?rs=697&context=SSCQGF&dc=DB520&dc=DB560&q1=SPML&uid=swg21295606&loc=en_US&cs=utf-8&lang=en


JDBC Connector Padding (related to APAR IO06218)
--------------------------------------------------
While update,insert or lookup for CHAR data type,JDBC Connector pads extra spaces if column size is greater then the string length. Following is the way to enable and disable padding.

Padding is enabled by default. User needs to call this methods in Prolog before initialize hook. Here are steps to do the same:

- In Connector's hook tab, go to prolog->before initialize.
- Add the script
<connectorname>.connector.setPaddingInUpdate(false);
this will disable padding while update and insert.
- Similarly if anybody wants to disable padding while lookup then he can use
<connectorname>.connector.setPaddingInLookup(false);

NOTE: Default padding for all operations is true.

Documentation regarding changes made to TAMeb Connector:
--------------------------------------------------------
In Iterator Mode, the TAM connector supports wildcards for the filter attribute of User and Group entry types only:

Asterisks can be used to create a UserName wildcard search pattern. The UserName pattern is interpreted as a string of characters that matches zero or more characters of the User’s UserName attribute. Asterisks can be located at the beginning, in the middle or at the end of the UserName pattern, and the UserName can contain multiple asterisks.

Asterisks can be used to create a GroupName wildcard search pattern. The GroupName pattern is interpreted as a string of characters that matches zero or more characters of the Groups’s GroupName attribute. Asterisks can be located at the beginning, in the middle or at the end of the GroupName pattern, and the GroupName can contain multiple asterisks.


Problem with SI and GMI scripts on Windows with Language support
----------------------------------------------------------------
http://www-1.ibm.com/support/docview.wss?rs=697&context=SSCQGF&dc=DB520&dc=DB560&uid=swg21292036&loc=en_US&cs=utf-8&lang=en



7. CONTACTING CUSTOMER SUPPORT
==============================
IBM Tivoli Directory Integrator(TDI) homepage: http://www-306.ibm.com/software/sysmgmt/products/support/IBMDirectoryIntegrator.html