2.4.1 Functionality that you can use with EJB access
The following table describes the functionality that you can use with EJB access. For details on the functionality, see the description in Reference location.
|
Category |
Functionality |
Explanation |
Reference manual# |
Reference location |
|
|---|---|---|---|---|---|
|
JNDI |
Basic functionality |
Binding and lookup of objects to JNDI namespace |
You can lookup the reference of EJB home objects and business interface from Naming Service by using automatically bound name (Portable Global JNDI name or name starting with HITACHI_EJB) or user-specified namespace. |
Common Container Functionality Guide |
2.3 |
|
Extended functionality |
Searching CORBA Naming Service with round-robin policy |
For the systems, which are configured with multiple Naming Service and J2EE servers, you can perform lookup from a batch application with round robin. Accordingly, you can achieve load balancing. |
2.7 |
||
|
Caching by naming management functionality |
You can maintain (cache) objects, looked up from Naming Service, on memory. You can decrease cost on access performance to Naming Service by using cache. |
2.8 |
|||
|
EJB |
Executing Enterprise Bean |
You can invoke Enterprise Bean, being executed in EJB container, from a batch application. However, you can use only remote invocation method. You cannot perform local invocation. |
EJB Container Functionality Guide |
2.2 |
|
|
Invoking Enterprise Bean |
3.4 |
||||
|
Acquiring RMI-IIOP stub and interface |
You can invoke an application from a batch application by using RMI-IIOP functionality of Cosminexus TPBroker. |
3.7 |
|||
|
Invoking remote interface of EJB |
You can select send operation if communication failure occurs when invoking EJB from a batch application. |
2.13 |
|||
|
Transaction |
Transaction management |
You can start and conclude transactions in a batch application. However, you cannot use global transactions in a batch application. |
Common Container Functionality Guide |
3.4 |
|
|
Implementing transactions in EJB client application |
You can start and conclude transactions in a batch application by acquiring UserTransaction. The following two methods are used to acquire UserTransaction:
|
EJB Container Functionality Guide |
3.5 |
||
|
Others |
Setting timeout in EJB container |
You can set up a timeout of the RMI-IIOP communication in communication between a batch server and a Naming Service, and a batch server and a J2EE server. In a batch application, a timeout of Stateful Session Bean, timeout of EJB object of Entity Bean, and timeout of instance acquisition waiting are not applicable. |
EJB Container Functionality Guide |
2.11 |
|
|
Performance analysis of system that uses performance analysis trace |
You can output performance analysis trace of batch application. |
Maintenance and Migration Guide |
Chapter 7 |
||
|
Outputting user log of an application |
You can output log of a batch application. |
This manual |
|||
# uCosminexus Application Server is omitted in the manual names mentioned in Reference manual.