You should now be familiar with the following concepts:
How to create an appropriate test. Specifically, it should be a scale model of the production environment.
Which test types should be run to minimize the risk of encountering a problem in the production environment. These test types are correctness tests, performance tests, stress tests, and endurance tests.
How to generate realistic test scenarios and proper workload mixes. These should be derived from real-world users.
How to enact proper change control by restricting administrative privileges, logging administrative accesses, regularly creating backups of your configuration, keeping a log history, and documenting procedures.
When locating an error in a complex environment, it is useful to diagram the path of the request, beginning with the client all the way to the back-end.
Once an error has been located, first assume that the error is valid until it can be verified that it happened under erroneous circumstances.
When an error occurs, try to determine what, if anything, might have changed in the environment that could have contributed to the condition which promoted the error.
Try to re-create the error with the simplest test scenario, the simplest application, and the simplest environment.
WebSphere interim fixes and fix packs.
What resources are available for WebSphere support.
Working with IBM WebSphere support to resolve a WebSphere problem.