Add an Edge capability to an Edge site

After you created and installed an Edge site, you can add an Edge capability to perform specific tasks on a data source. For example, you can register a data source using a JDBC connection that belongs to an Edge capability.

Prerequisites

• You have a global role that has the System administration global permission.
• You have a global role with the Manage connections and capabilities global permission, for example Edge integration engineer.
• You have a global role with the Register profiling information global permission. (optional)
• You have created and installed an Edge site.
• You have created a JDBC connection.

Steps

1. Open an Edge site.
   1. In the main menu, click , then Settings.
      The Collibra settings page opens.
   2. In the tab pane, click Edge.
      The Edge sites overview appears.
   3. In the Edge site overview, click the name of an Edge site with the status Healthy.
      The Edge site page appears.
2. In the Capabilities section, click Add capability.
   The Add capability page appears.
3. Enter the required information.

   Field	Description	Required
   Capability	This section contains the 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, which determines the next available sections. Select the Catalog JDBC ingestion capability template to register a data source. Select the JDBC Profiling capability template to profile and classify your data. Select the DQ Connector capability template to ingest Data Quality user-defined rules, metrics, and dimensions into Collibra Data Catalog. Important Data Quality is only available in beta. Please create a support ticket to get access. Select the S3 synchronization capability template to connect to Amazon S3.	Yes
   Custom properties	Custom properties as required by the capability template. You see the custom properties after you select a capability template.	Yes
   Connection	This section contains information to connect to the data source.
   JDBC connection	The connection to the data source.	Yes
   JDBC data source type	The data source type of the data source that you want to ingest.	Yes
   Supports schemas	A text field where you have to enter True to enable database registration of data sources that have no schema. If the data source has schemas, you can ignore this field. Tip If the data source does not have a schema, Data Catalog creates a Schema asset with the same name as the full name of the database.	No
   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 property to add a property. The possible properties are: Show properties Name Description Type Encryption Value ingest-schema-garbage-collector The garbage collector that is used by the capability. The default garbage collector is -XX:+UseParallelGC. For information about other possibilities, see AZUL documentation. Text Not encrypted (plain text) For example: -XX:+UseSerialGC ingest-schema-requests-cpu The minimum amount of CPU computing power requested by the capability. The amount is expressed in milliCPU. Text Not encrypted (plain text) For example: 100 ingest-schema-limits-cpu The maximum amount of CPU computing power requested by the capability. The amount is expressed in milliCPU. Text Not encrypted (plain text) For example: 950 ingest-schema-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: ingest-schema-limits-memory and ingest-schema-jvm-max-memory. Text Not encrypted (plain text) For example: 128 ingest-schema-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: ingest-schema-requests-memory and ingest-schema-jvm-max-memory. Text Not encrypted (plain text) For example: 384 ingest-schema-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 ingest-schema.limits-memory amount. Important If you add this property, you also need to add the properties: ingest-schema-requests-memory and ingest-schema-limits-memory. Text Not encrypted (plain text) For example: 256 Note No validation is performed on the values you add.	No
   DQ	This section contains information about the Collibra Data Quality connection.
   Base URL	Your Collibra Data Quality URL	Yes
   Username	The Collibra Data Quality username for this connection.	Yes
   Password	The Collibra Data Quality password for this connection.	Yes
   Encryption options	Select the type of encryption to use. Default: To be encrypted by Edge management server.
   Issuer of the JWT	If you have selected Encrypted with public key, enter your JWT issuer.	No
   Collibra metadata model	This section contains information about where to ingest Data Quality assets.
   DQ Rules domain id	The UUID of the Rulebook Domain for the ingested Data Quality rules.	Yes
   DQ Metrics domain id	The UUID of the Business Asset Domain for the ingested Data Quality metrics.	Yes
   DQ Dimensions domain id	The UUID of the Business Asset Domain for the ingested Data Quality dimensions.	Yes
   Default DQ Dimension name	The default Data Quality Dimension, for example Accuracy, Completeness, Consistency and so on. Default: Completeness.	Yes
   DQ Metric classified by DQ Dimension relation type id	The UUID of the Data Quality Metric classified by / classifies Data Quality Dimension relation. If left unspecified, this relation will not be added.	No
   Assets are imported in batches of this size	The batch size of the ingestion. Default: 5000.	Yes
   S3 service account	This section contains the information on how to connect to Amazon S3.
   AWS Connection	The AWS connection to be used.	Yes
   IAM role	The IAM role used by AWS Glue crawlers.	Yes
   Encryption options	Select the type of encryption used to store the IAM role. Default: To be encrypted by Edge management server.	Yes
   General	This section contains general information about logging. Note This section only applies to JDBC capabilities.
   Debug	An option to automatically send Edge infrastructure log files to Collibra Data Intelligence Cloud. By default, this option is set to false. Note We highly recommend to only send Edge infrastructure log files to Collibra Data Intelligence Cloud when you have issues with Edge. If you set it to true, it will automatically revert to false after 24h.	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

4. Click Save.
   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.