1 / 2

Project Odyssey – Proposed Architecture Changes

Project Odyssey – Proposed Architecture Changes. Drivers for Change in Architecture. The proposal for a change in architecture is driven by the following items:. Requirement for an eAI test environment to enable performance testing prior to RMS go-live

alden-ortiz
Download Presentation

Project Odyssey – Proposed Architecture Changes

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Project Odyssey – Proposed Architecture Changes Drivers for Change in Architecture The proposal for a change in architecture is driven by the following items: • Requirement for an eAI test environment to enable performance testing prior to RMS go-live • Reduction of ongoing technical support costs by rationalising number of UNIX partitions: • - operate RMS utilising single application server • - move backup server to existing node • Reduce complexity of RMS solution by removing requirement for load balancer Architectural Changes Key Changes: (highlighted) • Merge two Application Servers into one partition, combining resources • Create a new eAI Test Partition • Implement a new HACMP cluster to maintain Application Server resilience – should the web server fail a standby server will be automatically invoked • Move backup software onto RMS TRN partition, combining resources, and destroy Backup partition

  2. Project Odyssey – Proposed Architecture Changes Key Benefits Benefits associated with the change are as follows: • No load balancing hardware required when using a single Application Server • Increased performance from single Application Server (by using a larger shared memory ‘pool’) • Reduction in ongoing maintenance costs • Dedicated environment for eAI volume testing, replicating the eAI live environment as far as possible Costs/Benefits Additional configuration work is required to implement this change in architecture, as well as some additional hardware. Costs Benefits Risk Mitigation

More Related