Getting Started with Actian Avalanche
This page shows the basics to work with Actian Avalanche.
The database structure can be entirely reverse-engineered in a Metadata and then used in Mappings and Processes to design and adapt business rules that meet the user’s requirements.
Refer to Connect to your Data page which explains the procedure.
The Actian Avalanche third-party JDBC driver and the JDBC URL to use can be found in the Actian Avalanche Warehouse’s properties:
An example of a reverse-engineered Actian Avalanche Metadata is given below.
To optimize loading data to Actian Avalanche, Semarchy xDI uses a storage location to store temporary files before loading them into Actian Avalanche.
When configured, source data is first extracted to the temporary files that are uploaded to this temporary storage location, then loaded into Actian Avalanche using the dedicated Actian Avalanche loaders.
Currently, Semarchy xDI supports Google Storage as a temporary location.
There are two prerequisites to use temporary storage with Semarchy xDI:
In Semarchy xDI, the external storage location must be defined in the Actian Avalanche Metadata.
To configure the external storage in Semarchy xDI:
Open the Actian Avalanche Metadata.
Select the root server node, then go to the Storage tab.
Select the External Storage from the list. All the storage nodes available in the workspace appear in this list.
You can also drag and drop the Google Storage node from the Project Explorer to the External Storage property.
You can override the external storage location for individual schemas and tables. To configure this, select the Storage tab on the schema or table node and then select a specific External Storage value.
Your Metadata is ready and your tables reverse-engineered, you can now create your first Mappings.
The Actian Avalanche technology can be used like any other database in Semarchy xDI.
Drag and drop your sources, and targets, map the columns as usual and then configure the templates.