Boomi Integration
In this section
Register Boomi Tool
To create and establish connection for Boomi Tool:
Login to Opsera, and navigate to Tool Registry.
Click + Create New Tool.
Locate the Boomi tool and click Select Tool.
In the Create New Tool form, provide a Tool Name and any other field values.
Click Create button to save the tool.
Navigate to the new tool’s Connection tab and provide details for API Type, Tool URL, Username, and Password.
Click Save.
The tool will be successfully created in Tool Registry.
Configure Pipeline for Boomi
 The Boomi pipeline involves creating three pipeline steps:
Boomi Create Package Step
Boomi Deploy Package
Boomi Migrate Package
Boomi Create Package Step
Login to Opsera and navigate to Products > Pipeline.
Open a pipeline workflow, and click + to create a new step.
Click the pencil icon next to the step. In the Step Definition, enter the step name and choose the Tool as Boomi and click Save.
Click the gear icon next to the saved step.
In the Step Settings, enter the details for Boomi Tool, Job Type, SCM Service Type, SCM Tool, Repository, Branch, File Path and File Name.
Click Save.
The Pipeline step for create package will be created successfully.
Boomi Deploy Package Step
In the pipeline workflow, and click + to create a new step.
Click the pencil icon next to the step. In the Step Definition, enter the step name and choose the Tool as Boomi and click Save.
Click the gear icon next to the saved step.
In the Step Settings, enter the details for Boomi Tool, Job Type and Source Environment.
5. Click Save.
The Pipeline step for deploy package will be created successfully.
Boomi Migrate Package Step
In the pipeline workflow, and click + to create a new step.
Click the pencil icon next to the step. In the Step Definition, enter the step name and choose the Tool as Boomi and click Save.
Click the gear icon next to the saved step.
In the Step Settings, enter the details for Boomi Tool, Job Type, Environment and Target Environment.
Toggle Fetch Components from SCM, if you want to run a pipeline using only the migrate step in a pipeline. This option fetches the details of repository, source code, branch and file details to migrate the deployment package from source to target. Once the option is enabled, enter details for SCM Service Type, SCM Tool, Repository, Branch, File Path, and File Name.
Click Save.
The Pipeline step for migrate package will be created successfully.
View Pipeline Logs and Reports
Once the pipeline is executed, you can view the Pipeline logs and reports updated in real time.
To view pipeline Logs, navigate to the Pipeline Summary tab. Scroll down to view Pipeline Logs.
To view a detailed report on the Boomi pipeline execution, click on Report under Action column.
Boomi Pipeline Executions KPI
To view metrics for Boomi pipeline executions, add the Boomi Pipeline Executions KPI to your dashboard.
To add the Boomi KPI:
Login to Opsera and navigate to Products > Insights.
Open/Create a Dashboard → click + icon → Marketplace
Search for Boomi to view the Boomi Pipeline Executions KPI.
Click Details on the KPI
Click +Add To Dashboard. The KPI will be added successfully to the dashboard.
Navigate to the respective dashboard to view the following metrics on the KPI.
Successful Execution Rate: Displays the percentage of components successfully deployed.
Frequency: Displays the average number of components deployed.
Boomi Line Chart: Displays the failed and successful components deployed over a given time period.
7. To view the report on the KPI insights, click the magnifier icon on the KPI. The report displays the insights on the Boomi pipeline such as total executions, frequency, success percentage, run count, failed/successful components, and more. The metrics for Actionable insights are shown as three separate tabs for the three main Boomi steps: Create Package, Deploy Package and Migrate Package.
Total Executions: Displays the total number of executions.
Successful Execution Rate: Displays the percentage of components/packages successfully deployed.
Frequency: Displays the average number of components/packages deployed per day.
Â