An EJB client application uses the RMI-IIOP functionality of Cosminexus TPBroker to invoke applications.

When searching and obtaining the references of an EJB home object, settings must be specified in such way so that the following stubs and classes can be referenced in the EJB client application:

• Stubs of the EJB objects of an Enterprise Bean
• Stubs of the EJB home object of an Enterprise Bean
• All classes in which the stubs are used

Furthermore, you can reference the following interfaces and all classes from the EJB client application:

• Remote interface
• Home interface
• All classes that reference the interfaces

If the Enterprise Beans are invoked using a business interface, you can reference the business interface and the classes used for invoking the business interface.

These classes (RMI-IIOP stubs and RMI-IIOP interfaces) are downloaded using the server management commands or dynamic class loading.

Hint

Differentiating the use of the server management commands and the dynamic class loading

Instead of using the dynamic class loading, the use of server management commands for downloading the classes required for invocation is better from the viewpoint of performance. Therefore, Hitachi recommends that you use server management commands during the actual operation. On the other hand, Hitachi recommends the use of dynamic class loading for obtaining and updating the stubs during development and testing because the dynamic class loading does not consume much time.