Skip to end of metadata
Go to start of metadata

Since Solution Manager 7.2 SP08, SAP has delivered standard tool for automatic detection of Interfaces in the Managed Systems.

For more information on features, please see below.

 

What does Interface Discovery Provide?

 

General Features

  • Delivered with SAP Solution Manager 7.2 SP08. For a list of features available in the different Solution Manager SPs see below.
  • No add-on needed
  • Supports multiple technologies for interfaces in the managed systems
  • Built-in integration with Integration Repository
  • Extracts Interfaces from managed systems and stores interface data in SAP Solution Manager
  • Supports integration into Interface Monitoring

Solution Manager 7.2

SP10

  • Interface Discovery for Web Service

SP08

  • Interface Discovery for IDoc and qRFC

 

 

 

 

 

 

 

 

 

Interface Discovery helps you scan managed systems for interfaces and import the result into Integration Repository in Solution Manager. It is a two step process where you first initiate data collected in managed system and then import it into Integration Repository in Solution Manager. 

Interface Discovery is offered for managed systems with ST-A/PI release 01T*. 

IDoc Discovery

For technical prequisites, please see this.

Data Collection in Managed Systems

To trigger data collection for IDoc, please follow the below steps:

  1. In the Managed System, please execute report /SSA/EIM.
  2. In the seection screen of the report, select the IDoc Interface Disocvery option and select the available options (client, direction)
  3. Execute the report in background
  4. As soon as the report is successfully finished, you will get the data from Solution Manager
Import Discovered IDocs into Interface Repository

After performing data collection, please follow the below steps to import IDocs in Interface Repository:

  1. Go to Solution Manager Launchpad using transaction SM_WORKCENTER
  2. Launch transaction AGS_DCM_EXT_IMPORT. Otherwise, select the tile 'Integration Repository Tools' in the group 'Data Consistency Management' on Solution Manager Launchpad ( SP10 onwards )
  3. Select the tab 'Discovery'
  4. Choose 'IDoc' as Technology and choose relevant RFC Destination of the Managed System. Choose also a variant and direction for IDoc and click 'Get Data'. For descriptions on the variant, please see below table.

  5. Your IDocs are ready to be imported. Generate a JSON file.
  6. Now you can start Solution Administration (transaction SLAN) and use the generic import feature to upload the generated JSON file to the solution. See SAP online help at http://help.sap.com/ -> Technology Platform -> SAP Solution Manager -> SAP Solution Manager 7.2 -> Application Help (SAP Library) -> Process Management -> Solution Administration -> Import and Export of Content to find all details of Solution Administration’s import feature.

    Variant Descriptions for IDoc Discovery
    Variant Name
    Description

    Customized Interfaces

    IDocs which are customized in transaction WE20 in the managed system.

    Active Interfaces

    Customized IDocs with runtime information available in database table EDIDC in the managed system.

    Inactive Interfaces

    IDocs with runtime data in table EDIDC but no customizing available (anymore).

    Summarized Interfaces

    Aggregation of active IDocs on partner port, partner type and partner function for sender and receiver. Partner number is not available anymore after aggregation.

    Note that message processing function module name is not available for Customized Inbound Interfaces.

qRFC Discovery

For technical prequisites, please see this.

Data Collection in Managed Systems

To use this, please implement SAP Note 1042040 in the Managed System.

After successful implmentation of the note, please follow the below steps:

    1. execute the report /SSA/EIM in the Managed System
    2. In the selection screen, select option “Administration of qRFC Throughput Monitoring" and select generate program for qRFC integration by selecting the below option and press 'Execute'.

      Tip

      If you get a message saying the program is already generated, it is better to delete the program and regenerate it again just to avoid the case where the generated program is very old. You can delete the program by selecting the option 'Delete program to stop qRFC integration into ST-A/PI' and pressing Execute.



    3. Next, select “Administration of qRFC Table Shadowing". Activate the qRFC Table Shadowing and select the directions you would like to monitor.
    4. After a specific time interval (1 day or 1 week), Table Shadowing should be deactivated.
    5. Last step is to collect and store the qRFC statistics by choosing the below option and pressing execute. 
    6. On pressing execute, you get the below popup. Please choose the options marked for both 'Analyze Inbound Queue' and 'Analyze Outbound Queue' and press execute.
      1. Aggregation by second gives you the actual timestamp of the qRFCs found in your system
      2. You could also group by RFC Destination Name and Function Module Name
      3. It is important that you select the option 'Save result to /SSF/BTAB' to save the result for further use in Integration Repository.
      4. Length of the Queue Name Prefix can be changed (and based on this qRFC calls will be aggregated on your result list). Greater the length of Queue Name Prefix, lesser the aggregation.

                     


Import Discovered qRFCs into Interface Repository

After performing data collection, please follow the below steps to import qRFCs in Interface Repository:

    1. Go to Solution Manager Launchpad using transaction SM_WORKCENTER
    2. Launch transaction AGS_DCM_EXT_IMPORT. Otherwise, select the tile 'Integration Repository Tools' in the group 'Data Consistency Management' on Solution Manager Launchpad ( SP10 onwards )
    3. Select the tab 'Discovery'
    4. Choose 'qRFC' as Technology and choose relevant RFC Destination of the Managed System. Choose also a direction for qRFC and click 'Get Data'.
    5. Generate a JSON file after selecting the interfaces and start Solution Administration (transaction SLAN). Use the generic import feature to upload the generated JSON file to the solution.

Web Service Discovery

Introduction

With Solution Manager SP10, Web service technology is added to the Interface Discovery application. Until SP09, technologies IDoc and qRFC were supported. For Web services, you can choose between service providers and consumer proxies. Service providers represent the server side where the source system of the data extraction is providing the Web service. The consumer proxies represent the client side where the source system is calling a Web service from another system. 

The new functionality is part of Interface Discovery and therefore implemented in ST-A/PI. The data extraction can be run in every ABAP managed system where ST-A/PI is installed. 

For technical prerequisites, please see chapter Technical Prerequisites.

Data Collection in Managed Systems
  1. Execute program /SSA/EIM from SE38 
  2. Select the option “Web Service Discovery – Data Collection” 
  3. Mark the object types Provider and/or Consumer 
  4. Flag the checkbox “Save result to table /SSA/BTAB” 
  5. Execute the program. Alternatively, you can as well run the data extraction in background as it might take several minutes.
Import Discovered Web Service Interfaces into Interface Repository

After performing data collection, please follow the below steps to import Web Services into Interface Repository:

  1. Go to Solution Manager Launchpad using transaction SM_WORKCENTER
  2. Select the tile 'Integration Repository Tools' in the group 'Data Consistency Management' on Solution Manager Launchpad ( SP10 onwards ). Alternatively, launch transaction AGS_DCM_EXT_IMPORT. 
  3. Select the tab 'Discovery'
  4. Choose 'Web service' as Technology and choose relevant RFC Destination of the Managed System. Select the variant(s) for which you have executed the data extraction and press 'Get Data'.
  5. Generate a JSON file after selecting the interfaces and start Solution Administration (transaction SLAN). Use the generic import feature to upload the generated JSON file to the solution.


RFC Discovery using Unified Connectivity (UCON)

Introduction

With Solution Manager SP11, RFC Discovery is added to the Interface Discovery application. Until SP10, technologies IDoc, qRFC and Web Services were supported. RFC Discovery using UCON enables you to track all incoming RFC Calls to your managed system. This interface discovery approach accesses runtime information from the UCON tables. For more details on UCON, please check here.

The new functionality is part of Interface Discovery and therefore implemented in ST-A/PI. The data extraction can be run in every ABAP managed system where ST-A/PI is installed. 

For technical prerequisites, please see chapter Technical Prerequisites.

Data Collection in Managed Systems
  1. Execute program /SSA/EIM from SE38 
  2. Select the option “RFC Discovery – Data Collection” 
  3. Enter the system client for which you want to retrieve the interface data.
  4. Flag the checkbox “Save result to table /SSA/BTAB” 
  5. Execute the program. Alternatively, you can as well run the data extraction in background.
Import Discovered RFC Interfaces into Interface Repository

After performing data collection, please follow the below steps to import RFC interfaces into Interface Repository:

  1. Go to Solution Manager Launchpad using transaction SM_WORKCENTER
  2. Select the tile 'Integration Repository Tools' in the group 'Data Consistency Management' on Solution Manager Launchpad ( SP10 onwards ). Alternatively, launch transaction AGS_DCM_EXT_IMPORT. 
  3. Select the tab 'Discovery'
  4. Choose 'RFC (UCON)' as Technology and choose relevant RFC Destination of the Managed System. Then, press 'Get Data'.
  5. Select the interfaces you would like to import and generate a JSON file using the 'Download JSON' option.
  6. Start Solution Administration (transaction SLAN). Use the generic import feature to upload the generated JSON file to the solution.


RFC Discovery using STAD subrecords

This feature is planned for SP12.You select the data in the managed system as follows:

  1. In the Managed System, open the report /SSA/EIM.
  2. In the selection screen of the report, select the RFC Discovery – by collecting STAD RFC subrecords.
  3. Enter the timeframe for which you want to retrieve the interface data.
  4. Select Schedule periodic background job with selected timeframe and save data. Execute F8. Confirm the popup that you accept the system load.
  5. This will schedule a periodic background job. The job reads all STAD statistical records, doing one RFC dialog process per server in parallel. On systems with high RFC load it usually takes several job executions to collect a timeframe of e.g. one day. If the end date/time is in the future, then the periodic job will run until end of timeframe. The periodic job stops automatically ends after all data for timeframe are collected. If a new background is started without deleting previous results, then results will be merged. At same time a warning appears that results are a merge of different scan runs.


When the data collection is finished, you can perform the following steps to import the RFC interfaces into Interface Repository:

  1. On the SAP Solution Manager launchpad, go to the Data Consistency Management launchpad group and open the Integration Repository - Tools

Alternatively, launch transaction AGS_DCM_EXT_IMPORT.

  1. In the Integration Repository - Tools app, select the Discovery.
  2. Choose RFC (STAD<) as technology and choose the relevant RFC Destination of the Managed System.
  3. Choose Get Data.
  4. Select the interfaces you would like to import and generate a JSON file using the Download JSON option.
  5. Start Solution Administration (transaction SLAN). Use the generic import feature to upload the generated JSON file to the solution.



















Import from Enterprise Service Repository of SAP Process Integration

As a prerequisite for the import of ESR data an HTTP destination to the PI / PO system must be at hand as described in section Technical Prerequisites.

The import is done via the generic import feature of Solution Documentation. To prepare the data for import a text file in JSON format must be created in advance. This is done in application "Integration Repository Tools" in Solution Manager Launchpad that is accessible via transaction SM_WORKCENTER or via transaction AGS_DCM_EXT_IMPORT.

Choose the tab SAP PI/PO. The UI lets you select the source and target data step-by-step.


First, in section Solution and Source Branch, you have to select the solution context you like to import the data to (solution, branch). In section Select PI System, you select the relevant PI component from which the data shall be imported. Note that only PI components show up which are part of the solution you like to import the data to.


Next, in section Select Interfaces from Enterprise Service Repository, you can choose interfaces from the PI ESR based on Software Component Version and Namespace as available in the ESR. The navigation works from left to right, i.e. all objects are displayed which belong to the Software Component Version and Namespace selected before. With the arrow buttons, you can add and remove interfaces to the selection.

In section Specify Additional Interface Data for Solution Documentation, the interface to be imported must be aligned with the data model of Integration Repository. This particularly means that you have to set the PI Installation Type as well as the Sender Adapter technology and the Receiver Adapter technology. This information is not provided by the SAP PI ESR and thus must be set manually.


Finally, you can generate a JSON file with the Download JSON button. The system asks you to save the file to a location on your local PC. A preview of the JSON file is available after download.


Now you can start Solution Administration (transaction SLAN) and use the generic import feature to upload the generated JSON file to the solution. See SAP online help at http://help.sap.com/ -> Technology Platform -> SAP Solution Manager -> SAP Solution Manager 7.2 -> Application Help (SAP Library) -> Process Management -> Solution Administration -> Import and Export of Content to find all details of Solution Administration’s import feature.

Integration Directory of SAP PI/PO

With Solution Manager SP10, there exists a new integration of SAP Process Integration (PI) / Process Orchestration (PO) with the Integration Repository. There was already since Solution Manager 7.1 an integration with PI/PO, however it only extracted information from the Enterprise Service Repository (ESR). The ESR contains all available integration scenarios from PI side. It does not contain any information about which scenarios are configured and running. Therefore, enhanced integration is to connect to the Integration Directory of PI to retrieve configuration data combined with available runtime information. 

For technical prerequisites, please follow this page.

Logical Ports Creation

For each Web Service in consideration, depending on the installation stack of your PI System, follow the below procedure both in the PI system and Solution Manager.

In your PI system:

  • Open your Enterprise Services Repository. For this, get the URL of your PI system and append it with '/dir'.
  • Choose Services Registry under Enterprise Services Repository
  • Under Service Definition, search for the service name mentioned on the prerequisites page.
  • Select the tab Endpoint and under the section General, copy the path suffix of the service. For example, for the web service AdapterMessageMonitoring, the path suffix would be: /AdapterMessageMonitoring/basic?style=document

In your Solution Manager:

  1.  Go to transaction SPROXY in your Solution Manager and under the Namespaces, select http://sap.com/xi/BASIS.
    1. Under this namespace, select Object Types and then select Service Consumers.
    2. Under Objects, you will find the Web Services listed. For example, in the case of Dual Stack installation, you will find SenderAgreementIn listed as one of the services.
    3. Double Click on the service name. You will find Properties tab of the service. 
    4. Copy the ABAP Name of the Service from the Properties tab.
  2. Go to transaction LPCONFIG.
    1. Create a Logical Port ( Best Practice to use the ABAP Name from SPROXY and append '_<SystemID>' ) for each service per PI system.
    2. Keep the ABAP Name of the service as proxy class of the Logical Port.
    3. On the Global Settings tab of the section 'Application-Specific', mark 'State Management'.
    4. Choose Call Parameters tab.
      1. Set the HTTP Destination to your PI system's HTTP Destination SOL_API_<system id>.
      2. Paste the Path Suffix copied from the directory of your PI System for the service.
    5. In case this is the first Logical Port for the service, mark it as default port.
    6. Activate the Logical Port
Testing of Logical Ports created
  1. Go to transaction SPROXY in your Solution Manager.
  2. Double click on the Service.
  3. Click 'Test' icon on the tool bar.
  4. Enter the name of the Logical Port created for this service and for the system in scope (Value help may not work).
  5. Choose a Method using Value Help. For our example now, we will choose Query.
  6. Click Execute.
  7. From the toolbar, click 'XML Editor' icon.
  8. Remove the Section with tag <AdministrativeData>.
  9. Remove the section with tag  <Description>.
  10. Change all the attributes to * and press Execute.

  11. Evaluate the response and if you get the correct response, the Logical Port works right.
Execution Steps
  1. Launch the Integration Repository Tools application using the corresponding tile in the group Data Consistency Management SAP Solution Manager Launchpad. If the tile is not available, you can as well use transaction AGS_DCM_EXT_IMPORT. You have to select the solution context you like to import the data to (solution, branch). In PI System, you select the relevant PI component from which the data shall be imported. Note that only PI components show up which are part of the solution you like to import the data to.

  2. Stay on the tab 'Integration Directory' and choose the Logical Ports using the value help and press 'Get Data'. This is will display the interfaces from your PI system with runtime data. The Logical Ports have to be configured as described in the prerequisites.


    Note

    When the data is retrieved, you can see the interface attributes like communication channel or sender and receiver service in the attributes table below. The attributes table only shows entries when only one interface is selected in the header table.

  3. Choose the Interfaces you want to download, and then click 'Download JSON' at the top.


  4. Now you can start Solution Administration (transaction SLAN) and use the generic import feature to upload the generated JSON file to the solution. See SAP online help at http://help.sap.com/ -> Technology Platform -> SAP Solution Manager -> SAP Solution Manager 7.2 -> Application Help (SAP Library) -> Process Management -> Solution Administration -> Import and Export of Content to find all details of Solution Administration’s import feature.



With Solution Manager SP09, SAP delivered UI5 application Interface Search and Mass Maintenance allows searching for documented interfaces in Solution Manager and perform mass changes on these interfaces.

What is it?

This application helps you:

  • Update common attributes of multiple interfaces all at once. This means for the same interface technology, you can change all the attributes. With different technologies, you can only change a few or no attributes 

  • Avoid manually updating each interface one by one with the same value


You can change the displayed columns using the table settings 

How to use it?

This feature is planned for SP12.To perform mass maintenance on Interfaces maintained in Integration Repository, please follow the below steps:

  1. Open Solution Manager Launchpad using transaction SM_WORKCENTER
  2. Choose the tile Integration Repository Mass Maintenance
  3. Filter the result by entering the following mandatory parameters and hit Go. You can as well use the other search parameters to further restrict the results. 

    1.  Solution ID 

    2. Branch Name (fe. Operations) 

    3. System Role ID 

  4. Select the interfaces you would like to update and press edit button to maintain the values in Integration Repository. 


S/4 HANA Impact Analysis is performed on the caller program or called Function Modules of the interfaces documented in Integration Repository. This is done by executing ATC Check remotely in a Central Check System. To perform Impact Analysis please follow the below steps:

  1. Open Solution Manager Launchpad using transaction SM_WORKCENTER
  2. Choose the tile Integration Repository Mass Maintenance
  3. Filter the result by entering the following mandatory parameters and hit Go. You can as well use the other search parameters to further restrict the results. 
    1.  Solution ID 
    2. Branch Name (fe. Operations) 
    3. System Role ID 
  4. Select the interfaces you would like to update and press Impact Analysis button to maintain the values in Integration Repository. 
  5. A dialog opens and you need to enter the RFC Destination to central check system, managed system for which you would run the ATC check, check variant and object provider ID. All the inputs are mandatory. After entering all the details, you need to click Start Impact Analysis button. 
  6. Once impacted Analysis is completed, result will be stored in integration repository. 

To view the impact details of interfaces in the Interface Mass Maintenance and Analysis application, select the interfaces and click on Impact Details button. A dialog appears with a table containing details of impact against the interfaces selected. You can see the impacted objects with interface name, impacted object name, object type, simplification category and SAP note number.

          

          


Use <Leave Blank> to delete existing values from attributes 

<Keep Existing Values> indicates that the selected interfaces have different values for the same attribute 












In Service Pack 11, SAP now offers the ability to document Cloud Platform Integration – Integration Flows in the Integration Repository found in Solution Manager. The CPI Tool is a multi-step wizard which guides users through the process of retrieving Integration Flows from a CPI tenant, performing necessary mappings and importing the Integration Flows into the Integration Repository.

Technical Prerequisites

  • The Cloud Platform Integration tool requires Solution Manager 7.2 Service Pack 11
  • Google Chrome – In order to facilitate the retrieval of Integration Flows, the browser must make requests to the CPI tenant. Starting in Chrome 73, Google has added restrictions on how the browser can make these requests. These restrictions must be disabled for the tool to work. Please note, it is not recommended that this low security version of Chrome be used for web browsing, it should only be used for the purposes of running the Cloud Platform Integration tool.
    It is planned that future releases of this tool will not require this version of Chrome.
  • Neo Tenant – Currently, the APIs used to retrieve Integration Flows are only available on Neo tenants. Development of these APIs on Cloud Foundry tenants is ongoing.

 

 

Walk-through

1)      Open Solution Manager Launchpad using transaction SM_WORKCENTER.

2)      Choose the tile Integration Repository – Cloud Platform Integration.

3)      Enter the details of the CPI tenant, along with the Username and Password of a user on the tenant.


a)       In addition, you can define an inclusive date filter on the retrieved Integration Flows based on their deployed date.

4)      Select the Integration Flows you wish to document.

5)      Select the Solution, Branch and System Role. This will determine where the Integration Flows appear in Solution Documentation.

6)      Perform a mapping between Sender/Receiver systems and Logical Component Groups.

7)      Clicking on Review will give you the opportunity to review your selections and mappings.

8)      Clicking on Submit will open a dialog. Here you can provide a name for the folder containing the Integration Flows in Solution Documentation. The default name is ‘Import’. Clicking on Submit will send the Integration Flow details to Solution Documentation.

9)      From the Solution Manager Launchpad, choose the Solution Documentation tile.

Select the same Solution, Branch and System Role as you chose in the CPI tool. The imported Integration Flows folder will appear in the Interface Library.



  • No labels