Access Boomi Insights via Postman: Ready-to-Use Collection

Following our previous guide on retrieving your Boomi Public API Key, this post shows how to set up a Postman collection and environment to query telemetry metrics from Boomi Insights.

Using Postman allows you to test APIs, explore available widgets, and integrate metrics into dashboards or automation scripts.

---

Step 1: Import the Collection and Environment

1. Download the files:

   • 📑 Boomi_Insights_Collection.postman_collection.json

   • 🌍 Boomi_Insights_Env.postman_environment.json

2. Open Postman, then import both files.

3. Select the imported environment in the top-right corner.

---

Step 2: Configure Environment Variables

The environment uses three key variables:

Variable	Description
API_KEY	Your Boomi Public API Key 🔑
STACK	Your runtime stack name 🏗️
REGION_GATEWAY	Your Boomi region gateway 🌐 (e.g., us-east-prod-gateway)

💡 Tip: Updating these once applies them to all requests in the collection.

---

Step 3: Example Requests in the Collection

Name	Method	Description
CPU Metrics	GET	Fetches CPU utilization percentage for the stack
Memory Metrics	GET	Returns RAM usage percentage
Worker Count	GET	Number of active workers in the stack
Worker Execution Count	GET	Total executions by workers
List Widgets	GET	Retrieve all available telemetry widgets

Each request uses environment variables to keep URLs and API keys generic and reusable. Sample Request Structure All requests follow the same pattern: Endpoint URL: Uses REGION_GATEWAY and STACK variables Header: x-api-key uses API_KEY variable ⚡ Note: The {{VARIABLE}} syntax pulls values from your Postman environment, making it easy to switch stacks or regions. Step 4: Benefits of Using This Collection Test multiple endpoints quickly without manual URL edits Easily switch between runtime stacks or regions Standardize metrics collection across your team Serve as a foundation for dashboards or automated reporting

Using Boomi API Insights: A Step-by-Step Guide

Boomi provides API Insights, allowing you to monitor your integration runtime environments programmatically. From CPU and memory usage to worker counts and execution metrics, you can access telemetry data through the Insights API and integrate it into dashboards or monitoring tools.

This guide is split into two parts:

1. Retrieving your Boomi Public API Key

2. Accessing telemetry data using Postman

---

Part 1: Retrieving the Boomi Insights Public API Key

Before querying Boomi Insights APIs, you need an API Token and a Public API Key.

1. Generate an API Token

1. Log in to your Boomi account.

2. Go to Settings → User Profile.

3. In the left pane, click Platform API Tokens.

4. Generate a new token linked to your user account.

2. Access Boomi Insights

1. Navigate to Boomi Insights (region-specific URL).

2. Enter the following when prompted:

   • Account ID (where the token was created)

   • Username (associated with the token)

   • API Token

3. Get the Public API Key

1. Go to Managed Cloud Services → Runtime Dashboard.

2. Select your runtime stack.

3. Click Settings → Public API Settings.

4. Click Get API Key to retrieve it.

⚠️ Note: You must have the Boomi Insights Admin role to access the Public API Key.

---

Part 2: Accessing Insights Data Using Postman

Once you have the Public API Key, you can query telemetry metrics. Use a generic Postman collection with environment variables for easy configuration.

Generic API Endpoints

Metric	Endpoint	Description
CPU Usage	/telemetry?widget=cpu.utilisation.%25&stackname=YourStack	Shows CPU utilization
Memory Usage	/telemetry?widget=ram.used.%25&stackname=YourStack	Tracks memory consumption
Worker Count	/telemetry?widget=boomi.aw.count&stackname=YourStack	Returns the number of active workers
Worker Execution Count	/telemetry?widget=boomi.awExec.count&stackname=YourStack	Shows worker executions

🧘‍♂️ Monk Fasting: My 36-Hour Experiment with Hunger, Heritage, and Hot Water

Fasting has always fascinated me. Whether it's Karthika Masa Naktalu (evening-only meals), Ekadasi Ekabhuktam (twice a month), or my weekly Thursday fasting ritual, I’ve danced with hunger in different forms. And then came Monk Fasting—where you skip food for a full 36 hours. The idea was floated to me by one of the Educational Units (EUs) of WhatsApp University, and the benefits sounded like something out of a wellness brochure: detoxified digestion, sharpened focus, fat loss, and autophagy (that sci-fi-sounding cell-cleaning process). Despite years of fasting practice, sleeping with a completely empty stomach? That I could never dare.

☕The Hardest Part: Saying No to South Indian Coffee

Let’s talk priorities. I’m a coffee person—and not just your standard drip guy. My morning ritual involves mixing coffee powder with chicory root (3:1), brewing it in a moka pot, then blending that magic with freshly boiled whole milk and a generous splash of sugar. That, my friend, is South Indian coffee. After that comes mid-morning Indian tea, followed by an evening tea. And yes, the prep is a ceremony in itself. For this Monk Fast, I ditched the whole routine. No coffee. No tea. Just plain hot water, all day. Energy-wise, I was fine. But by evening, caffeine withdrawal kicked in and I got drowsy. At 10 PM—a whole two hours earlier than my usual schedule of watching the date change—I crashed. Slept like a baby until morning.

📆 The Timeline

• Started fasting: Wednesday 10 PM 
•  Broke fast: Friday 10 AM 
• Total intake: Hot water. And a ridiculous amount of it.

📉 Results (and a Marital Audit)

I weighed myself before and after: five pounds down. My wife, naturally skeptical, supervised the weigh-in like a hawk. Verdict? Certified by the Ministry of Marital Surveillance.

🤔 What I Learned

•  ✅ Weight loss: Probably temporary, but satisfying. 
•  🛑 Digestive break: Felt like my stomach got a spa treatment. 
•  😴 Drowsiness: Could’ve been the lack of caffeine more than the fasting.

🔄 Will I Do It Again?

Absolutely. It gave me more confidence around extended fasting and more respect for my usual caffeine reliance. If you're even half as crazy as I am, take it slow. Choose a day when you don't need to be an unpaid Uber driver or run marathons—and make sure your family’s nearby to make sure you are still alive.

Powershell hacks: How can I run powershell if I am not an admin

Dealing with admin restrictions on my laptop has become quite a hassle. My company won't allow me to have admin privileges, which means even running simple PowerShell commands requires me to ask for admin rights. This has added an extra layer of frustration to my workflow. Why do I need PowerShell, you might ask, when Python can solve many problems with scripts? Well, the catch is that even installing Python and importing libraries requires admin rights—leaving me stuck in a loop of limitations. After a bit of exploration, I found a way to work around this. Here's a simple trick:

powershell.exe -ExecutionPolicy bypass

Docker Diaries: Docker Pull Request for Ubuntu got Denied

Trying to install ubuntu image and executed the following command using Windows Power Shell. Apologies for not taking the screen capture. It looks something like this:

docker pull ubuntu default is latest Trying to pull ubuntu pull access denied for ubuntu does not exist or may

require 'docker login': denied: requested access to the resource is denied


So I exited from the Power Shell and logged in again to Docker. Then used docker pull command voila!! it worked. This time I took the screen capture of the output though :)

Windows PowerShell Copyright (C) Microsoft Corporation. All rights reserved. PS C:\Windows\system32> docker login Authenticating with existing credentials... Login Succeeded PS C:\Windows\system32> docker pull ubuntu Using default tag: latest latest: Pulling from library/ubuntu d51af753c3d3: Pull complete fc878cd0a91c: Pull complete 6154df8ff988: Pull complete fee5db0ff82f: Pull complete Digest: sha256:747d2dbbaaee995098c9792d99bd333c6783ce56150d1b11e333bbceed5c54d7 Status: Downloaded newer image for ubuntu:latest docker.io/library/ubuntu:latest PS C:\Windows\system32>

AMQ4036 Error connecting to queue manager on Linux using MQ Explorer or RFHUTILC

Issue: MQ Explorer fails to connect to a Queue manager located on Linux server. Fails with error AMQ4036 : Access not permitted. You are not authorized to perform this operation

Setup:

User has two IDs.
• Linux user ID: j1234d
• Windows ID: mydomain\jdove

Queue Manager (QM1) is on Linux machine and the Linux ID “j1234d” has access to the queue manager.
MQ Explorer is on Windows machine where the user is logged on with Windows ID “mydomain\jdove”.
When user tries to connect to QM1 from Windows machine using MQ Explorer, he/she gets the following error.

Resolution:

MQ Explorer makes a client connection and the credentials passed to the QM1 on Linux server would be “mydomain\jdove”. Since the ID “mydomain\jdove” is not defined on the Linux server, it fails to get authenticated.

Simple way to resolve:

1. Create ID “j1234d” on your Windows machine and use MQ Explorer to connect to the QM1 on Linux Server

However above fix would need you to log off current Windows session and sign in as “j1234d”. This is a pain.
Instead, do the following:

Create ID “j1234d” on your Windows machine and use MQ Explorer to connect to the QM1 on Linux Server
Create a Windows batch script as shown :

set APPDATA=

runas /env /user: "strmqcfg -d"

So for the above example it would be:

set APPDATA=D:\mqeclipse\mqcm5dev

runas /env /user:j1234d "strmqcfg -d"

When you run the above script, at the prompt enter the password you have set for the id you created for id ‘j1234d’

The runas  command makes the MQ Explorer to run under the local id which is the equivalent of the Linux id. When we run the MQ Explorer process under the id , the credentials will be passed as is ( eg:’j1234d’) and you will be able to connect to the queue manager since this ID on Linux server has access to the queue manager QM1.

The same solution can be used  if you are getting error "Not authorized" with RFHUTILC utility. The following screen shows the error.

Use the above approach to circumvent the error.
Hope this helps!!!

wsgw (mywsproxy): Valid backside connection could not be established: Failed to establish a backside connection

Setup:

1. Datapower XI50 is on corporate network
   
2. Microsoft Virtual PC 2007 with Windows XP and hosting WebSphere application server 6.1 ( mywasnode)
3. Web Service Proxy is virtualizing the Web services hosted on mywasnode.
   Following is the Web Services proxy set up.
   
   
   
   
   

Request comes to HTTP front side handler AddressSearchFSH via URI <dp:ipaddress>/EastAddressSearch and is directed to actual service end point

<remote-endpoint-host>:9080/EastAddress/Services/AddressSearch. This is a plain and simple setup. However, I have been encountering the following errors

After much head scratching, I found the solution and as it happens with all such issues, the resolution is very simple. The culprit was Windows XP firewall. Since I had WAS running locally, Windows XP firewall was obstructing all the requests coming from Datapower to my WAS Web Service. Added the Web services port (9080 in this case) to the firewall exception list, voila!! everything started working fine.

For those of you wondering where to add this, please see the following screen shots.

Go to Start> Settings. Control panel > Security center> click on Manage settings for Firewall, On the Windows firewall window , go to exceptions tab, click on Add Port button.

In the pop-up window enter the port number and give a description to your exception and click OK. You are done.


Hope this is helpful.

WebLogic Server does not start

Issue: When you start WebLogic Server instance, the server would not come up and the start script hangs.
Symptoms:
In the /servers/AdminServer/logs/Adminserver.log you would find the following error.
####<Aug 27, 2009 3:47:58 PM EDT> <Critical> <WebLogicServer> <gaalpltapp0040> <AdminServer> <main> <<WLS Kernel>> <> <> <1251402478485> <BEA-000386> <Server subsystem failed. Reason: java.lang.NumberFormatException: null
java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Integer.java:415)
at java.lang.Integer.parseInt(Integer.java:497)
at weblogic.ldap.EmbeddedLDAP.validateVDEDirectories(EmbeddedLDAP.java:1035)
at weblogic.ldap.EmbeddedLDAP.start(EmbeddedLDAP.java:212)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
####<Aug 27, 2009 3:47:58 PM EDT> <Notice> <WebLogicServer> <gaalpltapp0040> <AdminServer> <main> <<WLS Kernel>> <> <> <1251402478508> <BEA-000365> <Server state changed to FAILED>
####<Aug 27, 2009 3:47:58 PM EDT> <Error> <WebLogicServer> <gaalpltapp0040> <AdminServer> <main> <<WLS Kernel>> <> <> <1251402478509> <BEA-000383> <A critical service failed. The server will shut itself down>
####<Aug 27, 2009 3:47:58 PM EDT> <Notice> <WebLogicServer> <gaalpltapp0040> <AdminServer> <main> <<WLS Kernel>> <> <> <1251402478511> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>


Solution:

When you see above error, please check
1. if the disk space is full
2. if disk space is fine, then delete the following file
/servers/AdminServer/data/ldap/conf/replicas.prop
and restart the server. WLS sometimes corrupts the file replicas.prop and is often results in above error