Maximizing Performance and Scalability with IBM WebSphere

B

bandwidth. See bus bandwidth

Basic method

setting in Oracle Transparent Application Failover, 369

batch components and external applications

problems with using JNI on its own, 470 “471

within a WebSphere application environments, 469 “472

batch scripts

importance of compartmentalizing, 469

making thread safe in WebSphere application environments, 469

managing the operating priority of, 469

batch tier servers, 119

batch-based workloads

workload summary matrix for, 434

BEA JRocket JVM

vs. other JVMs, 289 “290

Wintel platform optimized JVM, 289 “290

Bean Managed Persistence (BMP), 27

vs. Container Managed Persistence (CMP, 415 “416

function of in J2EE database integration, 415 “416

in multiple JVM environments, 186

benchmarking and profiling. See profiling and benchmarking

Berkeley ps

example output from, 479 “480

Berkeley System Distribution (BSD), 435

BGP. See Border Gateway Protocol (BGP)

Big Brother

monitoring and alerting tool, 245

BMP. See Bean Managed Persistence (BMP)

Border Gateway Protocol (BGP)

rerouting traffic to a secondary router with, 353

smart routing protocol, 277

using to distribute traffic to multiple locations, 309

BSD. See Berkeley System Distribution (BSD)

BuffPage parameter

setting in IBM DB2, 441

building block rules

for WebSphere application environments, 155 “157

bus bandwidth

calculating performance of, 135 “136

business availability

matching with percentage availability, 38 “39

business availability index

understanding, 36 “39

understanding data redundancy, 37

understanding no redundancy, 37

understanding organization redundancy, 38

understanding people redundancy, 38

understanding system redundancy, 37

business improvements

measuring, 14 “19

business tier

avoiding overuse of Java niceties in, 403 “404

importance of avoiding stateful EJBs where possible, 404

importance of reusing EJB homes where possible, 401

importance of using constants in, 405

importance of writing local method calls for, 405 “406

performance in WebSphere applications, 400 “406

using abstraction in, 406

using a multithreaded logger instead of system.out.println(), 402

using container threading services instead of manually spawning threads in, 402 “403

using lazy initialization of objects in, 403

using Pass-by-Reference rather than Pass-by-Value, 401

Bytes Total/sec counter

for checking utilization of a Windows network interface, 495 “497