Windows Installation
Before installing the Collibra Integrator it's necessary that you have the HTTP-ODBC Server configured and running. Fortunately setup is straightforward - check the installation guide for instructions on how to install and setup the HTTP-ODBC server.
Once that's complete you will need to download collibra.zip from the latest release of the Collibra Integrator and follow the rest of the guide. Once downloaded, extract the file to a location of your choosing (we recommend you extract to C:\Program Files\Experian\Data Management Exporter\Collibra for Windows). Edit the collibra.bat file with the configuration options and run.
As you use and configure this integration we encourage you to look at the examples.
The integration works by using the HTTP-ODBC middleware as a way to access Pandora or Data Studio's reports and snapshots respectively that are exposed to ODBC. Therefore it's important that you are aware of how the files are should be structured. Please see the best practices for more information on this. A Data Studio best practice guide will be coming soon.
Please see the configuration options here. These options will need to be set as environment variables. We recommend creating a bat or sh script file and setting the environment variables locally that way they do not conflict with variables you already have set on your system.
To help facilitate this, we've included the collibra.bat file with some of the environment variables exposed for you to set. All you have to do is fill in the fields within the collibra.bat file:
set COLLIBRA_COMMUNITY_NAME="YOUR COMMUNITY NAME HERE"If you'd like to run the integration with only Rules or Profiles you can omit HTTP_ODBC_RULE_QUERY or HTTP_ODBC_PROFILE_QUERY respectively. In the console if you omit either you may see errors related to the lack of a query but the data (rules or profiles) being sent will still be sent as normal.
The program is atomic, meaning it is isolated from other programs. In addition it runs in its entirety once and exits. You can run the program (once configured) by running collibra.bat, collibra.exe, or your own script.
We recommend creating a new user in Collibra for the purposes of using this integration. This new user's username and password should be the ones that are used with the configuration above (Configuring the release).
After being run once, with a Community name of Sample, you will notice that attributes may not post (an import error in Collibra will show up, stating you do not have access to system resources). This can happen if you have not properly assigned your Community to the right scope.
To resolve this go to Scopes (https://your-collibra-environment.collibra.com/settings?tabbar=Scopes) and create a new Scope. When you're creating the scope, make sure you select the community you're using.
To ensure that you are able to populate Profile information, it's necessary that a Global Assignment for Column is added. To do this, go to Settings and then Asset Types. Finally, select Add assignment and select the scope you created in the previous step.
The user that is used with this integration must be at least a Super User or above. We recommend creating a user specifically for the use with this integration and ensuring that their setting is Super User, or above.
By default Collibra allows for 4 import operations concurrently. To improve the performance, the environment variable COLLIBRA_CONCURRENCY as well as Collibra itself can be set to a value up to 8.
As Collibra by default has a import limit of 10MB - the integrator has a limit of approximately 6000 rules that can be imported into Collibra at once. To raise this limit, please raise the Max file size limit under Upload configuration when using the Collibra Console. We recommend setting it to the maximum.
Collibra has a default of 150 uploads per user, per day. In order to get around this, we recommend setting the Max per day setting in the Collibra Console to the maximum.
Please create the following two relations (go to Settings -> Characteristics -> Relations):
Please see the Scheduling Guide for Windows.
Please note that when configuring the Windows environment, do not include quotations in the environment variables. So, for example if HTTP_ODBC_RULES_QUERY is querying rules from a Profile named Rules for Collibra your variable should be set as set HTTP_ODBC_RULE_QUERY=SELECT * FROM RULES_FOR_COLLIBRA and not set HTTP_ODBC_RULE_QUERY="SELECT * FROM \"RULES_FOR_COLLIBRA\""