InvokeEJB 2.1 Adapter Service

At design time, an InvokeEJB 2.1 service requires two inputs: the JNDI lookup name of the EJB and the identity of the bean method it should invoke. If the method has parameters, you can override the default names given to the parameters in Designer's adapter service editor. For more information about the parameters, see Configuring InvokeEJB 2.1 Services. In an InvokeEJB 2.1 service's input signature, the document name used to contain EJB method arguments is pre-configured and localized. The input document name is EJBObject_Args and is only visible if the bean method takes arguments.

Note that the output of a CreateEJB 2.1 adapter service (the remote EJBs it created) can serve as the input to an InvokeEJB 2.1 adapter service. Because the output of CreateEJB 2.1 is an array of one or more Handle objects representing EJBs of a specific class, you should configure an InvokeEJB 2.1 adapter service to work with the same EJB class returned by the CreateEJB 2.1 service.

Important:
Be careful when naming instances of these CreateEJB 2.1 and InvokeEJB 2.1 adapter services to avoid mismatching them. If a pair of CreateEJB 2.1 and InvokeEJB 2.1 services are mismatched in a flow, this condition will not be detected until that flow is executed.

When adding an InvokeEJB 2.1 adapter service to a flow, note that:

Any execution of an InvokeEJB 2.1 service must be preceded by an execution of a CreateEJB 2.1 service. Both services must be configured to operate against the same EJB class.

Any execution of an InvokeEJB 2.1 service will always require at least one input: the output of a prior CreateEJB 2.1 execution. That is, before you can execute an EJB method, you must first obtain that EJB. For more information, see Obtaining an EJB.