OCI Architecture En
-
Upload
rohan-punith -
Category
Documents
-
view
111 -
download
1
Transcript of OCI Architecture En
Peter Schwarze
Developer, SAP AG
OCI/OPI Architektur
SAP AG 2003, Title of Presentation, Speaker Name / 2
OCI/OPI Overview
Service Provider
InternetbrowserInternetBrowser
With the OCI resp the OPI it is possible to integrate service providers no matter wetherthey are located in the intranet or the internet
Internet
SRM ServerService Provider
IntranetUser
SAP AG 2003, Title of Presentation, Speaker Name / 3
OCI/OPI Architecture I: Call of the Services
Service Provider
InternetbrowserInternetBrowser
1. The SRM Server application shows the available service providers (product catalogs resp. vendor directories).
2. After the user has chosen one of them, the user will be redirected to the according web site. Therefore the parameters will be used, that have been maintained in the SRM Server customizing previously.
1. URL and parameters
2. HTTP Request with URL und parameters
SRM Server
SAP AG 2003, Title of Presentation, Speaker Name / 4
OCI/OPI Architecture II: Taking over Data into the SRM Server application
Service Provider
InternetbrowserInternetBrowser
1. The service provider creates a HTML page containing oci/opi compliant data. 2. The user sends this data to the SRM Server. 3. The SRM Server application takes over this data.
3. HTTP Request with form data
1. Form containing OCI/OPI data in a HTML-
page
SRM Server
2. submit
SAP AG 2003, Title of Presentation, Speaker Name / 5
Architecture I (detail): Call in external window
1. Call the JavaScript function launchCatalog() (This opens up browser window B).
2. Request containing the catalog ID and an OKCode to trigger the call of the selected catalog (automatic).
3. Response from EBP: HTML page with a form containing the URL and the parameters to call the catalog (this form submits itself and builds the request in 4.).
4. Request to the catalog (via the form from 3.).5. Response from the catalog.
1.
2.
3.
4.
5.
ITS SRM Server
A
B
Catalog Server
SAP AG 2003, Title of Presentation, Speaker Name / 6
Architecture II(detail): Data import
1. Response page from the catalog containing form with OCI data (including the Hook URL and the OKCode).
2. Now the user presses a button to submit this form to the EBP 3. The Form is sent to the EBP as a request 4. The EBP sends a response from the Application. The parameter
~caller triggers the file catalogback.htm (from service bbpglobal) to be included in the response template
5. The coding in catalogback.html triggers window A to refresh, and closes down window B.
5.
3.
1.
ITS SRM Server
A
B
Catalog Server
Submit
4.
2.
SAP AG 2003, Title of Presentation, Speaker Name / 7
Customizing I
SAP AG 2003, Title of Presentation, Speaker Name / 8
Customizing II
SAP AG 2003, Title of Presentation, Speaker Name / 9
Customizing III
SAP AG 2003, Title of Presentation, Speaker Name / 10
Customizing IV
SAP AG 2003, Title of Presentation, Speaker Name / 11
Customizing V
SAP AG 2003, Title of Presentation, Speaker Name / 12
Function group BBP_WS_API for integration of external Web Services such as OCI/OPI
SAP AG 2003, Title of Presentation, Speaker Name / 13
Business Add ins
IF_EX_BBP_CAT_CALL_ENRICH Zusätzliche Name/Wert Paare können an den Web Service
übertragen werden
IF_EX_BBP_CATALOG_TRANSFER Die aufbereiteten Schnittstellendaten können vor der Rückgabe an
die rufende Anwendung verändert werden
SAP AG 2003, Title of Presentation, Speaker Name / 14
END
Questions ?