Configuration Services Using SICF and Soamanager PDF

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: 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.
SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

© 2008 SAP AG 1
Configuration of Enterprise Services using SICF and SOA Manager
Table of Contents
Introduction .........................................................................................................................................................3
List of Steps – “How To” .....................................................................................................................................3
Disclaimer and Liability Notice ..........................................................................................................................25

© 2009 SAP AG 2
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 http://esworkplace.sap.com/. 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.

© 2009 SAP AG 3

© 2009 SAP AG 4
2. Go to the ABAP backend ECC system and go to transaction SICF.

© 2009 SAP AG 5
3. Enter the Hierarchy Type as “SERVICE” and then click on the execute button.

© 2009 SAP AG 6
4. Expand the default_host node under Virtuelle Hosts/Services section.

© 2009 SAP AG 7
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.

© 2009 SAP AG 8

© 2009 SAP AG 9
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.

© 2009 SAP AG 10
7. RightClick on the service ECC_PURCHASEORDER003QR selected in step 6. and Click on Activate

Service.

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

© 2009 SAP AG 12
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.

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

© 2009 SAP AG 14
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.

© 2009 SAP AG 15
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: Service
Search Patterns: *ECC_PURCHASEORDER*
Field: Both Names
In System: BH1/200
and then clicking on Go.

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

© 2009 SAP AG 17
15. Go to the Configurations tab under the section “Details of Service Definition:
ECC_PURCHASEORDER003QR” and click on the Create Service button.

© 2009 SAP AG 18
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: ECC_PURCHASEORDER003QR
Description: Purchase Order Item By Account Assignment Query
New Binding Name: ECC_PURCHASEORDER003QR_Binding
Click on the Apply Settings button in the popup.

© 2009 SAP AG 19
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.

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

© 2009 SAP AG 21
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”.

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

© 2009 SAP AG 23
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.

© 2009 SAP AG 24
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.

© 2009 SAP AG 25

Configuration Services Using SICF and Soamanager PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Configuration Services Using SICF and Soamanager PDF

Uploaded by

Copyright:

Available Formats

Configuration of Enterprise

Services using SICF and

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

List of Steps – “How To”

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

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

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

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

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

7. RightClick on the service ECC_PURCHASEORDER003QR selected in step 6. and Click on Activate

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

Disclaimer and Liability Notice

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

You might also like