Troubleshooting the SAP ABAP Application Server Component Suite

Problems may be experienced for any of the following reasons:

SAP Java Connector not installed properly

Check the installation and re-install if necessary.

XSL Stylesheets not available

The Connectors rely on XSL stylesheets to perform their operations. See this note on problems that can occur if the XSL folder is not available in the Solution directory.

Missing sapjco.jar

If you attempt to use the SAP ABAP Application Server RFC FC and get an error similar to the following message:

13:01:58  Error in: InitConnectors: java.lang.ClassCastException: 
     java.lang.NoClassDefFoundError 

java.lang.ClassCastException: java.lang.NoClassDefFoundError 

It may be that SAP JCo is not installed correctly. Check that sapjco.jar is in the Tivoli® Directory Integrator_Home/jars directory. Refer to the instructions in Configuring the SAP Java Connector.

Missing librfc32.dll

If you attempt to use SAP ABAP Application Server FC and get an error similar to the following message:
"The dynamic linked library LIBRFC32.dll could not be found in the specified path"
On Windows machines, ensure that librfc32.dll is in the Tivoli Directory Integrator_Home/libs directory. On Solaris and AIX machines, ensure that librfccm.{o/so} has been added to the loadable library path.

Old version of librfc32.dll

If you get an error of the following type:

java.lang.ClassCastException: java.lang.ExceptionInInitializerError

It is possible that the librfc32 being used is an older version and is not compatible with JCo 2.1.6. Check that there is no other librfc32 in your PATH. Also check that any librfc32*.{dll/so} that is in your system path is at least version 6403.3.81.4751.

15:13:44  [YourAssemblyLine] BEGIN	  selectEntries 

15:13:45  [YourAssemblyLine] handleException: initialize, 
java.lang.ClassCastException: java.lang.ExceptionInInitializerError 

15:13:45  [YourAssemblyLine] initialize 

java.lang.ClassCastException: java.lang.ExceptionInInitializerError 	
     at com.ibm.di.script.ScriptEngine.call(Unknown Source) 	
     at com.ibm.di.connector.ScriptConnector.selectEntries(Unknown Source) 	
     at com.ibm.di.server.AssemblyLineComponent.initialize(Unknown Source) 	
     at com.ibm.di.server.AssemblyLine.initConnectors(Unknown Source) 	
     at com.ibm.di.server.AssemblyLine.msInitConn(Unknown Source) 	
     at com.ibm.di.server.AssemblyLine.executeMainStep(Unknown Source) 	
     at com.ibm.di.server.AssemblyLine.executeMainLoop(Unknown Source) 	
     at com.ibm.di.server.AssemblyLine.executeAL(Unknown Source) 	
     at com.ibm.di.server.AssemblyLine.run(Unknown Source)

RFC_ERROR_SYSTEM_FAILURE: Screen output without connection to user

If the connector returns this message, please see SAP Note 49730 for more information.

Query Schema Issues

When performing a schema query using the Connectors with the IBM® Tivoli Directory Integrator GUI, an attempt to connect to the data source may result in an exception. These exceptions can be ignored. Any subsequent use of the discover schema button will succeed.

The Connectors do not support the Get Next Entry style of schema query. The Connectors support the Discover the Schema of the data source (Connect button) style of schema discovery.

User Registry Company Code Assignment

If the value associated with the XML element, <companyKeyName>, does not represent a valid company code within SAP, or is not supplied at all, SAP will assign the configured default.

Changing Mode of Connectors Already in AssemblyLine

During testing, it was observed that changing the mode of Connector in the AssemblyLine did not always work. The Connector sometimes appeared to execute in its original mode, resulting in AssemblyLine errors. If this occurs, delete the Connector and add it to the AssemblyLine in the new mode.

Function Component differences to SE37 Test RFC Feature

In some cases, the RFC Function Component exhibits slightly different behavior to that observed when executing a given RFC from SAP's Test Function Feature, available from transaction SE37. In some cases, the SAP test feature will automatically convert values to internal German abbreviated values (for example, BAPI_SALESORDER_GETLIST). Therefore, some of the values returned by the connector in Lookup and Iterator mode may differ slightly from those returned by the SAP test function feature. When you are required to provide input XML files to set the values of parameters, you should supply the internal values (that is, the same format as the values returned by the connector in Lookup and Iterator modes).

The RFC Function Component will not pad out values of character string types to the maximum length.

User Registry Connector Warnings

In some cases, the Connectors may log warning severity messages as a result of application level ABAP warnings return from SAP. An example of warning messages logged by the User Registry Connector running in Iterator mode is shown below.

15:50:10  [newGetUsers] W: Unable to read the address (69) (D:\Program 
   Files\IBM\IBMDirectoryIntegrator\xsl\bapi_user_get_detail_precall.xsl) 

15:50:10  [newGetUsers] W: Unable to determine the company (76) (D:\Program 
   Files\IBM\IBMDirectoryIntegrator\xsl\bapi_user_get_detail_precall.xsl)

In most cases, these warning messages can be ignored.

User Registry Connector In Update Mode

When run in this mode, the Connector expects the sapUserName attribute to be defined in the Link Criteria and as an XML element, <sapUserName>, within the value associated with the attribute sapUserXml. The values of sapUserName should match in both cases. The Connector does not verify the equality.

Password Behavior In SAP

After a new user is created in SAP, or the password of an existing user is changed, SAP will prompt that user to reset their password at the next logon. This is standard SAP behavior and occurs if the user is created or modified through the SAP transaction SU01, or the Connector.

Delete HR Personal Data With HR Connector

In some cases, an attempt to delete a Personal Data entry using the Connector, or SAP transaction PA30, may fail. The failure message states "Record cannot be deleted (time constraint 1)". Currently, there is no known solution to this problem.