Onboarding IT Admin - Continuous Control Monitoring (CCM)

Guide for IT Administrators to prepare for our solution zapAnalytics - Continuous Control Monitoring (CCM)

zapAnalytics - CCM

zapAnalytics - CCM licenses continuous monitoring of your SAP environment by automating the extraction and indicator-based controls of SAP data at regular intervals. The results can be seamlessly exported to third-party tools like Power BI or CRISAM, allowing the user to implement standard or customer specific controls.

Estimated preparation time: 90 minutes

Topics:

• General Information about zapAnalytics
• Technical Requirements: Hardware
• Technical Preparation: zapAnalytics
• Access to zapAnalytics
• Displaying Results in Third-Party Tools
• Connecting Third-Party Tools for Other Purposes
• Installation of Software Updates
• Impact on the SAP System

General Information about zapAnalytics

zapAnalytics is a web application based on Java Spring. SAP data extraction is performed via RFC and requires only a reading SAP user authorized with SAP standard function modules. A PostgreSQL database (embedded or standalone) is used, where all data is stored locally. 

The duration for data extraction and processing can vary significantly depending on the amount of data, and it may take several days. A stable network connection to the ERP and possibly the target system is required to ensure data flow.

Technical Requirements: Hardware

The hardware specifications depend on the data volume. For efficient data extraction and processing, we recommend a virtual machine with the following specifications:

• Operating System: Windows 64-bit (e.g., Windows Server 2022 or later)
• Processor: Modern multi-core processor (at least 8 cores)
• RAM: At least 64GB, scalable to 128GB
• Storage: At least 1 TB with read/write speeds of at least 100 MB/s
• Availability: Uninterrupted availability during data extraction and processing (disable or reschedule backups, updates or server reboots)

Average hardware setup time: 60 minutes

Technical Preparation: zapAnalytics

Preparation for installation:

• Administrator rights for installation.

• Ports in the internal network for SAP (3300, 3600, 3299) and optionally web access from client computers (9007 and optional 8080) must be allowed through the firewall.

• Set up Remote Desktop (RDP) access for the audit manager and optionally the auditors.

• Align Windows Updates (Patch Schedule) for the server with the project requirements and reschedule either updates or data extraction and processing if necessary.

Installation of zapAnalytics (possibly together with zapliance):

• Download the installation package and content bundle. Both are provided by zapliance.
• Install zapAnalytics. Here is a step-by-step installation guide.
• Register the zapAnalytics process as a Windows service (autostart) and adjust the RAM allocation if necessary. Here is a detailed guide for registration.
• Set up users and projects in the software.
• Upload the content bundle into zapAnalytics.
• Configuration of SAP connection details and, if necessary, performing comprehensive connection tests.
• Start first (manual) data extraction and processing.
• Once the initial results are available, the controls for continuous control monitoring have been determined and agreed upon with zapliance: Set up cron for automatic data extraction and processing

Average installation and setup time (excluding approval procedures): 30 minutes

Access to zapAnalytics

Access the web interface via https://localhost:9007/zapAnalytics/login on the server.

If a client computer is directly in the internal network, the web interface can also be accessed via the host's IP address (e.g., https://hostIP:9007/zapAnalytics/login).

The software includes a self-signed certificate (.jks), enabling standard HTTPS communication.

Displaying Results in Third-Party Tools

The result files from the zapAnalytics analyses contain the deliverables defined in the content package and are available for download in the following formats:

• .parquet
• .xlsx
• .csv

These can be imported into third-party tools like Power BI, CRISAM, Excel etc.

Furthermore, the zapAnalytics PostgreSQL database can be connected to third-party tools to transfer the files directly to the tool. This is only possible if the respective tool allows a connection to the database. 

Your preferred tool and the respective prerequisites will be discussed with zapliance beforehand.

If our offer includes a workshop, either:

• grant zapliance access to the chosen third-party tool and/or report, or
• only if Power BI is used: send the result files (.parquet files) to zapliance

Note: Licenses for third-party tools are generally not part of our offer.

In case Power BI is used:

Power BI template files (.pbit) are also provided for download.

The templates are opened with Power BI Desktop, and the results from the .parquet files are imported. This generates a Power BI report (.pbix).

Optionally, the Power BI Desktop report (.pbix) can be published and other microsoft user can be authorized to the report.

Note: We recommend 8GB RAM or more for using Power BI Desktop. Detailed setup information can be found in this article: Setup PowerBI

Connecting Third-Party Tools for Other Purposes

If you would like to integrate zapAnalytics further into your IT landscape (e.g. by using an API), an adequate solution can be discussed with zapliance.

Installing Software Updates

Software updates are regularly provided by zapliance. Customers receive update notifications via email and the Knowledge Base. Customers are responsible for updating the software, as this cannot be automated.

Software updates are performed by:

1. Reinstallation,

2. Importing updates or content bundles (during runtime).

All forms of updates can only be executed with encrypted, zapliance-signed files.

Reinstallation:

• Download the latest installation file from zapliance.
• Pause all data operations and stop the current process/service.
• Deregister the registered Windows service.
• Install the update by reinstalling with the new installation file.
• Adjust RAM allocation if necessary.
• Register the Windows service again.
• Start the Windows service.

Average update time: 10 minutes

Updates during runtime

zapliance offers engine files and content bundles (.zip) that can be uploaded during runtime to update functions or enable new features and analyses in the software. This process can be managed from the frontend without requiring direct access to the host machine, usually without IT support.

Average update time: 5 minutes

Data Access and Impact on the SAP System

Data is retrieved via the RFC interface of the SAP system. zapAnalytics only requires the SAP standard function modules and read rights.

In over 2000 projects, there have been no impacts on R3, ECC, or S4 systems.

Additional information about SAP Admin.

Need Help?

If you have any questions, please contact our support team at support@zapliance.com.

 

Last updated: August 14, 2025

 

Checklist to Get Started: