Virus Scanner Service 
Use
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 (see Virus Scan Report).
Integration
The virus scanner
service uses the 
virus scan
interface of SAP Web AS.
Prerequisites
In order to be able to carry out virus checks in KM; you first have to integrate anti virus programs in the configuration of SAP Web AS. These programs can come from different providers.
SAP does not deliver its own anti virus programs.
·
The virus scan
interface of SAP Web AS is configured correctly (see Setting Up the Virus
Scan Interface).
·
Virus scan
providers have been created in the visual administrator of the J2EE Engine
(see Setting
Up Virus Scan Providers).
Features
When a document is checked for viruses, a copy of the document is loaded to the memory or file system of the J2EE Engine. The configuration defines how many documents can be checked at once. An item is created in the J2EE Engine 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 included the following parameters:
Parameters of the Virus Scanner Service
Parameters |
Required |
Description |
Path for Temporary Files |
No |
Path to the directory in which temporary files for the check are stored. If the data to be scanned exceeds the value specified in the parameter Memory Limit, a temporary file is created in this directory. Leave this field empty if you want to use the JAVA temporary directory. This is defined in the JAVA system property java.io.tmpdir. Refer to the information on memory requirements above. |
Check Write |
No |
If activated a virus check is carried out when write operations take place (for example, when a document is uploaded to KM). If deactivated, data is initially stored without a virus check. You can carry out a virus check later on using a virus scan report. If read access takes place before the report runs, the virus check starts then. You must carry out a virus check before changing from a read-operation check to a write-operation check. If you do not do this users may access documents that have not been checked. If you deactivate this parameter, you must activate the application property service (properties) in the configuration of all selected repositories. This means that documents will only be checked when read access first takes place, rather than every time. |
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 the J2EE Engine. 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 parameter Memory Count. |
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 memory of the J2EE Engine. 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 memory of the J2EE Engine. 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 parameter if you want the repositories listed here to be checked. If you make no specification here, all repositories are checked. |
Virus Scan Profile |
No |
Virus scanner profile to be used by default for the virus check. If you do not select a profile, the default profile is used. |
Activities
To call up the configuration of the virus scanner service, choose Content Management ®Global Services ®Virus Scan Service.
Example
The virus scanner service can be configured as follows to imitate the standard delivery:
Path for Temporary Files = D:/temp/java
Active = Activated
Check Write = Activated
Clean Viruses = Activated
Positive List = Activated
File Count = 10
Maximum File Size (MB) = 1000
Memory Count = 10
Memory Limit (KB) = 100
Repositories =
Virus Scan Profile = McAfeeProfile