Virus Scan for ABAP Web Services
Use
On the provider side, you can use the Web services virus scan to scan incoming messages for viruses. Both the message payload and the message attachments are scanned for viruses at Web service runtime. If a virus infection is detected, message processing is stopped and a system error is displayed in the message monitor (transaction code SRT_MONI) and in the error log.
The virus scans are executed:
-
On the provider side, when the payload or the attachments are processed.
-
On the consumer and the provider side, when the payload or attachments are downloaded.
-
On the consumer and the provider side, when the payload or attachments are displayed in the message monitor, the payload trace monitor, the functional trace monitor, and the error log monitor.
Prerequisites
You use the virus scan interface of SAP NetWeaver.
For more information, see the SAP NetWeaver Library on the SAP Help Portal at http://help.sap.com
under .
Procedure
-
Display the messages in the message monitor (transaction code SRT_MONI).
-
For the messages with system errors, check the Error Information column. This is where the information about any detected viruses is displayed. It indicates whether the virus was detected in the message payload or in an attachment.
Note that if a virus was detected, a warning is displayed if you try to download the message or an attachment. A message in which a virus was detected can not be processed any further.
-
(Optional) To download an attachment, display the message properties by double-clicking an entry in the list.
On the left hand-side, right-click the attachment and choose Download. Before the download starts, the virus scan is performed again. You can only download the attachment if no virus was detected.
-
(Optional) To display the message payload, select an entry and choose Error Log. In the error log, double-click an the entry to display the error context and choose Payload. Before the message payload is displayed, the virus scan is performed.
More Information
For more information, see SAP Note 1671303
.

