Gateway for Legacy

[Shabarish_Nair]

Guys,

Quick one.

Gateway can expose SAP backend as oData services.

What about legacy non SAP backends?

What is the best approach in this case?

Regards,

Shabarish

[paschmann · Accepted solution]

Hello Shabarish,

Technically - Netweaver Gateway can only expose data of your SAP systems, for exposing/consuming date from legacy/non SAP backends, PI or other middleware is most probably a more viable option.

While this is a old slide deck - I like to use it for reference when considering high volume and non-SAP backends: http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00982670-748c-2a10-3985-cdd42fb43...

As mentioned in the blog post - Gateway does not replace these "true" middleware solutions but rather compliments them and provides more of a "System to Consumer" connectivity layer than a "System to System".

I hope this helps in defining your requirements/use cases for Gateway.

Paul

[Shabarish_Nair · Accepted solution]

adding to the earlier question;

if we have a development that needs to consume services from SAP and Non SAP backends, I am assuming this will mean now a combination of G/W and PI. Some questions on this;

1. Does gateway only expose OData services? What about simple REST services?

2. PI at this point does not expose OData

3. So considering 1&2 - What happens in typical implementations where a combination of g/w and PI is used to expose backend functionality to mobile/desktop/portal apps?