Skip to Content

Enterprise Widgets in Client/Server Environment


This Blog mainly explains on how the Enterprise widgets can consume service from the SAP Widget Foundation  which has been installed at the Remote Location.


Scenario :


The System A acts as a (Server) where the SAP widget Foundation has been configured. Then the service provider is created and configured with the SAP R/3 system. Now the other client system(b,c,d) should able to access the system A(server) with  the Server IP in order to consume their services. The  scenario is been represented in the form of a diagram below.


Steps to follow ( Server Side) :


  • First navigate to the installation folder .Open the Middleware.XML file in any text editor for modification (Example : Notepad).



  •  By default the HOST name is assigned to “localhost” with default Port Number : 7531


  • Replace the Host with the Server IP address(System A) as shown below.(use ipconfig command in DOS prompt to know your IP).By this we are configuring the Server IP.Port numbers can also be changed.Save all the changes and start your Widget Foundation.


Test the Following :

Right click on the SAP Widget Foundation ICON




Choose configuration option  in the context menu. Then replace the default HOST name and Port number with the modified one.(as mentioned in middleware.xml file)



If this works fine. Then try with the same URL from the client system(B) for accessing the server, which will again display the same page as above displayed.


In order to test the above scenario let us create a “Hello World” widget through the Wizard.


Steps in creating & Executing the Hello widget from a client/remote system.


  1. Create a Hello widget from the wizard.




  2.  Choose hello widget template and click finish.




 3. After the widget cretaion. Navigate to the Package explorer

    (left pane) and double click on the RFCRequest.js file in order

    to modify the URL settings.




  4 .  By default the URL will have the localhost or default IP. 




Now change those variable with the modified IP (Server IP) with the corresponding Port Number. (as mentioned in middleware.xml file)



Save the changes and execute the widget from the client system.


   5.   Provide service provider name of the Server system.This can

         be done through preference menu.




 Please provide the correct Service provider name(Server System) in the Preference menu.



Note : The above scenario may fail due to firewall or proxy setttings in the network.

To report this post you need to login first.


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

  1. Former Member
    Few thoughts:
    Can the service foundation handle multiple concurrent requests. It seems to freeze with multiple (long) SAP calls.

    Can you secure the configuration page to avoid multiple people from changing passwords etc?

    1. Former Member Post author

      I think it can handle multiple calls..

      Since this config file is placed in the server, we can provide normal file access for the protection.

      thanks for the comment..

      jaideep srinivasan


Leave a Reply