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. |