Patch Release V3.0 SP7

June 9, 2025

Patch files

V3.0 SP7 contains one file:

K-300SP07NEWR.SAR

Implementation procedures

Service pack installation and configuration

Where to install: Deploy this service pack to client 000 of your Central Monitoring System.
Configuration location: Perform all subsequent configuration tasks in the business client of your Central Monitoring System.
Complete instructions: For step-by-step installation procedures, consult Installation Guide V3.0 (Appendix VIII: Install Service Pack) or Admin Guide V3.0 (Section: Install Service Pack).
This service pack includes an enhancement to data provider NR_SAP_ABAP_WS. If you want to customize this data provider, see the Manual configuration steps for instructions.

Updates in this patch

The BTP/CALM API Host can now be accessed via the same proxy server configured for the Authentication HTTP destination. This enhancement is useful when the Central Monitoring System requires a proxy server to access BTP and/or CALM API endpoints.
The BTP/CALM service identifier attribute (SOURCE_ACCT) is now exported when telemetry data is sent to New Relic. This enhancement is useful when monitoring multiple BTP/CALM accounts.

Other updates

Updated NR_SAP_ABAP_WP to allow retrieval of all data and attributes under a Node Only tag.
Fixed a bug in NR_SAP_JOB_ALL where the timestamp for unfinished jobs was using local time as UTC time.
Fixed bugs in the Test function of the registry.
Added new configuration parameter BYPASS_PARA_ID for skipping configuration parameter pattern recognition when updating the configuration template. This prevents word strings in certain parameters, such as API_PATH and API_QUERY, from being recognized as SYS_ID.

Manual configuration steps

Configure NR_SAP_ABAP_WS to retrieve XML payload tags

Data Provider NR_SAP_ABAP_WS is designed with the capability to retrieve values from payload web service XML tags. Previously, only data type or attribute type tags could be retrieved. This service pack allows Node type tags to also be specified for retrieval.

The payload tag to be extracted is configured using the configuration parameter TAG_LIST. Here is an example:

Image of SAP NR_SAP_ABAP_WS data provider configuration for XML payload tag retrieval

In previous versions, only data or attribute tag names could be configured for retrieval. Here is an XML fragment:

<NodeTag Attribute = Attribute_value>
<DataTag> Data_value </DataTag>
</NodeTag>

To retrieve the data from the XML, the TAG_LIST is configured with the value: Attribute;DataTag.

Then the NR_SAP_ABAP_WS event will have these attributes:

Attribute: Attribute_value
DataTag: Data_value

Now the TAG_LIST can be configured as NodeTag. In this case, the event attributes are as follows:

NodeTag_Attribute: Attribute_value
NodeTag_DataTag: Data_value