Virus Scanner Service
The virus scanner service allows you to check documents for viruses.
This check can take place during read operations or write operations (for example, when you save or upload a document in KM). You can also start the check using a report. For more information, see Virus Check report.
The virus scanner service uses the virus scan interface of Application Server Java (AS Java).
In order to be able to carry out virus checks in KM, you first have to integrate anti virus programs in the configuration of AS Java. These programs can come from different providers.
SAP does not deliver its own anti virus programs.
- The virus scan interface of Application Server Java (AS Java) is configured correctly..
- The kmc_Default and htmlb_FileUpload profiles are active in the virus scan interface of AS Java.
When a document is checked for viruses, a copy of the document is loaded to the memory or file system of Application Server Java. The configuration defines how many documents can be checked at once. An item is created in the memory for each check, even if the final output is into a file.
The memory required is calculated as follows:
Memory Count x Memory Limit = required memory
File Count x File Limit = required memory in file system
This tells you how much memory you need to provide in the temporary directory.
The configuration of the virus scanner service includes the following parameters:
Parameters of the Virus Scanner Service
| Parameter | Required | Description |
|---|---|---|
|
Check Write |
No |
If activated, a virus check is carried out whenever read or write operations take place (for example, when a document is uploaded to KM, or a user accesses an uploaded document.) If deactivated, data is initially stored without a virus check. In case of write operations, a virus check is not carried out. However, a virus check is carried out whenever read access takes place. You can carry out a virus check later on using a Virus Check . If read access takes place before the report runs, the virus check starts then. If you deactivate this parameter, you must activate the application property service (properties) in the configuration of all selected repositories. |
|
Clean Viruses |
No |
If activated, the system tries to eliminate viruses that are found. If deactivated, it only reports viruses that are found. |
|
Positive List |
No |
If activated, only repositories specified in the parameter Repositories are checked for viruses. If deactivated, the list of specified repositories is seen as a list of repositories to exclude, and only repositories that are not specified are checked. |
|
File Count |
Yes |
Number of temporary data items stored in parallel in the file system of AS Java. If this number is reached, all further requests are blocked until sufficient resources are free. The value of this parameter should be smaller than or equal to the value in the Memory Count parameter. |
|
Maximum File Size |
Yes |
Files that exceed this size (in MB) are not checked for viruses. Such files cannot be loaded to KM for security reasons. |
|
Memory Count |
Yes |
Number of temporary data items stored in parallel in the AS Java memory. This determines the maximum number of virus checks that can be carried out in parallel. If this number is reached, all further requests are blocked until sufficient resources are free. |
|
Memory Limit |
Yes |
Maximum size in KB for which the temporary data can be stored in the AS Java memory. If the amount of data is larger than this, a file is created instead. |
|
Repositories |
No |
Repositories to be checked or not checked for viruses. Activate the Positive List parameter if you want the repositories listed here to be checked. If you do not make a specification and the Positive List parameter is not active, the system checks all repositories. |
To call up the configuration of the virus scanner service, choose Content Management → Global Services → Virus Scan Service.