Data source lookups for enterprise beans and web modules
During either application assembly or deployment, we must bind the resource reference to the JNDI name of the actual resource in the runtime environment. We can take this action in the assembly tool or as one of the steps during installation of the application EAR file.
Bean-managed persistence bean
When developing bean-managed persistence (BMP) bean we generally lack knowledge about the name of the data source on the target application server. In the code, do not look up the data source directly. Instead, we look up the resource reference from the java:comp/env namespace file. Let us assume that we look up the resource reference named ref/ds, for example:
javax.sql.DataSource dSource = (javax.sql.DataSource)((new InitialContext()).lookup("java:comp/env/ref/ds"));
In the assembly tool, we specify the name ref/ds in the Resource Reference page on the General Tab. If we know the name of the data source we can specify it in this Resource References page on the Bindings Tab. Note that if we do not specify it here, provide this JNDI name when we install the application EAR file.
Container-managed persistence bean
The data source binding process for the container-managed persistence (CMP) bean is the same process that we perform for bean-managed persistence (BMP) beans. Use the data source 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 data source exactly as you look it up in the BMP bean case.
Related:
Data sources Unshareable and shareable connections Create and configure a JDBC provider and data source using the JMX API Configure data access for the Application Client Create or change a resource reference Assemble data access (EJB) applications Migrate applications to use data sources of the current Java EE Connector Architecture (JCA) Configure a JDBC provider and data source