Add the JDBC Profiling capability

Before you can start profiling a data source via Edge, you need to add the JDBC Profiling capability to the JDBC connection for the data source.

Before you begin

• You have created and installed an Edge site.
• You have created a JDBC connection.

Required permissions

You have a global role that has the Manage connections and capabilities global permission, for example, Edge integration engineer.

Steps

1. Open an Edge site.
   1. On the main toolbar, click , and then click Settings.
      The Collibra settings page opens.
   2. In the tab pane, click Edge.
      The Sites tab opens and shows a table with an overview of the Edge sites.
   3. In the table, click the name of the Edge site whose status is Healthy.
      The Edge site page opens.
2. In the Capabilities section, click Add capability.
   The Add capability page is shown.
3. Select the JDBC Profiling capability template.
4. Enter the required information.

   Field	Description	Required
   Capability	This section contains general information about the capability.
   Name	The name of the Edge capability.	Yes
   Description	The description of the Edge capability.	No
   Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: JDBC Profiling	Yes
   Connection	This section contains information to connect to the data source.
   JDBC connection	The connection to the data source.	Yes
   Other Settings Others	This section can contain additional capability properties. Warning Adding additional properties can have a significant impact on your Edge site. Only add or update them together with Collibra Support. Click Add propertyAdd Other Settings to add a property. The possible properties are: Show properties Name Description Type Encryption Default value garbage-collector The garbage collector that is used by the capability. For information about other possibilities, see AZUL documentation. Text Not encrypted (plain text) -XX:+UseParallelGC requests-cpu The minimum amount of CPU computing power requested by the capability. The amount is expressed in milliCPU. Text Not encrypted (plain text) 1000 limits-cpu The maximum amount of CPU computing power requested by the capability. The amount is expressed in milliCPU. Text Not encrypted (plain text) 2000 requests-memory The minimum amount of memory requested by the capability. The amount is expressed in mebibytes (Mi). Important If you add this property, you also need to add the properties: limits-memory and jvm-max-memory. Text Not encrypted (plain text) 2048 limits-memory The maximum amount of memory requested by the capability. The amount is expressed in mebibytes (Mi). Important If you add this property, you also need to add the properties: requests-memory and jvm-max-memory. Text Not encrypted (plain text) 4096 jvm-max-memory The maximum amount of memory that can be used by the Java virtual machine (jvm). The amount is expressed in mebibytes (Mi). Warning Make sure this amount is lower than the limits-memory amount. Important If you add this property, you also need to add the properties: requests-memory and limits-memory. Text Not encrypted (plain text) 3072 table-profiling-queries-timeout The maximum amount of time, in the defined time unit, after which the query on the data source side stops. Integer number Not encrypted (plain text) 604800 table-profiling-queries-timeout-unit The unit of time used to calculate the maximum amount of time for one query attempt. The possible values are: Nanos, Micros, Millis, Seconds, Minutes, Hours, and Days. Text Not encrypted (plain text) 604800 table-profiling-processing-timeout The maximum amount of time, in the defined time unit, after which the data transfer and calculation of profiling statistics stops. Integer number Not encrypted (plain text) 604800 table-profiling-processing-timeout-unit The unit of time used to calculate the maximum amount of time for one processing attempt. The possible values are: Nanos, Micros, Millis, Seconds, Minutes, Hours, and Days. Text Not encrypted (plain text) Seconds dgc-client-max-attempts The maximum number of times the capability tries to send the profiling results to Collibra. The value must be between one and four. The first attempt also counts. Integer number Not encrypted (plain text) 2 dgc-client-read-timeout-amount The maximum amount of time, in the defined time unit, that the capability tries to send the profiling results to Collibra. Integer number Not encrypted (plain text) 1800 dgc-client-read-timeout-unit The unit of time used to calculate the maximum amount of time for one attempt. The possible values are: Nanos, Micros, Millis, Seconds, Minutes, and Hours. Text Not encrypted (plain text) Seconds Note No validation is performed on the values you add.	No
   General	This section contains general information about logging.
   Debug	An option to automatically send Edge infrastructure log files to Collibra Data Intelligence Platform. By default, this option is set to false. Note We highly recommend to only send Edge infrastructure log files to Collibra Data Intelligence Platform when you have issues with Edge. If you set it to true, it will automatically revert to false after 24h. For more information, go to logging.	No
   Log level	An option to determine the verbosity level of Catalog connector log files. By default, this option is set to No logging.	No

5. Click Create.
   The capability is added to the Edge site.
   The fields become read-only.

What's next?

You can now register a data source via Edge and profile the data.