This article is finished.
With the help of Carrie E
One of the main reasons for this problem is the use of the MSP (Microsoft Patch) installer that we are using for the Service Packs (as well as the Fix Packs) installations on the XI3.1 platform.
The install/validate check routine in this process takes approximately 80% of the install time. When using this installer the process to find and replace a large number of files takes a long time.
We use the MSI installer for the SP/FP installs in XIR2 which is a faster technology and will be moving back to this with the XI3.1 Fix Pack installations.
The only available workaround currently available to address the SP2 installation time is by using the silent installation mode. This will skip this install/validate check routine and hence will be much quicker.
Another preventive measure to be taken is disabling the Antivirus program before starting the installation so that the Antivirus program does not interfere with the installation process.
How do I perform a silent installation? (A silent installation is quicker than an U.I. installation.)
The file below (we named it response.ini file, but you can name it whatever you like) is simply a file that contains the configuration information that would normally be entered in the setup wizard. This file is a text file that can be used to record the different options selected when running the setup in 'recording mode' (in our case we called it "response.ini" as it was in the official documentation). This will allow you to easily run a silent installation.
Regarding how to run in Silent mode, please refer to the installation guide "xi31_sp2_install_en.pdf" page 21 for detailled information.
In simple words, generate an ini file first. To do so: Open a command line console. From the directory that contains the BusinessObjects setup.exe file, run the setup.exe command with the write option (-w) specified:
setup.exe -w <filepath>\<filename>.ini
where <filepath>is the location where you want the file created and filename.ini is the name you have given to your file. Some people named this file the "response.ini" file.
Press Enter to launch the installation program. Follow the on-screen instructions to enter your preferred installation settings until you reach the Start Installation dialog box. Click Cancel to abort the installation. (see the screen shot below). The file will be automaticaly created (after few minutes).
Then run the silent installation with the command line:
setup.exe -r <filepath>\<filename>.ini
where <filepath> is the path to the <filename>.ini file that you created.
This file (in ourcase we named it response.ini) should be like that :
SS_INDEX_LOCATION="C:\<Installation_Path>\BusinessObjects Enterprise 12.0\data/search"
During the installation/upgrade a log file is created in the folder: C:\Documents and Settings****\Local Settings\Temp. In parallel, your task manager is working a lot.
When the installation/upgrade is finished, this file is moved to your <Installdir>\logging.
You can open this file, go to the end of the file, and look for the following sentence: completed successfully.
|Installation type||Log file name|
|Server XI 3.1 (English)||BOEInstall_0.log|
|Server XI 3.1 (French)||BOEInstall_fr0.log|
|Server SAP KIT XI 3.1||SAPik_0.log|
|Server SP2 (english)||BOE_SP2_Install_0.log|
|Server SP2 (French)||BOE_FR_SP2_Install_0.log|
|Server SAP KIT SP2||SAP_SP2_Install_0.log|
|Client XI 3.1||BusinessObjectsClient_0.log|
Please note that if you go through the Silent Mode and an "ini" file (in our case we called it "response.ini" as it was in the official documentation) this ini file creation can take quite a bit of time.
| Computer XXX1
Windows 2003 SP2
2 Gb of Ram
3 languages: French, German, English
Of course this time is only a example and can change depending of your hardware, network, etc.
|Click on setup.exe||started: 0:00|
|Get the "welcome to the BusinessObejcts .." screen.||0:09|
|Fill all screens and click "cancel" before the installation start.||0:10|
|Get the "Setup is not complete. If ..." screen and click "Exit Setup".||0:10|
|Get the screen "BusinessObjects ... was interrupted ..." and click "OK".||0:11|
|The screen disappears.||0:18|
|18 minutes to create the ini file.|
Of course, depending on your computer, disk, CPU, and network ,you won't have the same time to upgrade your XI 3.1 installation.
So we decided to measure different installation types on the same computer and give you these metrics.
If your installation has one language (English), after the upgrade you will get one "BOE_SP2_Install_0.log" file. If your installation has multiple languages, after the upgrade you will get mutliple files, for example: BOE_DE_SP2_Install_0.log and BOE_FR_SP2_Install_0.log.
| Computer XXX1
Windows 2003 SP2
2 Gb of Ram
language : English
|To do the XI 3.1 installation with UI||0h52 (**)|
|To do the Sp2 upgrade with UI||6h30 (**)|
|To do the Sp2 upgrade using silent mode with response.ini file||0h59 (**)|
(**) We measured these values with the log file created during the upgrade: BOE_SP2_Install_0.log (in the folder <Installdir>\logging) (and BOE_FR_SP2_Install_0.log & BOE_DE_SP2_Install_0.log for the multilanguages)
=== Verbose logging started: 8/11/2009 16:03:12
MSI (c) (90:C8) [17:02:52:484]: Product: BusinessObjects Enterprise XI 3.1 SP2 -- Configuration completed successfully.
You can install your BusinessObjects product on the C disk or on other disks such as D, E ...disks.
**Note: This assumes that the C drive is your system drive (the drive where windows is installed).
Even if you install your BusinessObjects product on D and/or E disks you will need space on the C disk. But the installer checks only the space on the disk you have installed the XI3.1 BusinessObjects product. If you have installed BusinessObjects XI3.1 on the D disk, the installer will check the space on D and not on C.
If you don't have at least 4.5Gb on C, during the installation, when you run out of space on C, you will get an error with the message: "not enough space on C:"
However, you will need around 4.5 Gb of Disk space on C for English only during the installation. Once the installation is finished, the installer will keep around 2.5 Gb of this 4.5 Gb on C: .
|Disk|| Mandatory Space for the SP2 upgrade
if your current BusinessObjects SP1 is installed on D drive
|C:||4.5 GB (for temp files + msp files)|
|D:||5 Gb (for Sp1 (4.5 Gb) + upgrade SP2 (0.5Gb))|
We describe below the folder and files used by the installer. Some of these files will stay on your system when the installation is finished, some will be automaticaly deleted.
|Location File Name||File Type||Size||Stay or remove once the installation is done||Purpose|
|C:\WINDOWS\Installer||1653f8.msp (the name of this file change for each installation)||1.138.462Kb||This file will stay on your system.||Cache of the MSP used for modify/repair/uninstall operations|
|C:\WINDOWS\Installer||16481a.msp (the name this of file change for each installation)||1.138.462kb||Once you click Finish, this file will be deleted.||Some reason internal to MSI technology.|
|C:\WINDOWS\Installer\$PatchCache$\Managed\xxxx\12.1.0||*.*||1.129.955kb||This file will stay on your system.||The cache of what's been backed up. The max size of this can be controlled through group policy. If you exceed the max size, the install might prompt for old MSI+cab files.|
|C:\Documents and Settings\xxxx\Local Settings\Temp||6803e.msp (the name of this file change for each installation)||1.138.462kb||Once you click Finish, this file will be deleted.||MSI makes a local copy of the .msp file.|
|C:\Documents and Settings\xxxx\Local Settings\Temp||BOE_SP2_Install_0.log||100.194kb||Once you click Finish, this file will be cut and copied to the Businessobjects logging folder)||Install log.|
|D:\<InstallDir>\BusinessObjects Enterprise 12.0 (SP1 + upgrade SP2)||*.*||5.07 GB - 62 171 files, 5809 folders|
If you are upgrading any fixpack after FP1.5 then all the newer versions of a particular binary from FP1.6, FP1.7, FP1.8 will be replaced with the SP2 version of the file, which means you will lose those fixes inlcuded in these FP. You won't be prompted to warn you. So once your SP2 is installed, you need to install immediately the FP2.1 in order to get these fixes.
Same thing, if you are in XI3.1 FP1.9 and if you want to upgrade to SP2, once the SP2 is installed, you need to install immediately the FP2.3.
Please contact your account manager, if you have any question about this installation path.
We will provide mutliple packages for the following products:
• BusinessObjects Enterprise XI
• BusinessObjects Enterprise XI Client Tools
If you installed client tools using the Client Tools option from the full
BusinessObjects Enterprise XI installation program, you will need to use
the BusinessObjects XI update package to update those tools. The Client
Tools update package will work only if the tools were installed by
BusinessObjects Enterprise XI Client Tools installation program.
Otherwise ,you will get the following error: BusinessObjects Enterprise XI3.0 client tools have been detected. BusinessObjects Enterprise XI3.1 cannot be installed: STW00247