How to install the Upgrade Management Tool on Windows 7 – Amended to remove file
The upgrade management tool is a GUI interface to migrate instances from 3.1 systems to BOE 4 systems. For Unix users, the easy to use interface is not available as the UMT is only a command line interface. The following shows the steps to install the UMT using the Windows Server install. The only change is to remove the condition that the install be run on a server, this does not try to fool the installer that the desktop is a windows server, it just prevents the question from being evaluated.
- From the SAP Service Marketplace download the files for the Windows Install
- Extract the files to create the install source
- Go to directory BusinessObjectsServer_win\dunit\product.businessobjects64-4.0-core-32
- Edit product.seed.xml to origproduct.seed.xml remove the following lines
<prerequisite id=”getWindowsVersionPreReq 2″ description=”#prereq.WindowsServerVersionPreReqText#” reason=”#prereq.WindowsServerVersionPreReqNotOkText#” type=”error”>
<arg name=”maxVersion” value=””/>
<arg name=”minVersion” value=”6.0″/>
<arg name=”VersionNeedToCompare” value=”[$os.version]”/>
<arg name=”Property” value=”Windows2008Above”/>
<arg name=”AllowedSuffix” value=”Server”/>
<condition property=”Windows2008Above” value=”1″/>
- Save the file
- Run the installer
- Only Select the Upgrade Management Tool
- You need to connect to a running BOE 4 system to run the install
- Launch the tool
- Select incremental Upgrade
- Choose live to live
- Select some Objects from the BOE 3.1 System
- Import the objects
- Logon to the target system and view objecdts
The Upgrade management tools uses the binaries from the SOURCE and TARGET environments to move the objects between the environments, the UMT is only a GUI to make this easier.
Thanks for the post. I'm sure I'll need this one day!
Would you mind explaining what the difference is between both .XML?
The files are the same, there was an issue loaded it, that caused it to load twice.
After install method described - migration of most type of objects will fail as UMT requires server binaries present on machine on which its running (as described in the Upgrade guide).
This document is an example on how NOT to prepare for a migration as it does install UMT, but leaves is not operational
The only proper way to install UMT -- install full BO server stack on supported server OS, then leave all server components stopped.
Thanks Denis, much appreciated.
Patrick, this has been tested by myself and a number of coworkers and the content is migrated. There may be an issue with the content not be upgraded because the report conversion binaries are not there but this was a way to allow a number of objects to be migrated to validate the new environment and to ensure existing content would run.
I would not use this for a full migration but it does work, please clarify specifically what does not work, I am aware this is not a supported install but at the client I am working at they do not support Windows servers that would allow the solution you suggested.
This has been tested and the objects (webi, crystal, dashboards and folders) are deployed and can be run in the 4.1 environment.
Denis, I have installed this and tested both Windows to Windows migrations and Solaris to Solaris migrations and the objects that were imported could be used and run. The objects tested were Crystal Reports, Webi Reports, Dashboards and Folders. This was not a quick this might work, it has been with the above objects.
Universes and universe connections will not migrate in your scenario 100% (tested and reported many times).
Very surprised Webi reports worked for you, something is fishy here. Are you sure your Webi reports were refreshable after migration like this ?
See Upgrade guide Section :
4.1 Object types and feature requirements
Not only your solution will not work reliably, it is also not supported one, since you're installing server tool on a non-server OS.
I am not sure where you are coming from here, the installer installs the same files on the server and the Windows7 desktop when only the UMT tool is selected.
We have successfully done this using the upgrade management tool for BOE 4.1 SP1, the universes were migrated (as .unv) files and the webi reports were uploaded as well. The reports can be run / viewed / scheduled and they accept the parameters when being run.
I'm coming from official documentation on UMT object dependencies requirements.
And from official Supported Platforms guides, which state that Windows 7 is supported for client tool only. UMT is part of server install package. So it follows BI4.x server supported OS's. Which do not include Win7.
The process you're using to install it is a hack , which circumvents official installer pre-requisites requirements.
I'm also coming from observing this type of install failing to migrate content properly and customers have to go back to supported platform and install scenarios and need to re-migrate their content.
Dennis, Not to beat a dead horse here but the windows installer does allow the UMT to be installed standalone. The BINARIES that are required to run the tools exist on the source and target systems and do not need to be on the client machine. I have tested this using .biar to live and live to live and have not had any objects fail to import.
All the UMT does is manage the set of objects to be selected and builds the biar file. As this program is packaged as a windows install, it has the necessary files in the installer to do its tasks. The only requirement to run the binaries is the operating system being used must be 64 bit.
This is not supported by SAP but for UNIX based users, the functionality should be embedded as JAVA code in the CMC allowing all users of the product to have the same functionality.
The lines in the productseed.xml that need to be commented out or removed are:
<prerequisite id="getWindowsVersionPreReq 2" description="#prereq.WindowsServerVersionPreReqText#" reason="#prereq.WindowsServerVersionPreReqNotOkText#" type="error">
<arg name="maxVersion" value=""/>
<arg name="minVersion" value="6.0"/>
<arg name="VersionNeedToCompare" value="[$os.version]"/>
<arg name="Property" value="Windows2008Above"/>
<arg name="AllowedSuffix" value="Server"/>
<condition property="Windows2008Above" value="1"/>
These lines check to see if the install is being done on a server, to ensure that the future releases contain the necessary code, it is better to not use the attached product.xml file but remove or comment these lines.