Adapter for Enterprise JavaBeans 6.5 SP3 | webMethods Adapter for Enterprise JavaBeans Documentation | webMethods Adapter for Enterprise JavaBeans Installation and User’s Documentation | Overview of webMethods Adapter for Enterprise JavaBeans | Adapter Services | FetchEJB 3.0 Adapter Service | Run-Time Processing for a FetchEJB 3.0 Service
 
Run-Time Processing for a FetchEJB 3.0 Service
At run time, the service's only inputs are the parameter values required by the EJBObject method (if any).
If the operation is successful, the FetchEJB 3.0 service returns to the caller an array of javax.ejb.Handle instances that represent the remote EJBs found. These handles may subsequently be de-serialized by the caller to obtain the underlying EJBs or may be passed into a suitably configured InvokeEJB 3.0 adapter service.
Note:
In general, session EJBObject methods will always return a single EJBObject, entity EJBObject methods (for example, finder methods) may return multiple EJBObjects. To accommodate the possibility of multiple objects being returned, a FetchEJB 3.0 service always wraps the output of the service in an array.
If the FetchEJB 3.0 service fails, it throws an adapter exception.
Step
Description
1
An Integration Server client runs a flow service or Java service on Integration Server.
2
The flow or Java service invokes a FetchEJB 3.0 adapter service on Integration Server.
You configured the adapter service earlier using Designer.
3
The FetchEJB 3.0 adapter service gets a connection from the service's connection pool.
You created and enabled the adapter connection earlier using Integration Server Administrator.
4
Through its connection, the FetchEJB 3.0 adapter service accesses the application server's JNDI to look up the EJBRemote interface of the EJB for which the service was configured.
5
The FetchEJB 3.0 adapter service fetches the configured EJBObjects associated with the JNDI Name configured on the application server.
If the operation is successful, the adapter service returns an array of javax.ejb.Handle instances that represent the remote EJBs.
If the operation is unsuccessful, the adapter throws an AdapterException or AdapterConnectionException. For more information about how the adapter handles exceptions, see Adapter Logging and Exception Handling.
6
The FetchEJB 3.0 adapter service saves the resulting remote EJB handles and status on pipeline. These handles may then be de-serialized by the caller to obtain the underlying EJBs or simply passed into a suitably configured InvokeEJB 3.0 adapter service.