20
Copyright 2001 Perot Systems Europe. All rights reserved Web Architecture considerations Tim Taylor August 2000

Copyright 2001 Perot Systems Europe. All rights reserved Web Architecture considerations Tim Taylor August 2000

Embed Size (px)

Citation preview

Page 1: Copyright 2001 Perot Systems Europe. All rights reserved Web Architecture considerations Tim Taylor August 2000

Copyright 2001 Perot Systems Europe. All rights reserved

Web Architecture considerations

Tim Taylor

August 2000

Page 2: Copyright 2001 Perot Systems Europe. All rights reserved Web Architecture considerations Tim Taylor August 2000

Copyright 2001 Perot Systems Europe. All rights reserved 2

Agenda

Assumptions

Approach– dealing with uncertainty– service architecture– why use services?

Possible standards

“Straw Man” architecture

Issues

Next Steps

Page 3: Copyright 2001 Perot Systems Europe. All rights reserved Web Architecture considerations Tim Taylor August 2000

Copyright 2001 Perot Systems Europe. All rights reserved 3

Major Assumptions

There will be 3 main areas to be supported by the web architecture– “Intranet” provision of information to employees / co-workers– Extranet bi directional exchange of information with External Service

Provider’s (ESP’s)– E-business full integration with selected partners systems, including

financial transactions, eg: e-procurement

Systems architecture requiring integration

*Head Office Data Centre

SAP

*Head Office Data Centre

SAP Sales & Distribution

Head Offic ...

SAP BPP

*Head Offi ...

SAP Finance

Head ...

SAP HR

*Head Offi ...

SAPMaterials

*Head Offi ...

SAPProjects

*Head Offi ...

SAP ServiceManagement

Head Office Data Centre

CLASS

Customer Inventory

Head Office Data ...

Asset RepositoryAssets

UK Hea ...

COSH

Hazardous materials

HSE

Annual HSE report

UK Head Office

List Management

Supplier

Electronic Bill Presentment & Payment

CC OPS CallCentre

Outbound calling listsCall events

Head Office Data Centre

Mainframe Financials

Customer Inventory

ReconciliationAssets

Head Office Data Centre

www Sell Side Application

Orders

Order Status

Service issuesManual Order Entry

Head Office Data Centre

Customer Data Warehouse

Data Provider

Head Office Da ...

CampaignManagement

Web events

Campaign business rules

Head Office Da ...

MIS

*Head Offi ...

SAPReporting Head Office Da ...

GIS

Spatial data

*Region ...

End UserReporting

Manual report extracts

Manual report extracts

Head Office Da ...

Standard ETL

Aggregated customer data

Finance transactions

Customer credit

Head Office Data Centre

Custom ETL

Service calls

Finance transactions

External Data

Page 4: Copyright 2001 Perot Systems Europe. All rights reserved Web Architecture considerations Tim Taylor August 2000

Copyright 2001 Perot Systems Europe. All rights reserved 4

Approach - dealing with uncertainty

The current lack of clear business direction leads to some fundamental requirements for any proposed architecture, ie: it must be– scalable, able to support growth in a controlled manner, without extensive

reworking– flexible, able to support a variety of business models– adaptable, capable of including new functions without major rework

To achieve these objectives, an architecture based on Services is proposed– separating the elements of architecture and defining the communications required

between them

To reduce the risk of costly errors, implementation should start small– prove the architecture– expand delivery on to a proven platform

Page 5: Copyright 2001 Perot Systems Europe. All rights reserved Web Architecture considerations Tim Taylor August 2000

Copyright 2001 Perot Systems Europe. All rights reserved 5

Approach - service architecture

serv System

serv Presentation

serv Business Logic

serv Communication

serv Data Management

“Can I change my dd payment amount?”

“Can I change my dd payment amount?”

“Sorry, Mr anon, but your current balance of £nn does not allow this”

“Sorry, Mr anon, but your current balance of £nn does not allow this”

Dd payment must not be < curbal/12

Dd payment must not be < curbal/12

select dd payment & curbal where cust = anon

select dd payment & curbal where cust = anon

Logon.Logon.

Receipt of incoming requests from clients. Dispatch of requests for external processes.

Output of formatted information for presentation on client (for browser services likely to be HTML).

Application of business rules to data, eg: MIS, Workflow.

Management of interactions with back end data sources

System management and security.

A service is a component of the architecture which you ask a question of, and get a predictable response.

They have always been present in systems.

A service architecture just makes them explicit, and classifies them according to their function.

A service is a component of the architecture which you ask a question of, and get a predictable response.

They have always been present in systems.

A service architecture just makes them explicit, and classifies them according to their function.

*Head Office Data Centre

SAP

*Head Office Data Centre

SAP Sales & Distribution

Head Offic ...

SAP BPP

*Head Offi ...

SAP Finance

Head ...

SAP HR

*Head Offi ...

SAPMaterials

*Head Offi ...

SAPProjects

*Head Offi ...

SAP ServiceManagement

Head Office Data Centre

CLASS

Cus tomer Inventory

Head Office Data ...

Asse t RepositoryAssets

UK Hea ...

COSH

Hazardous materials

HSE

Annual HSE report

UK Head Office

List Management

Supplier

Electronic Bill Presentment & Payment

CC OPS CallCentre

Outbound calling listsCall events

Head Office Data Centre

Mainframe Financials

Cus tomer Inventory

ReconciliationAssets

Head Office Data Centre

www Sell Side Application

Orders

Order Status

Service issuesManual Order Entry

Head Office Data Centre

Customer Data Warehouse

Data Provider

Head Office Da ...

CampaignManagement

W eb events

Campaign business rules

Head Office Da ...

MIS

*Head Offi ...

SAPReporting Head Office Da ...

GIS

Spatial data

*Region ...

End UserReporting

Manual report extracts

Manual report extracts

Head Office Da ...

Standard ETL

Aggregated customer data

Finance transactions

Customer credit

Head Office Data Centre

Custom ETL

Service calls

Finance transactions

External Data

Page 6: Copyright 2001 Perot Systems Europe. All rights reserved Web Architecture considerations Tim Taylor August 2000

Copyright 2001 Perot Systems Europe. All rights reserved 6

Approach - why use services?

serv System

serv Presentation

serv Business Logic

serv Communication

serv Data Management

Ap

plica

tion

A

Ap

plica

tion

B

There may be some scope for reuse, eg: of databases, but this is often not maximised

There may be some scope for reuse, eg: of databases, but this is often not maximised

Integration and communication between systems is often only achievable at the data level

Integration and communication between systems is often only achievable at the data level

Clie

nt

Se

rver

Ma

infra

me

Traditional project specific architecture would implement most of these elements independently, many times.

Traditional project specific architecture would implement most of these elements independently, many times. Changes to one

component requires changes to others

Changes to one component requires changes to others

Hardware is dedicated to end to end processing for systems

Hardware is dedicated to end to end processing for systems

Page 7: Copyright 2001 Perot Systems Europe. All rights reserved Web Architecture considerations Tim Taylor August 2000

Copyright 2001 Perot Systems Europe. All rights reserved 7

Approach - why use services?

serv System

serv Presentation

serv Business Logic

serv Communication

serv Data Management

Application Server

App A App B

Data Server

Helps ensure that as many elements of the architecture as possible can be reused

Helps ensure that as many elements of the architecture as possible can be reused

Integration and communication between systems can be achieved where most appropriate

Integration and communication between systems can be achieved where most appropriate

Data can be reused by many applications

Data can be reused by many applications

If done properly, otherwise - CHAOS!If done properly, otherwise - CHAOS!

Changes to one component do not require changes to others

Changes to one component do not require changes to others

Web serverHardware can be optimised for specific tasks for multiple applications

Hardware can be optimised for specific tasks for multiple applications

*Head Office Data Centre

SAP

*Head Office Data Centre

SAP Sales & Distribution

Head Offic ...

SAP BPP

*Head Offi ...

SAP Finance

Head ...

SAP HR

*Head Offi ...

SAPMaterials

*Head Offi ...

SAPProjects

*Head Offi ...

SAP ServiceManagement

Head Office Data Centre

CLASS

Cus tomer Inventory

Head Office Data ...

Asse t RepositoryAssets

UK Hea ...

COSH

Hazardous materials

HSE

Annual HSE report

UK Head Office

List Management

Supplier

Electronic Bill Presentment & Payment

CC OPS CallCentre

Outbound calling listsCall events

Head Office Data Centre

Mainframe Financials

Cus tomer Inventory

ReconciliationAssets

Head Office Data Centre

www Sell Side Application

Orders

Order Status

Service issuesManual Order Entry

Head Office Data Centre

Customer Data Warehouse

Data Provider

Head Office Da ...

CampaignManagement

W eb events

Campaign business rules

Head Office Da ...

MIS

*Head Offi ...

SAPReporting Head Office Da ...

GIS

Spatial data

*Region ...

End UserReporting

Manual report extracts

Manual report extracts

Head Office Da ...

Standard ETL

Aggregated customer data

Finance transactions

Customer credit

Head Office Data Centre

Custom ETL

Service calls

Finance transactions

External Data

Page 8: Copyright 2001 Perot Systems Europe. All rights reserved Web Architecture considerations Tim Taylor August 2000

Copyright 2001 Perot Systems Europe. All rights reserved 8

PRIORITY• User groups• Security requirements

CONSIDERATIONS• Shared services• ESP / EDI standards

PRIORITY• User groups• Security requirements

CONSIDERATIONS• Shared services• ESP / EDI standards

serv System

serv Presentation

serv Business Logic

serv Communication

serv Data Management

Possible standards - Communication services

Networking Services– Network Protocols – TCP/IP, IPX/SPX, NetBEUI– Routing Protocols – ARP, ASs, BGP-4, EIGRP, ICMP– Network Topology – Star, Bus, Ring– Addressing– Router Topology– Network Utilisation

Directory Services (LDAP, X500)– Databases– Partitioning– Replication– Caching– Access Control– Organisation and data relationships

*Head Office Data Centre

SAP

*Head Office Data Centre

SAP Sales & Distribution

Head Offic ...

SAP BPP

*Head Offi ...

SAP Finance

Head ...

SAP HR

*Head Offi ...

SAPMaterials

*Head Offi ...

SAPProjects

*Head Offi ...

SAP ServiceManagement

Head Office Data Centre

CLASS

Customer Inventory

Head Office Data ...

Asset RepositoryAssets

UK Hea ...

COSH

Hazardous materials

HSE

Annual HSE report

UK Head Office

List Management

Supplier

Electronic Bill Presentment & Payment

CC OPS CallCentre

Outbound calling listsCall events

Head Office Data Centre

Mainframe Financials

Customer Inventory

ReconciliationAssets

Head Office Data Centre

www Sell Side Application

Orders

Order Status

Service issuesManual Order Entry

Head Office Data Centre

Customer Data Warehouse

Data Provider

Head Office Da ...

CampaignManagement

Web events

Campaign business rules

Head Office Da ...

MIS

*Head Offi ...

SAPReporting Head Office Da ...

GIS

Spatial data

*Region ...

End UserReporting

Manual report extracts

Manual report extracts

Head Office Da ...

Standard ETL

Aggregated customer data

Finance transactions

Customer credit

Head Office Data Centre

Custom ETL

Service calls

Finance transactions

External Data

Page 9: Copyright 2001 Perot Systems Europe. All rights reserved Web Architecture considerations Tim Taylor August 2000

Copyright 2001 Perot Systems Europe. All rights reserved 9

• “Style guide”• not a major priority?

• “Style guide”• not a major priority?

serv System

serv Presentation

serv Business Logic

serv Communication

serv Data Management

Possible standards - Presentation services

User Interface Design– Consistent User Interface– Human-Computer Interface Standards– Ease of Use

*Head Office Data Centre

SAP

*Head Office Data Centre

SAP Sales & Distribution

Head Offic ...

SAP BPP

*Head Offi ...

SAP Finance

Head ...

SAP HR

*Head Offi ...

SAPMaterials

*Head Offi ...

SAPProjects

*Head Offi ...

SAP ServiceManagement

Head Office Data Centre

CLASS

Customer Inventory

Head Office Data ...

Asset RepositoryAssets

UK Hea ...

COSH

Hazardous materials

HSE

Annual HSE report

UK Head Office

List Management

Supplier

Electronic Bill Presentment & Payment

CC OPS CallCentre

Outbound calling listsCall events

Head Office Data Centre

Mainframe Financials

Customer Inventory

ReconciliationAssets

Head Office Data Centre

www Sell Side Application

Orders

Order Status

Service issuesManual Order Entry

Head Office Data Centre

Customer Data Warehouse

Data Provider

Head Office Da ...

CampaignManagement

Web events

Campaign business rules

Head Office Da ...

MIS

*Head Offi ...

SAPReporting Head Office Da ...

GIS

Spatial data

*Region ...

End UserReporting

Manual report extracts

Manual report extracts

Head Office Da ...

Standard ETL

Aggregated customer data

Finance transactions

Customer credit

Head Office Data Centre

Custom ETL

Service calls

Finance transactions

External Data

Page 10: Copyright 2001 Perot Systems Europe. All rights reserved Web Architecture considerations Tim Taylor August 2000

Copyright 2001 Perot Systems Europe. All rights reserved 10

PRIORITY• Toolsets• Languages• Hardware

CONSIDERATIONS• Existing projects• Pilots• Skillsets

PRIORITY• Toolsets• Languages• Hardware

CONSIDERATIONS• Existing projects• Pilots• Skillsets

serv System

serv Presentation

serv Business Logic

serv Communication

serv Data Management

Possible standards - Business Logic services Application Programming Interfaces (API) and

Development Platform Services– Programming Languages – C/C++, Java– Development Tools & Strategies– Frameworks & Reusability– Threads– Inter-Process Communication– Internationalisation

GroupWare Services– E-mail Service– Fax Service– Web Servers

Transaction Services– Transaction Monitoring– Object Technology– Rollover and Rollback– Transactional Roles– ACID– Resource Manager– Transaction Manager

*Head Office Data Centre

SAP

*Head Office Data Centre

SAP Sales & Distribution

Head Offic ...

SAP BPP

*Head Offi ...

SAP Finance

Head ...

SAP HR

*Head Offi ...

SAPMaterials

*Head Offi ...

SAPProjects

*Head Offi ...

SAP ServiceManagement

Head Office Data Centre

CLASS

Customer Inventory

Head Office Data ...

Asset RepositoryAssets

UK Hea ...

COSH

Hazardous materials

HSE

Annual HSE report

UK Head Office

List Management

Supplier

Electronic Bill Presentment & Payment

CC OPS CallCentre

Outbound calling listsCall events

Head Office Data Centre

Mainframe Financials

Customer Inventory

ReconciliationAssets

Head Office Data Centre

www Sell Side Application

Orders

Order Status

Service issuesManual Order Entry

Head Office Data Centre

Customer Data Warehouse

Data Provider

Head Office Da ...

CampaignManagement

Web events

Campaign business rules

Head Office Da ...

MIS

*Head Offi ...

SAPReporting Head Office Da ...

GIS

Spatial data

*Region ...

End UserReporting

Manual report extracts

Manual report extracts

Head Office Da ...

Standard ETL

Aggregated customer data

Finance transactions

Customer credit

Head Office Data Centre

Custom ETL

Service calls

Finance transactions

External Data

Page 11: Copyright 2001 Perot Systems Europe. All rights reserved Web Architecture considerations Tim Taylor August 2000

Copyright 2001 Perot Systems Europe. All rights reserved 11

PRIORITY• Information

Architecture

CONSIDERATIONS• Current data

architecture• Existing projects• Pilots• Skillsets

PRIORITY• Information

Architecture

CONSIDERATIONS• Current data

architecture• Existing projects• Pilots• Skillsets

serv System

serv Presentation

serv Business Logic

serv Communication

serv Data Management

Possible standards - Data Management services Database Services

– Data Model– Database Engine– Database Model - Relational, Object-Oriented, etc– Connectivity Interfaces

Online Storage Devices and Services– FDDI– Hardware/Software RAID– Storage Area Networks

Offline Backup Storage Devices and Services– Tape Backup– Automated Scheduling Software

Integration with Legacy Systems– Mainframe/Mini Hardware`– Networking/Communication– Transaction Systems (CICS, VSAM, etc)– Database Systems– Legacy Applications– Emulation

*Head Office Data Centre

SAP

*Head Office Data Centre

SAP Sales & Distribution

Head Offic ...

SAP BPP

*Head Offi ...

SAP Finance

Head ...

SAP HR

*Head Offi ...

SAPMaterials

*Head Offi ...

SAPProjects

*Head Offi ...

SAP ServiceManagement

Head Office Data Centre

CLASS

Customer Inventory

Head Office Data ...

Asset RepositoryAssets

UK Hea ...

COSH

Hazardous materials

HSE

Annual HSE report

UK Head Office

List Management

Supplier

Electronic Bill Presentment & Payment

CC OPS CallCentre

Outbound calling listsCall events

Head Office Data Centre

Mainframe Financials

Customer Inventory

ReconciliationAssets

Head Office Data Centre

www Sell Side Application

Orders

Order Status

Service issuesManual Order Entry

Head Office Data Centre

Customer Data Warehouse

Data Provider

Head Office Da ...

CampaignManagement

Web events

Campaign business rules

Head Office Da ...

MIS

*Head Offi ...

SAPReporting Head Office Da ...

GIS

Spatial data

*Region ...

End UserReporting

Manual report extracts

Manual report extracts

Head Office Da ...

Standard ETL

Aggregated customer data

Finance transactions

Customer credit

Head Office Data Centre

Custom ETL

Service calls

Finance transactions

External Data

Page 12: Copyright 2001 Perot Systems Europe. All rights reserved Web Architecture considerations Tim Taylor August 2000

Copyright 2001 Perot Systems Europe. All rights reserved 12

PRIORITY• Security services• Firewall• Middleware• Basic systems

management

CONSIDERATIONS• Current systems• Existing projects• Shared services

PRIORITY• Security services• Firewall• Middleware• Basic systems

management

CONSIDERATIONS• Current systems• Existing projects• Shared services

serv System

serv Presentation

serv Business Logic

serv Communication

serv Data Management

Possible standards - System services Security Services

– Manageability versus strength– Inside versus outside the firewall– Cryptography – Public Key Cryptography, Digital Certs– Communications – SSL– Authentication - Kerberos

Environment, Distributed Objects, Component Models– Concepts - Components, Objected Oriented– Object Middleware - COM/DCOM, CORBA, EJB– Operating Systems - Windows, UNIX, Linux, Solaris– Web Server– Performance - Local, Network, Load Balancing, Clustering– Robustness , Resilience, Scalability– Failover & Recovery, Disaster Recovery

Management and Maintenance Services– Remote Management Services, Fault Alerts– Self Healing Mechanisms– Asset Management, Configuration Management

Device Sharing Services and Integration– Integration with external devices

*Head Office Data Centre

SAP

*Head Office Data Centre

SAP Sales & Distribution

Head Offic ...

SAP BPP

*Head Offi ...

SAP Finance

Head ...

SAP HR

*Head Offi ...

SAPMaterials

*Head Offi ...

SAPProjects

*Head Offi ...

SAP ServiceManagement

Head Office Data Centre

CLASS

Customer Inventory

Head Office Data ...

Asset RepositoryAssets

UK Hea ...

COSH

Hazardous materials

HSE

Annual HSE report

UK Head Office

List Management

Supplier

Electronic Bill Presentment & Payment

CC OPS CallCentre

Outbound calling listsCall events

Head Office Data Centre

Mainframe Financials

Customer Inventory

ReconciliationAssets

Head Office Data Centre

www Sell Side Application

Orders

Order Status

Service issuesManual Order Entry

Head Office Data Centre

Customer Data Warehouse

Data Provider

Head Office Da ...

CampaignManagement

Web events

Campaign business rules

Head Office Da ...

MIS

*Head Offi ...

SAPReporting Head Office Da ...

GIS

Spatial data

*Region ...

End UserReporting

Manual report extracts

Manual report extracts

Head Office Da ...

Standard ETL

Aggregated customer data

Finance transactions

Customer credit

Head Office Data Centre

Custom ETL

Service calls

Finance transactions

External Data

Page 13: Copyright 2001 Perot Systems Europe. All rights reserved Web Architecture considerations Tim Taylor August 2000

Copyright 2001 Perot Systems Europe. All rights reserved 13

Straw Man architecture - initial configuration

serv System

serv Presentation

serv Business Logic

serv Communication

serv Data Management

Web Server

Application & data Server

Hardware

Components• 1 x Web Server• 1 x app/db server• Cost: £5k - £10k

Options• SUN• HP• IBM

Hardware

Components• 1 x Web Server• 1 x app/db server• Cost: £5k - £10k

Options• SUN• HP• IBM

Software

Components• development toolkit• Cost: £5k-10k

Options• integrated, eg:

Oracle Internet Application Server (IAS)

• Components, eg: WebLogic, iPlanet Application Server, and WebSphere 3.5

Software

Components• development toolkit• Cost: £5k-10k

Options• integrated, eg:

Oracle Internet Application Server (IAS)

• Components, eg: WebLogic, iPlanet Application Server, and WebSphere 3.5

Total Cost: approx £10k - £20kTotal Cost: approx £10k - £20k *Head Office Data Centre

SAP

*Head Office Data Centre

SAP Sales & Distribution

Head Offic ...

SAP BPP

*Head Offi ...

SAP Finance

Head ...

SAP HR

*Head Offi ...

SAPMaterials

*Head Offi ...

SAPProjects

*Head Offi ...

SAP ServiceManagement

Head Office Data Centre

CLASS

Customer Inventory

Head Office Data ...

Asse t RepositoryAssets

UK Hea ...

COSH

Hazardous materials

HSE

Annual HSE report

UK Head Office

List Management

Supplier

Electronic Bill Presentment & Payment

CC OPS CallCentre

Outbound calling listsCall events

Head Office Data Centre

Mainframe Financials

Customer Inventory

ReconciliationAssets

Head Office Data Centre

www Sell Side Application

Orders

Order Status

Service issuesManual Order Entry

Head Office Data Centre

Customer Data Warehouse

Data Provider

Head Office Da ...

CampaignManagement

W eb events

Campaign business rules

Head Office Da ...

MIS

*Head Offi ...

SAPReporting Head Office Da ...

GIS

Spatial data

*Region ...

End UserReporting

Manual report extracts

Manual report extracts

Head Office Da ...

Standard ETL

Aggregated customer data

Finance transactions

Customer credit

Head Office Data Centre

Custom ETL

Service calls

Finance transactions

External Data

Page 14: Copyright 2001 Perot Systems Europe. All rights reserved Web Architecture considerations Tim Taylor August 2000

Copyright 2001 Perot Systems Europe. All rights reserved 14

Straw Man architecture - mid size

serv System

serv Presentation

serv Business Logic

serv Communication

serv Data Management

Web Server

Application & data Server

Hardware

Components• approx. £20k per

processor required• 1 x Web Server (1)• 1 x app/db server (2)• Cost: £50k - £100k

Options• SUN• HP• IBM

Hardware

Components• approx. £20k per

processor required• 1 x Web Server (1)• 1 x app/db server (2)• Cost: £50k - £100k

Options• SUN• HP• IBM

Software

Components• development toolkit• system management

tools• middleware• Cost: £25k-50k

Options• integrated, eg:

Oracle Internet Application Server (IAS)

• Components, eg: WebLogic, iPlanet Application Server, and WebSphere 3.5

Software

Components• development toolkit• system management

tools• middleware• Cost: £25k-50k

Options• integrated, eg:

Oracle Internet Application Server (IAS)

• Components, eg: WebLogic, iPlanet Application Server, and WebSphere 3.5

Total Cost: approx £75k - £150kTotal Cost: approx £75k - £150k *Head Office Data Centre

SAP

*Head Office Data Centre

SAP Sales & Distribution

Head Offic ...

SAP BPP

*Head Offi ...

SAP Finance

Head ...

SAP HR

*Head Offi ...

SAPMaterials

*Head Offi ...

SAPProjects

*Head Offi ...

SAP ServiceManagement

Head Office Data Centre

CLASS

Customer Inventory

Head Office Data ...

Asse t RepositoryAssets

UK Hea ...

COSH

Hazardous materials

HSE

Annual HSE report

UK Head Office

List Management

Supplier

Electronic Bill Presentment & Payment

CC OPS CallCentre

Outbound calling listsCall events

Head Office Data Centre

Mainframe Financials

Customer Inventory

ReconciliationAssets

Head Office Data Centre

www Sell Side Application

Orders

Order Status

Service issuesManual Order Entry

Head Office Data Centre

Customer Data Warehouse

Data Provider

Head Office Da ...

CampaignManagement

W eb events

Campaign business rules

Head Office Da ...

MIS

*Head Offi ...

SAPReporting Head Office Da ...

GIS

Spatial data

*Region ...

End UserReporting

Manual report extracts

Manual report extracts

Head Office Da ...

Standard ETL

Aggregated customer data

Finance transactions

Customer credit

Head Office Data Centre

Custom ETL

Service calls

Finance transactions

External Data

Page 15: Copyright 2001 Perot Systems Europe. All rights reserved Web Architecture considerations Tim Taylor August 2000

Copyright 2001 Perot Systems Europe. All rights reserved 15

Straw Man architecture - ‘full strength’

serv System

serv Presentation

serv Business Logic

serv Communication

serv Data Management

Web Server

Hardware

Components• approx. £20k per

processor required • n x Web Server• n x app server• n x db server• Cost: £100k - £200kOptions• SUN• HP• IBM

Hardware

Components• approx. £20k per

processor required • n x Web Server• n x app server• n x db server• Cost: £100k - £200kOptions• SUN• HP• IBM

Software

Components• development toolkit• system management

tools• middleware• Cost: £50k-100k

Options• integrated, eg:

Oracle Internet Application Server (IAS)

• Components, eg: WebLogic, iPlanet Application Server, and WebSphere 3.5

Software

Components• development toolkit• system management

tools• middleware• Cost: £50k-100k

Options• integrated, eg:

Oracle Internet Application Server (IAS)

• Components, eg: WebLogic, iPlanet Application Server, and WebSphere 3.5

Typical Cost: approx £150k - £300kTypical Cost: approx £150k - £300k

Application Server

Data Server

*Head Office Data Centre

SAP

*Head Office Data Centre

SAP Sales & Distribution

Head Offic ...

SAP BPP

*Head Offi ...

SAP Finance

Head ...

SAP HR

*Head Offi ...

SAPMaterials

*Head Offi ...

SAPProjects

*Head Offi ...

SAP ServiceManagement

Head Office Data Centre

CLASS

Customer Inventory

Head Office Data ...

Asse t RepositoryAssets

UK Hea ...

COSH

Hazardous materials

HSE

Annual HSE report

UK Head Office

List Management

Supplier

Electronic Bill Presentment & Payment

CC OPS CallCentre

Outbound calling listsCall events

Head Office Data Centre

Mainframe Financials

Customer Inventory

ReconciliationAssets

Head Office Data Centre

www Sell Side Application

Orders

Order Status

Service issuesManual Order Entry

Head Office Data Centre

Customer Data Warehouse

Data Provider

Head Office Da ...

CampaignManagement

W eb events

Campaign business rules

Head Office Da ...

MIS

*Head Offi ...

SAPReporting Head Office Da ...

GIS

Spatial data

*Region ...

End UserReporting

Manual report extracts

Manual report extracts

Head Office Da ...

Standard ETL

Aggregated customer data

Finance transactions

Customer credit

Head Office Data Centre

Custom ETL

Service calls

Finance transactions

External Data

Page 16: Copyright 2001 Perot Systems Europe. All rights reserved Web Architecture considerations Tim Taylor August 2000

Copyright 2001 Perot Systems Europe. All rights reserved 16

Example of a ‘full-strength’ architecture

Sun Enterprise 450

OS: Sun OS 2.5Processors: 1M em : 1GBDisk: 9.1GB

100 Base/T

UNIXProcessors: 8M em : 16GBDisk: 20GB x 3 (RAID)

UNIXProcessors: 8M em : 16GBDisk: 20GB x 3 (RAID)

Application ServersOracle Application

Server 4.0.8

MonitoringTivoli

IBM W orkgroup Server43P M odel 260

OS: IBM AIX 4.3Processors: 1M em : 512M BDisk:9.1GB x 2

GDS Servers

UNIXProcessors: 8M em : 16 GBDisk: 20GB x 3 (RAID)

UNIXProcessors: 8M em : 16GBDisk: 20GB x 3 (RAID)

Database ServersOracle 8.x

W indows NT 4.0Processor: 4M em : 2GBDisk: 9.1GB

Backup ServerVeritas Netback 3.2

W indows NT 4.0Processors: 8M em : 4GBDisk: 20GB x 3 (RAID)

DNS/Web ServerNetscape (iPlanet)

Web Server 4.0Enterprise Edition

Cisco 4700MDistributed Director

Site Load Balancing

W indows NT 4.0Processors: 8M em : 2GBDisk:9.1GB

FirewallCheckPoint Firewall

CiscoLocal Director

Tape S ilo

Example of Web-Based Hotel Central Reservation & PropertyManagement System

Central - Network Architecture

OS:Processors:M em :Disk:

Payment Server

UNIXProcessors: 8M em : 16GBDisk: 20GB x 3 (RAID)

ReplicationDatabase Server

Oracle 8.x

W indows NT 4.0Processors: 8M em : 1GBDisk: 20GB x 3 (RAID)

Fax/E-mail ServerMicrosoft ExchangeServer 5.5 with Fax

Connector

GuestConnection via

Internet

NetBackup Client (3.1.1)

Page 17: Copyright 2001 Perot Systems Europe. All rights reserved Web Architecture considerations Tim Taylor August 2000

Copyright 2001 Perot Systems Europe. All rights reserved 17

Issues

Complexity of web architecture - if poorly implemented will make the current situation look like a picnic!– multiple components– complex interactions– process driven– open to outside scrutiny

Needs to be integrated with other architectures– information (what data is being used)– functional (which business functions are being transacted)– business (needs to be process driven)

Relationship with other initiatives and architecture

Hosting / ASP

Uncertain business model (plans, priorities etc)

Business ownership and buy in

Page 18: Copyright 2001 Perot Systems Europe. All rights reserved Web Architecture considerations Tim Taylor August 2000

Copyright 2001 Perot Systems Europe. All rights reserved 18

Next Steps - framework

11 LearningLearning Gaining understanding of the e-business marketplace

22 PlanningPlanning Determining your e-commerce strategy

33 SystemSystem Evaluating your current system software

44 NetworkNetwork Evaluating your internal and external network infrastructure

55 SecuritySecurity Adding security to your web site, intranet and extranet

66 PaymentPayment How you will be paid, and how you will pay suppliers

77 BuyingBuying Purchasing from suppliers over the internet

88 SupplierSupplier Linking into a centralised suppliers catalogue for purchasing

99 LogisticsLogistics Using the internet to manage stock levels and deliver goods

1010 SellingSelling Creation of selling and affiliation tools for your web site

1111 CustomerCustomer Creating a community of customers through your web site

1212 PersonalisationPersonalisation Creating electronic relationships

Page 19: Copyright 2001 Perot Systems Europe. All rights reserved Web Architecture considerations Tim Taylor August 2000

Copyright 2001 Perot Systems Europe. All rights reserved 19

What are we currently addressing?

11 LearningLearning Gaining understanding of the e-business marketplace

22 PlanningPlanning Determining your e-commerce strategy

33 SystemSystem Evaluating your current system software

44 NetworkNetwork Evaluating your internal and external network infrastructure

55 SecuritySecurity Adding security to your web site, intranet and extranet

66 PaymentPayment How you will be paid, and how you will pay suppliers

77 BuyingBuying Purchasing from suppliers over the internet

88 SupplierSupplier Linking into a centralised suppliers catalogue for purchasing

99 LogisticsLogistics Using the internet to manage stock levels and deliver goods

1010 SellingSelling Creation of selling and affiliation tools for your web site

1111 CustomerCustomer Creating a community of customers through your web site

1212 PersonalisationPersonalisationCreating electronic relationships

33 SystemSystem Evaluating your current system software

44 NetworkNetwork Evaluating your internal and external network infrastructure

55 SecuritySecurity Adding security to your web site, intranet and extranet

Page 20: Copyright 2001 Perot Systems Europe. All rights reserved Web Architecture considerations Tim Taylor August 2000

Copyright 2001 Perot Systems Europe. All rights reserved 20

Next Steps

Connect with the business– what is the e-business strategy?– what current developments are happening in this area?– SELL, SELL, SELL

• the e-business framework• why they need an architectural approach

Understand related standards and architecture

Tie in with metadata repository and other architecture work– provide focus for detailed investigation– include in plan– include in model

Architecture Model