Index
Symbols
A
B
C
-
calling J2EE applications from TPBroker client or TPBroker OTM client, overview of
-
call issued to stateless session bean through remote interface
-
checking
-
class hierarchy in Explicit Memory Management functionality API
-
common prerequisite settings of session failover functionality
-
common settings for using Explicit Memory Management functionality (setting JavaVM options)
-
configuration file for disabling application exclusion of Explicit Memory Management functionality
-
configuration file for explicit memory management functionality application exclusion
-
connection with TPBroker/OTM client by using gateway functionality in CTM
-
contents checked in negotiation processing (database session failover functionality)
-
correspondence between Enterprise Bean scheduling functionality using CTM and purpose of systems
-
correspondence between other expanded functionality and purpose of systems
-
corresponding functionality used when executing batch applications and purpose of systems
-
CTM functions
D
-
definitions of JavaVM options in Explicit Memory Management functionality
-
deleting global session information (database session failover functionality)
-
deleting session information storage table and blank record information table
-
displaying list of batch application information (when not using scheduling functionality)
-
displaying list of batch application information (when using scheduling functionality)
-
dynamically changing number of concurrent executions of requests (CTM)
E
-
EJB client
-
ejbserver.application.userlog.CJLogHandler.handler-name.appname
-
ejbserver.application.userlog.CJLogHandler.handler-name.count
-
ejbserver.application.userlog.CJLogHandler.handler-name.encoding
-
ejbserver.application.userlog.CJLogHandler.handler-name.filter
-
ejbserver.application.userlog.CJLogHandler.handler-name.formatter
-
ejbserver.application.userlog.CJLogHandler.handler-name.level
-
ejbserver.application.userlog.CJLogHandler.handler-name.limit
-
ejbserver.application.userlog.CJLogHandler.handler-name.msgid
-
ejbserver.application.userlog.CJLogHandler.handler-name.path
-
ejbserver.application.userlog.CJLogHandler.handler-name.separator
-
ejbserver.application.userlog.Logger.logger-name.useParentHandlers
-
ejbserver.connectionpool.sharingOutsideTransactionScope.enabled
-
ejbserver.jndi.namingservice.group.<Specify group name>.providerurls
-
Enabling connection sharing outside transactions managed by Application Server
-
example of configuring system using scheduling functionality
-
executing batch applications (when not using scheduling functionality)
-
executing batch applications (when using scheduling functionality)
-
executing batch applications by using scheduling functionality
-
executing commands used in batch application (when not using scheduling functionality)
-
executing commands used in batch applications (when using scheduling functionality)
-
explicit memory block size represented by ExplicitMemory instance
-
explicit release reserving of Explicit memory block when automatic release functionality is disabled
-
explicit release reserving of Explicit memory block when automatic release functionality is enabled
F
-
flow of executing batch applications (when not using scheduling functionality)
-
flow of execution of batch applications (using scheduling functionality)
-
forced stopping of batch applications (when using scheduling functionality)
-
forcefully stopping batch application (when not using scheduling functionality)
-
functionality executed when using session failover functionality
-
functionality for controlling object movement to Explicit memory blocks
-
functionality for operating and maintaining application execution platform
-
functionality that defines refer-only request in HTTP session
-
functionality that you cannot implement in batch applications
-
functionality that you can set when using session failover functionality
H
-
handling authentication information when inheriting session information
-
how to forcefully stop batch application (when not using scheduling functionality)
-
How to start batch applications (when scheduling functionality is not used)
-
how to use filter/ formatter/ handler independently created by user
-
HTTP session attributes that are inherited as global session information
I
-
Implementing batch application (batch application creation rules)
-
implementing batch application (when connecting to resources)
-
implementing batch applications (migrating from Java applications)
-
implementing Java program that uses Explicit Memory Management functionality API
-
implementing to obtain statistics of Explicit Memory Management functionality
-
inheriting global session information when starting web application, [2]
-
inheriting session information depending on objects registered in HTTP session
-
items used for confirming whether web applications are matching
J
L
-
load balancing of requests
M
N
-
negotiation processing (database session failover functionality)
-
notes on using Explicit heap in objects related to HTTP session
-
number of concurrent executions (CTM)
O
-
objectives of using Explicit Memory Management functionality
-
operation if an object is being referenced from outside when releasing Explicit memory block
-
Operation of EJB client when communication failure occurs in remote interface
-
overview of management functionality by integrating with JP1
-
overview of memory space used in Explicit Memory Management functionality
-
overview of node switching functionality by integrating with cluster software
P
-
parameters for load balancing of requests in Easy Setup definition file
-
points to be considered when forcefully stopping batch application
-
policies
-
positioning of Explicit Memory Management functionality, [2]
-
precautions for using Explicit Memory Management functionality
-
precautions to be taken when using database session failover functionality
-
prerequisite configuration for session failover functionality
-
prerequisite settings of database session failover functionality
-
prerequisites for objects that you can place in Explicit heap
-
prerequisites for using Explicit Memory Management functionality
-
procedure for executing batch applications using scheduling functionality
-
procedure for operating batch servers and batch applications
-
procedure for storing session information (database session failover functionality)
-
processing considering that same objects are registered in different HTTP sessions
-
processing implemented in database session failover functionality
-
processing of ending batch application (when not using scheduling functionality)
-
processing of forced stop of batch application (when not using scheduling functionality)
-
processing of starting batch application (when scheduling functionality is not used)
-
process of releasing Explicit memory block when automatic release functionality is disabled
-
process of releasing Explicit memory block when automatic release functionality is enabled
R
-
reducing memory usage of Explicit heap that is used in HTTP session
-
reducing time required for processing of automatic release of Explicit memory blocks
-
relation between result of negotiation processing and web application states
-
relationship between ExplicitMemory instance and Explicit memory block
-
releasing Explicit memory block when automatic release functionality is disabled
-
releasing Explicit memory block when automatic release functionality is enabled
S
-
schedule queue (CTM)
-
setting and operating batch application execution environment when using scheduling functionality
-
Setting of not using Explicit Memory Management functionality
-
settings for inhibiting database session failover functionality
-
settings for integrating with JP1/AJS, BJEX and JP1/Advanced Shell
-
settings for length of schedule queue (Easy Setup definition file)
-
settings for schedule group name (Easy Setup definition file)
-
settings for using scheduling functionality(setting batch server)
-
settings for using scheduling functionality(Settings of command to be used with batch application)
-
setting up properties of application that does not include cosminexus.xml
-
setup and operation of batch application execution environment
-
sharing schedule queues, example of
-
state transition of batch application (when scheduling functionality is not used)
-
status transition of batch applications (when using scheduling functionality)
-
status transition of batch applications using scheduling functionality
-
systems integrated with JP1/AJS, BJEX and JP1/Advanced Shell
-
systems not integrated with JP1/AJS, BJEX and JP1/Advanced Shell