best build applications

7/31/2019 Best Build Applications

1/23

Introducing SAP Guidelines for

Best -Bu i l t App l ic a t ions

That Integrate with SAP Business Suite

Helping Partners Provide Customers With Applicationsthat Complement SAP Business Suite Software


2/23

SAP AG 2009. All rights reserved. / Page 2

Disc la imer

SAP assumes no responsibility for errors or omissions in this publication. SAP doesnot warrant the accuracy or completeness of the information, text, graphics, links orother items contained within this publication. This publication is provided without awarranty of any kind, either express or implied, including but not limited to, the impliedwarranties of merchantability, fitness for a particular purpose, or non-infringement.The only warranties for any SAP products and services are those that are set forth in

the express warranty statements accompanying such products and services, if any.Nothing herein should be construed as constituting an additional warranty.

SAP shall have no liability for damages of any kind including without limitation direct,special, indirect, or consequential damages that may result from the use of thispublication. This limitation shall not apply in cases of intent or gross negligence. Thestatutory liability for personal injury and defective products is not affected.

All statements in this publication with regards to strategies, developments and/orfunctionalities of SAP products represent intentions only and are not intended to bebinding upon SAP to any particular course of business, product strategy and/ordevelopment.


3/23


Agenda

1. Introduction to Best-Built Guidelines

Motivations for Best-Built Guidelines

What the Best-Built Guidelines Areand Arent

Benefits of Following the Best-Built Guidelines

2. How is Guidance Provided?

Areas Covered by the Best-Built Guidelines

Approach to Guidance

3. Adopting the Best-Built Guidelines Incremental and Iterative

Where to Find Out More


4/23


Opportunities for clear guidance on how SAP partners canbuild complementary solutions:

Help ISVs and system integrators make informed developmentdecisions

Provide guidance to partners who want their applications to beenterprise-ready

Architectural TrendsAffecting theEnterprise

Business Networks

Timeless software

End-to-end business

process solutions

Technology Change

Increasedheterogeneoustechnology choices fordevelopment andintegration in customerenvironments

Large number ofecosystem partnersdevelopingapplications thatcomplement the SAPBusiness Suite


5/23


Best-Built guidelines are simply guidance about what partners can do tobest align their complementary software with the SAP Business Suite

Par t ners choose w hether to fo l low t he gu idance

The Best-Built guidelines are: Recommendations from SAP

Descriptions of what to do, not how to do it

Iterative and incremental

Deal with currently available solutions

Similar to standards, best practices, andguidelines used to create SAP solutions

The Best-Built guidelines are not:

Mandates for partners

Statements of future direction

Certification- or brand-related


6/23


Integration

Lower integration costs for software built using SAP architecture guidelines,standards, and industry best practices

Support

Lower support costs when products use standard components and followsimilar patterns

SAP is reducing end-to-end support costs for customers, and ISVs should beable to achieve similar reductions

ISVs leveraging SAPs support infrastructure can reduce support costs

Familiarity Reduced operating and training costs when software runs like SAP solutions

Customers Can Gain From


7/23


Value to Customers

Delivering integration, support, andfamiliarity benefits to customers

Capabilities

More efficient and effectiveimplementation of applications thatcomplement the SAP Business Suite

Accelerated adoption of new SAPtechnologies, which makes for morepowerful products for SAP customers

Governance More secure software can enable

enforcement of policies like segregation ofduties through role management and properreporting of risk and compliance metrics

Partners Can Gain From


8/23


How Is Gu idanceProvided?

The Best-Built guidelines describe both what is recommended as wellas what is not recommended. The guidelines may make three sorts ofstatements about a particular technology or technique:

Recommended: This represents the safe way to do somethingthat likely fits into the long-term SAP product direction

Not encouraged: This represents an acceptable way to dosomething that may be altered in the future

Not recommended: This represents a way to do something thatshould be avoided


9/23


SAP Business Suite

Industry SolutionsIndustry Solutions

Connected to an SAPsolution

Partner products developed usingnon-SAP design time tools andrunning on non-SAP platforms thatintegrate with SAPs Business Suiteand other solutions

Migrated to run in theSAP environment

Partner applications that aredeveloped using non-SAPdesign time tools, but aremigrated to run on SAPstechnology platform

Designed with SAP tools to run inthe SAP environment

Partner applications built using SAP design anddevelopment tools. Such solutions will naturallybe deployed to run on the SAP technologyplatform


10/23


SAP Enterprise Portal

Web Dynpro iView Web Dynpro iView

ABAPWeb Dynpro

Runtime

ABAP

Server

BusinessAPI (BAPI,

Web Services)

Business

Data

J2EE

Web Dynpro

Runtime

Web DynproAppWeb Dynpro

App

J2EE

Server

EJB (e.a.) Business

Data

Web DynproApp

SAPNetWeaverDeveloper

Studio

Web Dynpro

App

ABAP

Workbench


11/23


SAP

NetWeaver AS

Java EE App Server

JBoss

WebSphere

Geronimo

Tomcat

Post-MigrationTests

Architectural Analysis

Environment Analysis

Source Code Analysis

Component Mapping

Migration Planning

Assessment Pre-MigrationTests

Implementation

Import Sources

Convert Descriptors

Modify Source Code

Configure Target System

Build and Deploy on SAPNetWeaver AS

Run and Record theApplication TestSuite on SAPNetWeaver AS

Compare withPre-Migration Tests

Migration Project: J2EE Compliant Server to SAP NetWeaver AS

Run and Record theApplication TestSuite on J2EECompliant Server


12/23


RubyPython

IBM WebSphere

PHP

SAP Business Suite

Industry SolutionsIndustry Solutions

Perl

Web ServiceProject

Microsoft .NET

EnterpriseServices

Explorer For.NET

3. Publish /Update

Service

1. DeployService

2. Retrieve

Service

Definition

LocalWeb Server

(IIS)

Service

Service

WSDL

Microsoft Visual Studio

ServicesRegistry

(Definitions)

ServiceDefinition

ServiceDefinition


13/23


Sam ple Guidel ine

Application Lifecycle Management sample guideline

Explanation

In Java, package names should be used to specify the namespace. ISVs can eitherrequest a unique namespace from SAP, or can use a namespace that is very unlikely tobe used by another company, such as com.mycompany.myapplication(assuming thatthe ISV owns the domain name mycompany.com). An ABAP namespace, which must beregistered with SAP, is 3 to 8 capital letters bounded by slashes (for example,

/MYAPP/)

Pointer

For requesting and registering namespaces and for more information, seehttp://service.sap.com/namespaces

Namespaces

The Best-Built guidelines recommend that software components be nameduniquely to avoid name collisions with SAP software and with softwarecomponents from other SAP partner companies.


14/23


The Best-Built guidelines provide guidance for the following areas:

Application Lifecycle Management

Process Orchestration and Service-Oriented Architecture

User Interface and User Experience

Data and Information Management

Application Development

Governance and Security


15/23


16/23


17/23


Best-Bui l t Guidel ines:L inks t o How -To In form at ion

sdn.sap.com SAP Community Network,

with blogs, forums, wikis Free self registration

help.sap.com

Deep dive architecturalinformation Public access

service.sap.com

Support and application lifecycle information

Access through PartnerEdge membership

sapdesignguild.org

Information on designing user interfaces for SAP customers Public access


18/23


The Publ ished Guidel i nes

Chapter 1 provides an overview of the motivation for andscope of this program.

Chapter 2 offers a comprehensive list of guidelines in sixareas: application lifecycle management, business processand service-oriented architecture, user interface and userexperience, data and information management, application

development, and governance and security.

Guidelines to be released incrementally. One chapter foreach of the six areas of guidelines will be published online.Those chapters contain more rationalizing details for theguidelines.

More will be released in 2010

Always find the up-to-date version of Best-Built Guidelines at:


19/23


SUMMARY

Guidelines for lifecycle management,process orchestration and SOA, userinterface and user experience, data andinformation, application development, andgovernance and security

Recommendations about what to do andwhat not to do

Information for all ISVs, whether they usethe SAP design time, run time, or neither

Helps ISVs create software that isenterprise-ready and works well with SAPapplications

Helps ISVs make development decisions


20/23


Visit the web site at

Latest version always available online

Download a PDF of the guidelines

Send us feedback

Online version of the guidelines with live links

Visit


21/23


22/23


Thank you!


23/23


No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained hereinmay be changed without prior notice.

Some software products marketed by SAP AG and its distri butors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries,eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+,POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex,MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Inform ix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or othercountries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W 3C, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under l icense for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respectivelogos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products andservices mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries.Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only.National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its aff iliated companies ("SAP Group") for informational purposes only,without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Groupproducts and services are those that are set for th in the express warranty statements accompanying such products and services, if any. Nothing herein should be construedas constituting an additional warrant.

Copyr ight 2009 SAP AGAl l Right s Reser ved

Copyr ight 2009 SAP AGAl l Right s Reser ved

best build applications

Documents