PQ62617: LAUNCHCLIENT ENVIRNOMENT DOES NOT SUPPORT USE OF EMBEDDED MERANTDRIVER AND CAUSES "LICENSE VERIFICATION FAILED" ERROR | |||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||
APAR status Closed as documentation error. Error description launchClient fails with license verification error because setting of the oemId field for the client application is not supported as launchClient does maintain or create datasource connections. The implementation class name of a datasource is configured using clientConfig. The launchClient runtime creates an instance of this class and sets properties that have been configured in the custom tab of clientConfig. Then, the launchClient runtime returns to the application an instance of this datasource class. No connection is created at this time as the J2EE specification requires that javax.sql.DataSource objects be returned for datasource resource references. The client application would have to then create a connection and set the oemID, which we do not allow and therefore fails.Local fix Using a Resource Reference and clientConfig to create a local instance of MERANT is not supported using the embedded driver because of our agreement with MERANT. Customers needing to use the launchClient would have to acquire a MERANT client license.Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server users of a * * launchClient environment. This does not * * support the use of embedded MERANT driver * * and causes "License verification failed" * * error. * **************************************************************** * PROBLEM DESCRIPTION: The WebSphere Application Server J2EE * * Application Client runtime * * (launchClient) does not support the * * use of the embedded MERANT database * * driver as a local client JDBC * * resource. Attempting to do so * * results in a "License verification * * failed" error. * **************************************************************** * RECOMMENDATION: * **************************************************************** In general, WebSphere Application Server does not provide client database drivers. If your client application uses a database directly, you must provide the database drivers on the client machine. This may involve contacting your database vendor to acquire client database driver code and licenses. Instead of accessing the database directly, it is recommended that your client application use an enterprise bean. Accessing a database through an enterprise bean eliminates the need to have database drivers on the client machine, since the database access is handled by the enterprise bean running on the WebSphere Application Server.Problem conclusion Close this APAR as a documentation change. (4.0.4 Release Notes)Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ62617
IBM Group: Software Group
Modified date: Jul 30, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.