Boomi with Solace

Naga

I have a Boomi listener process which is listening to a solace queue. When ever the local atom is offline the listener is stopped. When the atom is online the listener is not running automatically.. Manually we have to deploy the listener only then the listener is connecting to solace.

mhilmen

I meant the Listener in my previous comment, not Atom. Thanks for the clarification.
1) Have you tried to just restart the Listener, through the Atom Management tooling, and not redeploy it? If so, what behavior do you see?
2) Did you install the Boomi Atom with the "Run as Administrator" privileges? If not, you may get issues during restart.
https://community.boomi.com/s/article/HowtoInstallaLocalAtomMoleculeorCloud#jive_content_id_Permissions

[Deleted User]

@Naga were you able to get this working? If so, please click the “Yes” on Did this answer the question? where appropriate so that others can benefit! And if not, please let us know so we can continue to assist!

mhilmen

Can you provide a few more details as to what is happening?

• I assume that your Atom is on-premises and not in the Boomi Cloud, is that correct?
• If so, can you tell me if your Atom is running on Linux or on Windows?
• You mention the Atom going offline, is it being restarted or just losing its network connection?
• When you say re-deploy the Atom, are you restarting the Atom through the Atom Management tooling or actually pushing it down to the Atom again from the developer UI using the package and deploy process?
• Assuming its the later on my above deployment question, can you tell me if the listener is available for restart in the Atom Management tooling before you deploy? If it is, have you tried doing a restart of the listener instead of a deploy? Can you share with me what happens if you do?

mhilmen

If you are running on Linux, and if there is a restart of the OS, you need to take an extra step to have the Boomi Atom restart. In Windows, this is handled by Windows Services. Below is a link on how to create a systemd service in Linux to auto restart the Atom.
https://community.boomi.com/s/article/creatingalinuxsystemdservicetostarttheatom

Naga

@mhilmen said:
Can you provide a few more details as to what is happening?

• I assume that your Atom is on-premises and not in the Boomi Cloud, is that correct?

It is on premise on a Windows machine

• If so, can you tell me if your Atom is running on Linux or on Windows?

Windows

• You mention the Atom going offline, is it being restarted or just losing its network connection?

Currently it's on someone's laptop.If the laptop is shutdown..the atom goes offline.

• When you say re-deploy the Atom, are you restarting the Atom through the Atom Management tooling or actually pushing it down to the Atom again from the developer UI using the package and deploy process?

We are not redeploying the atom we are redeploying the listener process

• Assuming its the later on my above deployment question, can you tell me if the listener is available for restart in the Atom Management tooling before you deploy? If it is, have you tried doing a restart of the listener instead of a deploy? Can you share with me what happens if you do?

mhilmen

I meant the Listener in my previous comment, not Atom. Thanks for the clarification.
1) Have you tried to just restart the Listener, through the Atom Management tooling, and not redeploy it? If so, what behavior do you see?
2) Did you install the Boomi Atom with the "Run as Administrator" privileges? If not, you may get issues during restart.
https://community.boomi.com/s/article/HowtoInstallaLocalAtomMoleculeorCloud#jive_content_id_Permissions

[Deleted User]

@Naga were you able to get this working? If so, please click the “Yes” on Did this answer the question? where appropriate so that others can benefit! And if not, please let us know so we can continue to assist!