Business Objects Business Objects XI R2 SP1

Version: 11
Views: 3.1k  |  Created: 09/08/2006

Average Rating: 0
Business Objects XI R2 SP1 has 1 inventory records, 2 Questions, 0 Blogs and 0 links. Please help add to this by sharing more!

Deployment Tips (16)

Most Common Setup Type
Not Determined
Average Package Difficulty Rating
Rated 4 / 5 (Somewhat Difficult) based on 3 ratings
Most Commonly Reported Deployment Method
Windows Installer with Custom Transform (MST)
or cancel
122
Note
When deploying only Desktop Intelligence or Designer you can reduce the size of your package more than 85% by removing unnecessary cab files used for other install features.

Designer requires the following cabs: m10.cab
m2.cab, m9.cab, m12.cab, m13.cab, m14.cab, m15.cab, m16.cab, m17.cab, m18.cab, m19.cab, m20.cab, m21.cab, m22.cab, m23.cab, m24.cab, m26.cab, m32.cab, m37.cab, m59.cab, m77.cab, m79.cab, m84.cab, m86.cab, m88.cab, m90.cab, m92.cab, m93.cab, m96.cab, m98.cab, m102.cab, m103.cab, m104.cab, m107.cab, m109.cab, m121.cab, m125.cab, m144.cab, m153.cab, m160.cab, m164.cab, m166.cab, m169.cab, m171.cab, m172.cab, m175.cab, m180.cab, m183.cab, m189.cab, m197.cab, m201.cab, m202.cab, m205.cab, m207.cab, m208.cab, m212.cab, m221.cab, m230.cab, m231.cab, m232.cab, m233.cab, m234.cab, m235.cab, m236.cab, m237.cab, m238.cab, m239.cab, m240.cab, m241.cab, m247.cab, m249.cab, m250.cab, m251.cab, m252.cab, m253.cab, m254.cab, m255.cab, m256.cab, m257.cab, m258.cab, m259.cab, m260.cab, m261.cab, m264.cab, m267.cab, m270.cab, m271.cab, m272.cab, m273.cab, m274.cab, m275.cab, m276.cab, m277.cab, m278.cab, m279.cab, m280.cab, m281.cab, m284.cab, m287.cab, m288.cab, m289.cab, m290.cab, m291.cab, m292.cab, m293.cab, m295.cab, m296.cab, m298.cab, m300.cab, m301.cab, m302.cab, m303.cab, m304.cab, m305.cab, m306.cab, m307.cab, m310.cab, m314.cab, m315.cab, m316.cab, m317.cab, m322.cab, m323.cab, m324.cab, m325.cab, m326.cab, m327.cab, m328.cab, m329.cab, m330.cab, m331.cab, m332.cab, m333.cab, m334.cab, m338.cab, m344.cab, m352.cab, m360.cab, m375.cab, m379.cab, m386.cab, m387.cab, m388.cab, m389.cab, m390.cab, m391.cab, m392.cab, m393.cab, m397.cab, m398.cab, m403.cab, m404.cab, m405.cab, m406.cab, m407.cab, m408.cab, m409.cab, m411.cab, m412.cab, m413.cab, m414.cab, m415.cab, m416.cab, m417.cab, m423.cab, m427.cab, m428.cab, m429.cab, m430.cab, m431.cab, m432.cab, m433.cab, m434.cab, m435.cab, m439.cab, m440.cab, m464.cab, m470.cab, m471.cab, m472.cab, m476.cab, m478.cab, m482.cab, m483.cab, m485.cab, m486.cab, m493.cab, m494.cab, m495.cab, m496.cab, m497.cab, m500.cab, m501.cab, m502.cab, m503.cab, m504.cab, m505.cab, m506.cab, m507.cab, m508.cab, m509.cab, m510.cab, m511.cab, m512.cab, m515.cab, m516.cab, m519.cab, m52.cab, m520.cab, m521.cab, m522.cab, m523.cab, m524.cab, m525.cab, m526.cab, m527.cab, m535.cab, m536.cab, m537.cab, m539.cab, m540.cab, m541.cab, m543.cab, m545.cab, m546.cab, m547.cab, m548.cab, m552.cab, m553.cab, m554.cab, m555.cab, m556.cab, m557.cab, m558.cab, and m559.cab.

This may seem like a lot of cabs still, but their size is significantly smaller (242MB instead of 1.7GB). You can install only Desktop Intelligence with the following command line: Setup.exe /qb!- REBOOT=ReallySuppress CLIENTLANGUAGE=EN INSTALLLEVEL=4 INSTALLSWITCH="Client" ADDLOCAL="Reporter"

Similarly, you can install Designer with the following command line: Setup.exe /qb!- REBOOT=ReallySuppress CLIENTLANGUAGE=EN INSTALLLEVEL=4 INSTALLSWITCH="Client" ADDLOCAL="Designer"

The CAB files needed to install Designer are m2.cab, m9.cab, m10.cab, m26.cab, m32.cab, m37.cab, m52.cab, m59.cab, m72.cab, m76.cab, m77.cab, m79.cab, m84.cab, m86.cab, m88.cab, m90.cab, m92.cab, m93.cab, m96.cab, m97.cab, m98.cab, m102.cab, m103.cab, m104.cab, m107.cab, m109.cab, m121.cab, m125.cab, m126.cab, m130.cab, m144.cab, m153.cab, m160.cab, m164.cab, m165.cab, m166.cab, m169.cab, m171.cab, m175.cab, m180.cab, m183.cab, m188.cab, m189.cab, m197.cab, m201.cab, m202.cab, m205.cab, m207.cab, m208.cab, m212.cab, m219.cab, m220.cab, m221.cab, m241.cab, m247.cab, m264.cab, m267.cab, m268.cab, m284.cab, m287.cab, m288.cab, m289.cab, m290.cab, m291.cab, m292.cab, m293.cab, m295.cab, m296.cab, m298.cab, m300.cab, m301.cab, m302.cab, m303.cab, m304.cab, m305.cab, m306.cab, m307.cab, m310.cab, m314.cab, m315.cab, m316.cab, m317.cab, m338.cab, m344.cab, m350.cab, m352.cab, m360.cab, m366.cab, m368.cab, m375.cab, m376.cab, m377.cab, m378.cab, m379.cab, m380.cab, m397.cab, m398.cab, m404.cab, m405.cab, m406.cab, m407.cab, m408.cab, m409.cab, m411.cab, m412.cab, m413.cab, m414.cab, m415.cab, m416.cab, m417.cab, m423.cab, m439.cab, m440.cab, m464.cab, m470.cab, m471.cab, m472.cab, m476.cab, m478.cab, m480.cab, m481.cab, m485.cab, m493.cab, m494.cab, m496.cab, m497.cab, m500.cab, m501.cab, m502.cab, m503.cab, m504.cab, m505.cab, m506.cab, m507.cab, m508.cab, m509.cab, m510.cab, m511.cab, m512.cab, m515.cab, m516.cab, m519.cab, m520.cab, m524.cab, m525.cab, m532.cab, m535.cab, m536.cab, m537.cab, m539.cab, m540.cab, m541.cab, m543.cab, m545.cab, m546.cab, m547.cab, m548.cab, m552.cab, m553.cab, m554.cab, m555.cab, m556.cab, m557.cab, m558.cab, and m559.cab.

You can optionally combine both cab sets and use ADDLOCAL="Designer,Reporter" to install both. Most of the cabs are shared by both features, and so combining the two installs into one only increases the package size to 259MB.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
119
Command Line
The Client package is not supported for silent installs.
(Although the server is.) I found a way to do this - use the following:

msiexec /I "...\win32\BusinessObjects.msi" TRANSFORMS=:1033 INSTALLSWITCH="CLIENT" PIDKEY=xxxx-xxxx-xxxx-xxxx /qn

This installs the full set of client tools.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
119
Note
If someone wants to use the MSI file without the Setup.exe, for an example, deploying Business Objects using GPO or to run the MSI with the /qb switch?
Create an MST and peform the following changes:

In both the "InstallExecuteSequence" and "InstallUISequence" table find the action
"BlockUnlocalizedMlbInstall.9CED35E4_C9E6_11D3_9833_00A0C9DA4FE9" and change the condition to "0 And ProductLanguage = -1".

Now you should be able to use the /qb switch.
The application could now be deployed per machine using GPO without any changes.

To install only Desktop Intelligence, install the feature "Reporter".

Example:
msiexec /i "...\win32\BusinessObjects.msi" ADDLOCAL=Reporter

This will install only Desktop Intelligence client.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
119
Note
We ran into all sorts of issues getting this package to install using an MST. Here are the settings we used to create a succesful package.

I. Opened the MSI using Wise Package Studio.
II. Doing a save as we saved it as an MST.
III. Edited the MST.
A. In the poperties added PIDKEY and the license number

NOTE: without this the install will say it needs it. you may put this info in your SMS command line as well

B. made changes in the tables
1. InstallExecuteSequence
a. BlockUnlocalizedMlbInstall
1. 0 And ProductLanguage = -1
2. InstallUISequence
a. BlockUnlocalizedMlbInstall
1. 0 And ProductLanguage = -1

NOTE. This allowed the install to run without the setup EXE

C. Added MITMIN30.dll to always install files in system32

Note: You will find this in cabinet file M211. It will need to be renamed because Business Objects adds a bunch of numbers to the end. This needs to be added because for some reason the install won't find it otherwise.

IV. Compile and test

At this point you will have an MST that will transform the MSI, and do a full install, and be deployable through SMS.

Any other customizations are up to you, and your needs.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
119
Terminal Services

For your information, although BO Xi R2 is not supported on Citrix Presentation Server 4.0 (OS: W2K3 Standard Edition), we have successfully installed it on that platform, without any other customizations than needed for a "normal" install.

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
119
Command Line
The Client package is supported for silent installs.
I found a way to do this - use the following PROPERTIES for installing the Client (English) :

CLIENTLANGUAGE=EN INSTALLLEVEL=4 INSTALLSWITCH=Client TRANSFORMS=:1033 CLIENTUILEVEL=3 MSICLIENTUSESEXTERNALUI=1

Because we use a wrapperscript to start the msi i don't have to add the parameters for silent install (/qn) and the logging (/L*v %filepath%).

You can findout your parameters if you start the setup.exe with logging enabled. In the logfile you find the necessary PROPERTIES for your installation !
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
119
Note
When a new user log in the machine a self-healing operation may begin. To stop this you should edit .mst file to contain the following property values:

ReinstallRepain = o
UIReinstalMode = o

o = optional
r = required
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
118
Security
We have noticed that users need write access to
C:\Program Files\..\BusinessObjects Enterprise 11.5\win32_x86 if you use the Import Wizard.
Import Wizard creates log files under that folder.
Any information on how to change the log folder is welcome.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
118
Command Line
In Order to install any of the tools associated with the XI R2 SP1 11.x suite a command may be run against the .Exe to achive a nearly fully silent install....

For a Single Client Tool:
"<Path to setup.exe> /qn+ REBOOT=ReallySuppress CLIENTLANGUAGE=EN INSTALLLEVEL=4 INSTALLSWITCH="Client" ADDLOCAL="Clients,ClientFeatureName"

For Multiple Client Tools:
"<Path to setup.exe> /qn+ REBOOT=ReallySuppress CLIENTLANGUAGE=EN INSTALLLEVEL=4 INSTALLSWITCH="Client" ADDLOCAL="Clients,ClientFeatureName1,ClientFeatureName2,ClientFeatureName3"

***Using these methods the install will not display any dialogs during install but there will be a message box informing of the install completing where it is necessary to click OK.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
118
Security

BOXI R2 - Using Desktop Intelligence to retrieve a report with a locked down account generates an abort. This is due to a temp file trying to be created on root of C: - fixed with BO Fixpack 2.4

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
117
Note
Found that changing the CLIENTLANGUAGE property resolves issues with the MITMIN30.DLL file. In our instance we set CLIENTLANGUAGE to EN however there are other language versions.

In the initial MSI CLIENTLANGUAGE is set to MLB which doesn't correspond to any condition in the component table that allows a version of MITMIN30.DLL to install.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
117
Command Line

The INSTALLSWITCH property is case sensitive. For client installations the “Client” is the appropriate setting. If specify the setting correctly you will not need to use the PIDKEY property.

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
117
Note

Had to set the INSTALLLEVEL to at least 5. The default for INSTALLLEVEL is 3, and some of the features have an install level of 4 and 5.

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
117
Note
According to BusinessObjects documentation, an INSTALLLEVEL of 4 is enough for client tools.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
117
Command Line

The INSTALLSWITCH property is case sensitive. For client installations the “Client” is the appropriate setting. If specify the setting correctly you will not need to use the PIDKEY property.

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
116
Note

I needed DotNet1.1 installed as a pre requisite

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment

Inventory Records (1)

View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.

Versions

Business Objects XI R2 SP1

Version

11

Questions & Answers (2)

Questions & Answers related to Business Objects Business Objects XI R2 SP1

4
ANSWERS

Blogs (0)

Blog posts related to Business Objects Business Objects XI R2 SP1

Reviews (0)

Reviews related to Business Objects Business Objects XI R2 SP1