![]() ![]() Here’s what I have under “C:Program Files (x86)” Here’s what I have under “C:Program Files” So I guess my default installation directory really should have been “C:Program Files”. 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)”. Just note, when calculating my start time, and end time, I was taking screen shots and documenting at the same time. Can be added after.įinally, it was ready to begin actual installation Kept default option, not to integrate to Intrascope. Kept default option, not to configure SMD. Kept default Subversion configuration, and gave passwords, again as instructed earlier. I kept the default BOBJ user account name as “boeuser”, and filled in the passwords, as instructed above. I gave mine “Abcd1234” which worked fine. So if you wish to keep them all the same, start here. This error message is complaining about both “SQL Server Administrator” and “boeUser” users. Here is an error message you will get, if they are now. These last two user password requirements are more stringent. Password time… Remember, make sure it abides by any Group Policies you may have.Ĭoming soon you will have to also give passwords to the “SQL Server Administrator” and “boeUser” 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. ![]() 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). Notice the deselected options, fine for my purpose Also note, if you remove the “(x86)” from the path, it still installs into the “(x86)” directory. Update : I now realize it is a 64bit installation. ![]() I need to know a little more about this as I believe it is a 64bit installation. Interesting to note the “(86)” in the path. I chose “Custom / Expand” to show you the options, although I will be selecting them all, as with a “Full” installation. I believe you cannot add any after the initial installation, so choose any extra languages now. I continuedįilled out form, and fetched license key for “SBOP Enterprise Premium (4 CPU) I ran “setup.exe under” “51041015DATA_UNITSBusinessObjectsServer_win” directory. If you must perform a name change, do it after the extraction.Įxecute “51041015_part1”, by right clicking and “Run as administrator”. Tip: do not rename the “.exe” or “.rar” files, as they maynot extract successfully. 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Īll the latest offerings can be downloaded, according to your S-ID authorizations. Please note, if I did have a problem, i’d be the first to read it. The BI4 Installation Guide is rich and complete, however, I performed the steps below without reading it. The installation process, on the surface, is identical to SP0 and SP1, and the screen shots below are still valid. update:As I suspected, SP2 will cleanly install. The non existence of any previous SP, indicates that SP2 can be installed as a clean install (without any previous SP). If you decide to add a component after an SP installation, you will need to re-install the SP.Įven more important, you cannot add a language after the installation. ![]() Important: When preparing your BOBJ4 environment, be mindful that, SPs do not update components that are not installed. Although SP1 is out, you will still need to install this prior as SP1 will ask for it. I am now ready for installing BusinessObjects 4.0. Continuing from my last blog Caboodle – Part 2 – The NSP 7.02 Post Install ![]()
0 Comments
Leave a Reply. |