Professional Documents
Culture Documents
SAP WebService PDF
SAP WebService PDF
SAP WebService PDF
Agenda
Overview of the Web Service technology
Inside-out approach: Creating a Web Service from existing
business functionality
Demo: Create a Web Service
Consuming a Web Service from an ABAP program
Demo: Consume a Web Service
Summary
Agenda
Overview of the Web Service technology
Inside-out approach: Creating a Web Service from existing
business functionality
Demo: Create a Web Service
Consuming a Web Service from an ABAP program
Demo: Consume a Web Service
Summary
UDDI
UDDI
Service Directory
2
Discover Web service
Develop Client App
WSDL
Document
WSDL
Document
Web service
Web service
Client
SOAP
Bus. Functionality
Web service Execution
3
SAP AG 2005, SAP TechEd 05 / CD153 / 6
Company
Service Provider
CRM
Portal
iView
Get
Employee
Address
Information
Employee
Contact
Information
HR
Private
Address
= Web Service
SAP AG 2005, SAP TechEd 05 / CD153 / 8
Archiving
Database
Open Technology
Standards for Web
Services
XML, WSDL, SOAP, UDDI, WSI
Web Service
Technology
SAP NetWeaver
Referent
to business
semantics
RosettaNet,
Spec2000,
HR-XML,
XBRL, IFX,
papiNet,
....
BPML
CIM
OASIS
SAML
UBL
UDDI 2.0 / 3.0
WSRP
WS-Security
XML.org
Wf-XML
WS-I
Basic Profile 1.0
XMLA
UDDI4J
JAX-RPC
JAXM
and many others
Supported protocols
e.g. SOAP
Network address
e.g. http://a.com/order
Further information
Working Group:
http://www.w3.org/2002/ws/desc/
Specification:
http://www.w3.org/TR/wsdl12/
HTTP, SMTP,
SOAP
Header
Body
Application-specific data
Application Data
Type system
<SOAP-ENV:Body >
<pns:getEmployeePersonalAddress
xmlns:pns="urn:AddressWSVi">
<employeeID >1001</employeeID>
<addressType>HM</addressType>
<actualDate >2005-08-22</actualDate>
</pns:getEmployeePersonalAddress>
</SOAP-ENV:Body >
</SOAP-ENV:Envelope >
Deliverables
Profiles specify conformance requirements for Web services
Testing Tools can be used to test profile conformance
Sample Applications demonstrate interoperable implementations
UDDI
UDDI
Registry
WSDL
ABAP
Java
Web service
Meta Data
WS
Client
RFC
EJB
Java Class
BAPI
Business
Application
Web service
Runtime
IDOC
Standard
Interfaces
Web service
SOAP
Virtual Interface
XI Server Proxy
UDDI
UDDI
Registry
WSDL
ABAP
Java
Web service
Runtime
SOAP
Web service
Web service
Proxy
Web service
Meta Data
Bus. Functionality
Web service Provider
Web service
Client
Web service
Client
SOAP
SAP XI
Integration Server
3rd Party
Adapter
SAP System
XI Protocol
or SOAP
SAP Web AS
6.40
SOAP
Point-to-Point
Basic Web services
Adapter
Agenda
Overview of the Web Service technology
Inside-out approach: Creating a Web Service from existing
business functionality
Demo: Create a Web Service
Consuming a Web Service from an ABAP program
Demo: Consume a Web Service
Summary
Outside-In
Central design of interfaces that make business sense in
SAP XI Integration Repository
Using global data types
Reference to Governance Process for PIC
Generation of proxies from abstractly modeled interface
Implementation of glue code between proxy and business
function
Implementation can be changed without changes in interface
SAP AG 2005, SAP TechEd 05 / CD153 / 26
1
Implement
Business Application
WS Configuration
WS Variant /Definition *
Service/Virtual
Interface*
Generate
Web Service
2
Wizard based approach
Based on preconfigured profiles
Based on abstract behavior
Available for ABAP & Java
3
*Note:
The terms Service Interface
and Variant refer to the ABAP
7.0 implementation They
correlate to Virtual Interface
and WS Definition on the Java
stack and ABAP 6.40 release.
SAP AG 2005, SAP TechEd 05 / CD153 / 27
Activate /
Deploy Web Service
Deployment in Java
Activation in ABAP
Demo
Enter a
name of
the Service
Definition
and select
the endpoint
type.
Select the
Function
Module
Choose
authorization
profile and
release the
Web service
Demo
Overview
page
Result of the
Web service
test.
A Service Interface
provides abstraction from concrete implementation (=endpoint)
allows to publish a view on existing implementations as Web Service Interfaces
i.e. renaming, hiding of parameters/methods, default values
Note: The term Service Interface refers to the ABAP 7.0 implementation. It
correlates to a Virtual Interface on the Java stack and ABAP 6.40 releases.
<SOAP-ENV:Envelope>
<SOAP-ENV:Body>
<ns1:getHomeAddress>
<ns1:Employee>1001</ns1:Employee>
</ns1:getHomeAddress>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Rename
methods
getHomeAddress
Rename
parameters
Employee
(I)
<SOAP-ENV:Envelope>
Response
<SOAP-ENV:Body>
<rpl:getHomeAddressResponse>
<rpl:Response>
<tns:street>10 Main Street</tns:street>
<tns:city>Ottawa</tns:city>
<tns:province>Ontario</tns:province>
<tns:country>CAN</tns:country>
</rpl:Response>
</rpl:getHomeAddressResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Provide
default values and
hide parameters
Default Value
HM
street
(O)
city
(O)
province
e_city
(O)
e_county
(O)
(O)
country
(O)
Virtual
Interface
getEmployeePrivateAddress
i_employee
ID (I)
Implementation
Layer
SAP AG 2005, SAP TechEd 05 / CD153 / 39
i_address
_type(I)
e_street
(O)
e_country
(O)
Demo
Idea
describe this kind of behavior via abstract features
leave it to the Web Service Configurator to assign technical protocols to these
abstract features
Example:
Feature:
Technical Protocols:
Stateful
Stateful via HTTP-Cookies,
Stateful via URL-Extensions
Note: The term Web Service Variant refers to the ABAP 7.0 implementation. It correlates to a
Web Service Definition on the Java stack and ABAP 6.40 releases.
SAP AG 2005, SAP TechEd 05 / CD153 / 42
Demo
Deployment as usual
SDM deployment in Java
Demo
Agenda
Overview of the Web Service technology
Inside-out approach: Creating a Web Service from existing
business functionality
Demo: Create a Web Service
Consuming a Web Service from an ABAP program
Demo: Consume a Web Service
Summary
1
From UDDI
Via URL (from server)
From local Server
From File System
From XI repository
Retrieve WSDL
Generate
Web Service Proxy
Develop
Client Application
2
Environment specific
Available for ABAP & Java
3
Focus on Business Application
SOAP / XML handling hidden by proxy
Demo
Create
Proxy
Object
Agenda
Overview of the Web Service technology
Inside-out approach: Creating a Web Service from existing
business functionality
Demo: Create a Web Service
Consuming a Web Service from an ABAP program
Demo: Consume a Web Service
Summary
Summary
The Enterprise Service Architecture (ESA), SAPs
approach for building services-oriented business
applications utilizes Web Services as vital part of its
communication and integration strategy
SAPs rich business functionality, in conjunction with
state-of-the-art technology, enables you to establish
cross-company business processes as an integrated
part of your development efforts based on Web Services
SAP NetWeaver Application Server offers an easy,
convenient way to build Web services
Questions?
Q&A
SAP AG 2005, SAP TechEd 05 / CD153 / 55