SAP Gateway Embedded and Hub running at the same time

[Cristian]

Dear all,

Given that SAP_GWFND component is installed out of the box starting from 7.4 in sap business suites and sap gateway standalone hubs, would it be technically possible, in an already existing hub architecture with the SAP Gateway Hub and back end systems in 7.4, to enable the Gateway service in a backend system and, therefore, having ODATA services running in Hub mode and other scenarios running in Embedded mode? If so, is that recommended at all?

Many thanks in advance,

C.

[pjcools · Accepted solution]

Hi Charles

As already detailed by others the preferred approach is for all users to come through the SAP Gateway even though it is technically possible to have both in existence. BUT and it is a big but, always depends on the business requirements AND also on the future strategy (e.g. migrating to cloud technologies). From an architecture point of view it is also much simpler - simpler to maintain, simpler to understand and simpler to support. SAP Gateway is normally the preferred approach because of the security issues around users coming in directly to the SAP backend environments (ERP, SRM, CRM etc). As there are no business transactions or logic in SAP Gateway this is normally a better system for business users to hit - low impact rather than users having direct access to SAP ERP systems with full business logic and detailed transactions. SAP Gateway in front of ERP puts that additional security layer in place. But having said this, the SAP Gateway being in place needs to add value - especially now with SAP Cloud Platform and OData provisioning performing a similar function. On some recent client projects I have been involved in we did decide to activate OData services directly from the ERP system into OData provisioning rather than going through the SAP Gateway - mainly due to this being on a really old version and no continued maintenance in place.

If you did want to go embedded the question would come as to why then do you need the Gateway system and like Andre covered would depend on whether you wanted to process workflow items from multiple backends (although recently this can now be achieved through different OData services - other than TASKPROCESSING) but again if all OData services are currently established in the SAP Gateway then makes sense to continue this.

Lastly, decisions around SAP Fiori architectures should be based on a full set of business requirements and future strategies but the main thing is that each option is detailed and the pros and cons of each highlighted so that an informed decision can be made. SAP recently updated their SAP Fiori Deployment Options and System Landscape Recommendations paper so take a look at this as well - may provide you with more information.

https://www.sap.com/documents/2018/02/f0148939-f27c-0010-82c7-eda71af511fa.html

Good Luck! These are normally stressful decisions and does take a bit of time!! 🙂

Thanks

Phil Cooley

[Cristian · Accepted solution]

Many thanks for such a great explanation.

C.

[Andre_Fischer]

• If you don't use the features of the hub like getting workflow items from several backend and consume them using MyInbox
• If you want to save the hardware for a separate hub server
• If you have several backend but the users of these systems do belong to distinct groups
• Your backend is using an expensive HA solution and you do not want to setup a separate HA solution for the hub.

Regards,

Andre

If one or more answers have answered your question please click on "✓ Accept"

[Cristian]

Many thanks for your response.

C.

[Andre_Fischer]

Jakob is right that there will be no issues but significant gain of performance due to the embedded deployment will only be available for systems that are based on SAP NetWeaver 750 SP04 or later.

https://blogs.sap.com/2016/10/10/take-advantage-performance-improvements-sap-gateway-sap-netweaver-7...

If one or more answers have answered your question please click on "✓ Accept"

[Cristian]

Many thanks Andre for your response.

What is your view then for landscapes not yet in 7.5 SP04? Any use case for not going through the Gateway Hub?

Thanks.

Regard,

C.

[UxKjaer]

Hi Andre,

Thanks you for pointing towards the notes. We tried the co deployed at a client and didn't get any significant performance gains even though the app was using a lot of calls. I understand it as if there is a large data transfer or metadata file then the co deployed really pays off.

Just clarifying is it the recommendation now a days to use the co deployed setup in a hub scenario?

[UxKjaer]

There are no issues with enabling the gateway as embedded as well. You can also leverage the co-deployed functionality this way. Search the oss for another on that.

However I don't really understand why you would run on the embedded as well. Why not just through run everything through the Gateway. Then you can handle network security as well.

[Cristian]

Jakob many thanks for your prompt response. Very much appreciated.

If we wanted to expose our service to the external world with SAP API Management (security would be managed here), which architecture would you go for?

Many thanks!

C.

[Andre_Fischer]

If one or more answers have answered your question please click on "✓ Accept"