Maximizing Performance and Scalability with IBM WebSphere

J

J2EE application integration. See legacy systems integration

J2EE database integration

Container Managed Persistence (CMP), 414 “415

persistence layer implementation, 414 “427

J2EE environment

Web container as component of, 59 “60

J2EE-based application

NFS as a solid data sharing technology for, 347 “350

J2EE-based application server environment

container as key component of, 371 “372

key areas that affect application performance, 27

JACs. See Java application clients (JACs)

Java

management of memory allocation and deallocation by, 158

Java 2 Enterprise Edition (J2EE) applications

the need for performance in, 1 “5

Java application clients (JACs)

effect on memory consumption, 471 “472

Java Application Clients (JACs)

failover support for in WebSphere, 306

Java components

in WebSphere business tier , 400

Java Database Connectivity (JDBC) and pooling

requests serviced by the application server, 59

Java Database Connectivity (JDBC) pool

effect on performance, 8

Java IIOP vs. RMI-IIOP, 456

Java Message Service (JMS), 27

interfacing WebSphere-based J2EE applications with, 455 “456

requests serviced by the application server, 59

Java Naming and Directory Interface (JNDI) services

requests serviced by the application server, 59

Java Native Interface (JNI)

problems with using it on its own, 470 “471

Java Server Pages (JSPs)

Web container processing of, 59 “60

Java Virtual Machine (JVM)

effect on performance, 8

Java Virtual Machine (JVM) profiler

HPjmeter from Hewlett-Packard, 511 “513

Java/J2EE environments

performance degradation caused by garbage collection in, 249 “250

Java/JVM memory and object management

management of application queues with, 27

JavaMail components

provided by WebSphere, 215

JavaMail services

requests serviced by the application server, 59

Java/Swing-based Graphical User Interface (GUI)

WebSphere version 4 managed by, 53

JBOD (Just a Basic Old Disk), 136

JCA container

function of in WebSphere 5, 75

JDBC

function of, 423 “426

JDBC Application Programming Interface (API)

support for exception messages to perform events, 359

JDBC connection pool data source

setting the Idle Timeout to tune, 448

setting the Orphan Timeout to tune, 448

JDBC connection pool manager

main areas to tune to gain performance, 444

WebSphere queue settings, 286 “287

JDBC Connection Pool Manager settings

tuning in WebSphere, 27 “28

JDBC connection pool tuning

in WebSphere 5, 449 “451

JDBC pool manager

cause of a StaleConnectionException on, 216

JDBC resources

importance of releasing when no longer needed, 407 “408

JDBC type 1 driver

as JDBC-ODBC bridge, 423 “424

JDBC type 2 drivers

implementation of, 424

JDBC type 3 drivers

implementation of, 425

JDBC type 4 driver (JDBC thin driver)

implementation of, 425 “426

JDBC URL configuration file

example of, 367

JDBC-based database interface

provided by WebSphere, 215 “216

JDBC/Container Managed Persistence (CMP), 27

Jinsight

Web site address for downloading, 516

JMS server

function of in WebSphere 5, 75 “76

JProbe profiling tool (Quest Software), 243

extended memory profiler screen example, 510

getting an application operation statistical profile with, 504 “505

memory profiler screen example, 509

plug-in support for most leading IDEs, 510

specifications, 511

using, 508 “511

Web site address for downloading, 508

JRocket JVM. See BEA JRocket JVM

<jsp: usebean ()> tag

importance of using carefully in applications, 400

JVM (Java Virtual Machine)

garbage collection monitoring, 159 “160

memory characteristics, 157 “161

multiapplication single-channel topology, 183 “190

obtaining verbose garbage collection from, 249

operating system thread to JVM thread ratio, 93

other memory issues to consider, 160 “161

rules of thumb to follow for, 159

threading characteristics, 161 “162

tuning, 287 “288

JVM environments

advantages of multiple, 188

considerations for multiple, 184 “186

disadvantages of, 189

JVM implementation vendors , 158

JVM tuning and performance options, 288 “290

JVP Performance Interface (JVMPI) requests serviced by the application server, 59