How gregorwolf/sap-malware-scanning-vsi works
This small ABAP integration implements SAP’s Virus Scan Interface BAdI using SAP Malware Scanning Service. The documented workflow is that the SAP virus-scanning runtime invokes the configured VSCAN_INSTANCE implementation, which provides malware scanning through the service. The README also requires installing a separate generated ABAP client. Source excerpts were unavailable, so internal calls between the two repository classes and the client’s exact role cannot be confirmed; those links are omitted or marked unverified.
Main entry points: zcl_mwscan_vscan_badi.clas.abap VSCAN BAdI
Components 5
Other components
- SAP Virus Scan
- VSCAN BAdI
src/zcl_mwscan_vscan_badi.clas.abap - Scanner Adapter
src/zcl_mwscan_vscan.clas.abap - ABAP API Client
- Malware Scanning Service
Connections 3
- SAP Virus Scan → VSCAN BAdI: invokes implementation
README.md - VSCAN BAdI → Malware Scanning Service: provides scanning
README.md - ABAP API Client → Malware Scanning Service: API integration