Skip to content

Commit e809bbd

Browse files
committed
Update mde-linux-deployment-on-sap.md
1 parent 30d74f7 commit e809bbd

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

defender-endpoint/mde-linux-deployment-on-sap.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ Conventional security defenses that have been commonly used to protect SAP syste
4848
- SAP only supports certain Linux File systems. In general, XFS and EXT3 are used. Oracle Automatic Storage Management (ASM) filesystem is sometimes used for Oracle DBMS and can't be read by Defender for Endpoint.
4949
- Some SAP applications use "standalone engines" such as TREX, Adobe Document Server, Content Server and LiveCache. These engines require specific configuration and file exclusions.
5050
- SAP applications often have Transport and Interface directories with many thousands of small files. If the number of files is larger than 100,000, it might and affect performance. It's recommended to archive files.
51-
- It's strongly recommended to deploy Defender for Endpoint to nonproductive SAP landscapes for several weeks before deploying to production. The SAP Basis Team should use tools such as sysstat, KSAR, and nmon to verify if CPU and other performance parameters are impacted.
51+
- It's strongly recommended to deploy Defender for Endpoint to nonproductive SAP landscapes for several weeks before deploying to production. The SAP Basis Team should use tools such as `sysstat`, `KSAR`, and `nmon` to verify if CPU and other performance parameters are impacted.
5252

5353
## Prerequisites for deploying Microsoft Defender for Endpoint on Linux on SAP VMs
5454

0 commit comments

Comments
 (0)