How to determine if my local atom or Atom Cloud is actually functioning.

Document created by pete_mccoy1.3055586893899446E12 Employee on Apr 20, 2015Last modified by dave_lesshafft on Mar 2, 2016
Version 2Show Document
  • View in full screen mode
Scenario 1:
Local atom or Atom Cloud is shown as being off-line in the UI Atom Management tab, and/or you've received notification that your local atom or Atom Cloud is off-line, however process reporting tab indicates that scheduled processes and listener triggered processes are executing.

 

Scenario 2:
Atom is shown as On-line in the UI Atom Management tab, but no processes are executing.

Most likely, the cause for Scenario 1 is a communication failure between the server that hosts the local atom/Atom Cloud, and the Boomi Platform.  Usually, in this situation, the impact is as follows:
   1.  Documents and log files associated with process executions are not available.
   2.  Process executions cannot be manually initiated.
   3.  The Atom Container logs are not available via the Atom Managment UI.  (You are still able to access the atom container logs from the <AtomHome>\logs
         directory.)

 

Corrective actions for Scenario 1:
    1.  Stop the Atom.exe process, wait 5 minutes, then start the atom.  If this does not restore the atom to the appropriate status,  stop the Atom.exe job, then, (if
          possible, restart the server hosting the local atom.)
    2.  If stopping and starting the Atom/Server, do not clear the issue, reach out to your network administration resource for additional assistance confirming that the
          appropriate ports have the correct privileges and the server has the correct firewall/proxy setting configured.

 

Most likely the cause for Scenario 2 is an atom integrity issue encountered during the Restart/Startup.  You can check your endpoints to see if they are receiving expected updates.  Usually, in this situation, the impact is as follows:
   1.  No process executions show in Process reporting.
   2.  Documents and log files associated with process executions are not available.
   3.  The Atom Container logs are not available via the Atom Managment UI.  (You are still able to access the atom container logs from the <AtomHome>\logs
         directory.)

 

Corrective actions for Scenario 2:
    1.  Stop the Atom.exe process, wait 5 minutes, then start the atom.  If this does not restore the atom to the appropriate status,  stop the Atom.exe job, then, (if
          possible, restart the server hosting the local atom.)
    2.  If stopping and starting the Atom/Server, do not clear the issue, reach out to your network administration resource for additional assistance confirming that the
          appropriate ports have the correct privileges and the server has the correct firewall/proxy setting configured.

 

In the event that the corrective actions described above, do not clear the issue, please open a support case.  Please be sure to include the following information:

 

1.  Account Id.
2.  Atom Id:
3.  Container logs.  (If available)
4.  Brief description of the issue, when it started,  what the symptoms are, (Atom displays as off-line, but schedules still being  followed, atom off-line no executions,
      no process endpoint updates.)

 

 

 

 

 

 


Attachments

    Outcomes