About NextGen ETL
About NextGen ETL Integration Platform
This is implemented using the Boomi Integration Platform. Using the Boomi Platform Integration service, you have access to an intuitive interface, data mapping tools, process building recipes, and a library of connectors to accelerate your process using low/no code capabilities.
In Integration, a process represents a business process or transaction-level interface between two or more systems. There are three major parts to an integration process as follows:
| Build | Build workflows to integrate source of data, transform the data based upon the destination requirements, and send the data to the destination system. |
| Deploy | Deploy your built workflows to your runtime environment to be able to execute the integration between your source and destination systems. |
| Manage | Manage the lifecycle of your built workflows including manual and scheduled execution, scheduling changes, and viewing workflow execution logs. |
Terminology
| Term | Definition |
|---|---|
| Process | A workflow that integrates data between a source and destination. |
| Execution | A workflow execution in the runtime environment. |
| JVM | An instance of a Java Virtual Machine |
| Atom | An Atom is a minimalistic runtime environment that is remotely managed from the Boomi Integration Platform. Within the context of APM Connect, a Boomi Atom is deployed on-premise and a Cloud Atom deployment is not available. As part of an Atom deployment, integration processes are made available to your Atom. An Integration process contains all the components required to run your processes from end to end, including connectors, transformation rules, decision handling, and processing logic. |
| Computer | A physical or Virtual Machine instance on which an Atom can be deployed. |
| CPU | Central Processing Unit |
| Memory or RAM | Random Access Memory |
| Hard Disk or Storage | A storage device used by the computer for persistent data retention. |
| Integration Packs | Integration Packs Integration packs are content developed by GE for integrating your APM solution with specific source systems. This content contains the workflows necessary to extract data from the source system and deliver it to APM for use in your asset management work processes. APM Connect Release Integration pack and process folders will contain the below workflows and their dependencies:
|
| Extensions | Extensions are variables that are defined for each environment and integration pack deployment. These variables are used by the integration pack for a specific environment to dynamically allow an end user to configure parameters in the workflow that will be unique to their individual environment. The use of extensions in integration packs allows for standard workflow content without the need to rebuild and deploy a workflow that is unique for each environment and customer. In the APM Connect Integration packs, parameters of multiple extensions are defined and utilized. Details regarding the extensions are available in the environment connection setting steps in the installation portion of the document. |
| Environment | Environments give you greater control over change management and support different connection configurations using extensions. An environment is a workspace that users create and use for testing or production purposes. When you add an environment, you must select a classification: the choices are Production or Test. |
Architecture
The following image shows the architecture for on-premises environment.
