Boomi Runtimes Test

Monitoring Boomi runtime is vital for maintaining the reliability, performance, and security of the integration processes. Using this test, the administrators can quickly identify and address issues, optimize resource usage, and ensure that the Boomi integrations are functioning as intended.

Target of the test : Boomi Service

Agent deploying the test : A remote agent

Outputs of the test : One set of results for each Runtime type:Runtime in the target Boomi Service being monitored.

Configurable parameters for the test
Parameter Description

Test period

How often should the test be executed.

Host

The host for which the test is to be configured.

Port

The port number at which the specified host listens to.

Boomi Platform Base URL

Specify the URL - https://api.boomi.com/ that is used towards user registration for accessing the Boomi console.

Account ID

Specify the user Account ID that is auto-generated while registering the user in Boomi console. To know more, refer to Creating a new user and assigning user role in Boomi console topic in How does eG Enterprise Monitor Boomi AtomSphere? chapter.

Boomi User Account

Specify the email ID of the user in the Boomi User Account text box that is used towards user registration for accessing the Boomi console. To know more, refer to Creating a new user and assigning user role in Boomi console topic in How does eG Enterprise Monitor Boomi AtomSphere? chapter.

API Token

Specify the API token value that was generated using the Boomi console. To know how to generate the API token in Boomi console, refer to Creating a new API token in Boomi console in How does eG Enterprise Monitor Boomi AtomSphere?chapter.

Timeout

Specify the duration (in seconds) for which this test should wait for a response from the target Boomi Service. If there is no response from the target beyond the configured duration, the test will timeout. By default, this is set to 120 seconds.

DD Frequency

Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD frequency.

Detailed Diagnosis

To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability
  • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Status

Indicates the status of this runtime.

 

The values reported by this measure and its numeric equivalents are mentioned in the table below:

Measure Value

 Numeric Value
Offline 0
Warning 90
Online 100

Note:

By default, this measure reports the Measure Values listed in the table above to indicate the running status of runtime in Boomi Service. However, in the graph of this measure, states will be represented using the corresponding numeric equivalents only.

The detailed diagnosis of this measure lists the Atom Host name, ID, Installed, Purge immediate, Purge history days, Cloud id, Instance id, Force restart time, and Current version.

Online runtimes

Indicates the number of runtimes while online.

Number

 

Warning runtimes

Indicates the number of runtimes with warnings.

Number

Increased warnings in Boomi could signal performance degradation, such as slow response times, inefficient data processing, or resource usage. For example, if there are excessive warnings related to execution time or data processing, this could lead to slower integration processes.

Offline runtimes

Indicates the number of runtimes while offline.

Number

Offline runtimes in Boomi can occur due to issues like system outages, connectivity problems, or configuration errors, which can disrupt the normal flow of data.

If the system is offline for extended periods, it might miss critical updates or processes, potentially leading to data loss.