Skip Ribbon Commands
Skip to main content
Sign In

Quick Launch

Average Rating:

(3 Ratings)
facebook Twitter
Email
Print Bookmark Alert me when this article is updated

Feedback

Automate object onboarding from Enterprise Data Catalog to Axon
Content

ONBOARDING PROCESS 

 ​
The fields linked with the glossary under the Axon resource in EDC would be identified and the data sets and attributes would be automatically created in Axon. This process is called onboarding.

Following are the prerequisites for assets onboarding in Axon:

1. The EDC version integrated with Axon should be 10.2.2 or greater than 10.2.2
2. The field "Enable Automated onboarding" is checked from the Admin Panel > Customize and Configure > Configure Axon.
3. The value "Data Set" must be available in the drop-down Data Set Type. Check this from Admin Panel > Meta-Model Administration > Dropdown Configurations.
4. At least one resource from EDC must be linked to Axon systems

The onboarding criteria are as follows:

1. When a field is linked to a glossary in the EDC (Linked Glossary is used for onboarding): An attribute with the linked glossary name is created in Axon.
2. When fields in EDC are linked to a data domain and the data domain is linked to a glossary: An attribute with the name same as that of glossary linked with the domain is created in Axon.
3. When the field displays recommended glossaries in EDC.
4. When a glossary is linked to a data domain discovery rule in Axon.

The linked glossaries are used to onboard the assets in Axon. Axon sends the notification to the glossary stakeholders about the discovered objects.

Therefore, each linked glossary must have stakeholders so that they can receive the onboarding notifications.

When the onboarding job is run for the first time, it on-boards all discovered data sets and attributes but when the job is run next time, only the newly discovered attributes are on-boarded.

Following are a few points regarding onboarding process:
  • Attributes in Axon are created with the glossary name from EDC during the onboarding process
  • The “Parent” name in the EDC for the fields is the name of the data set
  • If an attribute is rejected once in onboarding, it is not on-boarded again

Onboarding Scenarios: 

There are three onboarding scenarios from EDC to AXON. Before proceeding to this, a few points must be kept in mind for a better understanding of the concept:

1. While onboarding, the attributes in Axon are created with the glossary name it is linked to in EDC.
2. Axon allows attributes of the same name under different data sets and data sets of the same names under a different system.

Let us discuss various scenarios:

Case 1: A system in Axon is linked to one resource in EDC: This is a one-one relationship. 

Suppose the resource in EDC is R1 which has two tables T1 and T2. Let T1 has columns C1 and C2 and T2 has columns C3 and C4. 
 
a. If all the columns of these tables are linked to different glossaries as follows:

COLUMNS​​​ ​GLOSSARIES
T1​.C1 ​G1
​T1.C2 ​G2
T2.C3 G3
T2.C4 ​G4
 

The above is the snapshot from EDC. Attributes are onboarded to Axon as follows:

 System: S1
     
DATA SET : T1​ DATA SET : T2​
G1​ ​G3
​G2 ​G4
                      


b. If all the columns of these tables are linked to the single glossary as follows: 

Snapshot from EDC:
  
​COLUMNS GLOSSARIES​
​T1.C1 ​G1
T1.C2​ ​G1
T2.C3 ​G1
​T2.C4 ​G1
 

Snapshot from Axon after onboarding:

System: S1

DATA SET: T1​ DATA SET : T2​
​G1 ​G1
 
                   
Axon does not allow duplicate attributes under the same data set so only  one attribute is created under each data set

Case 2: A system in Axon is linked to many resources in EDC: This is a one-many relationship. 

Suppose the resource in EDC is R1 and R2. System S1 in Axon is linked to both R1 and R2.

a. Let R1 and R2 have tables of same name T1 and the columns of both tables are linked to different glossaries:

Snapshot from EDC :

COLUMNS​ ​GLOSSARIES
R1.T1.C1​ G1
R1.T1.C2​ G2
R2.T1.C3​ ​G3
R2.T1.C4​ G4
 

Snapshot from Axon :
                           
 System: S1
 Data Set: T1

ATTRIBUTE IN TABLE T1​
G1​
​G2
​G3
​G4
 

b. Let R1 and R2 have tables of same name T1 and the columns of both tables are linked to same glossaries:

Snapshot from EDC:  

COLUMNS​ ​GLOSSARIES
​R1.T1.C1 G1
​R1.T1.C2 ​G1
​R2.T1.C3 ​G1
​R2.T1.C4 ​G1
 

Snapshot from Axon after onboarding:

SYSTEM : S1​
DATA SET : T1​
ATTRIBUTES IN T1​
​G1
 

c. Let R1 and R2 have tables of name T1 and T2 respectively and the columns of both tables are linked to the same glossaries:

Snapshot from EDC :

​COLUMNS ​GLOSSARIES
R1.T1.C1​ ​G1
​R1.T1.C2 ​G1
​R2.T2.C3 ​G1
​R2.T2.C4 ​G1
 

Snapshot from Axon :
                            
System: S1

DATA SET : T1​ ​DATA SET : T2 
ATTRIBUTE​ ​ATTRIBUTE
​G1 ​   G1
 

d. Let R1 and R2 have tables of name T1 and T2 respectively and the columns of both tables are linked to different glossaries:

Snapshot from EDC :

COLUMNS​ ​GLOSSARIES
​R1.T1.C1 ​G1
R1.T1.C2​ ​G2
R2.T2.C3​ ​G3
R2.T2.C4​ ​G4
 

Snapshot from Axon :
                            
System: S1

​DATA SET :T1 ​DATA SET : T2
ATTRIBUTES​ ​ATTRIBUTES
​G1 ​G3
G2 ​G4
 
Case 3: Many systems in Axon is linked to one resource in EDC: This is a type of many-one relationship. 

Suppose the resource in EDC is R1. System S1 and S2 in Axon are linked to R1.

a. Let R1  has T1 and T2 and the columns of both tables are linked to different glossaries:

Snapshot from EDC :

​COLUMNS ​GLOSSARIES
​R1.T1.C1 ​G1
R1.T1.C2​ G2
​R1.T2.C3 ​G3
​R1.T2.C4 G4
 

Snapshot from Axon :
                            
System: S1

DATA SET : T1​ ​DATA SET: T2
​G1 G3
​G2 G4
 

System: S2

​DATA SET : T1 ​DATA SET: T2
​G1 G3
​G2 ​G4
 

b. Let R1 has table T1 and T2 the columns of both tables are linked to same glossaries:

Snapshot from EDC :

COLUMNS​ ​GLOSSARIES
​R1.T1.C1 ​G1
​R1.T1.C2 ​G1
​R1.T2.C3 ​G1
​R1.T2.C4 ​G1
 

Snapshot from Axon :
                            
System: S1

​DATA SET : T1 ​DATA SET:T2
G1​ ​G1
 

System: S2

DATA SET : T1​ DATA SET:T2
G1​ G1
 

The Glossary stakeholders are notified about the onboarded attributes and data sets. Please note that the glossaries should have stakeholders assigned so that they can receive notifications. This can be checked from the bell icon on the menu bar where a separate column for the discovered attributes is provided.

Let us walk through the onboarding process now:

1. Link the Axon system to one of the EDC resource (here SYS1 to Hive_Resource).

2. The fields under that resource would be fetched. Click on the field that you want to link the glossary too. This would redirect to the EDC catalog page.
e1.JPG 
 


 3. The glossary "3 Days Arrear Amount" is linked to the field "idnum" in the figure as follows:
 E2.JPG

The glossary would appear under the "Linked Glossary" column for the field "idnum":

E3.JPG 
 



 4. Open the Axon server and navigate to the location < Axon_install_directory>/axonhome/axonhome/axon_asset_onboarder/.This directory has all the required file that asset on broader job needs. 

Navigate to the "scripts" directory. The script "onboard_assets.sh" to onboard the assets are available under this location. Execute this script. The default time for an on-boarder job to run is set to 2 AM. However, the user can change this time. Once the script is executed, the assets would be on-boarded in Axon.

The attribute would be created with the name of a linked Glossary:

E4S.JPG 
 

The "Origin" of the attribute is "Enterprise Data Catalog" In case "Accept onboarded objects" field is not checked in Admin Panel, the Review Status of the attribute would be "Discovered". User can update the "Review Status" to Accept or Reject.

This process is known as curation. Once the asset is rejected, it would not be discovered again. The Glossary of the attribute is the same as the attribute name. 

5. The parent name of the field in EDC is used to create Data Set in Axon. 

 E5.JPG


The glossary for the data set would be the same as that of the attribute. The Data set would be created under the system which is linked to the resource containing the Parent. The Type of data set is Data Set. The Glossary Stakeholder receives the notification about the discovered assets.
 
E6.JPG 
 


The  John Admin receives notifications regarding the assets uploaded during the onboarding process.
E7.JPG 
 
The on-boarded objects can be viewed in Axon from the following locations:

1. Unison grid: Jump to the Attribute facet in unison grid and filter the attributes using the filter Origin and select the value Enterprise Data Catalog. The attributes on-boarded from EDC would be displayed.
     E8.JPG

Along with the attributes, the Data sets on-boarded from EDC would also be filtered:
E9.JPG 
 

Navigate to the Glossary that was linked to the EDC field and is responsible for onboarding. Go to ‘Data’ tab. The ‘Data Sets’ page would contain the onboarded data set

e10.JPG 
 


  The Data Attributes section contains the on-boarded attribute.

E11.JPG 
 

The Enterprise Data Catalog tab would contain the EDC field to which the Glossary is linked.
E12E.JPG 
 

3. Navigate to the Data Set on-boarded from EDC. Go to Attributes tab. This contains the attributes on-boarded from EDC.
E13.JPG 
 


4. Navigate to the System Data. The Data Sets tab contains the list of on-boarded datasets. The value of  Name and Definition fields for the on-boarded Data Sets would be the same.
E14.JPG 
 


Navigate to the Data Attributes section of the System. This would contain on-boarded attributes along with the manually created attributes. For the onboarded attributes, the Origin field would have the value Enterprise Data Catalog.

Navigate to Enterprise Data Catalog Go to Resources. This would show the EDC resources linked to the system
E15.JPG 
 

  
Navigate to Fields. This would display all the fields fetched as a result of linking Resource to the Systems.
E16.JPG 
 


CURATING DISCOVERED ATTRIBUTES: The process of either accepting or rejecting the discovered assets is called curating. Before curating the attributes, confirm if the Data set of the attribute has the assigned stakeholder with Edit permissions.

1. Curating from Glossary Object: Navigate to Glossary > Data > Data Attributes. Select the attributes with the Review Status Discovered > Click on Actions. Choose either Accept or Reject. 
E18.JPG 
 
2)Curating from Unison Grid: Navigate to Attributes in the unison grid and filter the attributes discovered. Select the attributes returned after filtering and click on Bulk Update. Next, Change the Review Status to Accepted or Rejected.
E19.JPG 
 


3. Curating from Data Set: Navigate to the Data Set discovered during the onboarding process. Go to Attributes tab and select the attributes in Discovered status. Click on Actions and select either Accept or Reject
E20.JPG 
 


Once an attribute is rejected, Axon permanently deletes the attribute without changing the Review status to Rejected. It can be viewed from the History tab who curated the attribute.
E21.JPG 
 
​​​​​​


More Information
​Starting from Axon 6.2, there is no "Enterprise Catalog" link next to Search. it has been shifted to new place-->On the Menu Bar, Click on Create Manage Catalog Links: here you would find the Resources and Fields as it was present earlier under the Enterprise Catalog tab.


​After fresh installation of Axon 6.3, if you are unable to access the Manage Catalog Links from the Create tab, you need to first integrate Axon with an EDC instance from the Admin Panel in Axon 6.3 to view and access the Manage Catalog Links.​


Reference


Attachments


Applies To
Product: Axon Data Governance
Problem Type: Product Feature
User Type: Administrator
Project Phase: Onboard
Product Version: Axon 7.0; Axon 6.3
Database:
Operating System:
Other Software:

Last Modified Date: 6/24/2020 2:16 AM ID: 582688
People who viewed this also viewed

Feedback

Did this KB document help you?



What can we do to improve this information (2000 or fewer characters)