Data Management Installation and Update

Prerequisites

You have installed one of the following databases including drivers:
- Oracle
- MSSQL
- PostgreSQL
See also Database-specific restrictions.
You have an http proxy-Connection to INUBIT in the Backend Connections
You have downloaded the required workflow packages and repositories
You have downloaded the required BPC modules (.vam, .jar)

Procedure

INUBIT:

Create the user group "VAM" in INUBIT
1. Assign the desired users to the group
Import workflow and repository ZIPs into this user group
If necessary, import database drivers into INUBIT. Install database driver in INUBIT
Adjust database Parameters
1. INUBIT system diagram: Enter database connection
2. INUBIT system diagram: Check/change Connection pooling settings in the DB connectors
  
  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
  
  The module can be found in the VAM_api_main_newSession and VAM_api_attachUser workflows.
Manually connect to the database

For MSSQL, the name T_INUBIT_ASSETMANAGEMENT must be replaced with the real schema name in the SQL files.
Execute the following scripts manually:

The scripts are located in the previously imported INUBIT repository, e.g. .E.g. /Root/admin/VAM/backend/single-create-2.0.8-Oracle.sql.
1. the most recent single-create script matching the database
2. all single-upgrade scripts matching the database with a higher version number
In the event of errors, check the DB authorizations if necessary - often missing for Oracle Grant execute on ctxsys.ctx_ddl.
Activate workflows

BPC*:*

Deploy BPC modules bpc-fe-vam.war and bpc-be-vam.jar in the BPC
If the BPC URL differs from the standard, enter the individual BPC URL in the VAM_api_configuration module
Authorizations in the BPC or BPC identity backend set up

Simplest setup for Data Management users:
- for general read and write access: VAM administrator role
- for access to artefacts of the corresponding data pool ("organization"): Role VAM_organization_NAME - per organization!
  1. If necessary, set up a user to whom these role(s) are assigned
Log out and log back in with the user just set up in the BPC,
open the Data Management module once if necessary
If not available, set up HTTP proxy to INUBIT, see Backend Connections
Data Management Create module component
1. Enter HTTP proxy
2. Enter organization ID (freely selectable)
3. Save changes
The Data Management module can now be called up.
Without templates, however, only test queries, for example, can be created and deleted up to this point.

INUBIT:

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 user name of the user created in step 11.

Update

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

BPC

Download the latest versions of Data Management (.vam, .jar)
Switch to the BPC interface and open the Overview > Status tab in the administration area
icon
Upload the .vam and .jar files in the pop-up window

INUBIT

Download the latest versions of the zip files VAM.diagrams_ohne_Systemdiagramm and VAM.repository
Switch to the VAM user group in INUBIT
Open the settings of the VAM user group
VAM.diagrams_ohne_Systemdiagramm.XXXX.zip Import to replace the obsolete files
Switch from the Designer tab to the Repository tab.
Click on the VAM user group and import the latest VAM.repository.XXXX.zip file
If a new script has been published, manually execute the latest database script in your DBMS
Activate the imported workflows in the Designer tab

Database-specific restrictions

Oracle

Default field Description:
Description can only be a maximum of 4000 characters long
Context search on user names ("created by" and "changed by" / "contains"):
Search does not work due to an optimizer bug in some Oracle versions

MSSQL

Context search in standard fields:
Only search for prefixes of words possible
Character set encoding:
Use of non-Latin-1 characters in indexed fields (e.g. User-defined ID, user ID) problematic;
also with bad DB defaults Key only with differences in upper/lower case or accents
Key length:
Keys for indices may be a maximum of 931 characters long
(currently no known use case where this length is exceeded)

PostgreSQL

Context search:
Partly surprising effects (e.g. fragments are recognized as serially in the database).E.g. fragments recognized as server name or mail address not searchable)
INUBIT versions:
Does not work with INUBIT 8.0.20/21 due to JDBC problem with timestamps

Keywords: