These tools enable ML in the HC platform by setting up extensibility points that call out to R/Python scripts during ETLs. This is only for 4.0 and 4.2 versions of DOS.
- A SAM binding refreshes table A.
- A subsequent SAM binding, dependant on table A, hosts the extensibility point.
- This extensibility point runs the R file which reads from Table A.
- Since this R file pushes predictions to table B, the SQL query for B just creates the column structure
- Your environment is on DOS 4.0 of 4.2.
- You've already been able to push predictions to a destination database.
- The rest are here.
This doc details the entire process.
- AEs and analysts, if they can write to EDWAdmin, can do much of that work
- Sys admins / DBAs are needed for installing the ispac, which requires an RDP into the ETL server
- SSIS
- SQL Server Integration Services.
- SSMS
- SQL Server Management Studio. Where work happens.
- EDW Console
- Catalyst web app for viewing and configuring ETLs.
- Errors are surfaced here.
- Batches
- ETL jobs scheduled in EDW Console (web portal) by a AD/TD.
- SSIS packages
- are installed in: SSMS >
Integration Services Catalogs
>CatalystExtensibility
- are installed in: SSMS >
- DTSX File
- The actual SSIS package files that are installed via the .ispac file.
- ISPAC File
- This is the SSIS project deployment file, which is a self-contained unit of deployment that includes only the essential information about the packages and parameters in the project. reference