planning a mysap technical architecture derek prior, phd asug, may 2003

37
Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

Post on 20-Dec-2015

216 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

Planning a mySAP Technical Architecture

Derek Prior, PhD

ASUG, May 2003

Page 2: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

Because of increasing complexity of SAP technologies and infrastructures, all SAP enterprises must develop and maintain a technical architecture blueprint.

Technical

Architecture

Blueprint

The TechnicalArchitecture Blueprint

Page 3: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

Conclusions

SAP’s technical architecture has evolved into a comprehensive, Internet-centric offering.

SAP portal products offer leading business benefits to both R/3 and mySAP enterprises.

mySAP enterprises should plan for a more-complex technical architecture and infrastructure.

R/3 enterprises will need to plan for future changes to their technical infrastructure.

More techniques are emerging for developing and maintaining complex SAP technical architectures.

Page 4: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

Conclusions

SAP’s technical architecture has evolved into a comprehensive, Internet-centric offering.

SAP portal products offer leading business benefits to both R/3 and mySAP enterprises.

mySAP enterprises should plan for a more-complex technical architecture and infrastructure.

R/3 enterprises will need to plan for future changes to their technical infrastructure.

More techniques are emerging for developing and maintaining complex SAP technical architectures.

Page 5: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

3) Physical

SAP Application Application Module 1, … Application Module n

2) Software

Web Application Server

Data-base

SAPApplication

SAPApplication

WASWAS

1) Logical

Features/Protocols: Global operation Authorisations Archiving WebFlow, WfXML RFC, FTP DCOM, CORBA HTTP, HTTPS, LDAP SMTP, ESMTP, MIME XML, SOAP, WSDL

Develop > ABAP + Unicode> JavaScript , WebDAV Tools> Java: J2EE> ECLIPSE Environment> Web Dynpro

Run > OS, DB, Hardware choice> Sizing & Performance> CCMS, TMS> 64-bit Kernel> Security

Architecture of a SAP Application

Page 6: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

A New SoftwareInfrastructure Superpower?

Proprietary Application Platform Suite — NetWeaverProprietary Application Platform Suite — NetWeaver

PortalPortal

WASWAS

XIXI

BASISBASIS

Java, Top TierJava, Top Tier

J2EE or ABAP (Proprietary)J2EE or ABAP (Proprietary)

A2A and B2B Integration SuiteA2A and B2B Integration Suite

Business Foundation — NetWeaverBusiness Warehouse, Knowledge Management,

Content Management, Webflow and Business Process Modeling

Business Foundation — NetWeaverBusiness Warehouse, Knowledge Management,

Content Management, Webflow and Business Process Modeling

Business Collaboration (Smart Enterprise Suite)xApps — Cross-Enterprise Strategic Focus

Business Collaboration (Smart Enterprise Suite)xApps — Cross-Enterprise Strategic Focus 4

2

1

3 Business ApplicationsBusiness One, R/3 Enterprise, mySAP Business Suite

Business ApplicationsBusiness One, R/3 Enterprise, mySAP Business Suite

Page 7: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

SAP NetWeaver – The Platform

SAP NetWeaver is

the application and

integration platform

to unify and align

people,

information and

business processes

across

technologies and

organizations.

DB and OS Abstraction

.NET WebSphere…

People Integration

Com

posi

te A

pplic

ati

on F

ram

ew

ork

Process IntegrationIntegration

BrokerBusiness Process

Management

Information IntegrationBusiness

IntelligenceKnowledge

Management

Life C

ycle

Managem

en

t

Portal Collaboration

J2EE ABAP

Application Platform

Multi-Channel Access

SAP NetWeaverSAP NetWeaver

DB and OS Abstraction

Master Data Management

Page 8: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

SAP Technology: “Moving Terminology”

mySAP Technology – Web Services Architecture

Exchange Infrastructure

Process-centric Collaboration

Portal User-centric CollaborationInfrastructure

SAP Web Application Server

Web services

J2EE & ABAP

myS

AP

CR

M

SA

P R

/3 E

nte

rpri

se

myS

AP

SC

M

myS

AP

SR

M

myS

AP

PL

M

Leg

acy

...

Th

ird

-par

ty ..

.

Ext

ern

al ..

.

Vision 2001 Technology 2002

DB and OS Abstraction

.NET WebSphere…

People Integration

Com

posi

te A

pplic

ati

on F

ram

ew

ork

Process IntegrationIntegration

BrokerBusiness Process

Management

Information IntegrationBusiness

IntelligenceKnowledge

Management

Life C

ycle

Managem

ent

Portal Collaboration

J2EE ABAP

Application Platform

Multi-Channel Access

SAP NetWeaverSAP NetWeaver

DB and OS Abstraction

Master Data Management

Page 9: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

SAP NetWeaver: Enabling xApps

Web services architecture

Leverages existing IT investm.

Open, masters heterogeneity

Lower TCO

One application and integration platform

New, snap on cross-functional business processNew, snap on cross-functional business process

mySAP Business SuitemySAP Business Suiteand other applicationsand other applications

xAppxApp

Solves integration challenge at bus. level

New, snap-on business processes

Cross-functional processes

Continuous business innovation

xApps from SAP, ISVs, SIs

Technology 2002 SAP xApp Vision

DB and OS Abstraction

.NET WebSphere…

People Integration

Com

posi

te A

pplic

ati

on F

ram

ew

ork

Process IntegrationIntegration

BrokerBusiness Process

Management

Information IntegrationBusiness

IntelligenceKnowledge

Management

Life C

ycle

Managem

en

t

Portal Collaboration

J2EE ABAP

Application Platform

Multi-Channel Access

SAP NetWeaverSAP NetWeaver

DB and OS Abstraction

Master Data Management

Page 10: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

1. User Integration: U2A Enterprise Portal .NET Connector WAS

mySAPBusiness Applications

ABAP, JavaCCMS, TMSWorkflow64-bit KernelPlatform Choices

ABAP, JavaCCMS, TMSWorkflow64-bit KernelPlatform Choices

February 2003

WASWAS

2. Internal Integration: A2A RFCs, BAPIs Batch Input, Other BDocs, IDocs ALE Messaging R/3 Plug-Ins Interface Advisor Web Projector Exchange

Infrastructure (XI) CSP Software

Partners

Note: Internet Business Framework => mySAP Technology => NetWeaver

3. External Integration: B2B XML, SOAP WSDL Web Services Business Connector XML Schema Repository C 1’s xCBL XML BizTalk, RosettaNet WebFlow Collaboration Scenarios Exchange Infrastructure (XI) Technology Partners

mySAP Business SuiteIntegration Technologies

Page 11: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

IntegrationBroker

EXCHANGE LAYER ( XI )EXCHANGE LAYER ( XI )

B2B

A2A

A2A, B2B

Collaborative

Processes

WASWAS

Internet

WEB APPS

CustomWeb

CustomWebWASWAS

PORTAL LAYER PORTAL LAYER

U2A

U2A

BWWAS

WASWAS

Integrated mySAPBusiness Suite Components

CRMCRM APOAPOLegacy,

Non SAPWASWAS

R/3Enterprise

R/3Enterprise

WASWAS WASWAS

Page 12: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

Conclusions

SAP’s technical architecture has evolved into a comprehensive, Internet-centric offering.

SAP portal products offer leading business benefits to both R/3 and mySAP enterprises.

mySAP enterprises should plan for a more-complex technical architecture and infrastructure.

R/3 enterprises will need to plan for future changes to their technical infrastructure.

More techniques are emerging for developing and maintaining complex SAP technical architectures.

Page 13: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

BOSSR/3

How have most Managers used SAP ?

Page 14: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

SS

EnterprisePortal:Managerviews

What If Managers , . . . ?

Page 15: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

Apps

Internet

Casual Users

Legacy,Non SAP

SAPAppsSAPApps

BW

KM

EP 6.0- Unification

Browser User Interface: Single Sign-On Single Look and Feel Personalized Easy to Use

EP 6.0 - Collaboration

Drag & Relate: Interactive Data Transfer Minimize Re-entry

Mini Apps, iViews: Customized Displays 300+ Predefined Roles Predefined Content

YahooContent, Services

Basic Functions: Personal Details System Messages Search SAP: Top Customers SAP: Orders SAP: AR, Inv Data

Enterprise Portal Power

Page 16: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

LDAPDirectory

UnstructuredData

Structured Data

Portal ServerPortal ServerPresentation Comp Framework

iView Development: MS ASP, Visual Studio Java Tools, JSP Workset Groups

Unification

Unifiers: Hyperrelational

Data Metadata: All Apps Enable Drag

& Relate

SAPNon SAPPortal Framework

Page BuilderFast Caching

User/Role Mgt SSO

BW KM

ITSITS

SAPGUIfor

HTML Data-Base

SAP Enterprise Portal Architecture

Page 17: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

Piloting a SAP Enterprise Portal

Pilot

Pilot

Pilot

1. Determine Most Important User Needs

2. Seek Expert Assistance, Set Budget

3. Install All Infrastructure

4. Build Pilot Prototype

5. Test Pilot Prototype

6. Deploy, Plan Next Phase

Pilot Approach:

Page 18: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

Conclusions

SAP’s technical architecture has evolved into a comprehensive, Internet-centric offering.

SAP portal products offer leading business benefits to both R/3 and mySAP enterprises.

mySAP enterprises should plan for a more-complex technical architecture and infrastructure.

R/3 enterprises will need to plan for future changes to their technical infrastructure.

More techniques are emerging for developing and maintaining complex SAP technical architectures.

Page 19: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

( mySAP.com = SAP’s Internet Strategy = Confusion )

1. Technology: SAP NetWeaver

2. Business Applications: mySAP Solutions for collaborativebusiness, in addition to 22 Industry Solutions =

Supply Chain Management: APO, LES, ILOG, BW Customer Relationship Management: SAP CRM, Internet Sales, BWSupplier Relationship Management: SRM, EBP, BWProduct Life Cycle Management: PLM, QM, PS, EHS, BWFinancials: R/3 Enterprise, SEM, Real Estate, LeasingHuman Capital Management (HCM): R/3 Enterprise, ESS

3. Marketplaces: E-Marketplace Exchanges =SAP/Commerce One: MarketSet

4. Application Hosting: IDES, SAP Hosting, ASPs

Seller Seller

Buyer

Buyer

March 2003

mySAP Business Suite Summarized

New ! mySAP ERP: R/3 Enterprise / Financials / HCM + SAP NetWeaver

Page 20: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

EBPEBP R/3R/3 BWBWD/T/P D/PD/T/P

Clustered DBS PC

Client

Intranet Traffic

LAN Traffic

D/PD/P

Portal LayerPortal Layer

PortalServerPortal

Server

+ Load Balancing+ Load Balancing + Firewalls+ Firewalls

CS

ITS

WS

ITS ITS

WS WS

BC

BrowserPortal

mySAP Business Suite Infrastructure Example

Page 21: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

SAP CRM 3.1 Architecture

CRM ServerCRM Server

Sales Service Marketing CRM Middle

– Ware

Sales Service Marketing CRM Middle

– Ware

CRMCRMWASWAS

CRMCRM

WASWAS

Data-Base

Co-browse

Call TelephonyServer

CTI Server

Internet Services Java Apps IPC Catalog (3P)

WAS

Mobile Client AdminWorkstation

Mobile Apps

Comms Station Gateway DCOM

Mobile Client AdminWorkstation

Mobile Apps IPC

Channels:

Data-Base

Mobile Devt RepositoryWorkstation

Mobile Apps Development

Page 22: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

Conclusions

SAP’s technical architecture has evolved into a comprehensive, Internet-centric offering.

SAP portal products offer leading business benefits to both R/3 and mySAP enterprises.

mySAP enterprises should plan for a more-complex technical architecture and infrastructure.

R/3 enterprises will need to plan for future changes to their technical infrastructure.

More techniques are emerging for developing and maintaining complex SAP technical architectures.

Page 23: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

But What About R/3 Customers ?

Page 24: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003
Page 25: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

3.1I3.1I

4.0B4.0B

4.6C4.6C

4.5B4.5B

R/3

Now

December 2003 (4.6C: March 2005)

Technology:

Availability:

End ofSupport:

From R/3 to R/3 Enterprise

BASIS 4.6DBASIS 4.6D

2Q02 (Ramp Up)

1Q03 (GA)

R/3 Enterprise

Stable

4.70

Evolving 1.10, ...

R/3 Enterprise

Core

R/3 Enterprise

Core

Extensions

WAS 6.20WAS 6.20Upgrade:Proven ?

Risk ?Cost ?

Page 26: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

Conclusions

SAP’s technical architecture has evolved into a comprehensive, Internet-centric offering.

SAP portal products offer leading business benefits to both R/3 and mySAP enterprises.

mySAP enterprises should plan for a more-complex technical architecture and infrastructure.

R/3 enterprises will need to plan for future changes to their technical infrastructure.

More techniques are emerging for developing and maintaining complex SAP technical architectures.

Page 27: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

We Need an Architecture …

?

Architecture Maze

?Internet

Apps / DBs / OSs:“Why Have We GotOne of Everything?”

Company B2B StrategyDue Date: Tomorrow!

Recipe:Interface Spaghetti

Data-base

Page 28: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

Packaged application technical architecture(Not application development architecture)

Potential Architectural Tasks

Business process standardsFor example, enterprise and collaborativebusiness scenarios

MethodologiesTechniques/notations to design and model systems

Interfaces and modularizationDefine the “fault lines”: “City planning,” “building planning” Interfaces with tradingpartners, c-commerce e-services

Data architecture standardsShared data representation standards and formats

Infrastructure architectureServer landscapes, storage, Web layer

Page 29: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003
Page 30: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

Technical Architecture Blueprint

ArchitectureStandards

ArchitectureStandards

Business data Suite vs. BOB Interfaces Flexibility

Business data Suite vs. BOB Interfaces Flexibility

CompanyStandards

v 2.0

CompanyStandards

v 2.0

InfrastructureInfrastructure

Server consolidation Enterprise storage, SANs SAP Tools:

– Landscape planning CIM– MCOD, Solution Manager

Server consolidation Enterprise storage, SANs SAP Tools:

– Landscape planning CIM– MCOD, Solution Manager

Planning ProcessPlanning Process

Business strategy Top-down approach No standard

methodology yet

Business strategy Top-down approach No standard

methodology yet

Functions

Software

CRMCRM

Architecture Maze

Building a mySAP Enterprise Architecture

Page 31: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

Recommendations

To build an effective mySAP enterprise architecture:

Enterprises that already have a technical architecture blueprint should extend it to include mySAP applications, interfaces and infrastructure.

Other enterprises should build their own blueprints using a top-down approach and focusing on effects of globalization and their planned adoption of mySAP.

All enterprises should consider the definition of the interfaces between SAP and non-SAP applications in their technical architecture.

Page 32: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

More Recommendations

Enterprises should evaluate the emerging techniques for consolidating and managing complex mySAP infrastructure landscapes.

Enterprises that need extended access to R/3 or mySAP applications for new casual users should pilot the mySAP Enterprise Portal product using Gartner’s six-step iterative pilot approach.

Enterprises implementing mySAP CRM will need to plan their technical architecture more carefully than with other mySAP applications.

Enterprises planning to upgrade to R/3 Enterprise should budget for a less-disruptive upgrade than usual.

Page 33: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003
Page 34: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003
Page 35: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003
Page 36: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

Planning a mySAP Technical Architecture

Derek Prior, PhD

ASUG, May 2003

Page 37: Planning a mySAP Technical Architecture Derek Prior, PhD ASUG, May 2003

Planning a mySAP Technical Architecture

Derek Prior, PhD

ASUG, May 2003