IBM BPM, V8.0.1, All platforms > Get started with IBM BPM > Key concepts > Bindings > Binding types > EJB bindings

EJB import bindings

EJB import bindings allow an SCA module to call EJB implementations by specifying the way that the consuming module is bound to the external EJB. Importing services from an external EJB implementation allows users to plug their business logic into the IBM BPM environment and participate in a business process.

You use Integration Designer to create EJB import bindings. You can use either of the following procedures to generate the bindings:

The generated import has data bindings that make the Java-WSDL connection instead of requiring a Java bridge component.

You can directly wire a component with a Web Services Description Language (WSDL) reference to the EJB import that communicates to an EJB-based service using a Java interface.

The EJB import can interact with Java EE business logic using either the EJB 2.1 programming model or the EJB 3.0 programming model.

The invocation to the Java EE business logic can be local (for EJB 3.0 only) or remote.

When it configures the EJB binding, Integration Designer uses the JNDI name to determine the EJB programming model level and the type of invocation (local or remote).

EJB import bindings contain the following major components:

If your user scenario is not based on the JAX-WS mapping, you might need a custom data handler, function selector, and fault selector to perform the tasks otherwise completed by the components that are part of the EJB import bindings. This includes the mapping normally completed by the custom mapping algorithm.

EJB bindings


Related information:
Developing data handlers
Developing a custom fault selector