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.



















  • No labels