Configuration of Enterprise Services using SICF and SOA Manager

Transcription

1 Configuration of Enterprise Services using SICF and SOA Manager 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: 20 th 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 SAP AG 1

2 Table of Contents Introduction...3 List of Steps How To...3 Disclaimer and Liability Notice SAP AG 2

3 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. List of Steps How To We shall show the configuration by taking one enterprise service as an example. Let us take the example of the enterprise service FIND PURCHASE ORDER ITEM BY ACCOUNT ASSIGNMENT, i.e., we want to configure this enterprise service, say. The steps for the configuration are the same for any enterprise service implemented in ABAP backend. The following steps describes in detail with screenshots of how to configure enterprise services implemented in ABAP backend: 1. Go to ES Workplace Search for the enterprise service Find Purchase Order Item by Account Assignment. This enterprise service can be found here. In the Technical Data section -> Related Web Service Definition, copy the value ECC_PURCHASEORDER003QR for future use. Also note each of the fields like Software Component Version, Release Status, First Release with etc., so that you are absolutely sure that this enterprise service would really be available in the ABAP backend version you are using. In this case, say, the ABAP backend is an ECC 6 system with ES packs 604 installed SAP AG 3

4 2009 SAP AG 4

5 2. Go to the ABAP backend ECC system and go to transaction SICF SAP AG 5

6 3. Enter the Hierarchy Type as SERVICE and then click on the execute button SAP AG 6

7 4. Expand the default_host node under Virtuelle Hosts/Services section SAP AG 7

8 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 SAP AG 8

9 2009 SAP AG 9

10 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 SAP AG 10

11 7. RightClick on the service ECC_PURCHASEORDER003QR selected in step 6. and Click on Activate Service SAP AG 11

12 8. A popup opens after executing step 7. Click on the second Yes button in this popup SAP AG 12

13 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 SAP AG 13

14 10. Enter /osoamanager in the field for entering transaction codes, for running the transaction SOAMANAGER in another session SAP AG 14

15 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 SAP AG 15

16 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 and then clicking on Go SAP AG 16

17 14. Select the enterprise service ECC_PURCHASEORDER003QR from the table and then click on Apply Selection button 2009 SAP AG 17

18 15. Go to the Configurations tab under the section Details of Service Definition: ECC_PURCHASEORDER003QR and click on the Create Service button SAP AG 18

19 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 Click on the Apply Settings button in the popup SAP AG 19

20 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 SAP AG 20

21 18. The enterprise service has been configured successfully and an endpoint has also been created for it 2009 SAP AG 21

22 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 SAP AG 22

23 20. A new browser window opens where you can see the WSDL document for the selected enterprise service and its selected binding SAP AG 23

24 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 SAP AG 24

25 Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document SAP AG 25