Professional Documents
Culture Documents
Summary
Summary
Web Services
UDDI
UDDI
Service Directory
2 1
Discover Web service Direct WSDL exchange Create Web service
Develop Client App Create WSDL
Publish WSDL (opt.)
WSDL
WSDL
Document
Document
Web service
Web service
Client
SOAP
Bus. Functionality
Web service Execution Web service Provider
CRM
Get
Employee Employee
Portal Contact
iView Address
Information Information
Archiving
Database
HR
Private
Address
= Web Service
© SAP AG 2005, SAP TechEd ’05 / CD153 / 8
Web Services Overview: Fundamental Elements of the
complete Web Service Solution
Open Technology
Standards for Web
Services
Referent
XML, WSDL, SOAP, UDDI, WSI
to business
semantics
RosettaNet,
Spec2000,
HR-XML,
Web Service XBRL, IFX,
Technology papiNet,
....
SAP NetWeaver
Further information
Working Group: http://www.w3.org/2002/ws/desc/
Specification: http://www.w3.org/TR/wsdl12/
Transport Binding
HTTP, SMTP, …
Message Format
SOAP
Protocol specific data
Header (e.g. quality of service)
…
<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
XI Server Proxy
Virtual Interface
IDOC
Application
Interfaces
Standard
Business
SOAP Web service BAPI
Runtime RFC
Web service
EJB
Java Class
UDDI
UDDI
Registry
WSDL
ABAP Java
Web service
Meta Data
Web service Client
Web service
Application
Proxy
SOAP
Web service
Runtime
Web service
Bus. Functionality
Point-to-Point
“Basic” Web services
Summary
Inside-Out
Start of implementation in the backend system
Interface semantics pre-defined and reflects directly
implementation
Drawback: Implementation details are visible in the interface
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
1
Implement No Web service specific programming
Business Application New or existing applications
Defines standard interfaces
Well known programming models
WS Configuration 2
WS Variant /Definition * Generate
Wizard based approach
Service/Virtual
Web Service Based on preconfigured profiles
Interface* Based on abstract behavior
Available for ABAP & Java
3
Activate /
Deployment in Java
Deploy Web Service
*Note: Activation in ABAP
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.
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.
More expenses
A Service Interface …
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.
getHomeAddress
Employee Default Value street city province country
(I) HM (O) (O) (O) (O)
Virtual
Interface
getEmployeePrivateAddress
Demo
Motivation
A Web service is not only described by its interface but also by its behavior with respect to
stateless/stateful communication,
transactional behavior,
security requirements, …
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: Stateful
Technical Protocols: 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.
Benefits
The same Web Service Variant / Definition can be deployed to
various application servers which may differ in their technical
capabilities
Demo
Deployment as usual
SDM deployment in Java
Demo
Summary
1
From UDDI
Retrieve WSDL Via URL (from server)
From local Server
From File System
From XI repository
2
Generate
Web Service Proxy Environment specific
Available for ABAP & Java
3
Develop
Client Application Focus on Business Application
SOAP / XML handling hidden by proxy
Demo
Create
Proxy
Object
Summary
Q&A