uCosminexus Application Server, Expansion Guide
![[Contents]](FIGURE/CONTENT.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
Index
[Symbols]
[A][B][C][D][E][F][G][H][I][J][L][M][N][O][P][Q][R][S][T][U][V][W][Y]
- (Symbols)
- -XX:+HitachiJavaClassLibTrace
- -XX:+HitachiOutOfMemoryStackTrace
- -XX:+HitachiUseExplicitMemory
- -XX:+HitachiVerboseGC
- -XX:+HitachiVerboseGCPrintTenuringDistribution
- (A)
- Acquiring JavaVM log (JavaVM log file
- add.class.path
- add.jvm.arg
- add.library.path
- advantages of scheduling batch applications
- application identifier (database session failover functionality)
- application identifiers (EADs session failover functionality)
- application information table
- application procedure (EADs session failover functionality)
- application procedure (EADs session failover functionality)
- asynchronous thread processing
- Asynchronous thread processing by using WorkManager
- asynchronous timer processing
- asynchronous timer processing by using TimerManager
- automatic release reserving of Explicit memory block when automatic release functionality is enabled
- available session failover functionality
- (B)
- balancing number of resident threads
- batch.ctm.enabled
- batch.request.timeout
- batch.schedule.group.name
- batch.service.enabled
- batch.vbroker.agent.port
- batch application execution functionality
- batch application scheduling functionality
- benefits of using session failover functionality
- blank record information table
- (C)
- Caching of DataSource object
- call issued to stateless session bean through remote interface
- calling J2EE applications from TPBroker client or TPBroker OTM client, overview of
- Cancelling statements
- CCC#Ajp13
- CCC#HttpSession
- CCC#HttpSessionManager
- changing settings related to EADs session failover functionality
- checking
- operating status of schedule queues (CTM)
- CJLogRecord class
- class hierarchy in Explicit Memory Management functionality API
- classification for describing functionality
- classificationofapplicationserverfunctionality
- class loader executing batch application
- client applications that send requests
- cluster definition file
- common prerequisite settings of session failover functionality
- common settings for using Explicit Memory Management functionality (setting JavaVM options)
- Communication timeout of naming service
- comparing superiority of session failover functionality
- compatibility with Timer and Work Manager for Application Server
- concurrent execution functionality with same session ID
- concurrent execution with same session ID
- conditions for objects that you can place in Explicit heap
- configuration example of system that executes batch applications (when not using scheduling functionality)
- configuration file for disabling application exclusion of Explicit Memory Management functionality
- configuration file for explicit memory management functionality application exclusion
- Configuring system using scheduling functionality
- connection regulation
- connection with TPBroker/OTM client by using gateway functionality in CTM
- Connection acquisition retry
- Connection management thread
- Connection sweeper
- container extension libraries
- Container extension library
- contents checked in negotiation processing (database session failover functionality)
- contents confirmed in negotiation (EADs session failover functionality)
- controlling priority of requests (CTM)
- controlling requests (CTM)
- 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
- create-based selection policy
- creating and setting handlers
- creating and setting loggers
- creating cache
- creating database tables
- CTM
- configuration and deployment of processes
- flow-volume control, overview of
- process configuration for using
- processes necessary for using
- CTM daemon
- CTM domain
- CTM domain
- CTM domain manager
- CTM domain manager
- checking operating status
- checking operating status
- sharing information in different network segments
- sharing information in same network segment
- CTM functions
- connection with TPBroker/OTM client by using gateway functionality in CTM
- controlling priority of requests
- dynamically changing number of concurrent executions of requests
- flow-volume control of requests
- load balancing of requests
- locking and controlling requests
- monitoring and retaining request queues
- CTM regulator
- CTM, processing performed for using
- ctm.Agent
- customizing LogManager
- (D)
- Daemon Work
- Daemon Work and non-daemon Work
- database session failover functionality
- database session failover functionality
- database settings
- databases that can be connected
- defining refer-only requests of HTTP session
- definitions of database session failover functionality
- definitions of JavaVM options in Explicit Memory Management functionality
- deleting application information table
- deleting cache on EADs server
- deleting database tables
- deleting data on EADs server
- deleting global session information (database session failover functionality)
- deleting global session information (destroying HTTP session) (database session failover functionality)
- deleting global session information on EADs server (session information storage destination server)
- deleting global session information remaining on EADs server (session information copy destination server)
- deleting session information storage table and blank record information table
- destroying HTTP session (EADs session failover functionality)
- Detecting failure in a connection
- Developing application by using WorkManager
- difference between rise when you are not using Explicit Memory Management functionality and when you are using Explicit Memory Management functionality
- differencesbetweensessionfailoverfunctionality
- directly generating objects in Explicit memory block
- 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)
- mechanism of
- overview of
- (E)
- EADs client
- EADs server
- EADs session failover functionality
- EADs session failover functionality
- Easy Setup definition file
- ejbserver.client.ctm.RequestPriority
- ejbserver.ctm.ActivateTimeOut
- ejbserver.ctm.DeactivateTimeOut
- ejbserver.ctm.QueueLength
- EJB client
- calling business-processing programs
- EJB access functionality
- 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.filter
- ejbserver.application.userlog.Logger.logger-name.handlers
- ejbserver.application.userlog.Logger.logger-name.level
- ejbserver.application.userlog.Logger.logger-name.useParentHandlers
- ejbserver.application.userlog.loggers
- ejbserver.batch.application.exit.enabled
- ejbserver.batch.gc.watch.threshold
- ejbserver.batch.queue.length
- ejbserver.batch.schedule.group.name
- ejbserver.client.ctm.RequestPriority
- ejbserver.connectionpool.applicationAuthentication.disabled
- ejbserver.connectionpool.sharingOutsideTransactionScope.enabled
- ejbserver.container.rebindpolicy
- ejbserver.ctm.ActivateTimeOut
- ejbserver.ctm.DeactivateTimeOut
- ejbserver.ctm.enabled
- ejbserver.ctm.QueueLength
- ejbserver.distributedtx.XATransaction.enabled
- ejbserver.jndi.cache
- ejbserver.jndi.cache.interval
- ejbserver.jndi.cache.interval.clear.option
- ejbserver.jndi.cache.reference
- ejbserver.jndi.namingservice.group.<Specify group name>.providerurls
- ejbserver.jndi.namingservice.group.list
- ejbserver.jndi.request.timeout
- ejbserver.jta.TransactionManager.defaultTimeOut
- ejbserver.naming.host
- ejbserver.naming.port
- ejbserver.rmi.request.timeout
- Enabling connection sharing outside transactions managed by Application Server
- environment settings of database
- estimating disk space of database
- estimating memory
- estimating memory of EADs server
- estimating memory used in serialize processing
- estimating size of HTTP session attribute information
- event log output at each stage in life cycle
- events that occur and listeners to be operated
- exact match specification
- exact match specification
- example of configuring system using scheduling functionality
- examples of user log output of applications
- executing applications by using batch servers
- 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 heap
- Explicit heap
- Explicit memory blocks
- explicit memory block size represented by ExplicitMemory instance
- Explicit Memory Management
- Explicit Memory Management functionality
- Explicit Memory Management functionality API
- 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
- extending Explicit memory block
- extending user log output in EJB client applications
- (F)
- file and directory operations
- file format of batch application
- Fixing communication port and IP address of batch server
- flow-volume control
- flow-volume control (CTM)
- overview
- flow-volume control of requests (CTM)
- flow of executing batch applications (when not using scheduling functionality)
- flow of execution of batch applications (using scheduling functionality)
- flow of garbage collection control processing
- flow of processing when failure occurs in database
- flow of processing when failure occurs on EADs server
- flow of processing when failure occurs on web server or J2EE server (EADs session failover functionality)
- flow of processing when failure occurs on web server or J2EE server (database session failover functionality
- forced locking (schedule queue)
- forced stopping of batch applications (when using scheduling functionality)
- forcefully stopping batch application (when not using scheduling functionality)
- functionality as an application execution platform
- functionality executed when using session failover functionality
- Functionality for adjusting number of connections
- functionality for controlling object movement to Explicit memory blocks
- functionality for operating and maintaining application execution platform
- functionality for specifying classes to be excluded from application of Explicit Memory Management functionality
- 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
- (G)
- garbage collection algorithm
- global CORBA Naming Service
- global CORBA Naming Service
- global CORBA Naming Service
- global session
- global session information
- (H)
- handling authentication information when inheriting session information
- handler
- handlers
- Hitachi Trace Common Library
- Hitachi Trace Common Library format
- holding requests if J2EE server terminates abnormally
- how to connect to resources
- how to forcefully stop batch application (when not using scheduling functionality)
- how to set up resource adapters
- How to start batch applications (whenscheduling functionality is not used)
- how to use filter/ formatter/ handler independently created by user
- how to use resource adapter
- HTTP session attributes that are inherited as global session information
- HTTP session that is implicitly created in JSP
- (I)
- impact of servlet API
- Implementing batch application (batch application creation rules)
- implementing batch application (when accessing EJB)
- 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
- implementing to place objects in Explicit heap
- information included in global session information
- information in each field (instance of MemoryUsage class)
- inheriting global session information when starting web application
- inheriting global session information when starting web application
- inheriting session information between J2EE servers
- inheriting session information depending on objects registered in HTTP session
- inhibiting full garbage collection
- inhibiting session failover functionality
- initializing application information
- initializing database table
- Initializing Explicit memory block
- integrating with JP1/AJS
- integrity mode
- items used for confirming whether web applications are matching
- (J)
- J2EE application
- locking and controlling requests for
- overview of calling from TPBroker client or TPBroker OTM client
- J2EE application, replacing while system is online
- overview
- J2EE resource adapter
- java.naming.factory.initial
- Java EE functionality that you can use in asynchronous parallel processing of thread
- Java logging API
- job ID
- (L)
- life cycle of batch application
- Life cycle of daemon Work
- life cycle of Explicit memory block
- life cycle of Explicit memory block
- Life cycle of non-daemon Work
- life cycle of TimerManager
- Life cycle of WorkManager
- listeners that operate in association with events occurring in database session failover functionality
- listeners that operate in association with events occurring in EADs session failover functionality
- load balancing
- times when load balancing takes place
- times when load balancing takes place
- load balancing of requests
- parameters in Easy Setup definition file
- load balancing of requests (CTM)
- load status, watching
- load balancer
- locking and controlling requests
- for J2EE application
- for J2EE application (overview)
- for schedule queue
- for schedule queue (overview)
- locking requests (CTM)
- locking global session information
- log format
- log format
- logger
- loggers
- log output of batch application
- Long-life objects
- long-life Work
- (M)
- main updates in functionality of Application Server 09-50
- mapping of each stage in the life cycle and output event log
- mechanism of inhibiting full garbage collection
- mechanism of inhibiting full garbage collection by using Explicit Memory Management functionality
- mechanism of Java logging
- memory saving functionality of Explicit heap that is used in HTTP session
- method of scheduling thread by using TimerManager
- methods of Logger class used in user log output
- methods used in user log output
- migrating from Java applications
- migrating to environment using scheduling functionality
- Minimum value and maximum value of connection
- monitoring and retaining request queues
- Multiple schedule of TimerManager
- (N)
- Naming caching
- Naming management
- naming management functionality
- negotiation processing (database session failover functionality)
- negotiation processing (EADs session failover functionality)
- Non-daemon Work
- notes on batch application to be connected to resources
- notes on servlet API related to HttpSession objects
- notes on using Explicit heap in objects related to HTTP session
- number of concurrent executions (CTM)
- mechanism of dynamically changing
- value that can be specified
- (O)
- objectives of using Explicit Memory Management functionality
- objects for communication with redirector
- objects placed in Explicit heap
- objects related to HTTP session
- objects that are effective when placed in Explicit heap
- objects that you can place in Explicit heap
- operating batch application execution environment
- operation if an object is being referenced from outside when releasing Explicit memory block
- operation mode of database session failover functionality
- Operation of EJB client when communication failure occurs in remote interface
- operations performed when failure occurs during global session information operation (database session failover functionality)
- operations performed when a failure occurs during global session information operation (EADs session failover functionality)
- Optimizing sign-on in container management of DB Connector
- Outputting age distribution information of Survivor area
- overview of asynchronous parallel processing of threads
- overview of batch application execution functionality
- overview of container extension libraries
- overview of execution environment of batch applications
- overview of garbage collection control functionality
- 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
- overview of resource connections and transaction management
- overview of scheduling functionality
- (P)
- package to which CJLogRecord class belongs
- parameters for load balancing of requests in Easy Setup definition file
- points to be considered when creating batch application
- points to be considered when executing batch applications
- points to be considered when forcefully stopping batch application
- points to be considered when using scheduling functionality
- policies
- create-based selection policy
- schedule policy
- Pool size of CallableStatement
- Pool size of PreparedStatement
- positioning of Explicit Memory Management functionality
- positioning of Explicit Memory Management functionality
- precautions for using Explicit Memory Management functionality
- precautions to be taken when using database session failover functionality
- prefix macth specification
- prefix match specification
- preparations for EADs server
- 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
- prerequisites for using scheduling functionality
- priority of requests, controlling
- procedure for analyzing log that uses performance analysis trace
- procedure for asynchronous parallel processing of thread
- procedure for executing batch applications using scheduling functionality
- procedure for operating batch servers and batch applications
- procedure for setting resource adapter
- procedure for storing session information (database session failover functionality)
- procedure for storing session failover functionality (EADs session failover functionality
- procedure for user log output processing
- process configuration for using CTM
- processes necessary for using CTM
- processes required for scheduling functionality
- processing considering that same objects are registered in different HTTP sessions
- processing implemented in database session failover functionality
- processing implemented in EADs 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)
- processing that can be implemented in batch application
- process of releasing Explicit memory block when automatic release functionality is disabled
- process of releasing Explicit memory block when automatic release functionality is enabled
- (Q)
- queue
- queue name
- (R)
- realservername
- reducing HTTP session
- reducing HTTP session
- reducing memory usage of Explicit heap that is used in HTTP session
- reducing time required for processing of automatic release of Explicit memory blocks
- refer-only requests
- regulation
- how connections are regulated
- relation between result of negotiation processing and web application states
- relationship between ExplicitMemory instance and Explicit memory block
- releasing explicit memory blocks by using javagc command
- releasing Explicit memory block when automatic release functionality is disabled
- releasing Explicit memory block when automatic release functionality is enabled
- replacing J2EE application while system is online
- overview
- request scheduling, purpose of
- request that cannot be scheduled by CTM
- request transfer timeout
- requests controlled by using schedule queues
- requests that can be controlled by CTM, type of
- resident threads, balancing number of
- resource connection functionality
- Round robin search
- (S)
- schedule policy
- schedule queue
- schedule queue
- basis on which to create
- basis on which to create
- example of not sharing
- example of sharing (by beans)
- example of sharing (by J2EE applications)
- forced locking
- length
- locking and controlling requests for
- sharing
- sharing
- timeout-triggered locking
- timeout-triggered locking
- schedule queue (CTM)
- changing maximum number of concurrent executions
- checking operating status
- schedule queue monitoring expression
- schedule queue monitoring function
- schedule queue monitoring, example of
- schedule group
- schedule queue
- scheduling of batch applications
- server definition file
- Server start/stop hook functionality
- service lock
- session failover functionality
- session failover inhibitionion functionality
- session information
- session information storage table
- session management using global session
- set of manuals (function guides)
- setting and operating batch application execution environment when using scheduling functionality
- Setting for building server as batch server
- Setting for enabling light transaction functionality
- Setting for not using SecurityManager
- setting initial size and maximum size of Java heap
- setting maximum time for connecting to CTM
- setting of EADs session failover inhibition functionality
- Setting of JavaVM operation when invoking JavaVM end method
- Setting of not using explicit management heap functionality
- Setting of real server name
- settings for inhibiting database session failover functionality
- settings for integrating with JP1/AJS
- settings for integrating withJP1/AJS, BJEX and JP1/Advanced Shell
- settings for length of schedule queue (Easy Setup definition file)
- settings for port number used by Smart Agent
- settings for schedule group name (Easy Setup definition file)
- settings for schedule group name (usrconf.cfg)
- settings for using scheduling functionality(setting batch server)
- settings for using scheduling functionality(Settings of command to be used with batch application)
- settings for using Smart Agent
- settings of number of concurrent connections, number of concurrent executions, and connection pool size
- Setting up batch application execution environment
- setting up EADs server environment
- setting up properties of application that does not include cosminexus.xml
- setting up timeout
- setting user log output of J2EE applications
- setup and operation of batch application execution environment
- sharing schedule queues, example of
- by beans
- by J2EE applications
- short-life Work
- starting EADs server
- startup configuration file
- states of Explicit memory block
- state transition of batch application (when scheduling functionality is not used)
- state transition of TimerManager
- status transition of batch applications (when using scheduling functionality)
- status transition of batch applications using scheduling functionality
- sub-status of Explicit memory block
- systems executing batch applications
- systems integrated with JP1/AJS
- systems integrated with JP1/AJS, BJEX and JP1/Advanced Shell
- systems not integrated with JP1/AJS, BJEX and JP1/Advanced Shell
- systems using scheduling functionality
- (T)
- Thread pool and queue used in non-daemon Work
- timeout-triggered locking (schedule queue)
- timeout-triggered locking (schedule queue)
- Timeout of RMI-IIOP communication
- TimerManager
- TPBroker client
- overview of calling J2EE applications from
- TPBroker OTM client
- overview of calling J2EE applications from
- Transaction support level
- Types of DB Connector (RAR file)
- types of session failover functionality and differences between types
- (U)
- unlocking clusters
- use.security
- user-created class
- user connected to database
- user log
- user log functionality
- user log output for applications
- user log output of batch applications
- user log output of EJB client applications
- user log output of EJB client applications
- Using explicit management heap functionality
- using multibyte characters
- using object release rate information of Explicit memory block
- Using threads
- (V)
- values shown by each field (instance of MemoryUsage class)
- vbroker.agent.enableLocator
- vbroker.se.iiop_tp.host
- vbroker.se.iiop_tp.scm.iiop_tp.listener.port
- (W)
- Waiting for acquiring connections when connections exhaust
- Waiting time until database connection is established
- Warm-up of connection pool
- when creating batch application
- when migrating from existing batch application
- when serialization fails and its measures
- WorkManager
- (Y)
- your own filter/ formatter/ handler
All Rights Reserved. Copyright (C) 2013, 2015, Hitachi, Ltd.