Viewing and updating EJB import bindings

IBM BPM, V8.0.1, All platforms > Administer applications and processes in the runtime environment > Administer service applications and service modules > Work with imports and exports > Administer bindings > Administer EJB bindings
Viewing and updating EJB import bindings

You can view information about EJB import bindings using the WebSphere administrative console. You can also modify the JNDI name associated with the binding.

To see or edit an EJB binding, it must be installed as part of a Service Component Architecture application in your server profile.

You can modify only the JNDI name property. All other properties for an EJB binding import are read-only.
EJBs invoked by an EJB import can be running in any of the following combinations. For each one of these scenarios, make sure you consider the information in the JNDI configuration information column when you modify the JNDI name:

EJB import JNDI name configurations
EJB scenario JNDI configuration information
IBM BPM in a different Java™ EE module Set the JNDI name in the EJB import binding to match the global namespace. Also, confirm that the JNDI name specified in the EJB import binding matches what is specified in the Java EE module bindings file.
The JNDI name for local invocations, which apply only to the EJB 3.0 programming model, take the form ejblocal: followed by the fully qualified class name of the local interface.
You can find more information in the "JNDI name" topic.
Remote IBM BPM or WebSphere Application Server Create a namespace binding (of EJB binding type) using the IBM BPM administrative console.
To create the namespace binding, click Environment > Naming > Namespace.
The name specified in the namespace field for the namespace binding should match the JNDI name specified in the EJB import binding configuration.
Remote Java EE server (other than IBM BPM or WebSphere Application Server) Create a namespace binding using the IBM BPM administrative console.

If the Java EE server provides a COSNaming interface, create a namespace binding of type CORBA.
If the Java EE server does not provide a COSNaming interface, create a namespace binding of the indirect type.

To create the namespace binding, click Environment > Naming > Namespace.
The name specified in the namespace field for the namespace binding should match the JNDI name specified in the EJB import binding configuration.

If your implementation involves WebSphere Application Server, additional configuration using the WebSphere Application Server administrative console might be required.
To view or configure EJB import properties using the IBM BPM administrative console:

Procedure

Select the module that contains the binding by navigating to Applications > SCA Modules and clicking the module name.
Select the binding by performing the following steps:

In the Module components section, expand Imports.
Expand the import, and then expand Binding.
Click the binding to view information about its properties.

Optional: Change the JNDI name.
Save your changes to the master configuration.

Results
If you made any updates, the binding is changed for the selected module. The changes take effect after you restart the SCA module.
Restriction: If the module is redeployed, the configuration changes you made are replaced by the original settings.
To ensure that the changes you made remain with the module across deployments, use IBM Integration Designer to make the changes in the source code for the module.

Administer EJB bindings

Related concepts:
JNDI names and EJB import bindings

EJB scenario	JNDI configuration information
IBM BPM in a different Java™ EE module	Set the JNDI name in the EJB import binding to match the global namespace. Also, confirm that the JNDI name specified in the EJB import binding matches what is specified in the Java EE module bindings file. The JNDI name for local invocations, which apply only to the EJB 3.0 programming model, take the form ejblocal: followed by the fully qualified class name of the local interface. You can find more information in the "JNDI name" topic.
Remote IBM BPM or WebSphere Application Server	Create a namespace binding (of EJB binding type) using the IBM BPM administrative console. To create the namespace binding, click Environment > Naming > Namespace. The name specified in the namespace field for the namespace binding should match the JNDI name specified in the EJB import binding configuration.
Remote Java EE server (other than IBM BPM or WebSphere Application Server)	Create a namespace binding using the IBM BPM administrative console. If the Java EE server provides a COSNaming interface, create a namespace binding of type CORBA. If the Java EE server does not provide a COSNaming interface, create a namespace binding of the indirect type. To create the namespace binding, click Environment > Naming > Namespace. The name specified in the namespace field for the namespace binding should match the JNDI name specified in the EJB import binding configuration.