The following are known issues associated with this release of the connector:
Bug 7207232
Some Asian languages use multibyte character sets. If the character limit for fields on the target system is specified in bytes, then the number of Asian-language characters that you can enter in a particular field may be less than the number of English-language characters that you can enter in the same field. The following example illustrates this point:
Suppose you can enter 50 characters of English in the User Last Name field of the target system. If you have configured the target system for the Japanese language, then you would not be able to enter more than 25 characters in the same field.
See Section 4.13, "Modifying Field Lengths on the Process Form" for information about working around this issue.
Bug 8670307
If you enable connection pooling, then custom entries created in the Lookup.SAP.UM.ITResourceMapping lookup definition do not take effect.
Bug 9797993
On Oracle Identity Manager release 11.1.1, the SAP CUP Delete Recon scheduled task does not work.
Bug 9759483
The following issue is observed when you perform a request-based provisioning operation on Oracle Identity Manager release 11.1.1:
In the Role Name lookup field or Profile Name lookup field, the results displayed when you search for a role or profile do not show descriptions (Decode values) of the roles or profiles. Only Code Key values are displayed.
Bug 10361925
The Compliant User Provisioning feature of the connector does not work if Oracle Identity Manager is running on IBM WebSphere Application Server.
Bug 13429841
Limitation:
Whenever any jar is updated/modified, if application server is not restarted then it will throw the following error:
java.lang.UnsatisfiedLinkError: Native Library /usr/local/jco/libsapjco3.so
java.lang.UnsatisfiedLinkError: Native Library /usr/local/jco/libsapjco3.dll
already loaded in another classloader. It is limitation from SAP JCO.
Analysis:
Whenever any jar is updated/modified, the application server tries to register SAP destination data provider (SAP JCO) even though it is already registered. Therefore the application server throws an error.
Workaround:
Restart the application server if any jar is updated or modified in Oracle Identity Manager server.