1.2.1 Functionality used when executing batch applications
The following table describes the functionality used when executing batch applications. Select the functionality according to the purpose of the system. For details on the functionality, see Reference location in the table.
|
Functionality |
Purpose of system |
Compliance with Java EE Standard |
Reference location |
||||||
|---|---|---|---|---|---|---|---|---|---|
|
Reliability |
Performance |
Operation and maintenance |
Scalability |
Others |
Standard |
Extended |
|||
|
Functionality for executing batch applications |
Executing batch applications |
-- |
-- |
-- |
-- |
-- |
-- |
Y |
|
|
Forcefully stopping batch applications |
-- |
-- |
Y |
-- |
-- |
-- |
Y |
||
|
Displaying a list of the batch application information |
-- |
-- |
Y |
-- |
-- |
-- |
Y |
||
|
Output of batch application logs |
-- |
-- |
Y |
-- |
-- |
-- |
Y |
||
|
EJB access functionality |
Invoking Enterprise Beans |
-- |
-- |
-- |
Y |
-- |
Y |
Y |
|
|
Lookup of EJB home objects and references of business interfaces by using JND |
-- |
-- |
-- |
Y |
-- |
Y |
Y |
||
|
Implementing transactions |
-- |
-- |
-- |
Y |
-- |
Y |
Y |
||
|
Timeout for the RMI-IIOP communication |
-- |
-- |
-- |
Y |
-- |
Y |
Y |
||
|
Acquiring RMI-IIOP stubs and interfaces |
-- |
-- |
-- |
Y |
-- |
Y |
Y |
||
|
Functionality provided by naming management |
Lookup and binding of the objects to the JNDI name space |
-- |
-- |
-- |
Y |
-- |
Y |
Y |
2.5# |
|
Assigning optional names to J2EE resources (user specification name space functionality) |
-- |
-- |
-- |
Y |
-- |
-- |
Y |
||
|
Searching CORBA Naming Service by using the round-robin policy |
-- |
-- |
-- |
Y |
-- |
-- |
Y |
||
|
Caching with the naming management functionality |
-- |
Y |
-- |
-- |
-- |
-- |
Y |
||
|
Switching CORBA Naming Service |
-- |
-- |
-- |
Y |
-- |
-- |
Y |
||
|
Functionality provided by resource connections and transaction management |
Connection pooling |
-- |
Y |
-- |
-- |
-- |
Y |
Y |
2.7, |
|
Warming up of connection pool |
-- |
Y |
-- |
-- |
-- |
-- |
Y |
||
|
Functionality for adjusting the number of connection pools |
-- |
Y |
-- |
-- |
-- |
-- |
Y |
||
|
Connection sharing and association |
-- |
Y |
-- |
-- |
-- |
Y |
-- |
||
|
Statement pooling |
-- |
Y |
-- |
-- |
-- |
-- |
Y |
||
|
Light transactions |
-- |
Y |
-- |
-- |
-- |
-- |
Y |
||
|
Caching the DataSource object |
-- |
Y |
-- |
-- |
-- |
-- |
Y |
||
|
Optimizing sign-on for the container management of DB Connector |
-- |
Y |
-- |
-- |
-- |
-- |
Y |
||
|
Detecting connection failure |
Y |
-- |
-- |
-- |
-- |
Y |
Y |
||
|
Waiting for acquiring a connection when connections exhaust |
Y |
-- |
-- |
-- |
-- |
-- |
Y |
||
|
Retrying for acquiring a connection |
Y |
-- |
-- |
-- |
-- |
-- |
Y |
||
|
Displaying information of a connection pool |
Y |
-- |
-- |
-- |
-- |
-- |
Y |
||
|
Clearing connection pool |
Y |
-- |
-- |
-- |
-- |
-- |
Y |
||
|
Cancelling the transaction timeout and statements |
Y |
-- |
-- |
-- |
-- |
Y |
-- |
||
|
Output of SQL for the failure investigation |
-- |
-- |
Y |
-- |
-- |
-- |
Y |
||
|
Automatic closing of object |
Y |
-- |
-- |
-- |
-- |
Y |
-- |
||
|
Testing the connection with resources |
-- |
-- |
Y |
-- |
-- |
-- |
Y |
||
|
GC control functionality |
-- |
Y |
-- |
-- |
-- |
-- |
Y |
||
|
Container extension library |
-- |
-- |
-- |
Y |
-- |
-- |
Y |
||
|
JavaVM functionality |
-- |
-- |
Y |
-- |
-- |
-- |
Y |
||
- Legend:
-
Y: Supported
--: Not supported
- Note
-
The functionality, for which Y is specified in both the Standard and Extended columns of the Compliance with Java EE Standard column, indicates that the functionality unique to Application Server has been extended to the Java EE standard functionality. The functionality, for which Y is specified only in the Extended column, indicates the functionality unique to Application Server.
- #
-
In the case of batch applications, you can assign optional names only to J2EE resources. The description of Enterprise Beans is not applicable.