Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

In this section

Register Boomi Tool

To create and establish connection for Boomi Tool:

  1. Login to Opsera, and navigate to Tool Registry.

  2. Click + Create New Tool.

  3. Locate the Boomi tool and click Select Tool.

  4. In the Create New Tool form, provide a Tool Name and any other field values.

  5. Click Create button to save the tool.

  6. Navigate to the new tool’s Connection tab and provide details for API Type, Tool URL, Username, and Password.

  7. Click Save.
    The tool will be successfully created in Tool Registry.

Configure Pipeline for Boomi

 The Boomi pipeline involves creating three pipeline steps:

  1. Boomi Create Package Step

  2. Boomi Deploy Package

  3. Boomi Migrate Package

Boomi Create Package Step

  1. Login to Opsera and navigate to Products > Pipeline.

  2. Open a pipeline workflow, and click + to create a new step.

  3. 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.

  4. Click the gear icon next to the saved step.

  5. In the Step Settings, enter the details for Boomi Tool, Job Type, SCM Service Type, SCM Tool, Repository, Branch, File Path and File Name.

  6. Click Save.
    The Pipeline step for create package will be created successfully.

Boomi Deploy Package Step

  1. In the pipeline workflow, and click + to create a new step.

  2. 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.

  3. Click the gear icon next to the saved step.

  4. 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

  1. In the pipeline workflow, and click + to create a new step.

  2. 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.

  3. Click the gear icon next to the saved step.

  4. In the Step Settings, enter the details for Boomi Tool, Job Type, Environment and Target Environment.

  5. 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.

  6. 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:

  1. Login to Opsera and navigate to Products > Insights.

  2. Click Marketplace.

  3. Search for Boomi to view the Boomi Pipeline Executions KPI.

  4. Click Details on the KPI

  5. In the Boomi Pipeline Executions popup, select the Dashboard to which you want to add the KPI.

  6. Click +Add To Dashboard. The KPI will be added successfully to the dashboard.

  7. Navigate to the respective dashboard to view the following metrics on the KPI.

  • Successful Execution Rate: Displays the percentage based on the number of successful components.

  • Average Frequency: Displays the frequency based on the number of steps per day.

8. 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.

 

  • No labels