Skip to Content

Hello Folks,

Target Audience: Beginners in SAP Gateway.

Introduction:

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.

Book analogy.PNG

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.

gateway.PNG

Thus

  • 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.

book A.PNG

ch a.PNG

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.

book B.PNG

ch B.PNG

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.

book embeded.PNGembedded.PNG

Hope this helps in understanding the concept of Central Hub and Embedded deployment scenarios. 🙂

To report this post you need to login first.

16 Comments

You must be Logged on to comment or reply to a post.

  1. Jitendra Kansal

    Ekansh Saxena

    I don’t think we can have such a self explanatory blog other than yours. Very good write-up. Great job!

    You may also add few points with respect to SAP NW 7.4 as we have different component name over here.

    Regards,

    JK

    (0) 
  2. spandana N

    Hi Enkash,

       Thank’s for explaining the gateway process.

    Could you please help on the issue : while using mobile app: and trying the print to the LOCL printer , printing is not happening but spool is generating . ( Using mobile APP –  in SAP created the document and trying to print the document and in SAP has the Printer name LOCL which is the default printer. is there any config setting to get the print ?

    Thanks in advance.

    (0) 
  3. Prakash S

    Ekansh Saxena

    I have doubt regarding the second deployment option.

    • Its more like middle tier has publisher and and in same premise the printing press people have office to take request. 
    • But actual printing (data mining and processing) is still done in backend .
    • The only advantage here is that the whole backend printing press does not have to scale their infrastructure to communication level of Publisher.
    • Its more like a wrapper classes for call to actual BAPI’s , RFC’s etc.

    Let me know if you agree or disagree

    And update your blog with latest info for SAP NW 7.4 release. Now SAP is supplying SAP_GWFND. Means it will be good for future reader.

    SAP Gateway deployment options in a nutshell

    (0) 
    1. Ekansh Saxena Post author

      Hi Prakash,

      The second scenario has one more advantage, it supports ‘Multiple Origin Concept’ (MOC) in an easy way. This means that you can switch among multiple backend systems. Since you have developed the service at GW level and using BAPIs/RFCs just to get the data, you can add multiple backend instances given you have the same RFC in that system in contrast of having the DPC, MPC classes in all instances as in scenario 1.

      In terms of above analogy 🙂 , you can switch between raw material vendors without thinking of whether they have printing press or not. But in scenario 1, you have to consider only those vendors which have printing capability also.

      Yeah, I’ll also update the blog for 7.4.

      Regards,

      Ekansh

      (0) 
    1. Ekansh Saxena Post author

      Hi Fernando,

      Yes, the customer would prefer cheapest and quickest way but as a publisher I would like to have a model like scenario B. In that model, the publisher would not have to worry about the raw material vendor and it can switch among n number of vendors quickly. These multiple vendors may represent multiple SAP system/clients which serve the data. This is the concept of multiple origin. Getting Data from 2 ERP systems using Multi Origin & Multiple Origin Composition – SAP Gateway Foundation (SAP_GWFND) – SAP Library. 🙂

      Regards,

      Ekansh

      (0) 

Leave a Reply