Method for invoking an Enterprise Bean of another J2EE application with the component interface

This subsection describes how to invoke an Enterprise Bean of another J2EE application with the component interface, when the application is running in the same J2EE server and also when the application is running in another J2EE server.

Organization of this subsection: (1) For an Enterprise Bean running in another application on the same J2EE server; (2) For an Enterprise Bean running on another J2EE server

(1) For an Enterprise Bean running in another application on the same J2EE server

To invoke the Enterprise Bean:

Include the remote home interface and remote interfaces of the invoked Enterprise Bean as well as the user-created classes used in the interfaces in the invoking EJB-JAR file or the WAR file.
Specify the following property in the user-defined file for J2EE servers:
Specify app in the ejbserver.deploy.stub.generation.scope key of usrconf.properties.
For details on usrconf.properties, see 14.3 usrconf.properties (User property file for Java applications) in the uCosminexus Application Server Definition Reference Guide.
Use the Naming Service switching functionality to specify the lookup name of the Enterprise Bean beginning with corbaname and running in another J2EE application.
For details on the specification method, see 9.3.1 Reference definition of other Enterprise Beans in the uCosminexus Application Server Application Setup Guide.
An example of the specification is given below:
```
corbaname::NamingHost:900#HITACHI_EJB/SERVERS/MyServer/EJB/MyApplication/MyBean
```

(2) For an Enterprise Bean running on another J2EE server

To invoke the Enterprise Bean:

Include the remote home interface and remote interfaces of the invoked Enterprise Bean as well as the user-created classes used in the interfaces in the invoking EJB-JAR file or the WAR file.
Specify the following property in the user-defined file for J2EE servers:
Specify app in the ejbserver.deploy.stub.generation.scope key of usrconf.properties.
Use the Naming Service switching functionality to specify the lookup name of the Enterprise Bean beginning with corbaname and running in another J2EE application.
For details on the specification method, see 9.3.1 Reference definition of other Enterprise Beans in the uCosminexus Application Server Application Setup Guide.
An example of specification is given below:
```
corbaname::NamingHost:900#HITACHI_EJB/SERVERS/MyServer/EJB/MyApplication/MyBean
```

4.2.5 Method for invoking an Enterprise Bean of another J2EE application with the component interface

(1) For an Enterprise Bean running in another application on the same J2EE server

(2) For an Enterprise Bean running on another J2EE server