Configering Operations

Objective

After completing this lesson, you will be able to configure Operations

Configuration Options for SAP Cloud ALM for Operations

The primary aspects here are Data Collection from managed services and systems, as well as personalization and Configuration. If you are interested in using these functions, please refer to the SAP Course CALM40 – Operating with SAP Cloud ALM.

Data Collection

You have full control over which data from managed services and systems is transferred to SAP Cloud ALM. When you activate your SAP Cloud ALM tenant and register your systems and services in the Landscape Management app of SAP Cloud ALM, the collection of observability data is not started automatically. SAP Cloud ALM follows a central configuration approach: You need to explicitly configure the data collection processes.

Hint

Please note that SAP may change any aspect of data collection or configuration at any time. For the latest information, consult the in-app help .

Personalization and Configuration

In many apps, you can also perform application-specific personalizations and configurations by choosing Configuration in the top-right corner.

The following slides show examples of these configuration options.

Business Process Monitoring

The first slide shows the Business Process Monitoring Configuration options:

Slide showing SAP Cloud ALM – Business Process Monitoring configuration. Left panel displays “Configuration” with Managed Components (Services/Systems listing SAP S/4HANA Cloud and MySuccessFactorsHCM_01 with on/off toggles), KPI Management with example entries like “1st Customer KPI” and “Billing Document Line Items Created,” Data Volume (Total Size 164 MB), Aggregation (Retention time: 30 days for single execution and 365 days for aggregated execution), and Support with an Export button for “Import Configuration File.” Center screenshots show KPI Management and Processes lists (e.g., Lead to Cash, Hire to Retire BestRun, Purchasing, Germany) with action icons. Right-side callouts highlight capabilities: setting up events, customizing data collection, creating custom KPIs, creating custom processes, activating/deactivating access control, and creating access groups. Bottom-right image shows the Access Control page with an “Activate Access Control” button.
Service / System (##)

The Business Process Monitoring app includes a recurring auto-discovery mechanism that regularly and automatically identifies and activates business process KPIs. This mechanism only runs after the service or system has been connected to SAP Cloud ALM and the data collection has been activated accordingly.

Only if the auto-discovery detects relevant business data in your managed service or system, the service or system or individual KPI is activated in business process monitoring. Without relevant business data, the service, system, or KPI remains inactive and can't be monitored in business process monitoring.

After activation, you can stop data collection at any time by toggling the slider from On to Off. This changes the service or system status to Inactive. The service/system remains connected to Business Process Monitoring, and all previously collected data stays available.

KPI Management (##)

To make changes to your KPI configuration and to see more information about each KPI, choose (Configure KPIs). As a Process Monitoring Administrator, you have the following configuration options:

  • Setting Up Events
  • Customizing the Data Collection
  • Creating Custom KPIs
  • Creating Custom Processes
Data Volume
Check the total amount of database memory space that the Business Process Monitoring app is currently using.
Aggregation

Manage the retention time of individual business documents and aggregated data.

Support

Export configuration data for support purposes.

Access Control

Create access groups to manage users' access to end-to-end processes and individual process nodes. This will allow them to access the monitoring data for all associated KPIs and corresponding alerts.

For more Information, please consult the SAP Help Portal: Business Process Monitoring Configuration.

Integration & Exception Monitoring

The next screenshot shows the configuration options for Integration & Exception Monitoring:

The screenshots show the Integration & Exeption Monitroign configuration options:: Left side shows Configuration > Managed Components with “Services/Systems” listing items such as MyBapiNetwork_01 (Managed Gateway for SpendNetwork) and MyNetwork_03 (SAP Business Network for Procurement), each with on/off toggles and a delete icon. “Business Services” lists entries like AribaNetwork-42K, Ariba Network: Integration via CIS S/4HANA, TestService, CALAMO-FJ. Housekeeping panels display retention periods for messages and exceptions (options 7, 14, 30, 90, 180, 365 days). Center panels show configuration pages for Services/Systems and Business Services with status, last changed dates, and action icons. Aggregation settings enable aggregation of messages and exceptions, set time zone to UTC, message retention 30 days, exceptions retention 365 days. Data Volume shows memory usage (e.g., total around 158 MB). Right-side callouts summarize capabilities: activate/deactivate data collection (overall and per message category), filter messages, collect additional attributes, create events, remove configuration, add/edit/delete a business service, and configure a business service.
Service / System (##)

You can enable/disable the data collection for a service or system as required.

You can do the following customizations to the data collection for services and systems:

  • Activate or Deactivate Data Collection for Individual Message Categories
  • Use Filters to Collect Specific Messages
  • Collect Additional Attributes
  • Create Events
  • Remove (Monitoring) Configuration
Business Services (##)

Create a Business ServiceConfigure data collection and events for Business Services:

  • Event Settings
  • Filters
  • Parameters
  • Grouping
  • Event Actions
Application Settings - Section Housekeeping

In this section, you can configure the retention period for single messages and exceptions.

Application Settings - Section Aggregation

In this section, you can configure the aggregation settings for messages and exceptions, and their retention periods. When aggregation is enabled, the collected messages and exceptions are aggregated, and stored in the aggregated data store.

Application Settings - Section Data Volume

In this section, you can view the memory consumption details of the app. The total memory used to store messages and exceptions are displayed separately.

For more Information, consult: SAP Help Portal: Integration & Exception Monitoring.