|< Day Day Up >|
The IBM WebSphere software platform is an integral component of an on demand operating environment. WebSphere software provides a robust platform to develop, run, integrate and access business applications.
The IBM WebSphere Application Server is a high-performance and extremely scalable transaction engine for dynamic e-business applications. WebSphere software enables business process and application integration within and outside the enterprise. It provides a platform to develop consistent
WebSphere continues the evolution to a single Web services-enabled, Java
2 Enterprise Edition (J2EE) application server and development environment that addresses the essential elements needed for an on demand operating environment. With WebSphere Application Server V5.0.2, WebSphere
WebSphere Application Server delivers an on demand environment with:
A build-to-integrate platform by integration-ready applications that leverage existing software assets.
Maximize ROI and lower costs with
Create a competitive advantage and optimize price/performance while meeting the changing demands of dynamic e-business with a virtualized environment featuring industry-leading reliability, scalability, performance, and security.
The DB2 UDB database is the most advanced self-managing,
Innovative manageability DB2 UDB Version 8.1 provides significant automation capabilities. Robust e-business foundation DB2 UDB Version 8.1 provides performance, scalability and availability.
It provides integrated business intelligence for customers to gain a faster Return on Investment (ROI) from their data. DB2 UDB Version 8.1 provides sophisticated Business Intelligence capabilities to easily organize information to perform faster and more insightful queries.
Application development upon DB2's leadership in
IBM DB2 software plays a critical role in the on demand operating environment infrastructure. It supports all the key e-business on demand attributes: Integrated, open, virtualized, and autonomic. Here are a few of the DB2 capabilities supporting these attributes:
DB2 UDB Version 8.1 helps solve critical business problems by integrating information across the entire enterprise by leveraging the federated Web Services and XML and support for both structured and unstructured information.
Strong commitment to support Linux, Java, XML, Web services, grid computing, multi-vendor, and multi-platform standards.
Provides a clustered scalability to support expansion of a virtualized information environment.
Self-tuning capabilities of DB2 Universal Database including self-configuring, self-optimizing, and self-managing capabilities, and rapid DB2 deployment.
|< Day Day Up >|
|< Day Day Up >|
Performance is the way a computer system behaves given a particular workload. Performance is measured in terms of system response time, throughput, and availability. Performance is also affected by the resources available in your system and how well those resources are used and shared.
In general, you tune your system to improve its cost-benefit ratio. Specific goals could include:
Processing a larger, or more demanding, work load without increasing processing costs; for example, to increase the work load without buying new hardware or using more processor time.
Obtaining faster system response times, or higher throughput, without increasing processing costs.
Reducing processing costs without degrading service to your users.
Translating performance from technical terms to economic terms is difficult. Performance tuning
A balanced system is a system that has a
Type of workload and the CPU power required for the various transactions
The maximum number of concurrently connected users
The maximum number of concurrent jobs
Number of transactions within a certain period of time
Diagnosing some problems related to memory, swap files, CPU, disk storage, and other resources requires a thorough understanding of how a given operating system
Here is some important configuration information that you need to obtain:
Operating system patch level, installed software, and upgrade history
Swap and file cache settings
User data and file resource limits and per-user process limit
Inter-Processor communication (IPC) resource limits (message queues, shared memory segments, semaphores)
By tuning application server settings, you can control how an application server provides services for running applications and their components. WebSphere Application Server contains interrelated components that must be harmoniously
The application server, being a Java process, requires a Java virtual machine (JVM) to run, and to support the Java applications running on it. As part of configuring an application server, you can fine-tune settings that enhance system use of the JVM.
One of the parts of each WebSphere Application Server is a Web container. To route servlet
One of the parts of each application server in WebSphere Application Server is an EJB container. An EJB container is automatically created when you create an application server. After the EJB container is deployed, you can change the parameters to make adjustments that improve performance.
A data source is used to access data from the database. Certain parameters reveal how the number of physical connections within a connection pool can change performance.
An Object Request Broker (ORB) manages the interaction between
IBM WebSphere Application Server session support has features for tuning session performance and operating characteristics, particularly when sessions are configured in a distributed environment. These options support the administrator flexibility in determining the performance and failover characteristics for their environment.
When a DB2 UDB instance or a database is created, a corresponding configuration file is created with default parameter values. You can modify these parameter values to improve performance.
Do not allow DB2 UDB to needlessly close and
Do not allow extended lock waits.
Manage DB2 sort memory conservatively and do not mask
Analyze table access activity and identify tables with unusually high rows read per transaction or overflow counts.
Analyze the performance characteristics of each tablespace, and seek to improve the performance of the tablespaces with the slowest read times, longest write times, highest physical I/O read rates, worst hit ratios, and access attributes that are inconsistent with expectations.
Create multiple buffer pools, and make purposeful assignments of tablespaces to buffer pools such that access attributes are shared.
Examine DB2 UDB SQL statement Event Monitor information to discover which SQL statements are consuming the largest
Reevaluate configuration and physical design settings once high-cost SQL is eliminated.
Whether the program is new or purchased, small or large, the developers, the
Who is going to use the program
Situations in which the program will be run
How often those situations will arise and at what times of the
Whether those situations will also require additional uses of existing programs
Which systems the program will run on
How much data will be handled, and from where
Whether data created by or for the program will be used in other ways
Unless these ideas are elicited as part of the design process, they will probably be vague, and the programmers will almost certainly have different assumptions than the prospective users. Even in the apparently trivial case in which the programmer is also the user, leaving the assumptions unarticulated makes it
|< Day Day Up >|