on 11-18-2015 9:23 AM
Currently, we have already deployed an ABAP OO application that is exposing custom services directly from the ABAP stack. We are planning to migrate the service layer to Gateway and are now looking at what we need to arrange to get this running in both an embedded as well as central hub deployment.
In an embedded gateway scenario, I'll just be able to launch my ABAP code from the service implementation. But how does this work in a central hub deployment? Would I have to wrap all my methods into RFCs in order to call them from there?
Hello Jan,
I can see below options :
1. Register the service in GW Hub and deploy all the classes ( MPC & DPC ) in back-end system.
2. Register the service in GW Hub and also deploy all the classes ( MPC & DPC ) in GW Hub only by accessing the back-end logic through remote enabled function modules.
Below will help to decide the deployment options and provides detail information-> please check once.
Deployment Options - SAP Gateway Foundation (SAP_GWFND) - SAP Library
Embedded Versus Hub Deployment - SAP NetWeaver Gateway Master Guide - 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.
Thanks for helping Aswin
I think scenarion 1 would be our choice. Have gateway to service oData-requests, but have the actual logic in the back-end system.
Just a follow-up question. With "registering services", are you referring to RFC? Does that mean that the logic provided by the application should be wrapped in RFCs and exposed to the Gateway hub?
Thanks again!
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.