Installing a Virus Scan Server as a Self-Starter

Use

The self-starter is available to you as an alternative if you cannot use the application-server-starter. For example, if you are using a SAP NetWeaver AS under UNIX, but the external virus scan product or the external adapter is only available for Microsoft Windows.

Prerequisites

The self-starter starts the virus scan engine using a local XML configuration file. This is usually the file vscan_rfc.xml, which contains the parameters required by the virus scan adapter.

Procedure

Automatic Installation

The installation package at service.sap.com/swdc contains a standard configuration file, with which you can install a test adapter without an external virus scanning product (more information: SAP Note 964305 Information published on SAP site ). The server must be started, or, if necessary, restarted using operating system resources.

Manual Installation

Copy the relevant variant of the Virus Scan Server from the CD or the SAP Service Marketplace to a start directory.
Create the configuration file using the commands listed in the table below. You can also use these later to change the existing configuration.

Example

In this example, the following call generates both the server and the VSA configuration for vsalibrary.dll of the external virus scan product:

vscan_rfc get_config -V <drive:>\vsa\vsalibrary.dll -cfg <drive:>\vsa\vscan_rfc.xml

To set new parameters to overwrite existing parameters, execute additional commands and options in a new call. These are then set in the XML configuration.

In this example, you can change the call as follows:

vscan_rfc get_config -V <drive>:\vsa\vsalibrary.dll -cfg <drive:>\vsa\vscan_rfc.xml -a VSCAN_LOCAL -g <host name of SAP- gateway> -x <service name of SAP gateway> -c <SAP code page>

Command	Platform	Comment
`help`	All	Calls the online help for the commands and options.
`version`	All	Displays the internal version information of the Virus Scan Server. You must use at least internal version 1.5 (see SAP Note 782963 ).
`regonly`	All	Registers the virus scan server only at the gateway without starting the underlying engine. The CCMS uses this command to then call the RFC function VSCAN_RFC_INIT. Note that if you use this command outside the CCMS, the server is not ready for use.
`get_config`	All	Receives the VSA configuration and separate server configuration and stores them in a local XML configuration. (Option `‑cfg <file>` is mandatory for this). The options received using the command line are stored as the server configuration in this case. If you do not specify any command line options, the predefined values are set. Use this command to start the setup of a self-starter. If the file specified using the option cfg does not exist, a new file is created.
`install`	Microsoft Windows NT	Installs a "new" VSCAN_XX service in the Microsoft Windows NT Service Control Manager (SCM). The cfg option with a specification of a local configuration is mandatory for this command. If the VSA is successfully initialized, the service is installed . If you specify additional options, these are only stored in the XML file used. The srvc option specifies the number of the service; that is, you can install up to 100 services on a host. The default value for srvc is 00.
`remove`	Microsoft Windows NT	Deletes an existing VSCAN_XX service in the Microsoft Windows NT Service Control Manager. You can specify the service more exactly using the srvc option. Example: vscan_rfc remove srvc 1 deletes the existing service VSCAN_01.
`start`	Microsoft Windows NT	Starts an installed VSCAN_XX service. This command starts the service with the specified options. The Microsoft Windows NT command `net start VSCAN_XX` starts the previously installed service only if the local configuration is used.
`Stop`	Microsoft Windows NT	Stops a running VSCAN_XX service. This command corresponds to the Microsoft Windows NT command `net stop ...`.

In addition to the commands, you can specify the following options.

Option	Platform	Comment
`-a`	All	Program ID of the RFC destination, such as VSCAN_LOCAL
`-g`	All	Host name of the SAP Gateway
`-x`	All	Service name of the SAP gateways, such as sapgw00
`-cfg`	All	Complete path specification of the XML configuration file
`-f`	All	Path specification of the trace file to be used
`-l`	All	Trace level of the trace file: 0 := Errors 1 := Errors and warnings (such as virus infections) 2 := Errors, warnings, and virus scan engine calls 3 := Additional information, all RFC calls, and memory operations
`-c`	All	SAP code page for non-Unicode Virus Scan Servers
`-V`	All	Path specification of the virus scan adapter to be used. If you do not set this option, the environment variable VSA_LIB is used.
`-p`	All	Profile name (Default: VSA_CONFIG) for the current VSA configuration. This option allows differentiation if you are using multiple (different) VSA configurations in one XML file.
`-T`	All	Maximum number of threads that the server can use. Possible Values: 1 to 999.
`-m`	All	Minimum number of threads that the server can use. Note: The mean value of m and T is always used for the number of threads that are held open.
-L	All	Path specification for an SNC library
`-S`	All	The SNC name of this instance. Note: Setting L, S, or Q activates SNC for the server.
`-Q`	All	SNC security level. Possible Values: 1:=Authentication 2:=Integrity protection 3:=Encryption 7:=Minimum level 8:=DEFAULT 9:=Maximum level
`-P`	All	The SNC name of the SAP instance. Caution: If you set this name, only requests from SAP instances with this SNC identity are accepted.
`-I`	All	Timeout in seconds for the internal instance operations RELOAD and SHUTDOWN.
`-n`	All	Maximum number of trace lines for the memory trace. Default: 10000
`-h`	All	Retention period in seconds for the memory trace. Default: 86400 seconds
`-srvc`	Microsoft Windows NT	Service number of the Microsoft Windows NT commands install \| remove \| start \| stop
`-daemon`	UNIX	Starts the virus scan server as a daemon process with fork().