Professional Documents
Culture Documents
Applies to:
SAP NetWeaver 7.0 SP14 and above. For more information, visit the SOA Management homepage.
Summary
This document will provide a complete reference to configuring enterprise services for consumption in applications using the SICF and SOAMANAGER transactions. Author: Somnath Roy
Company: IBM India Pvt Ltd. Created on: 20th April 2009
Author Bio
Somnath Roy is working in IBM India as a SAP SOA Architect and developer and is engaged in the architecture, design and development of eSOA based composite applications using BPM, CAF, GP, Java Web Dynpro, EP. He has more than 4.5 years of experience in enterprise application development in SAP NetWeaver and Java/J2EE technologies.
Table of Contents
Introduction .........................................................................................................................................................3 List of Steps How To .....................................................................................................................................3 Disclaimer and Liability Notice ..........................................................................................................................25
Introduction
Any ESOA implementation requires enterprise services. Most of the enterprise services are ABAP based and a majority of these are SAP provided ABAP based enterprise services, i.e., enterprise services that have been implemented in ABAP. But to consume these enterprise services in applications, some configuration like creating endpoints, etc. is required for the enterprise services in the ABAP backend system. From SAP NetWeaver 7.0 SP14 onwards, the WSADMIN and WSCONGFIG transactions are obsolete and a new transaction SOAMANAGER has been introduced to administrate, configure and monitor the service definitions. SOAMANAGER helps to browse and configure the service definitions created from the ABAP system. This document gives all the steps required for this configuration using SOAMANAGER transaction in the ABAP backend system.
2.
3.
Enter the Hierarchy Type as SERVICE and then click on the execute button.
4.
5. Go to the node default_host/sap/bc/srt/xip/sap. All the enterprise services that are included in the ES pack that you have installed would be visible under this node.
6. Since you have copied the service ECC_PURCHASEORDER003QR in step 1. above, select the service ECC_PURCHASEORDER003QR under the node default_host/sap/bc/srt/xip/sap node. Note that the service is grayed because it has not yet been activated.
7. RightClick on the service ECC_PURCHASEORDER003QR selected in step 6. and Click on Activate Service.
8.
A popup opens after executing step 7. Click on the second Yes button in this popup.
9. The service is activated successfully. Note that the activation is client specific, i.e., if you activate a service in client 100 and try to run it using client 200 from the consuming application, it would not run.
10. Enter /osoamanager in the field for entering transaction codes, for running the transaction SOAMANAGER in another session.
11. A browser session starts along with a new session in the ABAP backend. Enter the username and password for the ECC system when the browser asks for the credentials.
12. After executing step 11, SOAMANAGER opens. Go to the Business Administration tab of the SOAMANAGER. Click on the Web Service Administration link.
13.
Search for the Enterprise Service ECC_PURCHASEORDER003QR by entering the following values: Search by: Search Patterns: Field: In System: Service *ECC_PURCHASEORDER* Both Names BH1/200
14. Select the enterprise service ECC_PURCHASEORDER003QR from the table and then click on Apply Selection button
15. Go to the Configurations tab under the section Details of Service Definition: ECC_PURCHASEORDER003QR and click on the Create Service button.
16. After executing step 15, a popup opens. Here you would provide all the parameters that are required for the service name, description and the creation of endpoints to the service. Fill the fields with the following values though you can give any other values according to your choice. New Service Name: Description: New Binding Name: ECC_PURCHASEORDER003QR Purchase Order Item By Account Assignment Query ECC_PURCHASEORDER003QR_Binding
17.
Scroll down below and go to the Provider Security tab. Select the following options No Transport Guarantee under the section Transport Guarantee - > Transport Guarantee Type.
User ID/Password under the section Authentication Settings -> Authentication Method -> HTTP Authentication. Leave all other fields in default. You may choose other options as well based on your requirements. Then click on the Save button.
18.
The enterprise service has been configured successfully and an endpoint has also been created for it
19. To see the WSDL document for the binding, select the enterprise service ECC_PURCHASEORDER003QR and go to the Overview tab. Click on the second link Open WSDL document for selected binding.
20. A new browser window opens where you can see the WSDL document for the selected enterprise service and its selected binding.
21. To test the enterprise service with the binding created, select the enterprise service ECC_PURCHASEORDER003QR and go to the Overview tab. Click on the third link Open Web Service navigator for selected binding. A new browser would open where you can test the service after giving your credentials.