13.3 Setting application bindings

At packaging time, you create references to resources. For an application to run, bind these references to the real resources, such as JDBC data sources, created from the console. This needs to be done for EJB references and resource references. You also need to define the enterprise bean's JNDI names, and security roles.

Bindings can be defined at development or deployment time. Most likely, developers will deliver a preconfigured EAR file that will then be modified at deployment time by the deployment team to suit the target environment.

All binding definitions are stored in the ibm-xxx-bnd.xmi files, where xxx can be ejb-jar, Web, application, or application-client.

In the next steps, you define the following bindings using the Application Server Toolkit:

EJB JNDI names

EJB references

Data source for entity beans

All sections below assume that you have started the Application Server Toolkit and imported the Plants by WebSphere source, as described in Import source code.