Contents

• Notices

• Preface

• 1. Purpose and Flow of Designing an Application Server System

  • 1.1 Purpose of designing an Application Server system

  • 1.2 Flow of system design

    • 1.2.1 For applications that execute online processing (J2EE applications)

    • 1.2.2 For applications that execute batch processing (batch applications)

• 2. Preparing for System Design

  • 2.1 Items to be determined before designing a system

  • 2.2 Identifying the types of business

  • 2.3 Determining the functionality to be used (when executing online processing)

    • 2.3.1 Process configuration

    • 2.3.2 Configuration of a J2EE server

    • 2.3.3 J2EE applications and J2EE component

    • 2.3.4 J2EE container

    • 2.3.5 J2EE service

    • 2.3.6 J2EE resource

    • 2.3.7 JPA Provider

    • 2.3.8 Container extension library

  • 2.4 Determining the functionality to be used (for executing batch processing)

    • 2.4.1 Process configuration

    • 2.4.2 Configuration of a batch server

    • 2.4.3 Batch application

    • 2.4.4 Batch service

    • 2.4.5 J2EE service

    • 2.4.6 J2EE resource

    • 2.4.7 Container extension library

  • 2.5 Determining the application configuration that suits the system purpose (for operations that execute online processing)

    • 2.5.1 Determining the J2EE applications to be executed

    • 2.5.2 Determining the processes to be used and preparing the required software

  • 2.6 Determining the application configuration that suits the system purpose (for businesses that execute batch processing)

    • 2.6.1 Determining batch applications to be executed

    • 2.6.2 Determining the processes to be used and preparing the required software

  • 2.7 Determining the operation method

    • 2.7.1 Operations of a system integrated with JP1

    • 2.7.2 Operations of system integrated with cluster software

• 3. Determining the System Configuration (J2EE Application Execution Platform)

  • 3.1 Points to be considered when determining the system configuration

    • 3.1.1 Purpose and configuration of the system

    • 3.1.2 Procedure for designing the system configuration

    • 3.1.3 Concept of system configuration

  • 3.2 Description of the system configuration

    • 3.2.1 Common points to be considered for the system configurations described in this chapter

    • 3.2.2 Legend items used for system configuration figures

  • 3.3 Determining the configuration of an application

    • 3.3.1 Configuration of an application and the access points

    • 3.3.2 Resource types and resource adapters

  • 3.4 Determining the configuration of the client and the server

    • 3.4.1 Configuration with servlets and JSPs as access points (for Web server integration)

    • 3.4.2 Configuration where servlets and JSPs are used as access points (when accessing the NIO HTTP server directly)

    • 3.4.3 Configuration with Session Beans and Entity Beans as access points

    • 3.4.4 Configuration where Stateless Session Bean is used as access point when using CTM

  • 3.5 Determining integration between servers

    • 3.5.1 Integration between servers invoking Session Bean and Entity Bean

    • 3.5.2 Integration between the servers that invokes Stateless Session Bean through CTM

  • 3.6 Determining the transaction type

    • 3.6.1 Configuration when using a local transaction

    • 3.6.2 Configuration when using a global transaction

    • 3.6.3 Configuration when using transaction context propagation

  • 3.7 Determining the load balancing method by the load-balancing cluster

    • 3.7.1 Load balancing with a load balancer in case of Web server integration (in the case of servlet or JSP)

    • 3.7.2 Load balancing with a load balancer when using the NIO HTTP server (when not going through a Web server)

    • 3.7.3 Load balancing with the CORBA Naming Service (in the case of Session Beans and Entity Beans)

    • 3.7.4 Load balancing when using CTM (for Stateless Session Bean)

  • 3.8 Determining the configuration for asynchronous communication between servers

    • 3.8.1 Configuration in which a Message-driven Bean is used as the access point (when using Cosminexus JMS provider)

    • 3.8.2 Configuration in which a Message-driven Bean is used as the access point (when using TP1/Message Queue)

    • 3.8.3 Configuration when using a Message-driven Bean as an access point (when using Cosminexus RM)

    • 3.8.4 Load balancing using the Message-driven Bean instance pool (when using TP1/Message Queue)

  • 3.9 Determining the deployment of the operation management process

    • 3.9.1 Configuration wherein the Management Server is deployed on each Management Server

    • 3.9.2 Configuration for deploying Management Server on each machine

    • 3.9.3 Configuration when operating with commands

  • 3.10 Determining the inheritance of session information

    • 3.10.1 Configuration using a database (database session failover functionality)

  • 3.11 Determining node switching when cluster software is used and an error occurs

    • 3.11.1 Configuration in which executing node and standby node of Application Server are in 1-to-1 ratio (when transaction service is not used)

    • 3.11.2 Configuration in which executing node and standby node of Application Server are in 1-to-1 ratio (when using transaction service)

    • 3.11.3 Configuration in which executing node and standby node of Management Server are in 1-to-1 ratio

    • 3.11.4 Configuration in which executing node and standby node of Application Server are mutually standby

    • 3.11.5 Configuration using server exclusive for recovery (N-to-1 recovery system)

    • 3.11.6 Configuration in which the executing node and standby node of the host unit management model are in an N-to-1 ratio

  • 3.12 Deploying a process for the output of the performance analysis trace file

    • 3.12.1 Features of the system configuration

    • 3.12.2 Required software and the processes to be invoked on the respective machines

  • 3.13 Determining integration with products other than Application Server

    • 3.13.1 Configuration when using JP1 for operations

    • 3.13.2 Configuration for invoking a Message-driven Bean from SUP of OpenTP1 using the TP1 inbound integrated function

    • 3.13.3 Configuration in which a Stateless Session Bean is invoked from other than an EJB client using the CTM gateway function

  • 3.14 Managing optional processes with operation management

    • 3.14.1 Features of the system configuration

    • 3.14.2 Processes to be invoked on the respective machines

  • 3.15 TCP/UDP port numbers used by Application Server processes

• 4. Determining the System Configuration (Batch Application Execution Platform)

  • 4.1 Points to be considered when determining the system configuration

    • 4.1.1 Purpose and configuration of system

    • 4.1.2 Procedure for designing the system configuration

    • 4.1.3 Precautions for the TCP/UDP port used in a system for executing batch applications

  • 4.2 System configuration when using a batch server

    • 4.2.1 System configuration of a system that does not use the scheduling functionality of batch applications

    • 4.2.2 System configuration of a system that uses the scheduling functionality of batch applications

• 5. Estimating Resources to be Used (J2EE Application Execution Platform)

  • 5.1 Resources used for each system configuration

    • 5.1.1 Resources used for deploying Web server and J2EE server on the same machine

    • 5.1.2 Resources used when Web server and J2EE server are deployed on different machines

    • 5.1.3 Resources used by the database

    • 5.1.4 Resources used by Management Server

    • 5.1.5 Resources used for CTM

  • 5.2 Resources used for each process

    • 5.2.1 Estimating the resources used by J2EE server

    • 5.2.2 Estimating the resources used by Administration Agent

    • 5.2.3 Estimating the resources used by performance tracer

    • 5.2.4 Estimating the resources used by CTM

    • 5.2.5 Estimating the number of threads used by the cjclstartap process

  • 5.3 Estimating memory used for each process

    • 5.3.1 Estimating virtual memory usage of the J2EE server

    • 5.3.2 Estimating memory used by CTM daemon process

• 6. Estimating Resources to be Used (Batch Application Execution Platform)

  • 6.1 Resources used for each system configuration

    • 6.1.1 Resources used for deploying batch server

    • 6.1.2 Resources used by the database

    • 6.1.3 Resources for using CTM

  • 6.2 Resources used for each process

    • 6.2.1 Estimating the resources used by batch server

    • 6.2.2 Estimating the resources used by Administration Agent

    • 6.2.3 Estimating the resources used by performance tracer

    • 6.2.4 Estimating the resources used by CTM

  • 6.3 Estimating virtual memory usage

    • 6.3.1 Formula for calculating virtual memory usage

    • 6.3.2 Notes when calculating the virtual memory usage

• 7. JavaVM Memory Tuning

  • 7.1 Overview of GC and JavaVM memory management

  • 7.2 Mechanism of serial GC

    • 7.2.1 Overview of serial GC

    • 7.2.2 Relation between the lifespan of an object and its age

    • 7.2.3 Mechanism of copy GC

    • 7.2.4 Saving objects

    • 7.2.5 Areas not subject to GC (using an Explicit heap area with the Explicit Memory Management functionality)

    • 7.2.6 Configuration of memory space used by JavaVM when using serial GC and JavaVM options

    • 7.2.7 Relationship between GC occurrence and memory space

  • 7.3 Overview of tuning to avoid Full GC

    • 7.3.1 Concept of tuning

    • 7.3.2 Tuning procedure

  • 7.4 Java heap tuning

    • 7.4.1 How to estimate the memory size of Java heap

    • 7.4.2 How to set the memory size in Java heap

    • 7.4.3 How to check the usage of memory size of Java heap

  • 7.5 Estimating the memory size of the Tenured area in Java heap

    • 7.5.1 Calculating the memory size required by an application

    • 7.5.2 Reason for adding the memory size of the New area in Java heap

  • 7.6 Estimating the memory size of the New area in Java heap

    • 7.6.1 Estimating the memory size of the Survivor area in Java heap

    • 7.6.2 Estimating the memory size of the Eden area in Java heap

  • 7.7 Determining the handling of objects that exist for a fixed time period in Java heap

    • 7.7.1 How to save in the New area in Java heap

    • 7.7.2 How to save in the Tenured area in Java heap

    • 7.7.3 How to save in the Explicit heap

  • 7.8 Deciding the maximum size or the initial size of Java heap

  • 7.9 Estimating the memory size of the Metaspace area in Java heap

  • 7.10 Analyzing the factors of Full GC using the extended verbosegc information

    • 7.10.1 Overview of the output format of extended verbosegc information

    • 7.10.2 Examples of extended verbosegc information output when Full GC occurs

  • 7.11 Explicit heap tuning

    • 7.11.1 How to estimate the memory size of Explicit heap (Estimating memory size used in J2EE server)

    • 7.11.2 Memory size used by the object related to the HTTP session

    • 7.11.3 Impact of using the Explicit Memory Management functionality when estimating memory size

    • 7.11.4 How to estimate using statistical information

  • 7.12 Estimating the memory size when using the Explicit Memory Management functionality in the application

    • 7.12.1 Determine whether to use the Explicit Memory Management functionality in the application

    • 7.12.2 Estimation concept

    • 7.12.3 Memory size used in the application

  • 7.13 Determining the usage of the Explicit heap using the automatic allocation functionality of the Explicit Memory Management functionality

    • 7.13.1 When there are objects that cause increase in the Tenured area in the application

    • 7.13.2 When the cause of increase in the used size of the Tenured area is not known

  • 7.14 Errors that occur during the application of the Explicit Memory Management functionality and the solutions

    • 7.14.1 Investigating the usage (snapshot) of Explicit heap at a certain point

    • 7.14.2 Investigating the transition of usage status

    • 7.14.3 Checking and measures when there is an overflow from the Explicit heap

    • 7.14.4 Checking and measures when the initialization of the Explicit memory block fails

    • 7.14.5 Checks and measures when an object is transited to the Java heap during the explicit release processing of the Explicit memory block

    • 7.14.6 Checks and measures when the automatic release processing of the Explicit memory block takes a long time

  • 7.15 Mechanism of G1 GC

    • 7.15.1 Overview of G1 GC

    • 7.15.2 Relationship between the lifespan of an object and its age

    • 7.15.3 GC mechanism that targets the New area

    • 7.15.4 Saving objects

    • 7.15.5 Relationship between memory space and region

    • 7.15.6 How regions are used

    • 7.15.7 GC implemented by G1 GC

    • 7.15.8 Young GC

    • 7.15.9 Concurrent Marking (CM)

    • 7.15.10 Mixed GC

    • 7.15.11 Full GC

  • 7.16 G1 GC tuning

    • 7.16.1 Tuning procedure

    • 7.16.2 Initial verification

    • 7.16.3 Tuning to suppress the occurrence of Full GC

    • 7.16.4 Tuning to shorten worst-case response times

    • 7.16.5 Tuning to improve throughput

• 8. Performance Tuning (J2EE Application Execution Platform)

  • 8.1 Points to be considered for performance tuning

    • 8.1.1 Viewpoints for performance tuning

    • 8.1.2 Tuning procedure

    • 8.1.3 Items that can be tuned for each type of application

  • 8.2 Tuning Method

    • 8.2.1 Tuning of J2EE server and Web server

    • 8.2.2 Tuning of applications or resources

    • 8.2.3 Tuning of the CTM operation

    • 8.2.4 Tuning other items

  • 8.3 Optimizing the number of concurrent executions

    • 8.3.1 Concept of number of concurrent executions control and pending queue control

    • 8.3.2 Procedure for requesting the maximum number of concurrent executions and pending queue

    • 8.3.3 Controlling the number of request-processing threads

    • 8.3.4 Controlling the number of concurrent executions of a Web application

    • 8.3.5 Controlling the number of concurrently executed threads in a Enterprise Bean

    • 8.3.6 Controlling the number of concurrent executions using CTM

    • 8.3.7 Tuning parameter for optimizing the number of concurrent executions

  • 8.4 Optimizing the method of invoking the Enterprise Bean

    • 8.4.1 Using the local interface

    • 8.4.2 Using the functionality for optimizing the local invocation of the remote interface

    • 8.4.3 Using the pass by reference functionality of the remote interface

    • 8.4.4 Tuning parameters for optimizing the method of invoking the Enterprise Bean

  • 8.5 Optimizing the database access method

    • 8.5.1 Using connection pooling

    • 8.5.2 Using statement pooling

    • 8.5.3 Tuning parameters for optimizing the method of accessing the database

  • 8.6 Setting a timeout

    • 8.6.1 Points where a timeout can be set

    • 8.6.2 Setting the timeout in a Web front-end system

    • 8.6.3 Setting a timeout in the back-end system

    • 8.6.4 Setting the transaction timeout

    • 8.6.5 Setting up a timeout in DB Connector

    • 8.6.6 Setting the database timeout

    • 8.6.7 Setting the method timeout in the J2EE application

    • 8.6.8 Tuning parameters for setting the timeout

  • 8.7 Optimizing the operations of the Web application

    • 8.7.1 Separating the deployment of the static contents and the Web application

    • 8.7.2 Caching static contents

    • 8.7.3 Tuning parameters for optimizing the operations of the Web application

  • 8.8 Optimizing the operation of CTM

    • 8.8.1 Tuning the monitoring interval of the operation state of CTM domain managers and CTM daemons

    • 8.8.2 Tuning the monitoring interval of the load status

    • 8.8.3 Setting up a timeout lock for CTM daemon

    • 8.8.4 Setting up a priority order for the requests distributed with CTM

    • 8.8.5 Tuning parameters for optimizing the operation of CTM

• 9. Performance Tuning (Batch Application Execution Platform)

  • 9.1 Points to be considered for performance tuning

    • 9.1.1 Viewpoints of performance tuning

    • 9.1.2 Tuning procedure

    • 9.1.3 Tuning items

  • 9.2 Tuning procedure

    • 9.2.1 Tuning a batch server

    • 9.2.2 Tuning a resource

  • 9.3 Setting up timeouts

    • 9.3.1 Points where you can set up a timeout

    • 9.3.2 Setting up the transaction timeout

    • 9.3.3 Tuning parameters for setting up the timeout

  • 9.4 Setting the thresholds for GC control

    • 9.4.1 Purpose of setting up a threshold value

    • 9.4.2 Concept of setting up the threshold value

    • 9.4.3 Tuning parameters for setting thresholds for GC control

• Appendixes

  • A. Efficient Usage of the Explicit Heap Used in an HTTP Session

    • A.1 Considering the life span of the objects stored in an HTTP session

    • A.2 Considering the update frequency of the objects stored in an HTTP session

    • A.3 Considering the timing at which an HTTP session is created

  • B. Effect on the Explicit Memory Management Functionality Due to the Life Span of the Objects Allocated to the Explicit heap

    • B.1 Effect on the automatic release processing of the Explicit memory block

    • B.2 Effect on the memory usage of the Explicit heap

    • B.3 Relation between the reference relationship and the life span of objects allocated to the Explicit heap

  • C. Tuning Parameters for Performing the Performance Tuning with Methods other than the Recommended Procedures

    • C.1 Tuning parameter for optimizing the number of concurrent executions (methods other than the recommended procedures)

    • C.2 Tuning parameters for optimizing the method of invoking the Enterprise Bean (methods other than the recommended procedures)

    • C.3 Tuning parameters for optimizing the methods of accessing the database (methods other than the recommended procedures)

    • C.4 Tuning parameters for specifying the timeout (methods other than the recommended procedures)

    • C.5 Tuning parameters for optimizing the operations of the Web application (methods other than the recommended procedures)

    • C.6 Tuning parameters for optimizing the operation of CTM (methods other than the recommended procedures)

    • C.7 Tuning parameters for setting up the threshold value that causes full garbage collection of the batch server (methods other than the recommended procedures)

  • D. Glossary

• Index

To Page Top