Defining Virus Scan Providers (SAP Library

Defining Virus Scan Providers

Use

The Virus Scan Provider defines either a Virus Scan Adapter or a Virus Scan Server.

The Virus Scan Adapter is a library that integrates virus scanners from certified vendors using an interface. The Virus Scan Adapter is loaded in AS ABAP, AS Java, or the Virus Scan Server.

The Virus Scan Server is an executable program that includes virus scanners from certified vendors using an interface and provides scan services to the application servers of the system as a registered RFC server.

The application server controls tasks such as starting, stopping, and monitoring the Virus Scan Server. You configure the data required to do this in this step.

Note

Use this procedure to create an entry for each Virus Scan Provider that you want to set up. For performance reasons, we recommend that, if possible, you load a Virus Scan Adapter directly in the application server. If this is not possible, you should set up at least one Virus Scan Server on every application server.

SAP does not provide any configuration data for Virus Scan Providers.

As soon as you can use a Virus Scan Adapter, you should stop using the Virus Scan Server. You can use the Virus Scan Providers to integrate a Virus Scan Adapter into the application server, that is, into the kernel. This means that the document does not have to be copied to the RFC server, meaning that this is the fastest scan variant. The AS ABAP scans the document directly for viruses. You can also administer the adapter more easily. You do not require, for example, the following administration tools:

● CCMS monitoring: the adapter runs in the work process and returns a CORE dump in the ABAP kernel if problems occur. The system then automatically restarts the work process and loads a new adapter.

● Load balancing: with an adapter, you do not need to explicitly attend to load balancing, since this is determined using the work processes.

● RFC destination: you do not need to create an RFC destination for adapters.

Prerequisites

● You have created at least one scanner group.

● You have decided whether you are creating the virus scan provider as an application-server-starter or as a self-starter (see Application-Server-Starter or Self-Starter).

Defining Virus Scan Servers

...

1. In transaction SM59, create an RFC connection with the connection type T.

Caution

Since the configuration of the Virus Scan Server requires the following naming convention, you must use it for the RFC destination of a Virus Scan Server:

● VSCAN_<host name>, if you only want to start one Virus Scan Server on the host.

● VSCAN_<host name>-<number>, if you want to start multiple Virus Scan Servers on the host. The number is a sequence number, which is separated from the host name with a hyphen.

Examples of possible names would therefore be VSCAN_HOST123, VSCAN_HOST345-1, VSCAN_HOST345-2.

a. Select Registered server program as activation type.

b. Use the name of the RFC destination as the program ID.

c. Enter the address of the gateway of the system as the gateway host and gateway service. If you are starting the Virus Scan Server on an application server using the Computing Center Management System, choose the gateway of that application server.

2. In the Implementation Guide, choose SAP NetWeaver →Application Server → System Administration → Virus Scan Interface (transaction VSCAN), and, if necessary, switch to change mode.

The screen View: Change "Virus Scan Provider Definition": Overview appears.

3. Choose New Entries.

The system displays the New Entries: Details of Added Entries screen.

4. Enter the data for the Virus Scan Server.

Data for the Virus Scan Server Definition

Field	Possible Values	Notes
Provider Type	Server (Virus Scan Server) <empty>(Virus Scan Server)	If you want to set up a Virus Scan Server, choose server (Virus Scan Server). You cannot select the value <empty> Virus Scan Server. It is used only to display older Virus Scan Servers.
Provider Name	VSCAN_<RFC Destination> The input help displays all VSCAN_RFC destinations that exist.	The name of a Virus Scan Server must be the same as the name of the RFC destination that contains the technical connection to the Virus Scan Server.
Scanner Group	All previously created scanner groups, which you can display using the input help.	The scanner group combines multiple Virus Scan Servers or allows the use of a BAdI implementation. If you create multiple Virus Scan Servers in a scanner group, you achieve load balancing. All of the Virus Scan Servers of a scanner group have the same set of configuration parameters and will therefore use the same scan engine.
Status	● ACTS (Active as a self-starter): Although the CCMS monitors the Virus Scan Server (if it is not available, an error status is triggered), it does not start or stop the Virus Scan Server. This status is suitable for Virus Scan Servers that are, for example, started as a service at operating system level. ● ACTV: Active (Application Server) The CCMS monitors the Virus Scan Server and, if necessary, starts it on the specified application server. ● INAC (Inactive on an Application Server) The CCMS monitors the Virus Scan Server is monitored and, if necessary, stops it on the specified application server. ● NONE: No monitoring: The CCMS does not monitor the Virus Scan Server.	Monitoring status of the Virus Scan Server in the CCMS. In the cases of the statuses NONE and INAC, the system’s automatic server selection can no longer find this Virus Scan Server.
Server	The input help provides a list of the existing servers. Do not specify a different server name.	Application server on which the Virus Scan Server is to be started and/or monitored.
Trace Level	● Errors only ● Errors and warnings ● Errors, warnings, and information ● Maximum output	Specifies the trace level for the Virus Scan Server, which is to be transferred to the CCMS at operating system level when the Virus Scan Server is started. We recommend that you only use one of the first two levels Errors Only or Errors and Warnings in production systems. The two other trace levels are available for finding errors during test operation in the test system.
ReinitInterv.	0 or <empty>: no automatic reinitialization If the vendor of your virus scanner uses the interface provided by SAP with which an initialization from outside the system can be performed, you can leave the field empty. This interface is available to certified vendors of virus scanners. <n>: Interval in hours	Specifies the number of hours after which the Virus Scan Server is to be regularly reinitialized. For the Virus Scan Server to load new virus definitions from the Virus Scan Server, you must reinitialize it. The automatic reinitialization is performed during the periodic monitoring of the Virus Scan Servers by the CCMS.
Adapter Path	Full path of the library that contains the Virus Scan Adapter	Specifies the full path of the Virus Scan Adapter. If you do not fill the field, the Virus Scan Server uses the content of the environment variable VSA_LIB.
Configuration	Full path to the configuration file of the Virus Scan Server	Specifies the full path to the configuration file of the Virus Scan Server The configuration file can contain optional parameters of the Virus Scan Server. For externally-started Virus Scan Servers, the configuration file has already been defined at the Virus Scan Server command line and you cannot therefore change it here.
Instance Name	V<system number>	Use this field if the external virus scan product fulfills the platform criteria (it is, for example, available for Linux), but not the processor criteria (there is, for example, only a 32 bit variant, and the application server is running under Linuxx86_64). A separate directory is necessary since the kernel directory cannot contain a mixture of 32 and 64 bit software due to the fact that some programs have the same names.
Max. Instances		Specifies the maximum number of scan instances provided by the Virus Scan Server. A Virus Scan Server may provide multiple scan instances. You can use the maximum number specified here to determine how many of these instances are provided. If this number is exceeded, the virus scanner is no longer available for scan requests. The number of instances should correspond to the number of work processes.
Code Page	Enter the codepage valid for the Virus Scan Server. It must correspond to the codepage of the application server that is communicating with the Virus Scan Server: ● If you are only using one codepage in your application servers, enter this codepage. ● If you have application servers in different codepages, set up a Virus Scan Server on each application server and specify the valid codepage in each case. ● If your system uses UNICODE, do not enter anything.	Codepage that the CCMS sets when the Virus Scan Server is started

5. Save your entries.

Defining Virus Scan Adapters

...

1. In the Implementation Guide, choose SAP NetWeaver →Application Server → System Administration → Virus Scan Interface (transaction VSCAN), and, if necessary, switch to change mode.

The screen View: Change "Virus Scan Provider Definition": Overview appears.

2. Choose New Entries.

The system displays the New Entries: Details of Added Entries screen.

3. Enter the data for the Virus Scan Adapter.

Data for the Virus Scan Adapter Definition

Field	Possible Values	Notes
Provider Type	ADAPTER (Virus Scan Adapter)	The vendor’s Virus Scan Adapter runs in the work process of the application server, that is, the external product must match the architecture of the SAP system (64 bit).
Provider Name	VSA_<Name> Default value: VSA_<host name>	You can overwrite the host name with any name. However, you must retain the VSA_ prefix.
Scanner Group	All previously created scanner groups, which you can display using the input help.	The scanner group combines multiple Virus Scan Providers or allows the use of a BAdI implementation. If you create multiple Virus Scan Providers in a scanner group, you achieve load balancing. All of the Virus Scan Providers in a scanner group have the same set of configuration parameters and will therefore use the same scan engine.
Status	● Active (Application server) ● Inactive (Application server)	The values active and inactive indicate whether the adapter is to be activated when the application server or a work process is restarted. Active: An adapter is loaded for the work process. Inactive: No adapter is loaded for the work process.
Server	The input help provides a list of the existing servers. Do not specify a different server name.	Application server on which the Virus Scan Adapter is to be started and/or monitored.
ReinitInterval	0 or <empty>: no automatic reinitialization If the vendor of your virus scanner uses the interface provided by SAP with which an initialization from outside the system can be performed, you can leave the field empty. This interface is available to certified vendors of virus scanners. <n>: Interval in hours	Specifies the number of hours after which the Virus Scan Adapter is to be regularly reinitialized. You need to reinitialize the Virus Scan Adapter so that it loads new virus definitions. The automatic reinitialization is performed during the periodic monitoring of the Virus Scan Providers by the CCMS.
Adapter Path	Full path of the library that contains the Virus Scan Adapter	Specifies the full path of the Virus Scan Adapter. If you do not fill the field, the Virus Scan Server uses the content of the environment variable VSA_LIB.