Boomi Long Run Executions Test
In Boomi, a long-running execution refers to a process or integration that takes an extended period of time to complete, often due to the volume of data being processed, the complexity of the process, or external system interactions. These executions can be part of batch jobs, real-time integrations, or operations involving large data sets or time-sensitive tasks (like waiting for external systems to respond). This test monitors and reports the status of the inbound and outbound documents that were processed during the long execution process. This test also alerts the administrators on the discarded status of the long execution process and take remedial action appropriately.
Target of the test : Boomi AtomSphere
Agent deploying the test : An internal agent
Outputs of the test : One set of results for each Application: Process Execution ID in the target Boomi AtomSphere being monitored.
| 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. |
|
Maxexecution Time in seconds |
Specify the maximum time for the execution process to happen in the Maxexecution Time in seconds text box. The default value is 300. |
|
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:
|
| Measurement | Description | Measurement Unit | Interpretation | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Status |
Indicates the status of the long execution process for this Process Execution ID. |
|
The values reported by this measure and its numeric equivalents are mentioned in the table below:
Note: By default, this measure reports the Measure Values listed in the table above to indicate the status of the long execution process for this Execution ID. However, in the graph of this measure, values will be represented using the corresponding numeric equivalents only. The detailed diagnosis of this measure lists the Boomi execution record details that includes Account, Execution time, Execution type, Message, Process id, Atom name, and Atom id. |
||||||||||||||||
|
Inbound documents |
Indicates the number of inbound documents for this Process Execution ID. |
Number |
|
||||||||||||||||
|
Inbound error documents |
Indicates the number of inbound error documents for this Process Execution ID. |
Number |
When there are more inbound error documents, there will be a greater load on error handling and processing logic. Each error document needs to be logged, tracked, and potentially retried, which consumes system resources like CPU, memory, and disk space. As the number of error documents grows, the system may experience slowdowns due to the overhead of error handling. The Boomi Atom or Cloud environment may struggle to keep up with both the incoming document load and the processing of errors, leading to delays in overall processing. |
||||||||||||||||
|
Outbound documents |
Indicates the number of outbound documents for this Process Execution ID. |
Number |
When there are more outbound error documents in Boomi long-run executions, it typically means that the integration process is facing difficulties when trying to send data to its destination or external systems. This leads to delays in data synchronization between systems, as the errors pile up and need to be addressed. |
||||||||||||||||
|
Inbound document size |
Indicates the size of the inbound documents for this Process Execution ID. |
Bytes |
|
||||||||||||||||
|
Outbound document size |
Indicates the size of the outbound documents for this Process Execution ID. |
Bytes |
|
||||||||||||||||
|
Execution duration |
Indicates the time of long execution process for this Process Execution ID. |
Seconds |
|
