Boomi Atom Test

Boomi AtomSphere manages the integration between the instances and on-premise applications/cloud. For a smooth integration to happen, the running status of the instances, the restart frequency of the instances, and the memory status of the instances should be monitored at regular intervals.

Atom Decommissioning is the process of shutting down or deactivating an Atom (the runtime engine that executes integration processes) at each instance. An Atom in Boomi is the core component that runs integration tasks, such as processing data transfers, executing business logic, and connecting to various endpoints. When this Atom stops in Decommissioning process, then Integration processes may continue running on the Atom, causing disruptions in integration workflows. Additionally, any new processes assigned to this Atom will not be able to execute correctly until the issue is resolved. This test helps the administrators to identify the issues related to Decommissioning process happening at each instance and troubleshoot them accordingly.

Target of the test : Boomi AtomSphere

Agent deploying the test : An internal agent

Outputs of the test : One set of results for each Atom in the target Boomi AtomSphere 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. The default value is NULL.

JMX Remote Port

This parameter appears only if the mode is set to JMX. Here, specify the port at which the JMX listens for requests from remote hosts. Ensure that you specify the same port that you configured in the management.properties file in the <JAVA_HOME>\jre\lib\management folder used by the target application . To know more, refer to Enabling JMX Support for JREtopic in Monitoring Java Application document.

JNDI Name

This parameter appears only if the mode is set to JMX. The JNDIname is a lookup name for connecting to the JMX connector. By default, this is jmxrmi. If you have resgistered the JMX connector in the RMI registery using a different lookup name, then you can change this default value to reflect the same. 

JMX User, JMX Password, and Confirm password

These parameters appear only if the Mode is set to JMX. If JMX requires authentication only (but no security), then ensure that the user and password parameters are configured with the credentials of a user with read-write access to JMX. To know how to create this user, refer to Configuring the eG Agent to Support JMX Authenticationtopic in Monitoring Java Application document. Confirm the password by retyping it in the Confirm Password text box.

Provider

This parameter appears only if the Mode is set to JMX. This test uses a JMX Provider to access the MBean attributes of the target Java application and collect metrics. Specify the package name of this JMX Provider here. By default, this is set to com.sun.jmx.remote.protocol.

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 Service?chapter.

Timeout

Specify the duration (in seconds) for which this test should wait for a response from Boomi AtomSphere. The default value is 120.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Atom status

Indicates the running status of this Atom.

 

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

Measure Value

 Numeric Value
Stopped 0
Stopping 1
Paused for stop 70
Pausing for stop 75
Paused 80
Pausing 85
Init_updating 90
Initializing 95
Running 100

Note:

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

Number of attached accounts

Indicates the number of accounts registered with this Atom.

Number

 

Atom decommission stage

Indicates the running status of decommission process for this Atom.

 

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

Measure Value

 Numeric Value
Initializing 1
Pausing_atom 2
Stopping_work_handlers 3
Flushing_reports 4
Draining_queues 5
Stopping_atom 6
Done 7

Note:

By default, this measure reports the Measure Values listed in the table above to indicate the running status of Atom decommission process in this instance. However, in the graph of this measure, values will be represented using the corresponding numeric equivalents only.

Is node the head cloudlet ?

Indicates whether/not the node is a head cloudlet for this Atom.

 

A Cloudlet in Boomi is a resource in Boomi’s cloud platform (part of AtomSphere) that represents a logical grouping or set of Atoms deployed in the cloud.

A Node refers to a single instance of an Atom (either On-Premise Atom or Cloud Atom) that performs the actual execution of integration processes. Node is part of a Cloudlet, but not necessarily the "head" Cloudlet.

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

Measure Value

 Numeric Value
No 0
Yes 1

Note:

By default, this measure reports the Measure Values listed in the table above to indicate whether/not the node is a head cloudlet for this instance. 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 Account details such as Account id, Account Name, Created, Support access, and Support level.

Is the Atom restarting ?

Indicates whether/not this Atom had restarted.

 

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

Measure Value

 Numeric Value
No 0
Yes 1

Note:

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

Is there a clustering problem ?

Indicates whether/not this Atom had encountered a clustering problem.

 

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

Measure Value

 Numeric Value
No 0
Yes 1

Note:

By default, this measure reports the Measure Values listed in the table above to indicate whether/not the Atom had encountered a clustering problem. However, in the graph of this measure, states will be represented using the corresponding numeric equivalents only.

Has the Atom entered into the low memory status ?

Indicates whether/not this Atom undergoes low memory.

 

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

Measure Value

 Numeric Value
No 0
Yes 1

Note:

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

Has the Atom encountered an OutOfMemory Error ?

Indicates whether/not this Atom had encountered error due to Out of Memory condition.

 

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

Measure Value

 Numeric Value
No 0
Yes 1

Note:

By default, this measure reports the Measure Values listed in the table above to indicate whether/not the Atom had encountered an Out Of Memory Error. However, in the graph of this measure, states will be represented using the corresponding numeric equivalents only.

Number of schedule configurations running on the Atom

Indicates the number of scheduled configurations running on this Atom.

Number