About Flow Services and Adapter for Enterprise Javabeans
Adapter for Enterprise Javabeans enables you to configure adapter services that create or fetch EJB instances on the application server. You can then create adapter services that execute a public method exposed by an EJB. This model implies a logical sequence, or flow of events:
Execute the adapter service to create or fetch the EJB.
Then execute the adapter service that, in turn, invokes one of the EJB's business methods.
Standalone Adapter for Enterprise Javabeans services have little value. Their value is only realized when the services are combined. There are several ways to do this on webMethods Integration Server, but the most common way is to combine the two operations in a single flow service. Using Designer’s flow service editor you can link or map the inputs and outputs of any individual step in a flow service to other steps in the same flow service. This function is important for the following reasons:
Any execution of an InvokeEJB 2.1 or InvokeEJB 3.0 service must be preceded by an execution of a corresponding CreateEJB 2.1 or FetchEJB 3.0 service.
Any execution of an InvokeEJB 2.1 or InvokeEJB 3.0 service always requires at least one input: the output of a prior CreateEJB 2.1 or FetchEJB 3.0 execution. That is, before you can execute an EJB method, you must first obtain that EJB.
Note:
The CreateEJB 2.1, InvokeEJB 2.1, and CreateInvokeEJB 2.1 adapter services are used to access the 2.1 or earlier versions of EJBs. The FetchEJB 3.0, InvokeEJB 3.0, and FetchInvokeEJB 3.0 adapter services are used to access the 3.0 EJBs. The 2.1 adapter services cannot be used with the 3.0 adapter services and vice versa. For more information about the adapter’s services, see
Adapter Services.