Configuration for Monitoring Template: HTTP Client (from ABAP)
The HTTP channel type is used to monitor the availability and performance of HTTP RFC destinations (type G and H) communication between the Concur Integration add-on in SAP ABAP and the Concur cloud solution.
For detailed setup information how to set up this channel type please refer to the configuration of HTTP channels. The RFC destination to Concur is maintained during the Concur setup in transaction CTE_SETUP. You can use this transaction to find out which RFC destinations were created, or you can check in transaction SM59 under type G.
Use the template HTTP Client (from ABAP) for the monitoring. For the metric parameter 'Destination' use the name of the RFC destination.
Configuration for Monitoring Template: RFC
The RFC monitoring template is used as a workaround until we have added the metric for 'Number of AppLog Errors ' to the HTTP template. We use this template to collect the number of exceptions that are written to the SAP Application Log by the Concur Integration add-on.
For detailed setup information how to set up this channel type please refer to the Interface and Connection Monitoring wiki for configuration of RFC channels.
When you set up this channel set the Target system = the Source system. This will create a channel pointing to itself and make sure the measuring point is correct. You don't have to add an interface to the channel.
Select the metric 'Number of AppLog Errors (RFC)' and maintain the following metric parameters:
- Technical system: your ABAP system
- Object name: CONCUR_INTEGRATION
- Sub-object name: you can select one of the following sub-objects or use '*'
The metrics for the Application Log Monitoring will create alerts based on the number of errors in the SAP Application Log. If you set up the Exception Management as well, you can analyze the single exceptions in Exception Management to find out more details about the errors that occurred.