Oracle® Identity Manager Connector Guide for SAP User Management Release 9.0.3 Part Number B32371-02 |
|
|
View PDF |
The following are known issues associated with this release of the connector:
The connection pool implementation is not feasible because the Oracle Identity Manager architecture does not support it.
Creation of a user on the SAP system involves running the Create User and Change Password functions in a sequence. This sequence makes three RFC calls to the SAP system. The Create User RFC and Change Password RFC functions commit the transaction explicitly at the end of the call. The commit is enforced by the SAP architecture. This architecture constraint of SAP makes it infeasible to conduct transactions such as Create User and Change Password.
When a user is created, the password specified is not allocated to the user. Later, the SAP system requires the user to specify the password again, which is assigned to the user at this stage. To prevent the occurrence of this event, when a new user is created, the user is assigned a dummy password and after user creation the Change Password function is called automatically. The password changes from the dummy password to the one entered by the user in the SAP User form in Oracle Identity Manager. This process is transparent to the user.
Some Asian languages use multibyte character sets. If the character limit for the fields in 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 limitation:
Suppose you can enter 50 characters of English in the User Last Name field of the target system. If you were using the Japanese language and if the character limit for the target system fields were specified in bytes, then you would not be able to enter more than 25 characters in the same field.
In SAP 4.7 or later, you cannot enter non-English letters in the E-mail Address field.
The connector uses the JCO API that supports JDK 1.4 to communicate with SAP User Management. Oracle Identity Manager supports the Oracle Containers for J2EE (OC4J) release that works on JDK 1.5. Therefore, the connector does not support OC4J.