Skip to end of metadata
Go to start of metadata

Contents


 

How to Find Business Application ID in a Web Service Provider System

This article describes how to get the business application ID of a Web service provider system for business scenario configuration in a Web service consumer system.

When business system adminstrators want to set up business connections between ABAP back-end systems via business Scenario Configuration in the consumer system an entity representing the Web Service Provider System called "Provider System" is required. This entity requires the business application ID in order to be able to search for bindings of services for that provider system in services registry or WSIL document.

Concept

Business application ID is used in business scenario configuration to search for bindings of services in the Services Registry. With the help of the business application ID a certain binding of a service can be determined on a specific provider system. Therefore the business application ID has to be known by the consumer system in order to be able to search for bindings by the ID of a certain system in order to configure a consumer against the binding.

Prerequisites

Business application ID is only  used in case of business scenario configuration.

Constraints

Although Business Application ID is used in Central Business Scenario Configuration there is no need of manual interaction in this case as the whole process in closed ABAP landscapes is done by the central system.

Procedure

To get Busines Application ID of a Provider System and enter it into consumer systems SOAManager, perform the following steps:

 

1. Start SOA Manager on Provider System.
Use the transaction code SOAMANAGER.

SOA Manager is a WebDynpro ABAP application. For this reason, its ICF node needs to be active. You can use transaction SICF to check that the ICF node for SOA Manager (/sap/bc/webdynpro/sap/appl_soap_management) is active.
More information: SAP Note 1124553

2. From the main screen of the SOA Manager, go to the Technical Administration tab.

3. Choose SAP Client Settings.

4. In GroupServices Identifier you will find the following Identifier.

  • Organisation Name
  • Business System
  • Business System ID
  • Business Application ID
    This is the Business Application ID used in the consumer system to identifiy the provider system and used for searching bindings in services registry or WSIL.

Copy this ID and insert it in consumer system's SOAManager in the corresponding Provider System Entity as Business Application ID on tab Business Applications (Step 8).

 

5. Start SOA Manager on Consumer System.
Use the transaction code SOAMANAGER.

SOA Manager is a WebDynpro ABAP application. For this reason, its ICF node needs to be active. You can use transaction SICF to check that the ICF node for SOA Manager (/sap/bc/webdynpro/sap/appl_soap_management) is active.
More information: SAP Note 1124553

  6. From the main screen of the SOA Manager, go to the Technical Administration tab.

7. Choose Provider Systems.

Mark the corresponding Provider System and choose Edit. Click on Next, click on Next.  

8. Create or Edit Business Application.

If no application is present yet, create the following entry:
Name: sap.com/BusinessApplicationABAP
Description: <Business System as specified in Provider System´s SOAManager>
Business Application ID: <Business Application ID as specified in Provider System's SOAManager>
If an application with name sap.com/BusinessApplicationABAP is present, choose Edit and insert the copied Business Application ID.

Save your settings.

   

Result

Now in the consumer system the correct information for searching of Service Bindings is present and consumer side Business Scenario Configuration can be performed on the consumer system. Prerequisite for successfull consumer configuration is that on provider system the requested Services Bindings are created beforehand.

  • No labels