Skip to Content

Step-by-Step Guide to install SAP BusinessObjects Business Intelligence (BI) platform 4.x on Windows OS with Best Practices (PART 1)

Hi,

Installing SAP BusinessObjects Business Intelligence (BI) platform 4.x on Windows Platform seems to be very simple if we keep the configuration, hardware, policies etc as per the requirements and recommendations from SAP. But Different companies has different configurations, rights assigned to bo admin, policies set for bo admin etc which affects the installation directly or indirectly.

I have accumulated the changes and best practices to install the SAP BI 4.x on Windows Operating in this document so that BO Administrators can install the product as smoothly as it can be installed on the server by following the best practices and making necessary changes on the windows operating system level.


In this document I am trying to install BI 4.2 SP2 on Windows 2012 server.You can follow the steps for installing BI 4.X on Any Windows Operating System.


This Document is applicable on below products :

  • SAP BusinessObjects Business Intelligence (BI) platform 4.x
  • SAP Crystal Server 4.x
  • SAP IPS 4.x
  • SAP Explorer 4.x
  • SAP Add-on like Design Studio, Data Services Etc
  • SAP Client Tools 4.x Installation on Client Machine.



Setting up the Machine ( Hardware requirements )


The best way to get the recommendations and to get FULL SUPPORT is to refer PAM Guide ( Product Availability Matrix ). In this guide Minimum Hardware recommendation and supported components which should be installed with your product is provided.

  • For Quick Information : Minimum 16 GB RAM (For Default Installation) / Minimum 4 Core (Recommended) is required / Supported OS as per PAM. Mosre importantly atleast 20 GB Free Space should be present in Installation drive and 4-6 GB in the Temp folder.

Preparing the BO Account / Service Account for Installation :


Here I have created BOADMIN account which is in BIPW2K12EN Domain to install the product. Most of the companies create a SERVICE ACCOUNT instead of giving rights and setting policies for the different users. The steps and configuration will be same for it too.


  • Open Computer Management Console



  • Here I have created BOADMIN as the service account to install and run BI.

  • Add the user to the Administrator Group.

  • Right Click >> Add To Group

  • Write the user name or in format DOMAIN\USERNAME and click Check Names.

  • It will automatically fetch the details for the account.

  • Click Apply and then OK which will confirm the user is in the Admin Group.

  • Open Local Security Policy From Administrator Tools.

  • Click User rights Assignment. Right Panel list of rights will be populated.
    • Below are the Policies where we are adding the BOADMIN
      • Act as a part of the operating system
      • Log on as a batch job
      • Log on as a service








  • After adding all the policies we are updating the Group Policy changes by running the command in Command Prompt.
    • Open cmd
    • Run : gpupdate

  • You should get the message for successful completion.

  • From Below section we are following the BEST PRACTICE KBA 1952120 - Installation/Update/Patching pre-requisites & best practices for SAP BusinessObjects XI 3.1 and SAP BusinessObjects Platform (BI) 4.0/4.1/4.2
  • Once the product is installed then you can revert back these changes if required.


    • Changing DEP Control . Data Execution Prevention (DEP) is a security feature that can help prevent damage to your computer from viruses and other security threats. Harmful programs can try to attack Windows by attempting to run (also known as execute) code from system memory locations reserved for Windows and other authorised programs. This option will allow the SAP product executable to be written in the system memory. You can also add the exception but I prefer to completely disable and them again enable once the installation is done.





  • After making the changes it will ask you to restart the system. Click OK.

  • Changing the UAC control.UAC is a security feature of Windows which helps prevent unauthorised changes to your computer. These changes can be initiated by applications or other users. User Account Control makes sure these changes are made only with approval from the administrator. To prevent this we make it to never notify and then once the installation is done we revert it back as per the company settings.

  • Drag the bar to the bottom as Never notify.


  • Network Interface Card (NIC) :

    • Multiple NIC Card Priority : It is becoming commonplace to have more than one Ethernet adapter in a PC or embedded controller, especially in systems where wired and wireless adapters are both present. However, the presence of more than one Network Interface Card (NIC) can cause connectivity problems if each network interface is not carefully configured to account for the overall network layout. Set the correct priority of the NIC card to avoid the communication issues.
    • On the windows server where BI4 will be installed, ensure that IPV4 is preferred over IPV6 by following:
      • Microsoft Kbase 929852 - Microsoft fix it 50410 (A server reboot is required after this step).
      • Check KBA : 1767633 - SIA node is not getting created during BI4 install


  • Open CMD and run : ipconfig.
  • Here I have 3 NIC adpaters and IPv6 Enabled. Where Ethernet is the primary. in many cases this is not set correct so follow below steps.

  • Open Network Connections.
  • Open CMD >> run : ncpa.cpl


  • Right click the Primary NIC Adapter >> Uncheck IPv6


  • Hold ALT key on the keyboard and Advance option will be enabled.
  • Click Advance Settings.


  • Set the priority of the Primary Adaptor to the top by using the up Arrow.


  • Re confirm by running the IPCONFIG again and IPv6 is disabled.



  • Most importantly please ensure ANTIVIRUS is completely Disabled / Turned Off.




Please click on Link for Part 2 :


Step-by-Step Guide to install SAP BusinessObjects Business Intelligence (BI) platform 4.x on Windows OS with Best Practices (PART 2)




Tags:
Former Member