10.4 Installing and configuring Trade 6.1
This section explains how we installed and configured the IBM Trade Performance Benchmark Sample for WAS (called Trade 6.1 throughout this book) into our lab environment.
Trade 6 is the fourth generation and latest release of the WebSphere end-to-end Trade benchmark and performance sample application. The Trade benchmark was designed and developed to cover the significantly expanding programming model and performance technologies associated with WAS. This application provides a real-world workload, enabling performance research and verification test of the J2EE 1.4 implementation in WAS, including key performance components and features.
Trade 6.1 is targeted for WAS 6.1. Updates in this package include hidden support for iSeries database for a single server, modifications to the Trade source and database schema required by a change in ejbdeploy-down mapping in WAS 6.1. Long run support is now the default option and is configurable via the web.xml file. Changes to the installation and configuration jacl scripts were made to reflect the new 6.1 SIBus security function. When security is enabled, users and groups need to be explicitly granted permission to access the SIBus.
Overall, the Trade application is primarily used for performance research on a wide range of software components and platforms. Trade's design enables performance research on J2EE 1.4 including...
- The new Enterprise Java Bean 2.1 component architecture
- message-driven beans
- transactions (1-phase, 2-phase commit)
- Web services (SOAP, WSDL, JAX-RPC, enterprise Web services)
Trade 6 also drives key WAS performance components such as dynamic caching, WebSphere Edge Server, and EJB caching.
For details about how Trade 6 exploits all of these functions, refer to the document tradeTech.pdf, which can be found inside the installation package. Trade 6 demonstrates several new features in WebSphere V6.1. All Trade versions are WebSphere version-dependent, so Trade 6.1 will only work with WAS V6.
Note: The most common configurations for Trade 6.1 are single server and horizontal clustering scenarios. For our scenario, we used a single server but do not take advantage of horizontal or vertical clustering.