Enterprise Java Bean (EJB) controls make it easy for you to use an existing, deployed EJB from within an application. This topic describes how to create a new EJB control and configure it to access a local EJB or a remote EJB.
Note: Before an EJB control will function, the EJB it represents must be deployed in WebLogic Server. To deploy an EJB, please refer to the WebLogic Server documentation, or refer to your system administrator.
A local EJB is an EJB that is deployed on the same instance of WebLogic Server that is running your application. A remote EJB is one that is deployed on a different server.
You can access remote EJBs using the EJB control, provided the server hosting the EJB control and the server to which the target EJB is deployed are in the same domain. You access remote EJBs by using special JNDI syntax in the jndi-name attribute. For example:
jndi://username:password@host:7001/my.resource.jndi.object
Note: Accessing a remote EJB in a different domain via the EJB control requires advanced transaction configuration. Please consult the "Configuring Domains for Inter-Domain Transactions" section of the Managing Transactions topic in the WebLogic Server documentation on edocs.bea.com.