APAR status
Closed as program error.
Error description
The WTX JNDI adapter retrieves a different character encoding than what is defined on the LDAP server.
Local fix
WTXCQ - WTX00039399 PB / PB Circumvention: None
Problem summary
Users Affected: WebSphere Transformation Extender JNDI adapter user that requires LDAP output results to match a specific encoding. Problem Description: The JNDI Adapter does not return the same character encoding as that contained on the LDAP Server. Platforms Affected: All
Problem conclusion
The JNDI Adapter can now be configured to return a particular character encoding. After looking up an LDAP entry, the Adapter will consult the JVM to determine if the system property, adapter.m4jndi.output_charset, contains a desired encoding. If so, then the output results of any LDAP searches will be returned in this specific encoding. When the system property is not set, the results are encoded in the default JVM platform encoding, which is now logged in the Adapter trace file for reference purposes. Delivered in: 8.1.0.6, 8.2.0.6, 8.3.0.5
Temporary fix
Comments
APAR Information
APAR number
PM52167
Reported component name
WSTX
Reported component ID
5724M4000
Reported release
830
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2011-11-14
Closed date
2011-11-22
Last modified date
2012-02-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WSTX
Fixed component ID
5724M4000
Applicable component levels
R810 PSY
UP
R820 PSY
UP
R830 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSD8","label":"IBM Transformation Extender"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.3","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
03 February 2012