How to succeed Multiple SAP back end (SAP )access with single Gateway dynamically?

[Former Member]

HI Gurus,

As of now we have single Gateway server where (we do GW config as well as coding to access back end ) connected with our back end SAP server development , Quality and production via RFC destination ..

How do I dynamically connect to different server ?

For example , if I make all three (dev, qs, prd ) as default in system alias, will I be able to connect to different back end dynamically ?

Appreciate your help..

Kind regards

Shiv..

[former_member184867 · Accepted solution]

You can try out Multi Origin capability of Gateway.

You need to configure three system aliases pointing to three different backend systems marking one as default.

To get data from a specific backend you need to pass ;o=<SYSTEM ALIAS FOR TARGET SYSTEM> while calling the OData service.  Here 'o' stands for Origin.

Example:

/sap/opu/odata/IWFND/RMTSAMPLEFLIGHT;o=N78_400_BEP/CarrierCollection

Read more at

Multiple Origin Composition - SAP Gateway Foundation (SAP_GWFND) - SAP Library

However I think it is not a very good idea to have only one Gateway server for all cases.

[Former Member · Accepted solution]

Hi Atanu ,

Thanks

When I make my Quality system as Default , and I would expect the Odata will extract data from Quality system ...

But instead I am getting error 500 , internal server error

------------------------------------

<?xml version="1.0" encoding="utf-8" ?>

- <error xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata">

<code>SY/530</code>

<message xml:lang="en">No service found for namespace /SAP/, name ZGW_SUPPLIER_SRV, version 0001.</message>

- <innererror>

<transactionid>2E36D6E50A58F1B09267005056A85E60</transactionid>

<timestamp>20160218115327.7220000</timestamp>

- <Error_Resolution>

<SAP_Transaction>Run transaction /IWFND/ERROR_LOG on SAP NW Gateway hub system and search for entries with the timestamp above for more details</SAP_Transaction>

<SAP_Note>See SAP Note 1797736 for error analysis (https://service.sap.com/sap/support/notes/1797736)</SAP_Note>

</Error_Resolution>

<errordetails />

</innererror>

</error>

-----------------------------

Appreciate your help ..

Kind regards

Shiv

[Former Member · Accepted solution]

Found out the issue ...resolved..

Thanks