BPM Admin Guide

Setting Universe Connection

This section describes the steps you need to follow to set up universe connection.

After you import the LCMBIAR file, universes and connections are stored in the CMS. To set database connection on the universes, you must create a project and a relational connection, retrieve universe files, assign a connection, and publish the universes.

This is all done in Information Design Tool. In Information Design Tool, a session to the CMS is required for certain operations. For information about sessions, as well as for more information and guides about creating projects, connections, and handling universe files, see documentation and tutorials on Information Design Tool.
Tip: See SAP for details about Information Design Tool:

http://scn.sap.com/docs/DOC-8461

To set a universe connection, you must:

  • Create a project
  • Create a relational connection
  • Retrieve the universe files
  • Set universe connections and publish

Create a Project

To create a project (skip this if a project is available already):

  1. Select File » New » Project .
  2. Enter a name for the project.
  3. Select a Project Location.

This is the folder where universe and connection files are stored in the project. By default, a folder under the user's profile is chosen. If other universe developers are to access the files, it is recommended that you select another folder (not under the user profile).

Create a Relational Connection

To create a relational connection (skip this if a connection is available already):

  1. Select File » New » Relational Connection .
  2. In the Resource Name window, enter a name for the connection. Click Next.
  3. In the Database Middleware Driver Selection window, choose a database type.
    • BPM supports Oracle and MS SQL Server connections.
    • For BPM Reporting, you must choose the database type of the Maconomy database.
    • For BPM Analysis and BPM People Planner, you must choose the database type of the BPM Data Warehouse or People Planner Data Warehouse database, respectively.
  4. In the Parameters window, enter the name of the database user, password, reference to TNS, service/database, port number, and SID/database. The parameters required depend on whether an Oracle or MS SQL Server connection is chosen, as well as whether a Client, ODBC, or JDBC connection is selected. Click Next.
  5. Choose default settings for the next Parameters screen.
  6. Set up the ALL_ROWS hint to speed up performance. E nter the following value for the custom property Hint:

    /*+ ALL_ROWS */

  7. Enable Cursor Sharing, if needed. Enter the following value for the custom property ConnectInit.
    • On Oracle connections:

      ALTER SESSION SET CURSOR_SHARING = FORCE

    • On MS SQL Server connections:

      FORCE PARAMETERIZATION

    Note: On many installations, performance is improved by applying Cursor Sharing. However, it can reduce performance on some systems.

    If the system has performance issues while Cursor Sharing is disabled, enable it to help improve performance. If the system has performance issues while Cursor Sharing enabled, disabling it may improve performance.

  8. Click Finish. A new connection file (type cnx) is added to the project.

    A cnx connection is a local connection and can be used for publishing universes locally on disk. However, it is recommended that you publish universes on the CMS. This requires a secure connection.

  9. To create a secure connection of the new connection file, right-click the cnx file and choose Publish Connection to a Repository.
  10. In the window that appears, browse for the CMS location in which the connection is to be stored. For example, select the default Connections folder of the CMS. Click Finish.
  11. A question window appears. Click Yes to retrieve a shortcut file to the secure connection. A secure connection file (type cns) is added to the project.
    Note:

    ALL_ROWS Information

    By default, the Maconomy database is set to retrieve a small number of records at a time for each query. This is convenient when entering and working in Maconomy workspaces or dialogs where you typically only see 10, 50, or 100 records at a time. However, when reporting, it is beneficial to retrieve all records at once, because a report document or dashboard is not refreshed until all records are retrieved.

    Cursor Sharing Information

    Often the reports that are run have the same query outline. Oracle and SQL Server can use this by saving a template of the queries that are executed. In many cases, this means that even if restrictions are changed (and the queries thereby differ), the database can skip the analysis of how to execute the queries, such as the creation of the explain plan. For many reports, the creation of the explain plan takes most of the time, so there is significant value in being able to reuse query templates.

Retrieve the Universe Files

To retrieve the universe files, follow these steps:

  1. Make sure the project is selected in the Local Projects view.
  2. Select File » Retrieve a Published Universe » From a Repository...
  3. In the window that appears, browse to the location of the universes. If the universe is an old BO 3.1 universe, it has no extension; otherwise, it has a unx extension. Retrieving a universe of type unv migrates the universe to the new BI 4 unx format. If a BO 3.1 universe should be kept in the BO 3.1 unv format, set connection with the Universe Designer tool instead.
  4. Select Save for All Users. Click OK. The Universe files (blx and dfx) are retrieved to a timestamp named folder under the project folder selected.
    Note: If needed, the universe files can be moved to another folder (for example, out of the timestamp named folder). However, this may break the local dependency that the blx file has to the dfx file and the local dependency that the dfx file has to the cnx/cns file. If this happens, open the dfx file and choose the connection again and possibly make some other minor change to force Information Design Tool to mark the dfx file as changed. Then save the file. Then open the blx file and choose Change Data Foundation. Here select the dfx file and possibly make some other small change to force Information Design Tool to mark the blx file as changed. Then save the file.

Set Universe Connections and Publish

To set universe connections and publish, follow these steps:

  1. Open the dfx file of a universe.
  2. Click the Connections tab.
  3. Click Change Connection...
  4. Select the connection file (for example, the newly created cns connection shortcut file). Click Finish.
  5. Save the dfx file.
  6. Right-click the blx file and choose Publish » To a Repository.
  7. Optionally, mark areas for checking integrity. Click Next.
  8. Browse to the CMS folder in which the universe is to be published. Click Finish. The universe has now been published with the selected database connection.
  9. Continue this process for all universes needed.