Configure Access to Enterprise Data Catalog
In Axon, you can configure Enterprise Data Catalog parameters from the Admin Panel. You must have the Super Admin profile to perform this task.
After you install Axon, you can configure Enterprise Data Catalog parameters from the Admin Panel in the following scenarios:
- •You did not select advanced configuration during Axon installation.
- •You want to update the connection settings for Enterprise Data Catalog after the installation.
- •You want to configure automatic object onboarding.
1. From the Axon toolbar, click the Admin Panel menu item under your user name.
2. In the menu on the left, under the Customize & Configure category, click System Settings.
3. In the Group list, select Enterprise Data Catalog.
4. Click Edit, and configure the following properties:
Property | Description |
|---|
Enterprise Data Catalog Server Host | URL of the Enterprise Data Catalog service in the following format: http(s)://<host_name> or http(s)://<IP_address> |
Enterprise Data Catalog Server Port | Port number of the Enterprise Data Catalog service |
Enterprise Data Catalog Server Login User Name | User name to log in to Enterprise Data Catalog server |
Enterprise Data Catalog Server Login Password | Password to log in to Enterprise Data Catalog server |
Enterprise Data Catalog Server Login Namespace | User security domain of Enterprise Data Catalog server |
Enterprise Data Catalog Resource Name | Name of the Axon resource created in Enterprise Data Catalog that connects to your specific Axon application |
Enable Automatic Onboarding | Optional. Automatically onboards the objects discovered in Enterprise Data Catalog to Axon. If you do not choose this option, the discovered objects are not onboarded automatically after the scheduled synchronization between Axon and Enterprise Data Catalog. |
Confidence Score Threshold | Required if you choose the Enable Automatic Onboarding option. The conformance percentage threshold to discover the objects from Enterprise Data Catalog. You can enter a value from 50 to 100. |
Accept Onboarded Objects | Optional. If you choose to accept onboarded object and the Confidence Score is 100%, the attributes from Enterprise Data Catalog appear with the Accepted review status in Axon. You do not have to curate these objects again in Axon. |
Axon Super Admin Email | Required. The email address of the SuperAdmin user responsible for onboarding discovered objects. |
Accept Lineage Recommendations and Create Links | Create attribute links automatically based on the lineage recommendations from Enterprise Data Catalog. If you do not select this option, you can manually create links later from the lineage recommendation notifications. |
Configure Onboarded Attribute Names | Choose to have either the glossary name or Enterprise Data Catalog physical field name for the onboarded attributes. The default value for this field is Glossary Name. |
5. Click Save.
6. In the Linux environment, run the following command to clear the Axon cache and restart the necessary services:
sh <INSTALLATION_DIR>/axonhome/third-party-app/scripts/paramsync
When you run the paramsync script, Axon restarts the HTTPD, Memcached, and email notification services.
Note: When you clear the cache and restart the Axon services, the Axon web interface might be disrupted for some users that are logged into Axon. Informatica recommends that you update the cache after you save your changes in all the System Settings pages. Additionally, perform this action during a maintenance period when very few users are using Axon.
Configure Custom Resource Types
In Axon, you can view custom resource types from Enterprise Data Catalog. You need to create custom resource types in Enterprise Data Catalog. For more information on custom resources, refer to Informatica® 10.2.2 Catalog Administrator Guide.
To view a custom resource type, you need to configure the required parameters, such as class type and label, for a field within a file in a predefined directory in Axon. Create a file with the name custom_edc_fields.yml in the following location:
<INSTALLATION_DIR>/axonhome/axon/src/Diaku/EIC/EICBundle/Resources/config/queries/custom
You can use the following syntax to configure the parameters in the custom_edc_fields.yml file:
In the file, you need to always start with the EDC_FIELDS : parameter to start configuring the parameters for a field in a custom resource type. Then, you need to enter a unique name for a field in the Enterprise Data Catalog resource that you want to display in Axon. Within the field, you need to configure the custom resource type parameters.
The following table lists the parameters that you need to configure within a field:
Parameter | Description |
|---|
classType | Required. The class type of the Enterprise Data Catalog field. |
label | Required. A unique label that you want to see in the Axon interface for this field. |
parentClassType | Required. The parent class type of the Enterprise Data Catalog field. |
parentIconFileName | Optional. The generic icon that you use for the parent file name. |
If you want to configure multiple custom resource types, you must create a separate section for each field to configure the parameters.
Before you deploy the configuration on the Axon server, you must validate the file using any YML validator tool.
In the Linux environment, run the following command to clear the Axon cache and restart the necessary services:
sh <INSTALLATION_DIR>/axonhome/third-party-app/scripts/paramsync
When you run the paramsync script, Axon restarts the HTTPD, Memcached, and email notification services.
Note: When you clear the cache and restart the Axon services, the Axon web interface might be disrupted for some users that are logged into Axon. Informatica recommends that you update the cache after you save your changes in all the System Settings pages. Additionally, perform this action during a maintenance period when very few users are using Axon.
Whenever you modify the custom_edc_fields.yml file, make sure that all Axon users clear their browser cache before they use Axon.
Example
The following sample file contains a field with parameters configured for a custom resource type:
EDC_FIELDS :
RELATIONAL_COLUMN :
classType : "com.ldm.custom.relational.column"
label : "RELATIONAL_COLUMN"
parentClassType : "com.ldm.custom.relational.table"
parentIconFileName : "dbcolumn"
In the example, the file starts with the EDC_FIELDS : parameter. The RELATIONAL_COLUMN field shows the configured parameters.