1.2.2 Functionality for scheduling Enterprise Beans using CTM
The following table describes the functionality for scheduling Enterprise Beans using CMT. Select the functionality according
to the purpose of the system. For details on the functionality, see Reference location in the table.
Table 1‒3: Correspondence between the Enterprise Bean scheduling functionality using CTM and the purpose of systems
|
Functionality
|
Purpose of system
|
Compliance with Java EE Standard
|
Reference location
|
|
Reliability
|
Performance
|
Operation and Maintenance
|
Scalability
|
Others
|
Standard
|
Extended
|
|
Flow-volume control of requests
|
Y
|
Y
|
--
|
--
|
--
|
--
|
Y
|
3.4
|
|
Controlling priority of requests
|
Y
|
Y
|
--
|
--
|
--
|
--
|
Y
|
3.5
|
|
Dynamically changing the number of concurrent executions of requests
|
Y
|
Y
|
Y
|
--
|
--
|
--
|
Y
|
3.6
|
|
Locking and controlling requests
|
Y
|
--
|
Y
|
--
|
--
|
--
|
Y
|
3.7
|
|
Load balancing of requests
|
Y
|
Y
|
--
|
Y
|
--
|
--
|
Y
|
3.8
|
|
Monitoring and retaining request queues
|
Y
|
--
|
Y
|
--
|
--
|
--
|
Y
|
3.9
|
|
Connection with the TPBroker/OTM client by using the gateway functionality in CTM
|
--
|
--
|
--
|
Y
|
--
|
--
|
Y
|
3.10
|
- Legend:
-
Y: Supported
--: Not supported
- #
-
The functionality, for which Y is specified only in the Extended column of the Compliance with Java EE Standard column, indicates the functionality unique to Application Server.
To Page Top
