Architecture of Hackolade

Please provide us with a architecture or Link to the of Hackolade architecture and working, to understand its Functioning. To know from where data can be fetched and where can it be pushed in for further use after reverse engineering.

Also can you provide us with the different formats that data can be pushed out of Hackolade. As we are using the trial version to evaluate the tool, it has lot of limitation to connect to sources and destination and also perform various function.

So, kindly also provide a link to the detailed description of the limitation one has to face in trial version. And the difference between the trial and special edition Hackolade.

Helpdesk May 07, 2018 22:16 Official comment

Great questions!

1) where data can be fetched: very simple and open! We persist model information on the file system in .json files using JSON Schema as a notation. You can therefore easily read this to integrate in a data dictionary for example, as many of our customers already do. Upon request at info@hackolade.com, we can provide the JSON Schema describing our model structure. This can also be supplemented by information (pictures) found in the HTML documentation. Links between persistence and documentation is done through GUIDs of each object in the model.

2) our free trial has no functional limitations. Only the community and personal editions have limitations. But to access the data sources, you need to first specify the target DB by creating a new model.

If you have any question, feel free to send to support@hackolade.com

Best regards,

Pascal

Architecture of Hackolade

1 comment