New Universe Service Pack Release

16.1. New Universe Service Pack Release

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 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. Choose the universe which is needed to install the attached stored procedure, which will enable exchange rate currency conversion. If this is not installed on the database, an error message will be received, saying that table or view does not exist when using a base or a target object in the report.

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

  9. If this is the main universe and platform is SQL Server, find the object named Prefix_Object in the Support class. The SQL definition of this object will be, for example, “SICS4LIFE” This could be changed 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. It can be tested 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.

    Example:

    BO_PREFIX_OBJECT.png

    Users need to change the definition of the object named Prefix Object according to their data base schema name. At the universe level, prefix_object should define this object as “Schema Name.“If the object is not defined properly, GET_EXCH_RATE_AND_EURO function related objects will not work.

  11. Select File -> Export…

  12. Note: It is necessary to log in as administrator to the Designer module. If it is logged in as an administrator, cannot overwrite the existing universe in the repository. It is important that to 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: An error message may be recieved 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. 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.

  16. As of the unified universes released 25.1 we are including/releasing the new version of universes. These are using informational design tool (IDT). These universes are different from the earlier delivered universes which uses the universe design tool (UDT). Going forward we will only release universe compatible with the IDT tool. The impact of this, is that you will have to - as a one-time exercise. Manually change the data source in all the reports. This will change them from using the old UDT universe to the new future proven IDT universes. The upgrade path is therefore a bit different this time.

  • Apply any and all customizations to the 25.1 UNV version of the universe.
    • You will have to go from the version of universe you are currently on to this 25.1 UNV version of the universe.
    • Add any customizations and overwrite the UNV universe versions - as a normal upgrade. This will upgrade the reports to 25.1 UNV standard.
  • Then export the 25.1 UNX version of the universe to a different repository folder
    • Again, apply any and all customizations to the 25.1 UNX version of the universes.
    • Then manually switch the universe source from the old 25.1 UNV to the new 25.1 UNX. As the folder and name structure is the same between the two version this should be a very quick and easy change to do. This means that the normal path of just overwriting the old universe with the new will not work. This one-time workaround upgrade path are for everyone. You need to have the versions of the universe side-by-side and move and repoint each query in the report so that the query will move from the old universe to the new universe.