I am planning to upgrade from 4.x to 5.x . Got 5.x installed just now. But didn’t find the upgrade wizard under tool menu is Supervisor. Where should I look for it ? Our version is 5.0.2.
Thanks
Abhijit
You should log into V5 supervisor using the original V4.1 GENERAL SUPERVISOR who created the repository and then it will automatically recognise that there is a previous Version and prompt you to upgrade. There is no upgrade tool in the Supervisor menu in V5
Tania Mason
Executive Computing Group
I am planning to upgrade from 4.x to 5.x . Got 5.x installed just now. But didn’t find the upgrade wizard under tool menu is Supervisor. Where should I
look for it ? Our version is 5.0.2.
Thanks
Abhijit
I think I was not able to communicate my issue properly last time. I have BO 4.1.6 production repository in Oracle database. I am planning for an upgrade to 5.0.2. I don’t want to dircetly apply the upgrade in production. So I installed BO 5.0.2 in a desktop and created a brand new 5.0.2 repository in another Oracle instance. When I did my last upgrade from 3.x to 4.x , I saw that upgrade wizard looks for source repository (repository to be upgraded) and destination repository. That way it was possible to upgrade it in a totally different area. Is it still possible in 5.0.2 ? I didn’t find the upgrade wizard in supervisor. Any suggestions … Thanks
Abhijit Bhattacharya
Instead of creating brand new repository in another oracle instance, import all the oracle objects from production instance andd export them to new oracle instance. Now start BO4 (NOTE BO4) supervisor create a BOMain.Key to new repository, Go to Tools–> Repository menu item and correct all the domain connections. (This would point to your old domain right. Change them to point to new domain.)
Then Start BO5 supervisor and connect to New repository, it will ask you for upgrade.
Hope it helps
Vasan
Baton Rouge International
Data Warehousing Division
ABhattacharya@EA.COM on 03/30/2000 11:31:59 AM I think I was not able to communicate my issue properly last time. I have BO 4.1.6 production repository in Oracle database. I am planning for an upgrade to 5.0.2. I don’t want to dircetly apply the upgrade in production. So I installed BO 5.0.2 in a desktop and created a brand new 5.0.2 repository in another Oracle instance. When I did my last upgrade from 3.x to 4.x , I saw that upgrade wizard looks for source repository (repository to be upgraded) and destination repository. That way it was possible to upgrade it in a totally different area. Is it still possible in 5.0.2 ? I didn’t find the upgrade wizard in supervisor. Any suggestions … Thanks
Abhijit Bhattacharya
******************************************************************************* Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Ernst & Young LLP
The workflow to go from 4.x to 5.0 is very different than it was to go from 3.x to 4.x.
The installation of the client does not require knowing about the existing repository.
Then, once you install and you are ready to work in the new version, you have to ask yourself whether you want to upgrade your existing repository (and keep all your user definitions and exported resources) or create a brand new one (and start from scratch). You decide when you enter Supervisor 5.0.
It sounds like you chose the latter, and you have a new BOMain.key for the 5.0 repository… no big deal.
During the client installations, you also have an option: whether to upgrade the application or install it separately. Choose whatever you desire (most people will upgrade the existing application). The critical thing to do is share with the new installations your new BOMain.key file.
I think this answers your question.
Just keep in mind that BO v4.x can login to a v5.0 repository, but BO v5.0 cannot use a v4.x repository.
Aleksejs - I don’t think you need to do step #2 because your clients get the BusObj executable from the server in a shared installation. After updating the server installation to 5.0.2, clients should automatically use 5.0.2.
That depends on how the master setup was done. If they set it up to share the executables from the server, then, yes, no reinstallation is necessary on the clients. If, however, they set it up to install locally from the server where the master setup was done, then a reinstall has to be done.
You can use automated install tools to perform the client installs in the middle of the night or when users log in. I did a job a few months ago where we used one from McAfee if I remember correctly. We built it to push the installed version of the application down to the client’s PC when they logged in to the network. This took care of all the executables and other files, as well as all the registry entries. It worked quite well.
Hope that helps,
Paul
On Thursday, April 27, 2000 9:41 AM, “Baranowski, George” [GBaranowski@QUADRAMED.COM] wrote:
Aleksejs - I don’t think you need to do step #2 because your clients get
the
BusObj executable from the server in a shared installation. After
updating
the server installation to 5.0.2, clients should automatically use 5.0.2.
George Baranowski
QuadraMed
Hello.
There is BO 5.0.1 and WebI 2.5.1. in our production environment. Now we need to install version 5.0.2.
Every BO user in our company uses BO shared installation. As far as I understand, We should:
Change master setup on a server;
Reinstall BO on every client computer.
Is It true? May be there is some kind of automatic version upgrade?
Any ideas? Thanks!
Aleksejs Jevsejenko
BO parvaldnieks
VID Datu Noliktavas projekts
A/S DATI, Skanstes iela 13
LV 1013 Riga, Latvija
Most of this is true.
To move from v5.0.1 to v5.0.2, you must
Update your current Master setup on the server. 2) The Shared client installations will be prompted to update when they login. Click Yes/Ok to start the quick setup program to update.
You got it right. That’s how you do it. The upgrade should go smoothly since you won’t need to retype all the product keys when simply installing a new service pack.
Pasi Pulkkinen (pasi.pulkkinen@affecto.fi) BusinessObjects Consultant
AFFECTO (Enator Group)
Kutojantie 7, 02630 Espoo, FINLAND
Tel. +358-400-121000
Yes, this is true. I just did this about a month ago. You’ll probably want to upgrade the full client BO that is on your WEBI server also. If you are also upgrading to Webi 2.5.2, make sure you backup the Storage directory on the webi server prior to upgrading. This way if you end up having to de-install Webi you can easily restore user profiles etc.