Scenario Overview
The objective of this scenario is to establish an environment in which an existing environment of WebSphere Application Server Network Deployment 6.1.0.25 with WebSphere Virtual Enterprise 6.1.1 is incorporated into a WebSphere Application Server Network Deployment V7.0.0.5 environment with WebSphere Virtual Enterprise 6.1, sharing existing hardware. The basic premise of the scenario is to install WebSphere Application Server Network Deployment Version 7.0.0.5 and Virtual Enterprise Version Version 6.1.1 on the same hardware of an existing WebSphere Application Server Network Deployment Version 6.1 and WebSphere Virtual Enterprise Version 6.1 cell, as a method of migrating applications to WebSphere Application Server Network Deployment Version 7.0 while still maintaining the existing WebSphere Application Server Network Deployment Version 6.1 cell.
Audience
This document is divided into Part 1 and Part 2. Part I gives a general overview of this scenario, environment details, and is intended for technical sales, marketing, or the interested customer who wishes to learn more about the WebSphere products and how they can coexist.
Part 2 - Advanced setup provides the more technical details of implementing the scenario and is intended for administrators of WebSphere systems who will establish the new environment and perform the migration.
Part 1
Environment details
The configuration was established to identify a series of benchmarks and points of failure within a complex environment. The environment, which had scenarios to cover coexistence, was composed of the following items:
Base Configuration
- WebSphere® Application Server Network Deployment Server Version 6.1.0.25 cluster (dynamic cluster using default ports across four nodes)
- WebSphere Virtual Enterprise 6.1.0.5 (Formerly WebSphere Extended Deployment Operations Optimization)
- A custom application
Coexisting Configuration
- WebSphere® Application Server Network Deployment Server Version 7.0.0.5 cluster (dynamic cluster using non-default ports across four nodes)
- WebSphere Virtual Enterprise 6.1.1
- Day Trader application
The environment was configured having one application (veApp1) installed into a dynamic cluster configured in the WebSphere Application Server Network Deployment Server Version 6.1 environment with WebSphere Virtual Enterprise and a second application (Day Trader) installed into a dynamic cluster configured in the WebSphere Application Server Network Deployment Server Version 7.0.0.5 environment using WebSphere Virtual Enterprise.
The test applications were profiled separately so that the Day Trader application would operate at a higher load level and as the more critical appliation higher n extended period of time. The usage pattern applied to this scenario was a situation with the following desired characteristics:
- An environment having multiple applications in which the importance and usage of one is higher than the other.
- A requirement to stage an upgrade path while retaining the existing environment.
- A requirement to leverage WebSphere Virtual Enterprise in both environments.
- The ability to maintain a complete back-level environment as a hot standby.
Implementation Diagram
The following diagram shows the relationship of the servers with regard to the physical nodes and the cells.
Application Placement Diagram
The diagram shows the relationship of the applications with regard to the physical nodes and the cells.
Validation information
The operational characteristics of the tests performed to verify the environment was as follows:
- Load driven from two JMeter controllers. One for each application.
- Each script running on the Jmeter controller had two sections, one for each on demand router.
- Load targets for the Day Trader application was 1000 virtual users for each controller with 2000 assigned to the application.
- Load targets for the veApp1 test application was at 250 virtual users for each controller with 500 assigned to the application.
- Ramp-up was set at 1000 seconds veApp1 and at 3000 for the Day Trader application
- Once the test load leveled off (fully ramped), the on demand routers operated at approximately 80% CPU utilization.
- Each Node operated at approximately 85% - 95% CPU utilization with a minimal number of valleys during the run as the load cycled through operation.
- The database server operated at approximately 30% throughout the run.
- This particual test was run for a duration of more than 12 hours at a constant high load after ramp-up completed.
- Ramp-up was approximately 25 minutes for veApp1 and 45 minutes for the Day Trader application.
Hardware Specifications
