ESOA Enablement - Project Task Management

ESOA Enablement - Project Task Management

Applies to: Enhancement Package (EhP) 1 for SAP NetWeaver Composition Environment (CE) 7.1

Enhancement Package (EhP) 4 for SAP ERP 6.0

For more information, visit the Enterprise Service - Oriented Architecture homepage.

Summary This article guided that the process of a typical CE Project from the discovery of suitable enterprise service from ES workplace and SAP ERP6.0 EhP4 to import into CAF and expose as webserivce. Provided Project Tasks template, we will get the overview in actual project implementation what is the needed steps for the project team and find out a various way to implement enterprise service.

Author: Chan Jin Park

Company: SAP Asia Pte

Created on: 31 March 2009

Author Bio Chan Jin Park is a senior support consultant in SAP Asia Singapore. For CoE Technology team in Active Global support, his role covers the full scale of on-site engagement in the area of SAP NetWeaver EP/KM/CE and support a various customer project and operation. He is also covering End to End (E2E) solution operations in the area of Root Cause Analysis, System Administration, Performance Optimization and teaching SOA, NW WAS/EP and E2E course.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com © 2009 SAP AG 1

https://www.sdn.sap.com/irj/sdn/enterprisesoa


Table of Contents 1. Introduction .....................................................................................................................................................3 2. Customer Project Scenario.............................................................................................................................4

2.1 Project Task Management ........................................................................................................................5 3. Business Process Design (Business Requirements) .....................................................................................6

3.1 Function Design ........................................................................................................................................6 3.2 Technical Design & Setup.........................................................................................................................7

3.2.1 Central SLD setup...............................................................................................................................................8 3.2.2 Optional: Local SLD setup for Solution Manager ................................................................................................9 3.2.3 NWDI setup.........................................................................................................................................................9 3.2.4 Enhancement Package update in backend system ..........................................................................................10 3.2.5 CE7.1 Setup......................................................................................................................................................11 3.2.6 Portal Integration...............................................................................................................................................12

4. Service Modeling ..........................................................................................................................................13 4.1 Creating of software component and design of Interface .......................................................................13

4.1.1 Create a new software component in the SLD..................................................................................................13 4.1.2 Creation of Process Modeling in ESR...............................................................................................................13

5. Service Provisioning .....................................................................................................................................17 5.1 Service Provisioning in Java ...................................................................................................................17

5.1.1 Create Web Service Provider............................................................................................................................17 5.1.2 Tailor of the interface direct web service import from Global Data Type (GDT) ESR........................................19

5.2 Service Provisioning in ABAP .................................................................................................................24 5.2.1 Proxy Generation ..............................................................................................................................................24 5.2.2 Service Implementation.....................................................................................................................................24 5.2.3 Endpoint Creation .............................................................................................................................................24 5.2.4 Publish Webservice ..........................................................................................................................................24

6. Service Discovery & Description ..................................................................................................................26 6.1 Discover ..................................................................................................................................................26 6.2 Evaluate ..................................................................................................................................................27 6.3 WebDynpro Java (WDJ) user Interface ..................................................................................................33

6.3.1 Building a WDJ UI from scratch ........................................................................................................................33 6.4 Visual Composer.....................................................................................................................................35 6.5 Creation of WDJ iview in Portal ...........................................................................................................37

7. Remain Tasks...............................................................................................................................................39 Related Content ............................................................................................................................................39 Reference document.....................................................................................................................................39

Copyright...........................................................................................................................................................40



1. Introduction This ESOA enablement is intended to show overall guideline how typical Enterprise Service Oriented Architectures (ESOA) Project is planning and moving forward to the actual project scoping. The latest SDN articles and the expert's blog give you the detail information for the subject matter, on top of that information, this document update that actual project task management based on the customer's scenario.

The document mainly focused on the main targets: • Lead System Architecture

- Understand of SAP ESOA Development Lifecycle and knowing that different technologies for the Service Provider and Service Consuming side.

• Project Management Office (PMO)

- Overall project scoping with the subject matters, compare with the purely SAP environment projects, Also, the steps PMO must define during the project scoping and familiar with the sequence

• Technical Consultant

- Knowing that different technologies set when it comes to actual implementation stage and recommended to technical setup procedure in case of webservice import and webservice enablement from SAP ERP6

• Business Process Expert

- How to create a new business process and discovering re-usable enterprise scenarios from ES Workplace.

Throughout this guide, we will take a look how typical ESOA project which runs by SAP Composite Environment (CE7.1) implement by the project team. We will take a look from Enterprise SOA Development Lifecycle point of view. However, this guide is mainly focus on "process flow of the project", it won't be touched the deep side of business logic coding which it requires Java EE5 development, ABAP coding and CAF manual java code implementation.

Figure 1: Enterprise SOA Development Lifecycle



2. Customer Project Scenario People4U is doing outsourcing Human Resources (HR) management. From Call center, Project Implementation outsourcing to temporary staffs servicing, their workplaces are quite various and submission of their expense claim and travel related process are all happened independently.

The most frequent business processes which it need to govern is as below: • Different submission date of expense claim and reimbursement date

• Expense Payment Inquiry

• Business Travel request and deliver of advance travel costs in cash

• Weekly, bi-weekly salary payment

All the travel related transactions run by the custom developed webservice program. Even though, they are running ECC5, but their main usage is FI/CO. HR master data has been maintained, but a lot of function need to be enhanced. So the team is looking for the enhanced featured from ECC and possibly to use of Global Data Type. It will warp the webservice with a more generic and understandable service. The decision, how many process will be created as a new and discover from ES workplace and apply as enhancement in ESR haven't make any choice yet.

The project team also looking for the best practice for this project not only implementation phase, also post go-live operation parts. The reason being that the project team is quite new for these topics and SAP Web Application Server (WAS) environment quite difficult to find out the ongoing tuning and all the complex of Java landscape when it come to performance.

Finally, with all the open conditions, the project team chose one scenario as a pilot process

Process Name: Expense Approval

Process description

On-site consultant enter their expense exposed enterprise service, it will be reviewed the line of business (LOB) manager. The Amount of expense such as, the line items for travel, over-time-meal and purchase of stationary items less than SGD200, doesn't required approval LOB manager, it will be triggered approval process automatically to the finance controller and the payment will be made the last Friday on the same week.

For the composite application development approach how to publish to service registry need to implement. The final decision from service consuming and creation of webservice still pending, the project team needs to know that all the different options ESOA development for the cases.

• Creation of webservice from outside in development point of view

• Expose webservice

• Creation of Visual Composer UI for the case of employee make inquiry payment

• WebDynpro for Java UI

Again, this guide will not be going through the complete lifecycle of development. It will be cover the above cases and see how efficiently required the service can create and get the glance of overview.



2.1 Project Task Management

Based on the project scoping, Project Management Office defined the task lists as below : The detail of Approval of Project Tasks, scoping of design tasks and number of development tasks will be decided later. More or less, the main stream of project task scoping will be controlled by defined project tasks.



.

3. Business Process Design (Business Requirements)

3.1 Function Design

Sketch "Expense Approval Process" within Process Composer

SAP NetWeaver (NW) Business Processes Management (BPM) is embedded into SAP NW BPM CE7.1 EhP1. To use of Process Composer, the team draw process name.



Pool Name: Expense Approval Process

Processor: Expense Claim Request

LOB Project Manager

ERP (Dedicated Backend: Finance Controller will be the last parties to make the Payment) Scenario: when on-site consultant enters their expense, the request comes to the LOB project manager based on the business process. The next steps, the project manager informs by the Business Rules (BR), if the amount of the claim is more than SGD 200, the submit will be reviewed by the project manager and if the amount of claim is less than SGD 200, it will be dispatched automatically to the Finance controller for the payment out within the same week.

Business Rules for expense approval Table

SAP NW Business Rules Management (BRM) which is embedded SA NW CE7.1 EhP1 can easily implements rules for the expense approval. Those are consultant who works in on-site project, the approval tables will be applied when the amount of claim is greater than SGD200, it requires going through approval. However, the expenses raise the location in the office, less than SGD 200 also need to approval.

3.2 Technical Design & Setup

Based on the project scoping, the technology team came up with system landscape. At this stage, the detail setup and configuration scenario from Technical point of view needs to be go through, more or less, the full stack of CE_Development_Full_stack has chosen from CE development template.



3.2.1 Central SLD setup

System Landscape Directory (SLD) is the central location of all the technical and system related information in SAP application. For the ESOA Project base, Enterprise Service Repository (ESR) can read its software components from SLD. Regarding how to setup SLD setup for the local and productive landscape, please refer to SAP service marketplace http://service.sap.com/sld

Connection Between Web AS ABAP Systems and SLD (SAP Library - System Landscape Directory)

Connection Between Web AS Java Systems and SLD (SAP Library - System Landscape Directory)

System Landscape Directory of SAP NetWeaver 7.1 User Manual


http://service.sap.com/sld

http://help.sap.com/saphelp_nw04s/helpdata/en/21/84570b3ae14e77b3047c82218974b9/frameset.htm

http://help.sap.com/saphelp_nw04s/helpdata/en/c9/dc37520bdf4b48bb8f6d4329f073d5/frameset.htm

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b09fe69e-46be-2a10-9fb0-9c11aeaa3557


3.2.2 Optional: Local SLD setup for Solution Manager

SAP solution manager is key product component to implement Run SAP methodology(http://service.sap.com/runsap) Solution manager itself requires either local SLD for solution manager or central SLD to retrieve technical or software component. E2E Root Cause Analysis (RCA) setup phase requires connect its agent to connect SLD.

So far, this project we are going to use Central SLD, in the area of SLD Bridge: Gateway information specified Central SLD hostname and service. The fetch and retrieve background jobs will be triggered the time interval 720 minutes as a default.

SLD and RZ70

3.2.3 NWDI setup

For the most of case, the local development such as local managed object and independent local repository can developed a standalone NWDS. However, it is strongly recommend using NWDI in shared environment and here is the major benefit to have NWDI in productive mode

• Seamless integration with SAP NetWeaver CE

• Provides team development and version control capabilities

• Version management

• Control of development governance


https://www.sdn.sap.com/irj/sdn/thread?messageID=511193


Currently, recommended for the deployment of SAP NetWeaver CE runtime systems is SP13+ onward.

Figure 2: NWDI Technical structure

More in detail how to setup NWDI along with NWDS please refer SDN documents.

How to Setup an NWDI Track for Composition Environment Development (SAP NetWeaver CE 7.1)

Working with SAP NetWeaver Development Infrastructure (NWDI) (SAP Library - Knowledge Management Development Manual)

A Quick Guide for SAP NetWeaver Developer Studio 7.10 Installation

Distributing Development Tools Made Easier: The New Update Server for the SAP NetWeaver Developer Studio

3.2.4 Enhancement Package update in backend system

Publishing of service into the Server Registry (SR) can be done a different ways. • Publish external service though SR User Interface (UI)

• Publish manually from ABAP Backend

• Publish from Enterprise Service Repository (ESR)

• Publish implicitly from ABAP and Java Environment

Service discovering, section 6, we have already found that the reusable enterprise service "ExpenseTravelManagment" is available in SAP ECC6 system. Then, the next step is to publish to the Service Registry using transaction SOAMANAGER or just directly uses the generated WSDL file from SPROXY. However, Expense and Reimbursement Management SAP Process component model only available on SAP ERP6 EhP4. So, remain tasks is to make the current ECC system as EhP useable system first then we manually plug in ESA ECC-SE 604.

For more information how to bring up your backed system SAP ERP6 to EhP, refer to the below documentation from SDN and SAP service marketplace http://service.sap.com/ehp-inst

Overview SAP Enhancement Packages - SAP Enhancement Packages - SAP Community Network Wiki

Lifecycle of an SAP Enhancement Package for SAP ERP

SAP Enhancement Packages for SAP ERP


https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/7014086d-3fd9-2910-80bd-be3417810c6f

http://help.sap.com/saphelp_nw04s/helpdata/en/45/1282b176a341e1e10000000a1553f6/frameset.htm

http://help.sap.com/saphelp_nw04s/helpdata/en/45/1282b176a341e1e10000000a1553f6/frameset.htm

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a0d1b193-0ac8-2a10-43ae-a93f3731028f

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a0989534-916e-2a10-8abc-a9b1a10ec6da

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a0989534-916e-2a10-8abc-a9b1a10ec6da

https://websmp201.sap-ag.de/ehp-inst

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/EHP/Overview%2bSAP%2bEnhancement%2bPackages

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/802e68b3-f640-2b10-468c-e2fd68e335f2

https://www.sdn.sap.com/irj/bpx/erp?rid=/webcontent/uuid/e0855959-7041-2b10-3790-e49d670c3eac


SAP Enhancement Packages for SAP NetWeaver: What Professionals Need to Know About Enhancement Packages for SAP NetWeaver and the SAP Enhancement Package Installer

3.2.5 CE7.1 Setup

To implement a scenario, see the corresponding section in the Master Guide – SAP NetWeaver CE (available under https://www.sdn.sap.com/irj/sdn/nw-ce) for required installation options

For example, for the scenario Developing applications using Java, you require the following:

A basic SAP NetWeaver Composition Environment installation including SAP NetWeaver CE Server and SAP NetWeaver Developer Studio

Either set up a development workplace or install the SAP NetWeaver CE Server on a central host and several SAP NetWeaver Developer Studios on your development hosts

Optionally, run the additional capability Adobe Document Services (if you wish to use SAP interactive forms by Adobe with WebDynpro)

If you want to use the SAP Component Model, you require the SAP NetWeaver Development Infrastructure (capability NetWeaver Development Infrastructure)

Either install the NWDI on an SAP NetWeaver CE 7.1 Server or use an NWDI based on AS Java 7.00 SP Stack 13 or higher

Figure 3: Sequence of setup CE7.1

Pre-configuration is performed automatically as part of the installation. After the installation, you should run the Configuration Wizard to make technical settings which are required for the technical processing of a system or a technical scenario, such as

• Initial setup of functional unit SLD

• Initial setup of functional unit Development Infrastructure (DI all-in-one)

• Creation of Services Registry Destinations


https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30da26d0-5e29-2b10-589d-adcd236f1ca9

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30da26d0-5e29-2b10-589d-adcd236f1ca9

https://www.sdn.sap.com/irj/sdn/nw-ce


3.2.6 Portal Integration

Refer to Master Guide SAP NetWeaver Composition Environment 7.1 � including Enhancement Package 1, http://service.sap.com/instguidesnwce711

Figure 4: SAP Netwever CE and SAP Backend systems

Mostly, the project will be run two separate instance of SAP Enterprise Portal (EP). The default CE7.1 installation comes with SAP J2EE 5 Portal application and backend system run, let's say BI runtime portal or Corporate Portal for ESS/MSS purpose. In order to implement this scenario, the best options would be to use of SAP WebDynpro Java iView (Remote) template in the iView Wizard on the SAP NetWeaver 7.0 portal to integrate WebDynpro Java applications running on the remote SAP NetWeaver CE system into local iViews.

More Information: Refer to the Creating WebDynpro Java iViews topic in the SAP NetWeaver 7.0 documentation.


http://service.sap.com/instguidesnwce711


4. Service Modeling

4.1 Creating of software component and design of Interface

A part from service discovery which it will cover from chapter 6, the project team needs to create a software component. A new created software component will be imported in ESR and design a new service interface based on the proper data type.

4.1.1 Create a new software component in the SLD

4.1.2 Creation of Process Modeling in ESR

• Select Software component creation from SLD

• Creation of Namespace



• Design the Enterprise Service interface in ESR copy from predefined DataType from ESM ERP604

ExpenseArrangmetnID

ExpenseArrangementSimpleByEmployeeQueryMessage_sync

ExpenseArrangementSimpleByEmployeeResponseMessage_sync

Above three GDT types are copied from http://sap.com/xi/Travel/SE/Global

• Assembling Message Type

- the message type which assemble the date type for software component SC_ES_EXPENSE 1.0 of people4u.com



• Designing a service interface

- Assembling the message types into Enterprise Service Interface



• Activation of all the changed lists



5. Service Provisioning After service modeling is done from ESR, the next step is to generate the proxy as CAF application service and fill the resulting Java class with the business logic coding. As result, we are able to test the webservice navigator.

Let's say, the employee make an inquiry whether their expense payment has been transmitted from Finance department. Then section 5.1. Service Provision in Java which will be done by CAF can be an easy way

5.1 Service Provisioning in Java

5.1.1 Create Web Service Provider

Generating proxy as Composite Application Framework (CAF) application service and filling the resulted Java class with some of business coding will be required after modeling is done.

First part, we are going to use SWDC which we created earlier in ESR. All the date type, message type, service interface define must be done before CAF create a webservice.

• Creation of CAF Project

• Creation of Web Service Provider

- CAF itself exposing as Web service provider. It means, available WSDL service which already created in ESR, Remote Location/File system and Service registry are easily imported in CAF.



• WSDL file imported in CAF as Application Service

• The tab "operation", the column Manually Implemented was selected. Here is the part, we are actually need to place business logic code

• Manually implemented code



5.1.2 Tailor of the interface direct web service import from Global Data Type (GDT) ESR

Application service as interface point of view, it can be tailored to be needed service consuming. This part, we will take GDT from ECC-SE 603 package at ECC6 EhP3 and then, tailed the service interface.

• Reuse the original GDT from enterprise service

• Import as web service



• Imported service Interface



• Encapsulate the expense header date and expense Item for the separate folder structure modeling

• Creation of Application service from the context menu



• Operation parameter mapping

• Creation of datasource mapping

• Expose as web service



• Generate webservice with Build

• Test with WSNavigator



5.2 Service Provisioning in ABAP

5.2.1 Proxy Generation

• Enterprise service brose within the ABAP Workbench to create proxy

5.2.2 Service Implementation

• ABAP workbench to code functionality or glue code to call existing functionality

5.2.3 Endpoint Creation

• SOA Management (Transaction Code : soamanager) to create Endpoints and configure the implemented service

5.2.4 Publish Webservice

• Transaction code WSPublish to publish service to Registry



6. Service Discovery & Description

6.1 Discover

As part of business and technical setup, the project team looks for different possibilities to search and discover whether the enterprise services are available in ES Workplace. There are few ways to search for its service in ES workplace (http://esworkplace.sap.com) via process component, Integration scenarios, solution maps and search functionality.

Via solution map, SAP Travel Management ESS Travle&Expense possibly provide the solution map


http://esworkplace.sap.com/


Value potentials figure showed that depends on the customer discussion; it can be fulfill up to 70% of standard function. However, the project team need to deicide that whether we can directly import from enterprise service with customizing as In-out development method.

6.2 Evaluate

For the evaluation purpose, searching at Enterprise Service Repository (ESR) which it comes with default CE7.1 installation. However, the required Software Component with namespace ESM ERP604 the namespace http://sap.com/xi/ESM/ERP isn't here.

If the defined service operation enhancement in ESR is fulfill the business process, it simply generate and enhancement proxy and implement the required logic, possible change of few business logic to backend system need to follow in order to publish to the service registry. At this moment, still evaluation mode, has not come to the logic of Enterprise Service-specific Business Add-In(BAdl) yet.

If you refer to "Master Guide SAP enhancement package 4 for SAP ERP 6.0", 4.3 Service-Oriented Architecture (SOA) Software Component Version what we want to use it, ESM ERP 604, deliver with SAP ERP6 "ready to use" enterprise service. What we need to do is, to publish as webservice into service registry after we enable of required enterprise service.


http://sap.com/xi/ESM/ERP


Again, SAP ERP6 EhP4, refer to the below table from the Master Guide SAP enhancement package 4 for SAP ERP 6.0 page 103, depends on SAP ERP EhP Product instance, there are different set of installation are required



SAP ERP EhP SW components with product instance ESA ECC-SE 604 publish these web services in the Service Registry using transaction SOAMANAGER or just directly use the generated WSDL file from SPROXY. However, the current SAP ERP6 hasn't been upgraded as Enhancement Package 4. The option, to use of enterprise service from ECC directly can't be consider until ECC fully upgraded to EhP4

The second evaluation option is to import ESR & XI content into ESR and possibly creating enhancement service. The content which needs to be import as object in ESR, it can be download from the service marketplace http://service.sap.com/patches


http://service.sap.com/patches


Successful ESR content as object import, we are able to see the whole modeling which comes with ESM ERP 604. Among them, search for Process Model "Expense and Reimbursement management"



SAP Process Component Model showed the all the service operation, service interface and data type are all there, it might be easy to implement. Feedback to application team, based on this process models, can it be achieved

• Developing enhancements in the ESR

• Creation enhancement proxies and implement ting BAdI in the backend system.

The last evaluation option is to search directly in service registry



After the execution of Test button, the team can know that the activated enterprise service is the reusable for the project.



6.3 WebDynpro Java (WDJ) user Interface

WebDynpro is SAP's standard toolset for the UI design development and execution. In the part, we are going to create a WDJ UI, ExpensePaymentNotifcation. When the approval request came out from the LOB Manager, the finance controller created this notification to the Explain Requestor. For example, the amount of expense claim and payment date will be informed to the employee. There are few ways to create of WDJ UI, but we are going to create as scratch.

6.3.1 Building a WDJ UI from scratch

• Creation of WDJ project component



• Creation of component controller and add manually Context and attribute

• Creation of Layout with Node and attribute



• Completion of design after Build and deployment

6.4 Visual Composer

The steps what we remain here possibly to design a user interface (UI) for initiating of our business process which we defined at the beginning. From modeling designing to service consuming, we look after a piece by piece, but more or less, the complete process point of view how to create a enterprise service is clear. VC is the tool that provides a code-free, freestyle modeling development. We are going to create a view with a VC tools afterwards it will be initiated by SAP NW portal integration.

• Create a new model



Creation of starting Expense process model name as composite iview, we will create a VC UI as when the employee make enquires whether the payment is ready for the reimbursement. Again, the finance controller needs to make an order for the payment when the condition is fully meet in case we refer to a decision table.

• Steps what it remains are as follow

Creation of three process UI for Expense Claim Request which include the WDJ/VC design of their initial expense entering

Creation of LOB Project Manger UI for approval

Creation of start process with it will combine the above UI process



6.5 Creation of WDJ iview in Portal

SAP Enterprise Portal (EP) will be in charge of integration for all the development which we went through this guide. It depends on the usage of portal, such as Federate Portal Network(FPN) External Facing Portal(EFP) and Central Portal, the Remote template that create as Java runtime iview can help and achieve to publish our developed composition to Portal Webservice.

• Search for the WebDynpro application inside of Portal content

• Copy the object to the new folder

• Paste as PCD object



7. Remain Tasks The targeted business process for Expense Approval Process hasn't be completed yet for this document. We tried many different ways to create of composite application from service modeling, service provision and service consuming as a single service of iview, WDJ and CAF web service. The next step what we have to do it to publish the service definition in the Services Registry. You specify the services you want to publish by grouping those services. In case of ABAP, SAP R/3 transaction wspbublish will do the task. For the Java case, service classification directly can be done inside of NWDS and use NetWeaver Administrator (NWA), Administrator can configuration of endpoint and publishing to the service registry. As a result, the service is now published and can be searched for in the service registry by name and classification

Again, the project team needs to analysis further looking for the change or extend the existing enterprise service. If there is legacy system which it require to enable to service to the existing enterprise service, then the team need to develop Process Integration by SAP NetWeaver.

More information regarding enhancing enterprise service, refer to the below SDN documentation.

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c0bb5687-00b2-2a10-ed8f-c9af69942e5d

Related Content

Figure 1: Enterprise SOA Development Lifecycle: Enterprise SOA Development Handbook 1.1 End to End Guide for Enterprise SOA Development, page 7 http://www.sdn.sap.com/

Figure 2: NWDI Technical structure: How to Setup an NWDI Track for Composition Environment Development (SAP NetWeaver CE 7.1)

Figure 3: Sequence of setup CE7.1: page 9, RKT for SAP EhP1 for SAP NW CE7.1 Appendix: Installation

Figure 4: SAP Netwever CE and SAP Backend systems, page 13 RKT for SAP EhP1 for SAP NW CE7.1 Appendix: Module 8 - Planning, system Landscape and Administration

Reference document

• Enterprise SOA Development Lifecycle: Enterprise SOA Development Handbook 1.1 End to End Guide for Enterprise SOA Development : http://www.sdn.sap.com

• SOA100 - SAP Enterprise SOA - Fundamentals : SAP Education

• SOA 300 - SAP Enterprise SOA - Design Time Governance in Enterprise SOA : SAP Education

• SOA 400 - SAP Enterprise SOA - Service Consumption : SAP Education

• RKT for SAP EhP1 for SAP NetWeaver Composition Environment 7.1 : SAP Education

• Building a Composite Business Process from Scratch with SAP NetWeaver BPM - Guide 1,2 and 3 Auther:Jie Deng SDN- http:www.bpx.sap.com

• SAP Standard eSOA Readiness Whitepaper, http://service.sap.com/standardsupport


https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c0bb5687-00b2-2a10-ed8f-c9af69942e5d



http://www.sdn.sap.com/

http://service.sap.com/standardsupport



Copyright © Copyright 2009 SAP AG. All rights reserved.

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 herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors 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 Informix 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 other countries.

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 W3C®, 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 license 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 respective logos 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 and services 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 affiliated 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 Group 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.

ESOA Enablement - Project Task Management

Documents

Transcript of ESOA Enablement - Project Task Management