Here is the scenario: Our delivery creation triggers a custom output type, which triggers a call to a function module that does an HTTP_POST of an XML out to some URL on the web and gets an XML string back to update some custom tables.
Works great in all test systems and even in production, except when the execution of the update task happens to fall on the DB server, then the HTTP call times out, because the DB server is not set up to allow calls out to the internet.
So I had the idea to create a RFC desination that bundles all application servers into a single destination, so that the function making the HTTP call will always make the call from an application server and never from the database server.
Unfortunately as the remote function call to this new destination does not seem to do anything. As soon as the same function is called without specifying the 'destination'-syntax, everything works fine (except as mentioned when the update task executes on the DB server).
What could be the problem with this remote call?