Data Management Installation and Update

Prerequisites

Procedure

INUBIT:

  1. Create the "VAM" user group in INUBIT

    1. Assign the desired users to the group

  2. Import the workflow and repository ZIP files into this user group

  3. If necessary, install the database driver in INUBIT

  4. Adjust the database parameters

    1. INUBIT system diagram: Enter the database connection

    2. INUBIT System Diagram: Check/change connection pooling settings in the DB connectors

      db connection

      The default settings apply to an Oracle database. Adjust these accordingly if a different DBMS is used.

    3. Enter the DB type ("oracle," "mssql," or "postgresql") in the VAM_api_configuration module

      db type

      You can find the module in the VAM_api_main_newSession and VAM_api_attachUser workflows.

  5. Connect to the database manually

    For MSSQL, the name T_INUBIT_ASSETMANAGEMENT must be replaced with the actual schema name in the SQL files.

  6. Manually run the following scripts:

    The scripts are located in the previously imported INUBIT repository, e.g., /Root/admin/VAM/backend/single-create-2.0.8-Oracle.sql.

    1. the most recent single-create script that matches the database

    2. all single-upgrade scripts that match the database and have a higher version number

  7. If errors occur, check the database permissions—this is often missing in Oracle Grant execute on ctxsys.ctx_ddl.

  8. Activate workflows

BPC:

  1. Deploy the BPC modules BPC-fe-vam.war and BPC-be-vam.jar to the BPC

  2. If the BPC URL differs from the default, enter the custom BPC URL in the VAM_api_configuration module

  3. Set up permissions in the BPC or BPC Identity Backend

    Simplest setup for Data Management users:

    • for general read and write access: VAM-administrator role

    • for access to artifacts of the corresponding data pool (“Organization”): VAM_organization_NAME role—one per organization!

      1. If necessary, create a user to whom these roles are assigned

  4. Log out of and back into BPC using the user you just created,
    Open the Data Management module once, if necessary

  5. If not already set up, configure an HTTP proxy to INUBIT, see Backend Connections

  6. Create the Data Management module component

    1. Enter the HTTP proxy

    2. Enter the organization ID (freely selectable)

    3. Save changes

    The Data Management module is now accessible.
    However, without templates, you can only create and delete test queries, for example, at this stage.

INUBIT:

  1. Generate a real password and enter it in the VAM_api_http_listener_protocol module

Use this password for automated access as well.
If necessary, create another ("technical") user in addition to bpcadmin for automated access, or use the username of the user created in Step 11.

Update

To update the entire Data Management application, both BPC and INUBIT must be updated.

BPC

  1. Download the latest versions of Data Management (.war, .jar)

  2. Go to the BPC interface and open the Overview > Status tab in the administration area

  3. Select the icon

  4. In the pop-up window, upload the .war and .jar files

    upload bpc module

INUBIT

  1. Download the latest versions of the zip files VAM.diagrams_ohne_Systemdiagramm and VAM.repository (Use the version without the system diagram, as updating the system diagram causes errors in some INUBIT installations)

  2. In INUBIT, switch to the VAM user group

  3. Switch to the Designer

  4. VAM.diagrams_ohne_Systemdiagramm.XXXX.zip Import to update the workflows

    vam update inubit diagram

  5. Reset the VAM_api_configuration module

  6. Reset the VAM_am_063_hooking workflow (if customized)

  7. If necessary, reset any other customized workflows and modules

  8. Switch from the Designer tab to the Repository tab

  9. Click on the VAM user group and import the latest VAM.repository.XXXX.zip file

  10. If necessary, restore any customizations here as well (normally not necessary, as no customization is intended)

    vam update inubit repo

  11. If there is an upgrade script for the database you are using in the repository, run this script manually in your DBMS. (If versions are skipped during the upgrade, there may be multiple upgrade scripts.)

  12. In the Designer tab, enable any newly imported workflows if necessary

  13. Manually execute the workflow VAM_api_zzz_reset_caches

  14. If applicable, note any specific release notes

Database-specific restrictions

Oracle

  • Standard field "Description":
    Description can be a maximum of 4,000 characters long

  • Context search by username (“created by” and “modified by” / “contains”):
    Search does not work in some Oracle versions due to an optimizer bug

MSSQL

  • Contextual search in standard fields:
    Only searches for word prefixes are possible

  • Character set encoding:
    Use of non-Latin-1 characters in indexed fields (e.g., custom ID, user ID) is problematic;
    the same applies if database defaults are poor; keys are case-sensitive or contain accents

  • Key length:
    Keys for indexes may be up to 931 characters long
    (currently no known use case where this length is exceeded)

PostgreSQL

  • Contextual search:
    Some surprising effects (e.g., fragments recognized as server names or email addresses are not searchable)

  • INUBIT versions:
    Does not work with INUBIT 8.0.20/21 due to a JDBC issue with timestamps

Keywords:
Press Esc to exit full screen
Modal image placeholder
Press Esc to exit full screen