Continuing from my last blog Caboodle – Part 2 – The NSP 7.02 Post Install
I am now ready for installing BusinessObjects 4.0. Although SP1 is out, you will still need to install this prior as SP1 will ask for it.
Important: When preparing your BOBJ4 environment, be mindful that, SPs do not update components that are not installed. If you decide to add a component after an SP installation, you will need to re-install the SP.
Even more important, you cannot add a language after the installation.
13.7.2011 update: Added the SP1 install.
29.7.2011 update: Now the whole suite is on SP2. The non existence of any previous SP, indicates that SP2 can be installed as a clean install (without any previous SP). I will try this, and update here.
1.8.2011 update: As I suspected, SP2 will cleanly install. No need for any previous installations. The installation process, on the surface, is identical to SP0 and SP1, and the screen shots below are still valid.
The BI4 Installation Guide is rich and complete, however, I performed the steps below without reading it. Please note, if I did have a problem, i’d be the first to read it.
You can get it using the Quick Link “instguides”
The blog is organized by
- SP1 Install
So to begin…
Four files/objects are required, for BOBJ Enterprise
51041015_1, 51041015_2, 51041015_3, 51041015_4
Under Software Downloads->BusinessObjects Downloads->Browse the SAP BusinessObjects Portfolio->Installation and Upgrade->SBOP BUSINESS INTELLIGENCE PLATFORM (SBOP ENTERPRISE)->SBOP BI PLATFORM 4.0->Installation and Upgrade->WINDOWS
All the latest offerings can be downloaded, according to your S-ID authorizations.
Tip: do not rename the “.exe” or “.rar” files, as they maynot extract successfully. If you must perform a name change, do it after the extraction.
Execute “51041015_part1”, by right clicking and “Run as administrator”. Extracts to directory “51041015” which is 3.70GB (3,982,624,464 bytes – 26,166 Files)
I ran “setup.exe under” “51041015DATA_UNITSBusinessObjectsServer_win” directory.
Interesting, note Windows version. Guess it does not like Windows 7. I continued
Accepted Terms, then “Next”
Filled out form, and fetched license key for “SBOP Enterprise Premium (4 CPU)
Kept default installation language. I believe you cannot add any after the initial installation, so choose any extra languages now.
I chose “Custom / Expand” to show you the options, although I will be selecting them all, as with a “Full” installation.
I kept default installation location. Interesting to note the “(86)” in the path. Looks like a 32bit installation. I need to know a little more about this as I believe it is a 64bit installation.
Update 7/7/2011: I now realize it is a 64bit installation. Also note, if you remove the “(x86)” from the path, it still installs into the “(x86)” directory. Obviously something broken here.
And now the options
Notice the deselected options, fine for my purpose
“Disk Cost”, for my options
If you select the four unselected option items (above), “Disk Cost” is exactly the same, except “Difference” went up 1 GB (must have spanned the GB, I cannot believe it contained 1GB of files).
Left default “Start a new …”
Now I read somewhere, that it is not good practice to call the SIA Node, the same name as the Server, so I called mine “BOBJ4”, and kept the default “SIA Port” at 6410.
Kept the default CMS Port as 6400
Password time… Remember, make sure it abides by any Group Policies you may have.
Coming soon you will have to also give passwords to the “SQL Server Administrator” and “boeUser”
These last two user password requirements are more stringent. Here is an error message you will get, if they are now. This error message is complaining about both “SQL Server Administrator” and “boeUser” users.
So if you wish to keep them all the same, start here.
I gave mine “Abcd1234” which worked fine.
I kept the default BOBJ user account name as “boeuser”, and filled in the passwords, as instructed above.
Left as is
Kept default Tomcat ports
Kept default WACS listening port
Kept default Subversion configuration, and gave passwords, again as instructed earlier.
Kept default option, not to configure SMD. Can be added after.
Kept default option, not to integrate to Intrascope. Can be added after.
Finally, it was ready to begin actual installation
10:42, sits here for quite a while
Just note, when calculating my start time, and end time, I was taking screen shots and documenting at the same time. Realisticly, it took just over an hour.
Now a re-boot.
Upon inspection, it seems nothing made it’s way into my 64bit program directory “C:Program Files”, rather into the 32bit, “C:Program Files (x86)”. So I guess my default installation directory really should have been “C:Program Files”. Assuming the version I have, IS 64 bit.
Here’s what I have under “C:Program Files”
Here’s what I have under “C:Program Files (x86)”
Here’s what I have under “C:Program Files (x86)SAP BusinessObjects”
Finally under “C:”
Mmmmm, interesting directory
Now here’s what I have as Programs
better view of above
Taking a look at the CCM
I see the BW Publisher Service but there were no prompts for BW System or other parameters. I will look into this later.
Digging deeper into the SIA, after logging in
The WebApplicationContainerServer did take a good 15 minutes, but it did eventually Run, and become “Enabled”
Starting the CMC
Not exactly sure what is going on, but everything is really slow.
15 minutes later …
And here, I finally arrive
After installing adobe flash 32bit, (64 wont work with IE9 at the moment), I fired up the “Monitor”.
To reveal no errors or otherwise
I am happy to conclude that the installation was rather uneventful, with absolutely no technical problems.
Returning to this blog, to document the un-eventful (which is good) SP1 install.
After downloading the SP1 file
executed to it’s own directory
kicked of the “setup.exe”
I kept the default language
prerequiste checks out ok
Accepted the license
Supplied the CMS credentials, and Administrator password
Off it goes, time? 08:00 (will take about 2 hours)
A look in Control Panel->Programs and Features. There it is
Continue to my next blog, Caboodle – Part 4 – The BOBJ4 Post Install