|
Problem(Abstract) |
This document describes how various application clients
should be configured to access IBM® WebSphere® Application Server V5 data
sources. |
|
|
|
Resolving the
problem |
Two primary types of application clients are supported by
WebSphere Application Server V5 releases:
J2EE application client
The J2EE™ application client is a Java™ application program that
accesses enterprise beans, Java Database Connectivity (JDBC™), and Java
Message Service message queues. The J2EE application client program runs
on client machines. This program follows the same Java programming model
as other Java programs. However, the J2EE application client depends on
the application client runtime in order to configure the execution
environment and uses the Java Naming and Directory Interface™ (JNDI) name
space to access resources.
The J2EE application client does not support looking up or directly
accessing data source resources that are configured on WebSphere
Application Server because the J2EE application client does not support
Java 2 Connection Factories. To use a data source directly from the client
application, you must configure the data source using the Application
Client Resource Configuration Tool (ACRCT). The ACRCT can be launched by
running clientConfig.bat (Windows® platforms) or clientConfig.sh (UNIX®),
located in the
install_root /bin directory.
You can use the ACRCT tool to configure data sources in the client
container for the J2EE application client, but not for the thin client.
Thin application client
The Thin application client provides a lightweight Java client
programming model. This client is best suited to situations where a Java
client application exists, but the application needs enhancements to use
enterprise beans, or where the client application requires a thinner, more
lightweight environment than the one offered by the J2EE application
client.
WebSphere Application Server and WebSphere Application Server clients do
not provide client database drivers to be used directly from a J2EE
application client. If your application client accesses a database
directly, you must provide the database drivers on the client machine.
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 WebSphere Application Server.
The following two WebSphere Application Server V5 Information Center
links contain step by step instructions on configuring access data from
application clients:
Configuring data access for application clients
http://publib.boulder.ibm.com/infocenter/wasinfo/v5r0/index.jsp?topic=
/com.ibm.websphere.base.doc/info/aes/ae/tdat_condacli.html
Accessing data from application clients
http://publib.boulder.ibm.com/infocenter/wasinfo/v5r0/index.jsp?topic=
/com.ibm.websphere.base.doc/info/aes/ae/tdat_accdfac.html |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|