INVIXO Migration Suite
The Invixo Migration Suite consists of four key components:
Extractor
This component allows you to effortlessly export details from Source platform and generate config files for the Config Builder. This includes all pipelines, mappings, related components etc. This tool is both used to get an overview of the platform’s interfaces and components, and also used as part of the migration process.
Config Builder
This component is used to build configurations, so they can be exported into the Integration Platform.
This includes ensuring naming standards are the same, collecting extracted configurations and pipelines from source system into relevant flows and subflows.
Transpiler
This component is used to migrate flow into the Integration Platform. This component ensures all flows are either migrated into known components – or if not possible, then into “unknown” components, which the client can then refactor to ensure they fit with the expected patterns on the Platform server.
Unit Tester
This component is used to verify, that pipelines, configurations and mappings has been migrated correctly to the new platform. In essence this component retrieves before and after messages on Source System, sends these messages to the platform, and compare the new output with output from Source System and generates a report for all messages sent.
Extractor
This component is used to build configurations, so they can be exported into the Integration Platform.
This includes ensuring naming standards are the same, collecting extracted configurations and pipelines from source system into relevant flows and subflows.
Config Builder
The Config Builder empowers you to create configurations for seamless export into AppConnect. This feature streamlines operations by aligning naming standards and organising extracted data into relevant flows and subflows.
Transpiler
This component is used to migrate flow into the Integration Platform. This component ensures all flows are either migrated into known components – or if not possible, then into “unknown” components, which the client can then refactor to ensure they fit with the expected patterns on the Platform server.
Unit Tester
This component is used to verify, that pipelines, configurations and mappings has been migrated correctly to the new platform. In essence this component retrieves before and after messages on Source System, sends these messages to the platform, and compare the new output with output from Source System and generates a report for all messages sent.