WebSphere Application Server Network Deployment, Version 6.0.x     Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Assembling data access applications

When you assemble enterprise bean code into files that can be deployed onto an application server, you configure properties that define how the application accesses an enterprise information system (EIS), such as a database.

Before you begin

This article assumes that you have created an enterprise application containing an EJB module that must transact with a database.

Why and when to perform this task

A data access application uses resources, such as data sources or connection factories, to connect with a database. During application assembly you perform activities that enable the application to use these resources. The process typically requires an assembly tool such as the Application Server Toolkit (AST) or Rational Web Developer.

Steps for this task

  1. Identify the logical names that are used by the EJB module to reference application resources. These logical names are called resource references. For further explanation, consult the Looking up data sources with resource references for relational access article.
  2. Start an assembly tool.
  3. If you have not done so already, configure the assembly tool for work on J2EE modules. Ensure that the J2EE capability is enabled.
  4. Define mapping and security properties for the resource references. This process includes the following activities:
    1. Bind the resource references to the application resources that provide database connectivity. See the Binding to a data source article for more information on the concept of binding. At deployment time you can alter your bindings if necessary.
    2. For each resource define an authentication type, which is the security configuration through which database connections are granted. There are two authentication types:
      Component-managed
      The enterprise bean code performs EIS signon for data source or connection factory connections.
      Container-managed
      WebSphere Application Server performs EIS signon.
      Consult the J2EE connector security topic for detailed reference on resource authentication.
  5. Configure access intent assembly settings for your enterprise beans.
    1. Right-click your EJB module in a Project Explorer view and click Open With > Deployment Descriptor Editor.
    2. In an EJB Deployment Descriptor editor, select the Access tab.
    3. Under Isolation Level, click Add.
    4. Select the isolation level, enterprise beans, and method elements. For information on isolation levels, press F1.
    5. Click Finish.
  6. Map enterprise beans to database tables.

Result

Files for the updated application are shown in the Project Explorer view.

What to do next

After testing your application, you are ready to deploy your application to an application server.



Sub-topics
Resource adapter archive file
Assembling resource adapter (connector) modules
Migrating a Version 4.0 data access application to Version 6.0

Related concepts
Connection factory
JDBC providers
Data sources

Related reference
Data access: Resources for learning

Task topic    

Terms of Use | Feedback

Last updated: Dec 11, 2005 4:07:15 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tatk_daass.html

© Copyright IBM Corporation 2002, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)