Binding to a data source

During either application assembly or deployment, bind the resource reference to the actual name of the resource in the run time environment. You can take this action in the Assembly Toolkit (ATK) or as one of the steps during installation of the application EAR file.

 

Bean-managed persistence bean

When developing your bean-managed persistence (BMP) bean you generally lack knowledge about the name of the data source on the target application server. In your code, do not look up the data source directly. Instead, you look up the resource reference from the java:comp/env namespace file. Let us assume that you look up the resource reference named ref/ds as illustrated in the code below.

javax.sql.DataSource dSource = (javax.sql.DataSource)((new InitialContext()).lookup("java:/comp/env/ref/ds"));

In the ATK, you specify the name ref/ds in the Resource Reference page on the General Tab. If you know the name of the data source you can specify it in this Resource References page on the Bindings Tab. Note that if you do not specify it here , provide this Java Naming and Directory Interface (JNDI) name when you install the application EAR file.

 

Container-managed persistence bean

In a container-managed persistence (CMP) bean you do not specify the DataSource in the code. Instead, you specify the CMP Connection Factory JNDI name as a WebSphere binding property for each bean during application assembly.

 

Servlets and JavaServer Pages Files

In a servlet application, you look up the DataSource exactly as you look it up in the BMP bean case.

---

Connection factory
Data sources
Unshareable and shareable connections

Creating and configuring a JDBC provider and data source using the Java Management Extensions API
Configuring data access for application clients
Creating or changing a resource reference
Assembling data access applications
Migrating a version 4.0 data access application to version 5.1
Creating and configuring a JDBC provider and data source
    

 

---