Question: Using RFC Web Services, how can remote calls to these RFCs be engineered in such a way as to be able to identify the calling server AND application name? What are the prerequisites for doing so?
Background: Over the course of time, many RFCs will inevitably be developed to meet the needs of numerous external and third-party applications such as web apps and the like. Some of these RFCs will likely be used by several of these applications. When it becomes necessary to modify a particular shared RFC, you will want to ensure that change has not broken existing implementation of it. Furthermore, over time, and personnel changes, a lack of documentation and training for internal processes can leave development teams struggling to come up with a test plan not knowing how a given RFC is being used in production. To increase the chances of a successful deployment, you must be able to identify these applications to be sure they remain unaffected by the changes or are updated to accommodate them.