Troubleshoot the Application Portlet Builder

The following section lists known problems and solutions related to the Application Portlet Builder.

 

Related to JDBC:

 

Problem: Missing or incorrect configuration for JDBC Builder causes error.

You will see the error: No configuration has been entered for this portlet. Click on the configure icon. There are two possible causes:

  • There is no configuration for a portlet at runtime.
  • There is a bad configuration that results in a communication failure of the portlet to its back end application.

Solution:

  • In edit mode, enter a user ID and a password.
  • In configuration mode, confirm that the configuration is specified.

 

Problem: JDBC Portlet Builder creates and runs portlets with invalid user ID and password on Cloudscape.

If you have a Cloudscape data source, you might find that an invalid user ID and password for the JDBC Portlet Builder and Portlet runtime (login) will not prevent you from successfully creating and running Cloudscape portlets.

Solution: The user ID and password are used for a JDBC connection. Authentication to Cloudscape in this manner is always successful regardless of user ID and password.

 

Problem: Runtime Errors

  • Error in log:Cannot use WebSphere Application Server 4 data source with a 2.3 servlet.

Solution: All data sources in WebSphere Application Server must be configured as version 5 data sources.

 

Problem: Configuration Hints

Solution:

  • JDBC Builder Configuration:The JNDI name entered must match a data source JDNI name where the Test Connection for that data source is successful. It might be necessary to stop and restart WebSphere Application Server and the WebSphere Portal appserver if you have reconfigured a WebSphere Application Server data source before successfully testing the connection.
  • JDBC Datasource:It might be necessary to stop and restart the WebSphere Application Server appserver and the WebSphere Portal application server for the Test Connection feature of a data source to be successful.

 

Problem: Create, Update, and Delete are not working.

Solution: Create, update, and delete operations are permitted only on tables with primary keys.

 

Problem: JNDI Naming Exceptions in the log or on the screen

Solution: The JDBC Provider and Data Source configurations must be under the Cell or Node Scope.

 

Problem: Issues with using Cloudscape

Solution:

The following tips may be used with Cloudscape:

  • For Cloudscape, only one open connection is permitted on a database at a time. If you successfully test the connection using the test connection button on the Cloudscape data source, you might need to restart the server.
  • If Cloudscape needs to be upgraded, set the Connection Attributes property in the Cloudscape data source to upgrade=true. This permits the upgrade.

    If you do this, you may no longer be able to use cview with that database until you upgrade cview.

  • If you are using Cloudscape viewer and you upgrade you might no longer be permitted to view this database. This is because the viewer tool says the tool needs an upgrade to view the upgraded database.

 

Problem: Issues with using DB2

Solution:

  • DB2 on Unix: have the DB2 environment sourced in before starting the WebSphere Application Server. The full error is java.lang.UnsatisfiedLinkerError: SQLConnect
  • DB2 on Windows 2000: reboot the machine after installing DB2 or the DB2 client. The full error is java.lang.UnsatisfiedLinkerError: SQLConnect
  • DB2 on a remote machine: Use the DB2 Configuration Assistant to set up an alias for the remote database you want to connect to.

 

Problem: Authentication or Authorization errors in the log or on the screen

Solution: DB2 and Oracle: Provide an authentication alias when configuring the data source for both component and container managed authentication. For DB2, the builder and portlets will work even if Test Connection fails on the data source. For Oracle, the builder portlets and Test Connection will always fail.

 

Related to Domino:

 

Problem: Cannot connect to your Domino server.

You will see the error: Invalid user ID and password.

Possible causes and related solutions:

  • The HTTP service on your Domino server is not started. Start HTTP service on your Domino server.
  • The DIIOP service on your Domino server is not started. Start DIIOP service on your Domino server.
  • If single sign on is enabled between your Domino server and your WebSphere Portal, the user name and password on the two systems must be identical. Make sure single sign on is configured correctly if it is enabled.
  • The Domino server name and port number entered are incorrect. Use the correct Domino server name and port number.
  • If single sign on is not enabled, the user name and password entered are incorrect. Use the correct user name and password.
  • Domino server Internet configuration does not allow HTTP clients to browse databases. In your Domino server, under Server Document > Internet Protocols > HTTP, select Yes to Allow HTTP clients to browse databases.

 

Problem: Error building a portlet

You might be able to connect to your Domino server and select a database. You may also be able to select views and forms. However, with subsequent portlet building steps you might see the following message: An expected error occurred. See log files for more details. This error might occur because the Domino database does not have correct access control.

Solution: To solve this problem, specify reader access for the anonymous user on the access control list for the database. This requirement might have security risks and will be fixed in a future release.

 

See also

Home |

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.