on 09-03-2015 2:12 PM
Hello all
When calling a gateway service, is it possible to dictate the GW hub server to connect to a specific backend application server which becomes known only at runtime, e.g. by providing the app server as an HTTP parameter?
Kind Regards
*-- Serdar
Hello Serdar,
Check the Multiple Origin Composition Concept.
Using Parameter SAP_Origin, System Alias can be passed and we can route the call from GW Hub to different Back-End systems.
Check the below :
Multiple Origin Composition - SAP Gateway Foundation (SAP_GWFND) - SAP Library
Regards,
Ashwin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ashwin
Thanks for your reply. Quite close but seems the SAP_Origin needs to be provided with existing configured system aliases. It is the servers of the same system we would like to address specifically, not different systems. Still, in order to resolve the problem, it may be possible to create RFC destinations for each app server and define system aliases for each as well. But this does not sound feasible.
Any way to pass the app server name with no static definition beforehands, i.e. with no config. required?
Kind Regards
*-- Serdar
Hello Serdar,
There is no such option available to completely dynamically decide the possible back end for an OData call. The multi origin option is the closest possible feature to meet your requirement.
If you have configured all POSSIBLE the system aliases, then you can navigate to the desired destination at runtime using the following notation ;o=<ALIAS NAME>
Example:
/sap/opu/odata/IWFND/RMTSAMPLEFLIGHT;o=ALIAS NAME/CarrierCollection
Regards
Atanu
Hi Serdar,
Apart from Using System Aliases, you could User RFC calls from your Service Implementation to access data from Multiple Backend system.
1. the service is implemented in your Gateway system.
2. RFC connections exist for the Backend system you want to Access.
3. Create Function Module in your backend system which retreives the data you require.
4. create the required Entity in your service implementation.
5. Pass teh RFC destination as input to your HTTP/URI, as Pointed out by Atanu mallik
Example:
/sap/opu/odata/IWFND/RMTSAMPLEFLIGHT;o=ALIAS NAME/CarrierCollection
6. use the retrieved Data to populate your Entity.
Kind Regards,
Vamsi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.