Can we have main process deployed on cloud and sub process on local aotm?
You can do it, but what the use case that you want to go for it?
Hi Srinivas, thank you for your reply.-The parent process is deployed on Boomi Atom Cloud to listen for REST request from external applications.-The sub process is deployed on local atom and contains connections to internal systems/applications which are not accessible from outside.
I want to call the sub process from parent process and pass the data.
Yes, you can deploy the sub process alone also in local atom. but start shape should be "No Data". then it will work.
Hi Vinod, if you deployed the subprocess to the local atom with Start shape as "No Data", it wouldn't receive the documents from the other process. I'm assuming the overall objective of the poster's original question is to pass data from the one process running in the cloud automatically to another process running locally.
Thanks Adam for making me clear, I assumed sub process is independent, so only i have given that solution...
Considering your use case answer is No.
I agree with the approach proposed by Adam.
The short answer is no, a process call shape cannot automatically shuttle documents between different Atoms.
The way to achieve this pattern is through web services. Publish the second process deployed to the local Atom also as a web service listener, and have the first process deployed to the cloud call it like any other HTTP endpoint. Of course this means there will be some firewall configuration in front of the local Atom to receive external traffic, however this can be configured to only whitelist requests coming from the Boomi Atom Cloud.
Another option to consider would be the use Atom Message Queuing. You could have the first process, the one running in the Boomi Atom Cloud, receive external requests via web service and write them to an Atom Message Queue. Then the second process, deployed locally behind your FW, would pick up the messages from the Atom Queue with a Get or Listen operation. This only works if you do not need synchronous real-time processing, tho, as there would be a small delay between putting the messages on the queue and picking them up. The upside is guaranteed message delivery and not having to open an inbound port on your FW. Just another option.
... on second thought, I don't believe you can access the Atom Que in one Atom directly from another Atom without the web service layer in between ... so Adam's suggestion above is probably the more elegant and workable solution.
Retrieving data ...