3 Testing the Connector

After you deploy the connector, you must test it to ensure that it functions as expected. Tests that you can run on the connector can be divided into the following categories:

• Provisioning Testing: This type of test involves using Oracle Identity Manager for provisioning or de-provisioning one of its users or organizations with a target resource. In other words, Oracle Identity Manager is the starting point of the connector, and the target resource is the end point.

• Reconciliation Testing: In this type of test, you reconcile Oracle Identity Manager with either a trusted source or a target resource. In other words, the trusted source or target resource is the starting point of the connector, and Oracle Identity Manager is the end point.

Note:

In earlier releases of this guide, the connector was referred to as the integration.

This chapter contains the following sections:

• Supported Platforms

• Running Test Cases

• Troubleshooting

Supported Platforms

The following table provides information about the environments on which this connector has been tested.

Oracle Identity Manager Release	Host Platform	Application Server	Database	SAP BASIS Version
8.5.3	Microsoft Windows 2003	JBoss 3.2.7	Oracle9i Database	4.7 and 4.6
8.5.3	Linux AS 2.1	BEA WebLogic 8.1 SP 3	Oracle9i Database	4.7 and 4.6
8.5.3	Solaris 9	IBM WebSphere 5.0.2.9	Oracle9i Database	4.7 and 4.6

Running Test Cases

You can use the troubleshooting utility to directly use the connector for identifying the cause of problems associated with connecting to the SAP CUA server and performing basic operations on the target system.

The SAPCUA_versionno\troubleshoot directory contains the troubleShoot.properties file. The troubleshooting utility uses this file to connect to the SAP CUA server. This file contains the following information:

• SAP connection parameters: Server-related information.

• User information: Field information required to create, modify, update, and delete a user profile.

• Reconciliation information: The "From date" timestamp information is passed from this file. The "To date" is set to the current time.

• CLASSPATH information: List of files to be included in the CLASSPATH.

This file also contains commands to test the following tasks:

• Create User

• Modify User

• Delete User

• Change Password

• Lock User and Unlock User

• Reconcile user information

In the C:\test\troubleshoot directory (path to troubleshoot directory), set the following SAP server connection parameters in the troubleshooting.properties file:

sapClient=800
sapUser=xellerate
sapPassword=project
sapLanguage=EN
sapSystem=00
sapIP=172.20.70.206
sapType=CUA
SAPsnc_mode=0
SAPsnc_myname=p:CN=win2003, OU=SAP, O=ORA, C=IN
SAPsnc_qop=3
SAPsnc_partnername=p:CN=I47, OU=SAP, O=ORA, C=IN 
SAPsnc_lib=C:\\usr\\sap\\sapcrypto.dll
ChangePasswordSystem=X
MasterSystem=CUA47

In the log.properties file in the same directory, set the path for the log files in the following parameter:

log4j.appender.logfile.File=log_file_path

Note:

Ensure that all the JAR files associated with this connector are included in the CLASSPATH.

Creating a User

To test the connector for the creation of a user, specify the following information for a new user object in the troubleshooting.properties file.

userId=CUAKT12
password=PASSNEW
dummyPassword=ADMIN
lockStatus=UnLock
userGroup=ADMIN
lastName=doe
firstName=john
userTitle=Mr.
langComm=E
department=IT
langLogIn=N
timeZone=AUSVIC
telephone=12345678
extension=1234
Fax=12345678
email=[e-mail]
dateFormat=1
decimalNotation=X
function=Function
roomNo=06
floor=1st
building=LBP
code=1
commType=FAX 
alias
startMenu=000
userType
roleProfile=SAP_WPS_ADMIN
roleProfileOption=Role
dummyPwd=DUMMY

On the command line, use the following command to create a user:

java -DTproperties=connector_test_directory\troubleshoot\troubleShoot.properties -Dlog4j.configuration=file:\connector_test_directory\troubleshoot\log.properties TroubleShootingUtility C

Deleting a User

Delete an SAP CUA user as follows:

java -DTproperties=connector_test_directory\troubleshoot\troubleShoot.properties -Dlog4j.configuration=file:\connector_test_directory\troubleshoot\log.properties TroubleShootingUtility D

Modifying a User

Specify the following parameters in the troubleshooting.properties file to modify a user:

changeUserId=cuakk21
fieldName=
fieldValue=jane
bapiKey=ADDRESS
bapiKeyX=ADDRESSX

Use the following command to modify a user:

java -DTproperties=connector_test_directory\troubleshoot\troubleShoot.properties -Dlog4j.configuration=file:\connector_test_directory\troubleshoot\log.properties TroubleShootingUtility M

Testing Reconciliation

To test reconciliation with the SAP CUA connector, specify a timestamp for the From Date of the reconciliation run as shown:

fromDate=Apr 10, 2006 at 10:00:00 GMT+05:30

To test reconciliation from the timestamp specified to the current time, run the following command:

java -DTproperties=connector_test_directory\troubleShoot.properties -Dlog4j.configuration=file:\connector_test_directory\troubleshoot\log.properties TroubleShootingUtility R

Troubleshooting

The following sections provide solutions to some commonly encountered problems associated with the connector:

• Connection Errors

• Common SNC Errors

• Create User Errors

• Delete User Errors

• Modify User Errors

• Child Data Errors

Connection Errors

The following table provides solutions to common connection errors.

Problem Description	Solution
Oracle Identity Manager cannot establish a connection to SAP CUA. Returned Error Message: SAP Connection exception Returned Error Code: INVALID_CONNECTION_ERROR	Ensure that the SAP CUA server is up and running. Verify that Oracle Identity Manager is running (that is, the database is running). Verify that all the adapters have been compiled. Examine the Oracle Identity Manager record (from the IT Resources form). Verify that the IP address, admin ID, and admin password are correct.
Target not available Returned Error Message: Target Server not available Returned Error Code: TARGET_UNAVAILABLE_ERROR	Verify that the given SAP connection values are correct. Ensure that the SAP CUA server is running
Authentication error Returned Error Message: Authentication error Returned Error Code: AUTHENTICATION_ERROR	Verify that the given SAP connection user ID and password are correct.

Common SNC Errors

The following table provides a solution to an SNC error.

Problem Descriptions	Solution
Trying to connect to SAP through the SNC. Returned Error Message: SAP Connection JCO Exception Returned Error Code: SNC required for this connection	Ensure that all the required information is given. The required information includes the following: SAPsnc_mode: 1 SAPsnc_myname: p:CN=win2003, OU=SAP, O=ORA, C=IN SAPsnc_qop: 3 SAPsnc_partnername: p:CN=I47, OU=SAP, O=ORA, C=IN SAPsnc_lib: C:\\usr\\sap\\sapcrypto.dll

Create User Errors

The following table provides solutions to common Create User errors.

Problem Descriptions	Solution
Oracle Identity Manager cannot create a user. Returned Error Message: Require information missing Returned Error Code: INSUFFICIENT_INFORMATION_PROVIDED	Ensure that all the required information has been provided. The required information includes the following: User ID User First Name User Last Name User Password UsergroupRole Profile Option Role or Profile
Oracle Identity Manager cannot create a user. Returned Error Message: User already exists Returned Error Code: USER_ALREADY_EXIST	User with the assigned ID already exists in SAP. Assign a new ID to this user, and try again.
Oracle Identity Manager cannot create a user. Returned Error Message: User creation failed Returned Error Code: USER_CREATION_FAILED	User may not have been created because of one of the following errors: The Change Password operation fails Role/profile assignment fails

Delete User Errors

The following table provides solutions to common Delete User errors.

Problem Descriptions	Solution
Oracle Identity Manager cannot delete a user. Returned Error Message: Require information missing Returned Error Code: INSUFFICIENT_INFORMATION_PROVIDED	Ensure that all the required information has been provided. The required information is the user ID.
Oracle Identity Manager cannot delete a user. Returned Error Message: User does not exist in target Returned Error Code: USER_DOESNOT_EXIST	The specified user ID does not exist in SAP.

Modify User Errors

The following table provides solutions to common Modify User errors.

Problem Descriptions	Solution
Oracle Identity Manager cannot update new information about a user. Returned Error Message: Error while updating user info Returned Error Code: USER_MODIFICATION_FAILED	Generic error. Refer to the log file for more details.
Oracle Identity Manager cannot update a user. Returned Error Message: User does not exist in target Returned Error Code: USER_DOESNOT_EXIST	The specified user ID does not exist in SAP.

Child Data Errors

The following table provides solutions to common Child Data errors.

Problem Descriptions	Solution
Oracle Identity Manager cannot add a user to a profile. Returned Error Message: Profile does not exist Returned Error Code: PROFILE_NOT_MEMBER_OF_TARGET_SYSTEM	The profile specified does not exist in SAP. Check the profile name.
Oracle Identity Manager cannot assign a role to a user. Returned Error Message: Role does not exist Returned Error Code: ROLE_NOT_MEMBER_OF_TARGET_SYSTEM	The specified role for the user in Oracle Identity Manager does not exist in SAP. Check the role name.
Trying to add a duplicate value to a profile or role fails. Returned Error Message: Duplicate value Returned Error Code: ROLE_ALREADY_EXISTS PROFILE_ALREADY_EXISTS	The user has already been added to the particular profile or role.