Is there a possibility to exchange document data/ payload data between 2 Atoms ?
Hi Peter Verschueren ,
There is no direct way to do that,one of way calling web services listener processes deployed on one atom by other atom.
another way by using FTP server .Giving FTP access to both atoms by using that we can get and write files from one atom to other atom.
Peter Verschueren .. Interesting question, any specific reason that is driving you towards that design approach?
Chandan Mishra It could be a way to overcome a challenge to communicate between a Cloud based Atom and an on premise Atom.
Use the cloud atom to connect to SaaS solutions, exchange data with the on premise Atom which connects to the enterprise applications hosted in private data center.
Peter Verschueren this is a very valid scenario and we have customers using boomi to do the same. You can leverage boomi's inbuilt queue, persist the data and expose that as a web service on the atom cloud. ANd the final step in your process will be call "execute process api" for the on-premsie process, which will then call the web service and this way you can exchange information. Let me know if you need more information and i have some architecture diagrams i can share with you.
Thameem Khan Thanks for the direction. Goind to try this out.
Thameem Khan I have a similar requirement, so would appreciate if you could share the architecture diagrams and/or examples.
would it be possible to share a bit more information? This approach may be better for are org as we would not need to punch so many holes in the firewall.
Thameem Khan, you can achieve the same with 1 local Atom on premise. What's the benefit of using a combi of cloud and local atoms?
In the case of communicating between a SAAS application and an on premise app behind a firewall, it should only be necessary to deploy a single atom on premise. This will communicate both with your on premise application as well as the SAAS app, assuming the proper ports are open in your firewall.
Looking into this thread, want to
I'm very much interested in looking at any architecture diagrams.
Thameem Khan can you help here with a sample one?
Adam Arrowsmith any pointers form your end?
In short, the options for atom-to-atom communicated as stated above are:
Here's a reference architecture diagram showing a "cloud gateway" pattern to that uses the public Atom Cloud to receive inbound requests from external clients and just forwarding to the local Atom via a single trusted connection/IP range (not VPN):
Thanks Adam Arrowsmith very much valid answer.
This makes perfect sense now.
Retrieving data ...