Skip to Content

When we start a new project involving custom WebDynpro JAVA Applications, the following questions are asked:-

  1. What is SAP’s recommended SAPS and Memory required for my JAVA Server(Portal) to run the WD JAVA Applications?
  2. How much additional SAPS and memory is required for SAP R/3 Server?
  3. How much additional bandwidth required at datacenter?

 

Most likely we turn to SAP Quicksizer to find the answers and are let down since there is no “direct” template to size hardware for custom WebDynpro JAVA Applications. Then we ask around other basis experts, friends working in same area and finally decide on sizing based on our experience and not based on any scientific technique. However this can lead to problems incase the hardware we procured is not enough to run our applications.

 

In this blog I will try an address the first two questions. I will address question 3 in a seperate blog as network sizing is very generic topic.

 

SAP Quicksizer Template

In SAP Quicksizer there is a template provided under “SAP ERP > Human Capital Management > ESS / MSS Sizing” that can be used to size Custom WebDynpro JAVA Applications as well. All you need is

  • Familiarity with the SAP ESS Applications
  • Complete knowledge of your application

Here is how the template looks in Quicksizer(Check Table 2)

image

 

Explanation for Categories(Element)

Now that we have chosen the template, here is the explanation on how to use the elements of the same:

  • ESS LEAVE: This can be used for estimating light weight applications. The UI of custom application should be comparable to ESS LEAVE Application. The backend RFCs should be comparable to Leave Request RFCs PT_ARQ_REQUEST_*. I compare this to applications with simple UI calling 1-5 RFCs.
  • ESS CATS: This can be used for estimating medium weight applications. The UI of custom application should be comparable to ESS CATS Application. The backend RFCs should be comparable to ESS CATS RFCs HRXSS_CAT_WD_*. I compare this to applications with medium complex UI calling 6-10 RFCs.
  • ESS TRAVEL: This can be used for estimating heavy weight applications. The UI of custom application should be comparable to ESS TRAVEL Application. The backend RFCs should be comparable to Travel Management RFCs PTRA_WEB_*. I  compare this to applications with complex UI calling more than 10 RFCs

 

Explanation of Input Parameters:

Once we have categorized all our custom applications based on explanation above, lets look at the values to be specified in input parameters 

  • We are doing sizing for maximum load during a span of one hour. Considering that an user will execute all types of scenarios – light medium and heavy – in one hour duration, we assume the distribution as follows – Light Tansaction – 10 Minutes, Medium Transactions – 40 Minutes, Heavy Transactions – 10 minutes.
  • Assuming that it takes around 2 minutes for the users to execute and analyze a Light scenario, in 10 minutes the user can execute around 5 transactions
  • Assuming that it takes around 5 minutes for the users to execute and analyze a Medium scenario, in 40 minutes the user can execute around 8 transactions
  • Assuming that it takes around 10 minutes for the users to execute and analyze a Heavy scenario, in 10 minutes the user can execute 1 transaction
  • I assume that in each transaction user does 4 steps on an average

 

Analyzing the Result

Now that we have provided the input and calculated the result, its time to analyze the same. Here is how the result looks for the input parameters I have provided

 SAPS  Memory
 Sizing Result - SAPS  Sizing Result - Memory

Here are some key points:

  • Typically we use the throughput results as they are more accurate
  • In most cases the ABAP and JAVA App Servers are on two different physical servers and hence the SAPS/Memory should be used as shown for the Individual App Servers
  • Incase you already have the ABAP and JAVA App Servers running, you should choose the “System Extension” radio button as shown in the image above
  • This sizing is for running pure WebDynpro Applications. However if you run these applications and portal on same WAS, you atleast need to Size Portal Server by using template SAP Netweaver > SAP Netweaver > Portal & KMC for Active Users

 

Once you analyzed the results you can provide the numbers to your hardware vendor who will recommend the appropriate hardware to you.

 

I hope you will find this blog helpful in sizing hardware for your custom WD Java  applications . However since this blog is based on my experience, I would end this blog with following disclaimer

 

Disclaimer 

  • In this blog I have shared my experience and technique for sizing. You are free NOT to use this at all. However in that case I would really feel obliged if you can share your sizing  technique so that all of us can benefit and learn more on this topic
  • The explanation of categories provided above is based on my  understanding of ESS applications. You may use the template  as per your understanding
  • All the numbers provided in the Input parameters above suit my  applications. You have to change these depending on your applications.
To report this post you need to login first.

1 Comment

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

  1. Eneko Jon Bilbao
    Great blog Shubham! Useful and well written. I agree with your approach and this is the basis for which I have estimated past java webdynpro sizing projects myself. Thanks for sharing with the community.
    (0) 

Leave a Reply