Using JNDI Provider to invoke an EJB session bean on a remote WebLogic domain
In the recipe, Exposing an EJB session bean as a service on the OSB using the EJB transport, we have assumed that the EJB session bean is deployed on the OSB server and by that in the same WebLogic domain.
If the EJB session bean to invoke is deployed on another WebLogic domain, which in the real world is the more typical scenario, then a JNDI Provider resource needs to be created on the OSB configuration.
Getting ready
Make sure that the EJB session bean is deployed to the OSB server as shown in the Introduction section of this chapter.
Import the OSB project containing the solution from the recipe, Exposing an EJB session bean as a service on the OSB using the EJB transport, into Eclipse from \chapter-4\getting-ready\using-jndi-provider-to-invoke-remote-ejb.
How to do it...
In Eclipse OEPE, perform the following steps to register a JNDI Provider resource:
Right-click on the obs-cookbook-configuration configuration...
