CMS RE-ENGINEERING

Client Profile

The Engineering and Construction Group of one of the world's largest providers of oil field services and has operations in more than 100 countries.

Client Situation

The client planned to re-engineer and enhance their existing system developed with a 2-tier architecture into a 3-tier, which would be scalable and reliable to withstand the heavy network traffic. They also intended to segregate their business process layer of the application into separate modules. Further the client also asked for a methodical case study of the existing systems failure on design and development and incorporate those feature limitations into the re-engineered system.

SCMC's Solution

The technical analysts’ of SCMC studied the entire working process of the system and came up with the causes for the failure of the system. It was found that the system had lots of architectural limitations.

It was found the existing system architecture didn’t fully adhered to Microsoft’s Enterprise Development Strategy, combining Internet and three-tier client/server applications. With the present limitations, both with design and implementation of the business logics it was very remote to achieve high performance and scalability.

Further the existing system used number of connections to the database from the COM and as the network traffic increased or when the users accessing the system came under concurrency (more than one user accessing the resources at the same instance of time), the existing system was unable to handle the bottleneck. Further the system maintained, “connected record sets” which were carrying the overload of active connections to the database.

SCMC came with a plan to develop and re-engineer the existing system through Microsoft Solutions Framework (MSF), adhering to “ACID” during Transaction and Microsoft's Enterprise Development Strategy, combining Internet and 3-tier client/server applications architecture. The existing system was fully re-engineered with the new design and architecture and the entire business logic was encapsulated in COM+ components and deployed in Component services / MTS so as to avail the benefits of Transaction services, Statelessness and Database connection pooling and disconnected record sets.

And it was found in the final analysis of the re-engineered system; 2,000-user using this stateless system with a think time of one minute would require (on average) fewer than 40 database connections only. As the number of clients rise into the hundreds and thousands, the newly built stateless components conserved server resources and produced maximum performance out put against a compressed database size of 14.8 GB.

• Better performance
• Scalable
• Careful usage of system resource
• Stateless system Components
• Disconnected record sets
• Optimal memory usage
• Maintainable and upgradeable