Timeline: How AXA's IT Architecture Evolved

By Julia King

February 9, 2004 12:00 PM ET

Recommended

(1)

Digg

Twitter

Share/Email

Computerworld -

Release 1, 1989-92

Architectural focus/objective: Connectivity and common data access; middleware to front-end mainframe.
Key technologies: CICS, SNA/APPC LU 6.2 and Easel Corp.'s CASE tool. Front-end PCs run OS/2. Workstations communicate directly with the mainframe.
Number of applications benefiting from code reuse: 11
Estimated cost savings: $10 million

Release 2, 1993-96

Architectural focus/objective: Client/server. Focus on data transport, messaging, security, and common customer and agent files and directories.
Key technologies: Windows replaces OS/2. TCP/IP used for data communications between workstations and servers. Server-to-mainframe communications remain on IBM's SNA.

AXA develops an enterprise customer file, an enterprise directory and an agent file. It also introduces a proprietary application security system for authentication and authorization.
Number of applications benefiting from code reuse: Five
Estimated cost savings: $8 million

Release 3, 1997-2001

Architectural focus/objective: Web and open systems.
Key technologies: CORBA, Iona Technologies Ltd.'s Orbix product. Web application server software from Sun Microsystems' NetDynamics. Also deploys Solaris and Sun ONE Directory Server, Sun ONE Portal Server and Sun Webserver. The PC browser software is Netscape. IBM's MQSeries middleware (subsequently rebranded WebSphere MQ); Candle's Roma software (now PathWAI).
Number of applications benefiting from code reuse: 14
Estimated cost savings: $37 million

Release 4, 2002-Present

Architectural focus/objective: Deploying vendor-provided, standards-based products.
Key technologies: J2EE, IBM's WebSphere MQ, Microsoft Metadirectory Services, BEA's WebLogic Server, Oblix Inc.'s NetPoint software for centralized security, Siebel's CRM applications. Also IBM's DB2-based Client Information Integration Solution to replace its proprietary customer file system.
Number of applications benefiting from code reuse: Five
Estimated cost savings: To be determined

Recommend Digg Twitter ShareThis

Email Print Send Feedback Reprints

Jump to comments

Development

Additional Resources

WHITE PAPER

Do You Know the 7 Steps to Successful Data Migration?

Approximately 60 percent of data migration projects overrun time or budget, while some fail completely. Download this white paper, "Enhancing Your Chance for Successful Data Migration," to learn the critical steps you need to take to execute a data migration project with minimum cost and risk to your business.

WHITE PAPER

Total Cost of Ownership of Server Computing Vs. PCs

Read the Gartner research note to learn why the TCO of a server-based computing deployment used to deliver all applications to users is around 50% lower than that of an unmanaged desktop deployment.

WHITE PAPER

IDC White Paper: Linux in a Global Recession

Economic downturns have a tendency to accelerate emerging technologies, boost the adoption of effective solutions, and punish solutions that are not cost competitive or that are out of synch with industry trends. This IDC White Paper presents the results of an IDC survey of 330 companies in Western Europe, Asia/Pacific and the Americas that measures the receptiveness to Linux and takes into consideration changing views driven by the disruptive economic environment that businesses face today.