New Universe Service Pack Release

2 minute read

Upgrading a Universe Version

  1. Copy the new universe and the folder containing LOV files named the same as the universe to your universes directory. Overwrite file if older version exists.

  2. Note: Do NOT delete the universe from the repository.

  3. Remember: Do not update the Log universe if that has been customised and is in use in your deployment. The Log universe delivered is only an example universe, which has to be customised to be able to be used efficiently.

  4. Open the Business Objects Designer module (as an administrator) and open the new universe.

  5. Note: Clients that do not have access to the Designer module can contact their Competency Centre for further instructions.

  6. Select Parameters… and select the required connection from the drop-down list.

  7. Before you can use the universe you need to install the attached stored procedure, which will enable exchange rate currency conversion. If this is not installed on the database you will receive an error message saying that table or view does not exist when using a base or a target object in the report. There are no changes to the exchange rate stored procedure for this release so if you already have one in your database from versions after 3.1.0 you do not need to make any changes to this.

  8. For more information about the stored procedure, refer to in the System Administrators Guide.

  9. If this is the main universe and your platform is SQL Server, find the object named Prefix_Object in the Support class. The SQL definition of this object will be, for example, “sicsnt.LFTEST31.” You should change this to the required database and user account (Note the 2 full stops).

  10. This object (Prefix_Object) is used by all other objects in the universe where currency conversions are carried out. You can test if this object works by Parsing the “Test Prefix Object by Parsing”, this object is located immediately above the Prefix_Object. This test object will invoke the Prefix_Object and the Stored procedure.

  11. Select File -> Export…

  12. Note: It is necessary to log in as administrator to the Designer module. If you do not log in as an administrator you cannot overwrite the existing universe in the repository. It is important that you DO NOT delete the old universe version on the repository and then export the new universe. This might confuse Business Objects into thinking that there is a new universe instead of just updating an existing version.

  13. Export the universe to the required domain (if a repository is set up) and overwrite the existing one.

  14. Note: You may receive an error message at the end of the export process saying that Designer could not write the LOV files to C:\Documents and Settings\etc. Ignore this message as the LOVs have been exported to the repository and users who import the universe from the repository will receive all the LOV files.

  15. The delivered universes are developed in, and therefore compatible with, BOXI 3.1 SP6 and later service packs.

  16. Note that the universes will change filename and get the long name of the universe as a file name when downloaded from the BOXI repository.