IBM Security Directory Integrator Version 7.2.0 Fix Pack 9 README

Abstract

Readme documentation for IBM® Security Directory Integrator Version 7.2.0 Fix Pack 9 includes installation-related instructions, prerequisites and corequisites, and list of fixes.

Readme file for: IBM® Security Directory Integrator
Product/Component Release: 7.2.0
Update Name: Fix Pack 9
Fix ID: 7.2.0-ISS-SDI-FP0009
Publication date: January 2023

Contents

Download location
Prerequisites and corequisites
Detailed System Requirements
Known issues
Installation information
Steps to install fixpack for all Platforms
Performing the necessary tasks after fix pack installation
Steps for rolling back the latest Security Directory Integrator version 7.2.0 fixpack
List of fixes
Copyright and trademark information
Document change history

Download location

Download IBM Security Directory Integrator Version 7.2.0 Fix Pack 9 from http://www.ibm.com/support/fixcentral/ or access the fix from the table below.

Product/Component Name	Platform	File Name
IBM Security Directory Integrator 7.2.0 Fix Pack 9 - 7.2.0-ISS-SDI-FP0009	All Platforms	7.2.0-ISS-SDI-FP0009.zip

Security Directory Integrator Documentation

SDI v7.2 documentation can be accessed at the IBM Documentation.

IBM Security Learning Academy

SDI courses from the IBM Security Learning Academy can be accessed at the Directory Integrator Courses.
This link may also be accessed from the Help menu in the Configuration Editor.

Prerequisites and corequisites

SDI 7.2.0 GA or SDI 7.2.0 GA with any previous fix pack. Each FixPack is cumulative, and includes all of the changes and improvements of all prior FixPacks.
It is necessary only to install the most recent Fixpack to bring your SDI installation fully up to date.
Upgrade to IBM JVM 8. JVM 8 is required for applying the fix pack. See install Java 8 for SDI .

Detailed System Requirements

SDI 7.2 supported operating systems are listed here. See detailed system requirements .

Known issues

SDI v7.2.0 Update Installer

Before you install Fix Pack 9, it is recommended that you patch your SDI Update Installer, so that Fix Pack 9 is applied properly.
If the Update Installer patch is not applied older version of Axis2 jars will not be removed during the fix pack installation. See Axis2 updated to version 1.7.6.

Instructions for patching the SDI Update Installer:

Copy the file UpdateInstaller.jar from the fixpack package and replace the copy in the <SDI_install_dir>/maintenance directory

Installation Information

Files Included in package: 7.2.0-ISS-SDI-FP0009.zip

FileName	Purpose	Size	md5 checksum
SDI-7.2-FP0009.zip	The file is used as the parameter for the applyUpdates -update <filename>	115,094,253	6b7a55100c765a3613fb9c30ec331bd6
UpdateInstaller.jar	Update Installer for fixpack on all the platforms.	95,322	91100c26f625cfe2a0e8b853ef396912

Steps to install fixpack for all Platforms.

Shut down SDI.
Download the 7.2.0-ISS-SDI-FP0009.zip and unzip the contents in any preferred folder.
Copy the file UpdateInstaller.jar from the fixpack package and replace the copy in the <SDI_install_dir>\maintenance directory.
On Windows:
- Execute the following command <SDI_install_dir>\bin\applyUpdates.bat -update SDI-7.2-FP0009.zip
On Unix :
- Execute the following command <SDI_install_dir>/bin/applyUpdates.sh -update SDI-7.2-FP0009.zip
- After upgrade, need to chmod new shell script: chmod +x bin/updateLog4j.sh bin/removeAMC.sh
Use the new command updateLog4j.sh or updateLog4j.bat to move log4j-1.2.16.jar to the backup folder. This will also update bin/applyUpdates.sh or bin\applyUpdates.bat.

Unix : <SDI_install_dir>bin/updateLog4j.sh
Windows : <SDI_install_dir>bin/updateLog4j.bat

Use the new command removeAMC.sh or removeAMC.bat to remove the AMC and LWI folder

Unix : <SDI_install_dir>bin/removeAMC.sh
Windows : <SDI_install_dir>bin/removeAMC.bat

If using Windows Service and the solution folder is different from the installation folder: win32_service/ibmdiservice.exe should be copied to the solution folder(s). Use OS commands to check for all instance of ibmdiservice.exe outside of 'win32_service' that should be manually updated.

Performing the necessary tasks after fix pack installation

Verify Installation

After the fix pack is installed, ensure that the updateLog4j.sh / updateLog4j.sh command has been run.
To verify the Security Directory Integrator fix pack version installed on your system. Run the following command to verify the latest fix applied to Security Directory Integrator:

Unix/Linux: <SDI_install_dir>/bin/applyUpdates.sh -queryreg
Windows: <SDI_install_dir>\bin\applyUpdates.bat -queryreg

Post Install steps for Federated Directory Server (FDS).

Note: These steps are not required for standard SDI Installations.

Backup files in the <SDI_solution_dir>\configs folder, the <SDI_solution_dir>\SCIM folder, and the <SDI_solution_dir>\LDAPSync folder to a temporary location.

When <SDI_install_dir> = <SDI_solution_dir>.

<SDI_install_dir>\LDAPSync

<SDI_solution_dir>\configs

When <SDI_install_dir> AND <SDI_solution_dir> are different.

<SDI_install_dir>\LDAPSync

<SDI_solution_dir>\configs

<SDI_install_dir>\LDAPSync

<SDI_solution_dir>\LDAPSync

To use SCIM target plugin in FDS:

<SDI_install_dir>\LDAPSync

<SDI_solution_dir>\configs

New properties for SCIM service can be referred to in SCIM.properties.reference file. This file must be used for updating the existing SCIM.properties.

<SDI_install_dir>\SCIM\ReadMe.txt

Steps for rolling back the latest Security Directory Integrator version 7.2.0 fixpack

If it is necessary to rollback the fixpack, a temporary batch file must be used.
Windows :
- copy bin\applyUpdates.bat bin\applyUpdates2.bat
- <SDI_install_dir>bin\applyUpdates2.bat -rollback
- del <SDI_install_dir>bin\applyUpdates2.bat
Unix :
- cp <SDI_install_dir>bin/applyUpdates.sh bin/applyUpdates2.sh
- <SDI_install_dir>bin/applyUpdates2.sh -rollback
- rm <SDI_install_dir>bin/applyUpdates2.sh

Notes about updated components

SDI Fix Pack 9 upgrades Spring to Spring 5.3.22.
SDI Fix Pack 9 upgrades ActiveMQ to ActiveMQ 5.16.5.

Notes about log4j v2

SDI Fix Pack 8 upgrades log4j to log4j 2.17.1. Following are some additional details about the use of log4j.
Instead of etc/log4j.properties we now use etc/log4j2.xml. The old etc/log4j.properties is still available for viewing in case special logging was added there, but it is not used.
The naming convention for old log files is a little bit different, with the version number in front of ".log".
Feel free to make local changes in etc/log4j2.xml, to try out exciting new log4j v2 features.
Here is a link describing the log4j v2 configuration format: https://logging.apache.org/log4j/2.x/manual/appenders.html
By adding .gz to a filePattern, the rolled file will be compressed, saving disk space.
The date format %d{ISO8601} now has a T between date and time. %d{DEFAULT} behaves the same way as the old %d{ISO8601}.

TADDM Connector and log4j

The TADDM Connector depends on TADDM SDK.
The TADDM API JAR files are not shipped with IBM Security Directory Integrator, and must be installed separately.
The TADDM API jar files depends on log4j v1. This may not interoperate with SDI, which is using log4j v2.

3rd Party library and log4j

Any 3rd party library which requires log4j v1, may be affected by this SDI update. The log4j 1.2 bridge is used, so regular log4j v1 logging will be routed to log4j v2. But if the library is using internal log4j v1 methods or classes, problems may be experienced.

AssemblyLine loggers

NTEventLogAppender and CustomAppender loggers do not have log4j v2 equivalent and have been retired from fix pack 8 onwards.

New Properties`

The new property com.ibm.di.suppressSchema=true will not save schema items in the configuration file.
The schema items are mainly used for building the solution. When an attempt is made to transfer with RMI a SDI configuration file having large number of schema items, a stack overflow error may be thrown.
This could happen e.g. between the Configuration Editor and the server, or between the server and AMC.
See http://www.ibm.com/support/docview.wss?uid=swg21623396. for description.

The new property com.ibm.di.SSLProtocols and com.ibm.di.SSLServerProtocols will enable only those protocols mentioned against these properties.
Setting these property to TLSv1, TLSv1.1,TLSv1.2 will ensure that TLS protocol cannot be negotiated down to SSL. These properties should be added to the existing solution.properties.
For maximum security, only TLS1.2 should be used, if possible.

Support for SAP Java Connector (JCo) version 3.

For detailed documentation refer to the SAP_JCo_V3_SUPPORT_README.txt file in the 7.2.0-ISS-SDI-FP0006.zip package.

New library files

RXA Jars update

SDI 7.2.0 Fix Pack 4 onwards, RXA 2.3 jars shipped in SDI have been updated to the RXA fix pack version 2.3.0.14. ( Also included in Fix Pack 9)

SDI 7.2.0 Fix Pack 6 onwards, ssh jars shipped as part of RXA have been updated. Details of the new functionality can be accessed here.

Axis2 updated to version 1.7.6

SDI 7.2.0 Fix Pack 4 ships Axis2 version 1.7.6. ( Also included in Fix Pack 9)

Note: It is recommended to patch the SDI Update Installer. If the Update Installer is not patched, older version of Axis2 jars will not be removed during the fix pack installation.

List of fixes

**APAR fixes included in Fix Pack 1**
APAR No.	Sev.	Abstract
IO20596	3	TDISRVCTL FAILS WITH CTGDJB125E
IO20602	3	THE HTTP SERVER CONNECTOR DOES NOT DISPLAY THE WORK OBJECT DATA IN THE HTTP.BODY AS EXPECTED.
IO20656	3	AXIS2WSCLIENT FUNCTION COMPONENT STACK OVERFLOW
IO20664	3	NOCLASSDEFFOUNDERROR WHEN USING TDISRVCTL
IO20895	3	NOTES CONNECTOR NOT RETURNING HANDLE TO CURRENTLY READ DOCUMENT
IO21045	3	TDISRVCTL IS RETURNING AN ERROR
IO21203	3	THE LOG4J LOGGER FAILS TO APPEND TO LOG FILE AFTER FIRST ASSEMBLYLINE EXECUTION
IO21299	3	PROTECTED PROPERTIES STORED IN CLEAR TEXT AFTER DOWNLOAD FROM SERVER
IO21296	3	DOMINOUSERCONNECTOR IS UNABLE TO CREATE USERS WHOSE FULL NAMES DIFFER ONLY FOR THE ORGANIZATION
IO21471	3	RXA 2.3 JARS UPDATED to 2.3.0.9

**APAR fixes included in Fix Pack 2**
APAR No.	Sev.	Abstract
IO21728	3	HTTPSERVER CONNECTOR CRASHING WITH INCOMPLETE TRAILING ESCAPE
IO21861	3	ASSEMBLYLINE POOL NULLPOINTEREXCEPTION WHEN COM.IBM.DI.SERVER.PERFSTATS IS ENABLED.
IO20951	3	ECLIPSE PLUG-IN FAILS INSTALLATION
IO21911	3	REMOTECOMMANDLINE FC USING SYSTEM USER
IO22070	3	TDI TPAEIFCHANGEDETECTIONCONNECTOR FAILS WITH A COM.IBM.DB2.JCC.C.SQLEXCEPTION
IO22088	3	DSMLV2SOAPSERVERCONNECTOR THROWS ILLEGALARGUMENTEXCEPTION AND STOPS
IO22068	3	THREE BACKSLASH CHARACTERS APPEAR WITHIN DN WHEN HANDLING SPECIAL CHARACTERS
IO22241	3	ASSEMBLY LINE CONNECTOR ONLY ALLOWING ITERATOR MODE
IO22100	3	TARGET USER RDN ATTRIBUTE IS NOT CUSTOMIZABLE

**APAR fixes included in Fix Pack 3**
APAR No.	Sev.	Abstract
IO22674	3	THE DSMLV2SOAPCONNECTOR THROWS A JAVA.LANG.CLASSCASTEXCEPTION:[B INCOMPATIBLE WITH JAVA.LANG.STRINGBUFFER ERROR.
IO22711	3	THE TDI SERVER DOCUMENT DOES NOT MANAGE THE ACTIVEMQ MANAGEMENT AND ACTIVEMQ TRANSPORT PORTS CORRECTLY
IO22799	3	IBMDIRECTORYSERVERCHANGELOGCONNECTOR DOES NOT RETURN THE TARGETDN WHEN MERGE MODE = "RETURN ONLY CHANGED DATA"
IO22976	3	DOMINO CHANGE DETECTION CONNECTOR CRASHES SDI/TDI AND DOMINO SERVER WHEN CONNECTING TO DOMINO SERVER V9.0 OVER IIOP SESSION
IO22999	3	COMPLEXTYPEGENERATORFC AND JDK 7 FAILS TO BUILD JAR
IO23212	3	THE VIRTUAL DIRECTORY (VIRTDIR) EXAMPLE FAILS: "ERROR WHILE INITIALIZING SYSTEM STORE FOR PAGING SUPPORT."
IO23213	3	THE EXCEPTION JAVA/LANG/OUTOFMEMORYERROR "FAILED TO CREATE A THREAD" RECEIVED USING DOMINO CHANGE DETECTION CONNECTOR.
IO23350	3	SDI DERBY STARTING WITH SYSTEM JVM
IO23298	3	THE SANDBOX RECORD/PLAYBACK FUNCTION DOES NOT WORK
IO23352	3	A JAVA.LANG.STRINGINDEXOUTOFBOUNDSEXCEPTION MAY OCCUR WHEN USING THE ITIMAGENTCONNECTOR
IO23353	3	THE ITIMAGENTCONNECTOR DOES NOT SEND A DELETE REQUEST TO THE DAML AGENT AS EXPECTED
IO23318	3	THE TDISRVCLT UTILITY FAILS TO READ THE 'ITERATESTATEKEY' VALUE SET BY A CHANGELOG CONNECTOR
IO23650	3	INCORRECT TDI_SOLDIR
IO23651	3	THE LDIFPARSER IS NOT PROPERLY PARSING THE CR CHARACTER
IO23639	3	SCHEDULER IGNORING SERVER OPTION -M (SIMULATION MODE)
IO23653	3	DSMLV2SOAPCONNECTOR IS NOT PASSING REQUESTID ATTRIBUTE AS PART OF THE < BATCHREQUEST > TAG.
IO23654	3	THE TDISRVCTL -OP STATUS COMMAND DOES NOT LIST ALL CONFIGS RUNNING, ALTHOUGH THE ASSEMBLYLINES ARE LISTED.
IO23724	3	FXTAG FILE FROM FIXPACKS HAVE INVALID XML FORMAT FOR THE FIXID TAG
IO23657	3	PERFORMANCE ISSUES IN SDI 7.2 FP 2 WITH PROCESSING JAVASCRIPT
IO23685	3	FLOW SIMPLE ATTRIBUTE MAPPING IN FDS
IO23823	3	TDISRVCTL UTILITY FAILS TO CONNECT TO TDI SERVER
IO23824	3	TDI PASSWORD PLUGIN ENCRYPTION RESULTS IN WRONG ECRYPTED DATA IN MULTIPLE LDAP SYNC SCENARIO
IO23817	3	TIMERCONNECTOR DOES NOT CORRECTLY WORKS WITH MOSCOW TIME
IO23878	3	DELTA ENGINE FAILS AFTER FIXPACK INSTALL

**APAR fixes included in Fix Pack 4**
APAR No.	Sev.	Abstract
IO22097	3	STATEMENT 'CONTINUE' ISSUE WITHIN A WHILE LOOP
IO24040	3	SDI 7.2 RUNNING ON FDS INCORRECTLY IMPORTS THE CN OF A PERSON FROM AD
IO24366	3	UNKNOWN MEMBER 'GETSTRING' IN JAVA CLASS 'JAVA.LANG.STRING'
IO24497	3	WEAK CIPHERS CAUSE CONNECTION PROBLEMS FOR COMPONENT USING RXA RESOURCES
IO24535	3	STARTING THE CONFIG EDITOR MAY UPDATE THE PROPERTY FILE WITH OLD VALUES
IO24648	3	HTTP CLIENT CONNECTOR LACKS THE "HOST" HTTP-HEADER IN THE "CONNECT" REQUEST
IO24674	3	AXIS EASY WEB SERVICE SERVER CONNECTOR REMOVE THE NEED TO AUTHENTICATION WHEN REQUESTING THE WSDL
IO24672	3	SAP ALE IDOC CONNECTOR THROWS EXCEPTION ORG.XML.SAX.SAXPARSEREXCEPTION:INVALID BYTE 2-3 BYTE UTF8 SEQ
IO24690	3	THE INCREMENTAL SYNCHRONIZATION IN FDS UNEXPECTEDLY DELETES USERS FROM SDS AND ISAM
IO24776	3	DELTA STORE HAS NAMING ISSUES WHEN USING MIXED CASE
IO25931	3	PROJECT FILES ARE NOT TRANSLATED CORRECTLY.
IO24999	3	DOMINO CHANGE DETECTOR CONNECTOR ISSUES WITH DOMINO 9
IO25914	3	JMSCONNECTOR DOES NOT RECOGNIZE A BYTE ARRAY IN THE "MESSAGE" ATTRIBUTE OF THE CONN ENTRY.
IO25617	3	SAP ALE IDOC CONNECTOR THROWS EXCEPTION ORG.XML.SAX.SAXPARSEREXCEPTION:INVALID BYTE 2-3 BYTE UTF8 SEQ
IO25212	3	SQLEXCEPTION: INVALID PARAMETER: UNKNOWN COLUMN NAME TABLE_NAME. ERRORCODE=-4460, SQLSTATE=NULL
IO25282	3	COMPROXY.DLL FAILS TO CAPTURE EXCEPTION MESSAGE
IO25906	3	UNABLE TO GET SPECIAL CHARACTERS FROM SYSTEM.SHELLCOM
IO25907	3	ORACLE DIRECTORY SERVER TIMEOUT IS NOT RECOGNIZED BY THE SUN DIRECTORY CHANGE DETECTION CONNECTOR
IO25908	3	THE 'DROP TABLE CANNOT BE PERFORMED ON IDI_DS_TABLE' ERROR OCCURS IN THE "SERVER PROPERTY STORE EDITOR
IO25909	3	GETNEXTDOCUMENT(OLDDOC) METHOD IN NOTES CONNECTOR RETURNS OLDDOC INSTEAD OF THE NEXT DOCUMENT.
IO25910	3	SAP JCO V3 CONNECTOR - CLASSNOTFOUND ERROR
IO25911	3	THE JCO.CLIENT.PASSWD PASSWORD VALUE IS SHOWN IN CLEAR TEXT
IO25912	3	DELTA VALUES PERTAINING TO DOUBLE AND INTEGER TYPE ARE NOT UPDATED IN TARGET RESOURCE
IO25863	3	KEEPALIVE FOR THE LDAP SERVER CONNECTOR
IO25915	3	ORACLE DIRECTORY SERVER TIMEOUT IS NOT RECOGNIZED BY THE SUN DIRECTORY CHANGE DETECTION CONNECTOR
IO25916	3	SERVER IGNORES CERTIFICATE ALIAS DEFINED FOR API.KEY.ALIAS PARAMETER
IO25885	3	SAP COMPONENT SUITE NO MORE WORKING WITH SAP JCO GREATER 3.0.14.
IO25887	3	NO TYPE=B CONNECTION POSSIBLE WITH SAP COMPONENT SUITE
IO25919	3	IBM DIRECTORY SERVER CHANGELOG CONNECTOR FAILS TO FIND CHANGELOG NUMBER
IO25920	3	DASHBOARD 'LDAP SERVER AUTHENTICATION' FAILS TO ENFORCE GROUP MEMBERSHIP
IO25921	3	DASHBOARD AUTHENTICATION UNKNOWINGLY DISABLED
IO25922	3	SUN DIRECTORY CHANGE DETECTION CONNECTOR FAILS TO RETURN OPERATIONAL ATTRIBUTES
IO25923	3	IBM DIRECTORY SERVER CHANGELOG CONNECTOR DOES NOT RECONNECT AFTER TIMEOUT
IO25956	3	HOW TO USE PROXY WITH AXIS2WSCLIENT FC
IO25924	3	INVOKESOAPWS FUNCTION COMPONENT FAILS WITH A 'CONNECTION RESET' DUE TO AN INVALID 'SOAPACTION' HTTP HEADER
IO25925	3	HTTPCLIENT CONNECTOR FAILS TO CONNECT TO SERVER REQUIRING SNI EXTENSION IN TLS
IO25987	3	THE CONN OBJECT IS FOUND AS UNDEFINED
IO25989	3	PROBLEM PARSING COMPONENT DEFINITION FILE IDI.INF

**APAR fixes included in Fix Pack 5**
APAR No.	Sev.	Abstract
IO25913	3	AMC AND AM SUPPORT FOR TLS COMMUNICATIONS
IO26269	3	XML PARSING PROBLEM OCCURS READING CONFIGURATION FILES

**APAR fixes included in Fix Pack 6**
APAR No.	Sev.	Abstract
IO26846	3	NTLM AUTHENTICATION FOR HTTP CLIENT CONNECTOR
IO27043	3	THE AXIOM LIBRARY CLASSIFIES WHITE SPACE AS "TEXT_NODE", WHILE IT SHOULD HAVE USED "SPACE_NODE"
IO27049	3	SUN DIRECTORY CHANGE DETECTION CONNECTOR FAILS AGAINST ORACLE UNIFIED DIRECTORY 12G SERVER
IO27003	3	PACKET DUMP DATA APPEARS IN NON-DEBUG LOG OF LDAP SERVER CONNECTOR
IO26915	3	TOLOCALELOWERCASE([LOCALE]) DOES NOT TAKE OPTIONAL PARAMETER 'LOCALE'
IO27032	3	HTPCLIENTCONNECTOR CANNOT CONNECT WITH NTLM; RETURNS TWO WW-AUTHENTICATE" HEADERS
IO27065	3	PROBLEM WITH DELTA TDI AND AD CHANGE LOG CONNECTOR
IO26914	3	CONFIGURATION XML FILE SHOWS PASSWORD FIELD ENCRYPTED VALUE WHEN INHERITING FROM EXTERNAL PROPERTY
IO26984	3	HTTPSERVERCONNECTOR WILL TERMINATE AL ON THE "%" CHARACTER PASSED AT THE END OF URL
IO26882	3	JMS CONNECTOR ACCEPTS ONLY PREDEFINED VALUES FOR "SSL CIPHERSUITE" PARAMETER
IO26451	3	JAVACLASSFC FAILS WITH 'ENTRY NOT FOUND
IO26653	3	AXIS2 WS CLIENT FC, SETTING TIMEOUT VALUE
IO27116	3	FDS - INITIAL SYNCHRONIZATION FOR GROUP FAILS
IO27117	3	FDS - INCREMENTAL SYNCHRONIZATION FOR GROUP FAILS WITH [LDAP:ERROR CODE 32 - NO SUCH OBJECT]
IO26891	3	TDI ISSUE WITH SUB AL AFTER HANDLED ERROR
IO27121	3	THE JDBCSELECT PARAMETER IS INCORRECTLY USED IN LOOKUP MODE

**APAR fixes included in Fix Pack 7**
APAR No.	Sev.	Abstract
IO27118	3	FDS - LOG STATEMENT REFERS TO 'UNKNOWN' HOOK
IO27650	3	THE FEDERATED DIRECTORY SERVER (FDS) INCREMENTAL SYNCHRONIZATION FAILS TO TIMEOUT
IO27216	3	SAP ABAP APPLICATION SERVER FUNCTION COMPONENT (SAPR3RFCFCV3) FAILS TO RETURN JCO EXCEPTION TO THE ASSEMBLYLINE ERROR OBJECT
IO27288	3	TOISOSTRING() DOES NOT CONFIRM TO THE TOISOSTRING() METHOD DEFINED IN LATER ECMASCRIPT VERSIONS.
IO26915	3	TOLOCALELOWERCASE([LOCALE]) DOES NOT TAKE OPTIONAL PARAMETER 'LOCALE'
IO27412	3	CONFIGURATION EDITOR ABORTS WITH 'UNHANDLED EVENT LOOP EXCEPTION - JAVA.LANG.STACKOVERFLOWERROR
IO27626	3	CONTAINERS ARE NOT FILTERED BASED ON THE INCLUDE/EXCLUDE FIELD
IO26914	3	CONFIGURATION XML FILE SHOWS PASSWORD FIELD ENCRYPTED VALUE WHEN INHERITING FROM EXTERNAL PROPERTY
IO26984	3	HTTPSERVERCONNECTOR WILL TERMINATE AL ON THE "%" CHARACTER PASSED AT THE END OF URL
IO27518	3	EXPRESSION EDITOR FAILS TO FIND PROPERTY
IO27538	3	SDI ERROR CTGDIK222E - INITIALIZATION OF REPOSITORY DESTINATION *** FAILED: PARAMETER PASSWORD ('JCO.CLIENT.PASSWD') IS MISSING
IO27589	3	CE - CONNECT AND NEXT BUTTON FOR IDS CHANGELOG CONNECTOR DOES NOT FETCH ATTRIBUTES
IO27116	3	FDS - INITIAL SYNCHRONIZATION FOR GROUP FAILS
IO27117	3	FDS - INCREMENTAL SYNCHRONIZATION FOR GROUP FAILS WITH [LDAP:ERROR CODE 32 - NO SUCH OBJECT]
IO27855	3	AXIS2WSCLIENTFC RETURNS NPE AT LOGIN ATTEMPT
IO27856	3	SDI CE BUILD ERROR AFTER IMPORTING CONFIG WITH "CONTAINER NAME=PACKAGE
IO27810	3	HTTP CLIENT CONNECTOR WITH OUT PARSER USES ONLY ISO-8859-1 ENCODING
IO27791	3	CTGDIS895E INVALID PROPERTY NAME PASSED TO THE CONSTRUCTOR
IO28240	3	UNABLE TO USE ISAM REGISTRY ATTRIBUTES WITH ISAM V2 CONNECTOR
IO28213	3	SENDEMAIL FUNCTION COMPONENT FAILS WITH PROTOCOL BEYOND TLSV1
IO27663	3	LARGE INCREASE IN HEAP USAGE IS SEEN DUE TO CLASSINFOCACHE
IO28235	3	PATCH METHOD MISSING FROM HTTPCLIENT CONNECTOR DROP-DOWN LIST

**APAR fixes included in Fix Pack 8**
APAR No.	Sev.	Abstract
IO28235	3	JSON PARSER DOES NOT WRITE COMMA SEPARATOR BETWEEN JSON OBJECTS
IO28452	3	SUN DIRECTORY CHANGE DETECTION CONNECTOR QUERY BUTTON FAILS
IO28576	3	MAXAUTH HEADER USED FOR MAXIMO AUTHENTICATION

Copyright and trademark information

http://www.ibm.com/legal/copytrade.shtml

Notices

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 jurisdictions 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 publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Microsoft, Windows, and Windows Server are trademarks of Microsoft Corporation in the United States, other countries, or both.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

Other company, product, or service names may be trademarks or service marks of others.

THIRD-PARTY LICENSE TERMS AND CONDITIONS, NOTICES AND INFORMATION

The license agreement for this product refers you to this file for details concerning terms and conditions applicable to third party software code included in this product, and for certain notices and other information IBM must provide to you under its license to certain software code. The relevant terms and conditions, notices and other information are provided or referenced below. Please note that any non-English version of the licenses below is unofficial and is provided to you for your convenience only. The English version of the licenses below, provided as part of the English version of this file, is the official version.

Notwithstanding the terms and conditions of any other agreement you may have with IBM or any of its related or affiliated entities (collectively "IBM"), the third party software code identified below are "Excluded Components" and are subject to the following terms and conditions:

the Excluded Components are provided on an "AS IS" basis
IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
IBM will not be liable to you or indemnify you for any claims related to the Excluded Components
IBM will not be liable for any direct, indirect, incidental, special, exemplary, punitive or consequential damages with respect to the Excluded Components.

Document change history

Change Date	Reason	Modified by
January 2023	Create initial 7.2.0-ISS-SDI-FP0009	SDI L3

End of Document