Book Analogy to understand Central Hub and Embedded Scenario
Target Audience: Beginners in SAP Gateway.
Here I am going to explain the deployment scenario of SAP gateway with relating it to the books.
There are 4 objects here: customer, publisher, printer and papers(or raw materials). Suppose the customer wants 50 copies of some novel ‘Novel ABC’. Here is the process:
- The customer requests this to Publisher of the novel.
- The publisher checks who is the printer for this novel and asks the printer to print 50 copies.
- The printer checks for the raw material and if the raw material is not available, it asks for the raw material.
- As soon as the printer receives the papers(or raw materials), it prints the copies and send it to the publisher.
- The publisher receives the copies and send the requested copies to the customer.
Relate it with Gateway scenarios:
Lets relate the above scenario with gateway.
|Books Analogy||Customer||Publisher||Printer||Papers (Raw Material)|
|Gateway Scenarios||Browser||Front End Components||Back-End Components||Data (ECC)|
The process is:
- The browser requests it to the front end system. (Where service is registered)
- The front end checks that the requested service is registered against which system. (checks the back-end system which registered the service and where all the classes are presented)
- The back-end receives the request, checks and asks for the data. (control comes to the classes of the service and asks for the data)
- When the back-end gets the data, it sends the data back to the front-end system.
- The front end system sends the response to the browser.
- Creating the service = Printing the book
- Registering the service = Publishing the book
- Getting the data or calling the FM = getting the papers
For deployment options, we can check the SAP help page Embedded Versus Hub Deployment – SAP NetWeaver Gateway Master Guide – SAP Library
Scenario A: Central Hub Deployment — Development in SAP Business Suite Backend System
When Printing Press has the papers or raw materials
This approach suggests that the printing press has papers i.e. the backend system has the classes/methods of created service as well as data.
This means that Publishing house does not have the capability of printing the book i.e. the gateway service is developed at the backend system and only registered at front end hub system.
So we will have front end components(GW_CORE, IW_FND) at the Hub system and backend system will have IW_BEP copmonents.
Scenario B: Central Hub Deployment — Development in SAP NetWeaver Gateway System
When Publishing House also prints the book
This approach suggests that the Publishing House also has Printing Press but not the papers i.e. the front end system has the classes/methods of created service but not the data.
This means that Publishing house does have the capability of printing the book i.e. the gateway service is developed at the front end system and only data is fetched from ECC system.
So we will have front end components as well as backend components (GW_CORE, IW_FND & IW_BEP) at the Hub system.
Scenario C: Embedded Deployment — Development in SAP Business Suite Backend System
When publishing house prints the book as well as has the papers
This approach suggests that the Publishing House, Printing Press as well as papers or raw materials are at one place i.e. everything is in one system.
This means that Publishing house does have the capability of printing the book and also have the papers i.e. the gateway service is developed at the backend system, registered at the same system and data is also fetched from same system.
So we will have front end components as well as backend components (GW_CORE, IW_FND & IW_BEP) at the backend system.
Hope this helps in understanding the concept of Central Hub and Embedded deployment scenarios. 🙂