Maximizing Performance and Scalability with IBM WebSphere

C

cache cleanup interval

setting for the EBJ container, 383 “384

cache size

setting in the EBJ container, 383

Call-by-Reference

setting in the Application Assembly Tool (AAT), 155

Call-by-Value

calling EJBs via, 155

capacity management

basic format of this approach, 506

Carrot model

showing correct queuing configuration, 280

cell

defined, 71

vs. WebSphere 4 domain, 70

cells

reducing management overhead associated with, 72

channel

defined, 173

checklist

for database-to-WebSphere implementation, 427 “428

choke tier

in a 3-tier firewall topology, 169 “170

CISC or x86 processors

cost of vs. RISC-based processors, 97

Cisco PIX firewalls

HSRP capabilities supported by, 353

ClawHammer. See AMD AthIon 64 (ClawHammer)

client tier API

in JDBC type 3 driver implementation, 425

CloneID directive

use of in WebSphere 4 and 5 plug-in files, 313

clones

function of in WebSphere 4, 66 “68

vs. server groups, 66 “67

cloning

extending load-balancing capability of WebSphere with, 67 “68

and workload management flowchart in WebSphere 4, 68

closed queuing model

function of, 279

cluster. See WebSphere cluster environment

ClusterAddress directive

code example showing use of, 321

forcing requests to an external load balancer with, 320 “322

clustered active-standby configuration example of, 221 “222

clustering

to achieve performance improvement, 293 “299

clustering systems

using other active-standby or IP takeover, 369 “370

clusterware

use of in active-standby databases, 220 “222

using to cluster components , 294 “295

clusterware solutions

well-known and WebSphere supported, 294 “295

CMP. See Container Managed Persistence (CMP)

code example

for declaring the ConnectTimeout setting and value, 322 “323

for handling database errors in application code, 361

of HTTP plug-in configuration file, 55 “56

for implementing MQ asynchronous transactions, 460 “461

of a JDBC URL configuration file, 367

for mapping WebSphere 4 dual instance Web container configuration, 314 “315

for mapping WebSphere 5 dual instance Web container configuration, 315 “316

of Oracle TNS names configuration file for Transparent Application Failover, 368

of Oracle TNS names configuration file for server failover, 366

for referencing an external or non-standard data type, 466

of server cluster directive, 314

of server group directive, 314

showing proper object closure in databases, 420 “421

showing use of ClusterAddress directive, 321

of WebSphere 4 HTTP plug-in configuration file, 311 “312

WebSphere 4 key CloneID changes, 316

of WebSphere 5 HTTP plug-in configuration file, 312

WebSphere 5 key CloneID changes, 316 “317

cold disaster recovery sites

typical configuration and function of, 301

COMM_FAILURE message, 339

Compaq/HP TruCluster

clustering solution, 295

comparison chart (CPU)

x86/IA-64/x86-64 platform (Intel and AMD), 90 “91

COMPLETE_STATUS message, 339

Complex Instruction Set Computing (CISC)-based processors vs. RISC-based UltraSPARC processors, 96

component architecture

WebSphere 4 and 5, 51 “79

component modeling

in multiple JVM environments, 185

components

reasons for splitting into their own tiers, 194 “195

concurrent and registered users

effect of on response times, 236

configuration and tuning parameters

for Oracle systems, 437 “438

configuration repository

function of in WebSphere 5, 77

configuration settings

use of administrative repository for in WebSphere 4, 68 “69

conn.close() command

closing the JDBC database connection with, 421

connection pool manager. See also WebSphere connection pool manager

provided by WebSphere, 215 “217

connection pool managers

closing connections in WebSphere applications with, 362

Connection Timeout

setting in WebSphere 4 and 5, 446 “447

Connection Timeout setting

in JDBC connection pool manager, 444

ConnectTime

setting in WebSphere 5, 332 “333

ConnectTimeout setting

in WebSphere 5, 322 “323

ConnectTimeout setting and value

code example for declaring, 322 “323

Container Managed Persistence (CMP)

in J2EE database integration, 414 “415

in multiple JVM environments, 186

Container Managed Persistence (CMP) vs. Bean Managed Persistence (BMP), 415 “416

container threading services

using instead of manually spawning threads, 402 “403

container-managed persistence (CMP)

using only for high-read database access, 408

containers

the EJB container, 374 “377

high-level application server framework view, 372

an overview, 371 “372

within WebSphere, 372

what they do, 373 “377

context switches

in vmstat output, 477

cookies

popular means of session management in WebSphere, 327 “328

CORBA

example implementation within a WebSphere platform, 457

example transaction with WebSphere, 458

having all components with a shared application server, 459 “460

key communications status messages, 338 “340

CORBA integration

platform and language independency of, 456

CORBA Object Request Broker (ORB) services

requests serviced by the application server, 59

CORBA.INTERNAL exception, 340

cost comparisons

for optimization vs. upgrade for pilot application, 17

cost impact factors

that help determine downtime costs, 45

CPU and overall server load

measuring in Windows, 481 “484

CPU and server comparison matrix

for selecting model for your needs, 104

CPU and system load

key load and performance identifiers in Unix, 475 “481

CPU comparison chart

x86/IA-64/x86-64 platform (Intel and AMD), 90 “91

CPUs

determining best for your needs, 105 “108

for development and desktop needs, 92 “93

for server and high-end server needs, 93

CPUs and servers

best for medium production environments, 106 “107

best for small production environments, 105 “106

Curl

command line tool for probing Internet services, 245

Curl/Perl/Lynx

software for custom building stress and volume testing suites, 246

customer administration application

in a single-channel 3-tier topology, 178 “180

Категории