EJB references [Settings]
For each EJB reference defined in either an ejb-jar.xml file, a web.xml file, or an @EJB annotation in the composition unit, we can specify the JNDI name by which the EJB reference is known in the runtime environment.
This panel shows one row of information for each EJB reference. The final column, EJB Reference JNDI Name, specifies the JNDI name to which the EJB reference is mapped.
If a JNDI name mapping for an EJB reference is defined in either an ibm-ejb-jar-bnd.xml file or an ibm-web-bnd.xml file in the bundle, the corresponding JNDI name is displayed in the EJB Reference JNDI Name column for that EJB reference, otherwise the column is empty. We can modify any existing mappings, and specify new ones, as required, by entering the appropriate values in the EJB Reference JNDI Name column.
To view this panel in the administrative console, click one of the following paths:
- Applications > Application Types > Business-level applications > application_name > [Deployed assets] Add > Add Asset > asset_name > Wizard step: Map EJB references
- Applications > Application Types > Business-level applications > application_name > composition_unit_name > [Additional Properties] EJB references
The Map EJB references wizard step and the EJB references property are visible only if the OSGi application contains at least one EJB reference, defined either in an ejb-jar.xml file, a web.xml file, or in an @EJB annotation.
For each enterprise bean, the panel shows the following information:
- Bundle symbolic name
- The non-localizable name for this bundle.
- Bundle version
- The version of this bundle.
- URI
- The URI of the location where the EJB reference is defined. The following table describes the syntax of the URI depending on the location of the EJB reference:
Location of EJB reference URI syntax Examples ejb-jar.xml file Path to the file, followed by the name of the enterprise bean from which the reference is defined. META-INF/ejb-jar.xml/CustomerDetails or WEB-INF/ejb-jar.xml/CustomerDetails web.xml file Path to the file. WEB-INF/web.xml @EJB annotation in an enterprise bean Path to the ejb-jar.xml file containing the definition of the enterprise bean in which the @EJB annotation is declared, followed by the name of the enterprise bean. META-INF/ejb-jar.xml/CustomerDetails or WEB-INF/ejb-jar.xml/CustomerDetails @EJB annotation in a servlet Path to the web.xml file containing the definition of the servlet in which the @EJB annotation is declared. WEB-INF/web.xml
- EJB Reference Name
- The name of the EJB reference. This corresponds to the EJB reference name defined in the <ejb-ref-name> element in the ejb-jar.xml file or the web.xml file, or the fully qualified EJB reference name if the EJB reference is defined in an @EJB annotation.
- Business Interface
- The fully qualified local or remote interface name of the enterprise bean to which the EJB reference refers.
- EJB Reference JNDI Name
- The JNDI name to which the EJB reference is mapped. We can change the value in this column as required.
Add an EBA asset to a composition unit by Add an EBA asset to a composition unit using wsadmin commands Modify the configuration of an OSGi composition unit Accessing Enterprise JavaBeans in OSGi applications Administrative console buttons Administrative console preferences
File name: was55.html
prettyPrint();