As outlined at the beginning of this guide it’s recommended to follow the best practice approach for Interface Management in SAP Solution Manager. After having documented the interfaces and their attribute data in Interface Documentation (typically done during design phase of a project) it’s recommended to configure interface monitoring at least for the most critical interfaces in the landscape (to be done prior to go-live of the project). An integration between Interface Documentation and the Interface & Connection Monitoring (ICMon) setup tool is available via the Default Values functionality which supports the smooth transition between those two phases. Attribute values which were maintained in Interface Documentation can be loaded into the ICMon setup tool into respective Interface Channels, to avoid having to configure the same data another time to get the monitoring running. This integration is independent of the entry point for monitoring setup. You can use it if you start from Solution Documentation (to configure monitoring in a business process context), or if you call ICMon setup in the context of a Technical Scenario.
There’s no 1:1 relation between the two tools, Interface Documentation and ICMon. Firstly, not all interface technologies which are available in Solution Documentation are reflected in ICMon, and vice versa. See Table 6 to find a mapping between monitoring templates in ICMon and interface technologies in Solution Documentation. All monitoring templates listed here can use the Default Values functionality and thus benefit from data already maintained in the system.
Table 6: Mapping between Monitoring Templates and Interface Technologies
Monitoring Template(s) in ICMon
Interface Technology (with Subtype) in Interface Documentation
Background RFC (bgRFC)
RFC (transactional bgRFC, queued bgRFC)
BDoc (Analyis), BDoc (Real-time Monitoring), CRM Middleware
File (ABAP), File (Diagnostic Agent), File (Remote)
HTTP Client (from Introscope)
HTTP (ABAP, JAVA, General)
HTTP Server (ABAP)
IDoc (Analysis), IDoc (Real-time Monitoring)
Process Integration (PI), Process Integration (PI – ABAP only)
RFC (queued RFC)
RFC (synchronous RFC)
RFC (transactional RFC)
Web Service ABAP
Web Service (from Introscope)
HTTP (ABAP, JAVA, General)
Secondly only selected attribute values can be loaded into the respective setup parameters in ICMon. Some attributes which are used in Interface Documentation don’t appear in the configuration of the respective monitoring templates since they are only used to describe the interface. Thus, they are not useful when configuring monitoring and feeding a data collector to select appropriate data for monitoring & alerting (example: the RFC Logon group). Vice versa, the monitoring templates contain a couple of parameters which are actually needed to check the status of an interface (like IDoc Status). This kind of information isn’t needed in Interface Documentation as it represents runtime data of single instances of the interface which is not relevant for documentation.
Rules for Default Values
If the Default Values button is greyed out in ICMon setup the functionality is not available for the corresponding interface or metric (as no mapping exists for the current context between interface attributes and monitoring configuration parameters).
When you call the Default Values functionality in ICMon setup for one of the above mentioned monitoring templates all Interface Documentation objects are listed which exist in the system and fulfill the following rules:
- The interface technology of the Interface Documentation object matches the monitoring template according to Table 6.
- Source and target system of the Interface Channel correspond to the sender and receiver system of the Interface Documentation object.
Note that the Interface Documentation object can exist in different solution contexts depending on branch, site and system role of the solution. It can happen that the Default Values don’t show a documented Interface although you expect it to (because the same systems which you used for the Interface Channel exist in your solution, too). However, it could be that you have configured the Interface Documentation in a different solution context. In this case go to the same context in your solution where the systems behind the LCGs correspond to the source and target system of the Interface Channel, open the Interface Documentation object and explicitly save it. Afterwards the Default Values will show the Interface Documentation.
- The client of the measuring point of the Interface Channel must be identical to the client of the respective system in the Interface Documentation. For example, if the Interface Channel measures the source system, the client of the sender system in the Interface Documentation must be identical to the source client of the Interface Channel.
Note that this rule only applies if the monitoring template monitors ABAP systems which require you to provide a client for the measuring point. Other monitoring templates which are used for different system types (for example JAVA-based systems) don’t require you to provide a client. In this case the Default Values ignore the client of the respective systems in the Interface Documentation object.
Using Default Values in ICMon
You have to perform the following steps to use the Default Values functionality in ICMon setup:
- Create an appropriate Interface Channel in ICMon setup. Then navigate either to the Interface or the Metric configuration tab. Press button Default Values.
- A new window opens which shows all Interface Documentation objects matching the current Interface Channel. By selecting one of the Interface Documentation objects from the list you can view all attribute values maintained in the Interface Documentation, and to which monitoring configuration parameters they will be transferred. When you have decided which Interface Documentation data should be imported press OK.
- You return to the ICMon setup main screen where you can view the imported attribute values. Note that importing data via Default Values overwrites all existing configuration for the current interface or parameter set, respectively. So, the recommended procedure is to import all available attribute values via Default Values first, and then add missing configuration data which was not available in the Interface Documentation. It’s possible to adjust all imported attribute values at any time.
Note: For the following scenario only a single Interface Documentation shows up in the Default Values selection dialog:
- In Solution Documentation you have assigned an Interface object for which Interface Documentation exists to a business process.
- Then you configure monitoring for this Interface using a monitoring template which corresponds to the interface technology of the Interface according to Table 6.
In that case it’s clear from the business process context that the monitoring you’re about to configure targets the Interface which is assigned in Solution Documentation. That’s why Default Values only provides the Interface Documentation which is attached to this particular Interface. Other documented Interfaces which technically would match the Interface Channel settings according to the rules listed above are ignored.