To Debug Adapter Connection Problems

This section describes methods for debugging some common adapter connection problems.

The topics in this section are organized as follows:

• Adapter Authentication Problems

• Active Sync Adapter Problems

• Domino Gateway Adapter Problems

• Mainframe Host Adapter Problems

• PeopleSoft Adapter Problems

• SAP Adapter Problems

• UNIX Adapter Problems

Generally, you can identify adapter connection issues by tracing the adapter class com.waveset.adapter.adapter_classname. For example:

com.waveset.adapter.ADSIResourceAdapter

If necessary, review instructions for enabling trace in Tracing the Waveset Server.

Adapter Authentication Problems

Some common authentication problems include

• Missing authentication properties

  You must include a property name for the specified DataSource type in the set of names output in the trace.

• An Waveset user is missing a matching resource account

  If authentication succeeds for the resource adapter, but an exception occurs indicating that no Waveset user could be found with a matching resource account ID, be sure that the resource accountId associated with the user is the same as the accountId returned by your resource adapter’s authenticate method.

  To verify the Waveset user’s resource accountId, review Waveset’s Edit Trace Configuration page (debug/Show_Trace.jsp). If a mismatch exists, change the content of the name being returned by your authenticate method or change your resource’s ID template. The template must generate a resource accountId that matches the accountId being returned by the authenticate method.

Active Sync Adapter Problems

The most common problems with custom Active Sync adapters are form-related. These errors generally occur because you have not provided necessary information, such as password or email information, in a required field.

Waveset prints form validation errors to the adapter log after the final XML of the view. For example:

20030414 17:23:57.469: result from submit (blank means no errors):
 20030414 17:23:57.509: Validation error: missing required field password

Waveset also prints all messages to the adapter log. These messages include account creation and update times, adapter errors, and a summary of the schema map data.

Active Sync resource adapters store information about the last change processed in the SYNC.resourceName XMLData object.

Domino Gateway Adapter Problems

Following are some common Domino gateway and adapter configuration errors and instructions for fixing these problems:

• If an error message states the ’New Domino Gateway’ resource is not accessible and the connection is refused, try stopping and restarting the Oracle Waveset Gateway.

• If an error message states no ID file name is specified and the path to the userID file is set incorrectly, specify a target location for the userID file and edit the resource adapter to set this attribute to a correct path. Typically, the target location for the userID file is the directory into which you installed the Gateway.

• If an error message states you are not authorized to use the server, you have not set the correct access permissions for the ID file. Specify the correct permissions for this file and retry.

Mainframe Host Adapter Problems

When RACF, ACF2, or TopSecret host adapters fail to reuse or cache connections, users are forced to log in frequently, which negatively impacts performance. Generally, the cache timeout setting causes this problem.

To check the cache timeout setting, trace Waveset’s adapter connection pool as follows:

1. From Waveset’s Edit Configuration Object page, trace the com.waveset.adapter.HostConnPool#reapConnections method at level 4.

   If necessary, review instructions for enabling trace in Tracing the Waveset Server.

2. Capture trace for a sufficiently long period of time (at least 30-60 minutes), while the adapter performs operations.

3. Review the trace output in the application server stdout or trace file and look for Info reaping connection entries.

   If this entry occurs more than once every 30 minutes, you have a good indication that connections are being timed out unnecessarily.

   To resolve this problem, increase the Idle Timeout resource attribute value to prevent connections from being reaped too frequently. The Idle Timeout attribute controls how long a connection remains idle before the connection is logged out. The default value is 90 seconds, which causes new logins to occur frequently.

   Ideally, specify a value that is greater than the average idle time for your deployment environment. For example, adjust the Idle Timeout attribute to 30 minutes (1800000 milliseconds) or more.

PeopleSoft Adapter Problems

This section describes methods for troubleshooting the following PeopleSoft adapter problems:

• Executing a “Test Connection” from the PeopleSoft resource adapter causes a failure with a generic exception.

  1. Open the Waveset.properties file and set exception.trace=true.

  2. Retry the test connection, and if you see the following results:

     FormState: expansion complete java.lang.NullPointerException: PSProperties not loaded from file WavesetException: WavesetException: ==> com.waveset.util.WavesetException: FormState: derivation Log in to the PeopleSoft web interface to verify that you are using the correct UID and password.

• The PeopleSoft application server logs are not showing login attempts.

  This problem generally occurs because you did not use the psjoa.jar file supplied with the PeopleSoft installation to which you are connecting. (See the Oracle Waveset 8.1.1 Resources Reference for more information about the PeopleSoft resource adapter).

SAP Adapter Problems

If an error results when you try to test the connection from an SAP or SAP HR Active Sync adapter to the SAP system, open a command window and run this command from your installation directory WEB-INF/lib:

java -jar sapjco.jar

The sapjco.jar command shows which version of the SAP Java Connector (JCO) is installed and whether the adapter is installed correctly. The command also returns the Java Native Interface (JNI) platform-dependent and the RFC libraries that communicate with the SAP system.

If these platform-dependent libraries are not found, consult the SAP documentation to find out how to correctly install the SAP Java Connector.

UNIX Adapter Problems

This section contains information about debugging some common problems with UNIX adapters.

• If you see timeout errors when provisioning to a UNIX resource adapter, you can determine where the provisioning process is failing by tracing the com.waveset.adapter.ScriptedConnection method at Method/Class level 4, which gives you the maximum logging output.

• When becoming root to perform administrative commands, if the resource adapter executes a su root command instead of a su - root command, the environment does not inherit any of the custom environment variables defined for root; including any custom prompts (environment variable of PS1).

  When configuring a UNIX adapter, you can determine which prompt to enter into the Root Shell Prompt field as follows:

  1. Telnet or ssh to the system as the user you specified in the Login User field.

  2. After typing the password and logging in, type su root without a dash and press return.

  3. Type the root password.

  4. The next prompt displayed is the prompt you must enter into the Root Shell Prompt field.