Thank you for interesting in our services. We are a non-profit group that run this website to share documents. We need your help to maintenance this website. Please help us to share our service with your friends. Share Embed Donate. All rights reserved.

Author:Samurr Tezahn
Language:English (Spanish)
Published (Last):1 August 2015
PDF File Size:5.20 Mb
ePub File Size:19.14 Mb
Price:Free* [*Free Regsitration Required]

Thank you for interesting in our services. We are a non-profit group that run this website to share documents. We need your help to maintenance this website. Please help us to share our service with your friends. Share Embed Donate. 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. Additionally this publication and its contents are provided solely for your use, this publication and its contents may not be rented, transferred or sold 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. All other products mentioned are trademarks or registered trademarks of their respective companies. About This Handbook This handbook is intended to complement the instructor-led presentation of this course, and serve as a source of reference. It is not suitable for self-study. Typographic Conventions American English is the standard used in this handbook.

The following typographic conventions are also used. Type Style Description Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths, and options. Also used for cross-references to other documentation both internal in this documentation and external in other locations, such as SAPNet. Example text Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, and passages of the source text of a program.

Example text Exact user entry. These are words and characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

Your training course administrator will name the system for you together with the training clients and other specifications. Please only use this system and these clients for your course. Demonstration and exercise data: As a rule, the necessary data will have been generated for your training course clients beforehand. If in exceptional cases this has not been done, if the course is being held at a customer site for example , you will need to run the data generation progam. You will then be prompted to specify the type and quantity.

User IDs and initial passwords for participants: You can use the adm user ID and the corresponding adm password to log on to the system and then copy a separate user using the SU01 transaction. Unlike the application data, you must always re-create the user IDs. Please use your own user ID as a template when copying.

Change requests and customizing requests for participants: We recommend that you simulate project work. In other words, create a change request and customizing request with tasks for each user group. General notes on the overall course: The time specifications are provided as a recommendation only. However you must ensure that the full content can be presented.

Sections that contain key points for the participants should be presented in comprehensive detail. These sections generally provide the basis for the corresponding exercises also.

The material provided should allow the participants to work through the course again on their own. It therefore contains numerous explanations and additional information. Your task is now to emphasize the most important points. The figures displayed in the HTML presentation and the points they illustrate should form a crucial part of this process.

These notes can be used to lead on to more detailed notes in each unit and again in each lesson. In addition, the material will always contain further detailed notes wherever we consider it necessary to the success of the presentation. Otherwise an error message is displayed when you create the Web service client proxy.

If you do not do this, the participants will be mutually locked out during proxy generation. Unit Overview This unit provides an introduction to Web services. Business Example You want to describe the Web service paradigm and the standard Internet technologies used in combination with Web services.

What is a Web service? Business processes are divided into a certain number of process steps. You can assign one or more functions to each of these steps and an executing software component to each of these functions. If you look at a typical heterogeneous system landscape in an organization, it is quickly apparent that the necessary functions in a business process are not all implemented using the same technology and the same components.

In particular, the integration of an ever increasing number of business partners further complicates this problem. A modern software infrastructure must therefore be capable of integrating functions that are implemented on very different software components into an efficient global process. Internet technology already provides the basis for communicating with distributed services. Superimposed onto this simple, globally accepted communication standard, XML eXtensible Markup Language provides the basis for defining additional necessary standards.

It is only when we turn away from proprietary definitions and move towards generally accepted standards that there can be any guarantee of smoothly integrating all of the functions and partners involved in the process. The result is Web services. Based on XML standards, these application functions can be described, made available, located, transformed, or called via standard Internet protocols.

Each Web service therefore encapsulates a piece of functionality that can be used, for example, to forward a price query to a provider, check the availability of an item in an enterprise resource planning system, locate a telephone number, or even to run credit card checks, convert currencies, or implement payroll functionality. In principle, any programming language can be used to implement this service. When publishing a service, the service provider transmits information about itself and a description of the service it is offering and transfers this to the service registry.

In addition to other data, it also provides information on calling the Web service, for example. The service registry therefore provides a description of the Web service only. This description forms an abstraction layer and is therefore not dependent on the corresponding implementation. The Web service itself is hosted by the service provider. The user of a Web service is called a service requester. A service requester can be, for example, someone who locates a Web service using a Web browser and then uses this service.

In most cases however, the service requester is an application that accesses the Web service. However, if the application recognizes the provider and the call details, it can obviously use the Web service without having to access the service registry. If Web services are to be called from any application, a standardized description is required. The Web service provider must also be able to make its offer publicly available as easily as possible.

The specification provides a detailed description of how to locate and register services. SOAP provides a more straightforward standard that allows you to call Web services in decentralized, distributed landscapes. SOAP defines what is known as an Envelope.

This Envelope contains the actual XML-based message and additional information on how the message is to be processed, for example.

A further series of conventions was also adopted for describing the technical constraints. XML documents are increasingly used to support the exchange of business documents and messages, and thereby strengthen cooperation between companies. This protocol is used to call Web services in distributed system landscapes.

A SOAP message has a header additional information concerning security and transaction and a body content of the message. WSDL documents are broken down into the names of the services, messages that are exchanged to use these services, links to specific transport protocols, and addresses at which a Web service is available. UDDI is different from other registry services insofar as it does not store documents or specifications, but only references them. The literature often uses the terms Publish, Find, and Bind in this context.

These refer to the interaction between the roles of service provider, service registry, and service requester: Publish: A Web service provider registers its Web service on an UDDI server.

This process is known as publishing. This can be carried out by querying an UDDI server for example, which can take place at two stages: At design time, in order to obtain the necessary information for the application, or at runtime, in order to dynamically retrieve the binding information.

Bind: To be able to communicate with a Web service at runtime , the Find operation is used to determine the binding information and the Bind operation is used to locate and contact the Web service.

The following figure shows how a Web service can be used to integrate a credit card check into a process landscape. We can do this by searching for a publicly available Web service on the pages of www. As this Web site is updated regularly, only the basic procedure is described in the following steps. When preparing for the course, it is essential that the course instructor visits this Web site and searches for a suitable Web service. For example, the eBay Price Watcher Web service is available on the pages of www.

Click the name of the Web service to get detailed information on the Web service. You can see the WSDL description. The WSDL description required for this can be generated automatically.

If asked, point out to customers that Web services in 6. After an upgrade, you only need to call a Web service wizard once to reconfigure the service. SAP provides a standardized architecture and set of tools for creating Web services. This means that SAP users can provide Web services with a minimum of effort.


BC416 - ABAP Web Services.pdf

Facebook Google Twitter. Password Hide. Remember me. I agree to the Terms.


ABAP Web Services

Due to the temporary closure of training centers current status here , all planned classroom training courses in the affected countries have been converted to our virtual learning method SAP Live Class until further notice - thus the original offer is still fully available in these countries. Re-opening of the International Training Centre in Walldorf as of 15 June in compliance with the necessary hygiene regulations and safety precautions. For more details please check our FAQ. Is the course not scheduled? Or looking for other dates and locations that fit your schedule?


SAP BC 系列教程(BC400至BC680)免费下载


Related Articles