8.4 Optimizing the method of invoking the Enterprise Bean

This chapter describes how to optimize the method of invoking the Enterprise Bean.

Normally, the Enterprise Bean is invoked through an RMI-IIOP by using the remote interface. In this method, the overheads are similar to those in the case of remote connection, even when invoked from the Enterprise Bean running in the same J2EE application and the same J2EE server.

The following methods can be used in optimizing the method of invoking the Enterprise Bean and enhancing the throughput:

Each of these methods has the following features as listed in the table below. In this table, the methods are compared on the basis of four features that are as follows:

  1. Standard specifications: Does it conform to standard specifications?
  2. Performance: Does it enhance the performance?
  3. Location transparency: Is there location transparency?
  4. Maintainability: Is it easily maintainable?

Determine the method to be used based on the features of the application and system.

Table 8-18 Features of the methods of invoking Enterprise Bean

Type of method used for invocationStandard specificationsPerformanceLocation transparencyMaintainability
Local interfaceFFNF
Local invocation of remote interfaceFPFF
Pass by reference for remote interfaceNFPN
Legend:
F: Fully supported. Excellent.
P: Partially supported. Not good
N: Not supported. Poor

For more details about local interface, see the EJB specifications.

For details about the local invocation of the remote interface and the pass by reference of the remote interface, see 2.13 Invoking EJB remote interface in the uCosminexus Application Server EJB Container Functionality Guide.

Organization of this section
8.4.1 Using the local interface
8.4.2 Using the functionality for optimizing the local invocation of the remote interface
8.4.3 Using the pass by reference functionality of the remote interface
8.4.4 Tuning parameters for optimizing the method of invoking the Enterprise Bean