Versions Compared

Version Old Version 33 New Version Current
Changes made by

Troels Holm (Unlicensed)

Norman Cummins (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Create a new Insights database (e.g. "dzreporting") next to the DAM database.
    Note: Make sure the Insights database has the same collation as the DAM database.

  2. Create a new SQL server login (e.g. "insights").
    You can use any authentication you want (Windows/SQL), but it should have the following properties:
    1. Default database = "dzreporting" (database created in 1). Be sure to uncheck the "Enforce Password Policy, and select the DZreporting database under Default Database (changing it from master to DZreporting).
    2. Under User Mapping set  "db_owner, public" for the insights database, and "db_datareader" for the DAM database.

  3. Unblock and unpack the database zip file into a local folder.

  4. Edit the file "Digizuite.Insights.DbUpgrade.exe.config" with a text-editor and change to match your setup:
    1. ConnectionString (use credentials created in step 2). Remember to set the Initial Catalog = dzreporting.
    2. DAMDatabaseName (to be typed in under "value= ")
    3. (Best pratice) Remember to backup the database i.e. yourdatabasename_dam before prior to step 5.
  5. Run the executable "Digizuite.Insights.DbUpgrade.exe" and inspect the output (optionally using the created 'log.txt').

...

Note

When using the SELFSERVICE access, caution should be taken about usage. In this scenario, you are typically not controlling the usage and update schdules.
This could potentially lead to overloaded usage and locking. If you are not controlling these schedules, it is recommended to setup the Insights solution with a datawarehouse


Client registrations

Analytics data needs to be sent to the API in order to show in Digizuite(tm) Insights. Applications that send data are considered to be Insights clients. Some clients always send these informations to the API while others needs to be configured for it:

  • DAM Center is always registered to send analytics data.
  • Media Manager needs to opt-in by setting the app setting "EnableDAMStats" to "true".


Insights Installation & Configuration Guides

...

In the New Database dialogue box type a name for the Database EG DZReporting and click OK

Select Options and ensure the DZReporting Database is using the same Colation as the DAM Database.

This can be configured from Options in the left hand pane.

On the SQL Server expand Databases and check the Database has been created

...

The gateway is now ready for use.


Tip


If the connection fails it could be because the PowerBI Gateway Service has not started, to start the service.

Open Command Prompt as Administrator and run the following commands:

net stop PBIEgwService

net start PBIEgwService

Once the service is running your Gateway Connection should succeed.