[8.5.5.7 or later]

Generating deployment descriptors for WebSphere managed beans bindings

You can generate deployment descriptors for WebSphere managed beans bindings for your enterprise applications and web projects. The deployment descriptors are automatically added to the new ibm-managed-beans-bnd.xml file, which you can open in the Managed Beans Bindings Editor.

Before you begin

Ensure that one or more of the Enterprise JavaBeans (EJB), web, or application client facets are enabled, and that you did not already generate an ibm-managed-beans-bnd.xml file for your application project. If at least one of the EJB, web, or application client facets is not enabled, or if an ibm-managed-beans-bnd.xml file exists, then you cannot generate an ibm-managed-beans-bnd.xml file.

About this task

Deployment descriptors for WebSphere managed beans bindings map the name that is used in the environment context to the Java Naming and Directory Interface (JNDI) name. The name that is used in the environment context is specified in the bean code. The JNDI name points to a resource available in a container. You can generate deployment descriptors for WebSphere managed beans binding for both enterprise applications and web projects.

Procedure

  1. Right-click your application project and select Java EE Tools > Generate WebSphere Managed Beans Bindings Deployment Descriptor.

    The ibm-managed-beans-bnd.xml file is generated in the META-INF directory of your application, and opened in the Managed Beans Bindings Editor. If a web facet is enabled on the project, then the file is generated in the WEB-INF directory instead.

  2. To reopen the ibm-managed-beans-bnd.xml file in the Managed Beans Bindings Editor later, double-click the file name.
Icon that indicates the type of topic Task topic
Timestamp icon Last updated: July 17, 2017 21:58

File name: tgenmanbeansdd.html