Home / Business Intelligence / Antivirus Software: Good or Bad for BO 4.1?

Antivirus Software: Good or Bad for BO 4.1?

Having antivirus software is great to maintain the immunity of a system, but in certain cases these AV softwares can start to over work themselves and it can really take a toll on the machine and can also affect the overall performance of Business Objects.

I have seen clients face issues such as long waiting time after opening a report, log in issues, Slow CMC etc. This happens when the scans on the system and Low-level monitoring are performed too constantly.

How do you know if it’s the AV product that is sucking minutes or hours of your productivity and performance away from your foreground tasks (BO)? You can do that by logging on to the Server where BO is installed and go to the Task Manager – Performance – Resource Monitor and observe the CPU usage.

A recent example of this is a screen shot from a client’s system below that shows the CPU usage by McAfee is very high during each scan. In Launchpad this caused delayed or log in failure and delays in opening a report and slow or unresponsive CMC.

anti-virus-good-or-bad-for-bo-4.1

So in such cases we need to Configure Anti-Virus software to exclude Binaries and Directories for BO 4.1 (SAP – KB: 1497394, 106267, and 1625003)

Note: Every Anitvirus (AV) works in a different way, but excluding the Binaries and Directories should help BO with its normal performance and also free up the CPU consumption by the AV software.

Configure Anti-Virus software to exclude Binaries and Directories

The following binaries should be excluded from active scanning:

SAP BusinessObjects Business Intelligence 4.1
AAAnalytics.exeAADashboard.exeSvcMgr.exeCMS.exeConnectionServer.exeConnectionServer.exe (32bit)crcache.execrproc.exe

crproc.exe (32bit)

crystalras.exe (32bit)

EventServer.exe

fileserver.exe

JobServer.exe

JobServerChild.exe

sia.exe

WIReportServer.exe

xccache.exe

xcproc.exe

java.exe

tomcat6.exe

sqlservr.exe

svnserve.exe (32bit)

dbsvr12.exe

tomcat7.exe

 

The following directories should be excluded from monitoring/scanning:

SAP BusinessObjects Business Intelligence 4.1
%INSTALLDIR%\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win32_x86%INSTALLDIR%\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64%INSTALLDIR%\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\logging%INSTALLDIR%\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java%INSTALLDIR%\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\data%INSTALLDIR%\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\FileStore%INSTALLDIR%\SAP BusinessObjects\MSSQLSERVER2008%INSTALLDIR%\SAP BusinessObjects\Tomcat6\bin

%INSTALLDIR%\SAP BusinessObjects\Tomcat6\webapps

%INSTALLDIR%\SAP BusinessObjects\Tomcat6\work

%INSTALLDIR%\SAP BusinessObjects\tomcat\bin

%INSTALLDIR%\SAP BusinessObjects\tomcat\webapps

%INSTALLDIR%\SAP BusinessObjects\tomcat\work

 

Note that although for performance reasons it’s recommended that active scanning of these files and directories be excluded during usual hours of operation and during report schedules, it is still recommended to run a full system scan during off peak hours/maintenance hours.

About Minith Patel

Minith Patel is a Senior Business Intelligence Consultant for InfoSol Inc. He is adroit in Business objects system administration and is well-versed in Version Manager and 360View. He has Project Management experience and has worked on global design, implementation and development projects for business objects and has over 5 years of experience in SAP industry. In his free time he is known to be a Japanophile.

Check Also

The Secret Behind the Naming of IBIS

The Secret Behind the Naming of IBIS

I was recently talking to Paul about the IBIS conference and I asked him how ...