ITS Sizing

[Former Member]

Hi experts,

I don't have any experience with ITS and I don't know how to solve this problem...

Hi have to set an architecture for connecting SAP Portal and R/3 4.6C ESS. I need to do this through ITS.

I'll have 32000 potential users and 2000 concurrent users and I don't know how to size the ITS. I tried with quicksizer but ITS doesn't appear...

I suppose I'll have to set multiple WGates connected to multiple AGates, but don't know anymore...

Could someone please tell me how many machines will I need for my scenario?

I was thinking in five machines.

Machine A with WGate

Machine B with WGate

Machine C with AGate

Machine D with AGate

Machine E with AGate.

Machines A & B (WGates) connected to all AGates.

Maybe I'm telling anything without sense... I've read different sap notes, forum post, sap help,... And don't know how to set this architecture!

Please tell me something, it's urgent...

Thanks a lot in advance.

Alberto.

[former_member316351 · Accepted solution]

Hello Alberto,

There is an ITS Tuning guide that can be found in the SAP Documentation:

http://help.sap.com/saphelp_nw04/helpdata/en/44/2a909d1a3a060de10000000a155369/frameset.htm

Your current thinking sounds okay, though it of course depend on other factors as well, such as the hardware (cpu, memory, etc) and the applications users will be requesting through the ITS.

You should also consider multiple agate processes on each of the AGate servers (MaxAgates). Please see note 720428 for assistance on this.

Edgar

[Former Member · Accepted solution]

Thanks Edgar.

I read that link before. I have also read the note, but... I think I'm not setting a correct architecture.

I was thinking in this type of machine (for productive environment)

2 CPU´s 2,4GHZ

3 GB RAM (1,5 GB x Server Node)

20 GB HDD

Could please someone tell me a correct sizing and settings for this ITS environment??

Thanks!

Alberto.

[Former Member · Accepted solution]

Hello Alberto

It sounds like a good size to start.

Maybe you can increase to 4GB RAM. This would allow you more flexibility for setting up several AGate processes.

(The WGate servers don't need that much memory.)

Everything really depends on the type of applications the gross of your users are calling.

some examples:

- ESS applications like "Personal Data", "Paystub" are usually quick applications.

An user doesn't spend more than 10-20 min. there, the R/3 transactions are quick and Database access is simple. This means processing times are short and memory consumption is low. ~timeout=15-20 min.

=> you can work with a smaller value for MaxWorkthreads and increase MaxSessions

- ESS applications like "Timesheet" or "Travel Expense" take longer and need more processing power. There is also more interaction with the Database.

=> you can still work with a smaller MaxWorkthreads and increase MaxSession, but you also have to increase the ~timeout=30-60 min. value for these services.

- webgui applications (e.g. MSS) need more memory and more processing power. Long running reports block Appserver processes and ITS Workthreads.

=> you need more Workthreads and cannot have so many MaxSessions. You might also have to adjust values like MaxRespSize and MaxCtxtSize.

If you have many users using simple ESS apps and only a few using very demanding webgui apps, you might want to think about creating two ITS instances and size the memory containers, maxworkthreads and maxsessions accordingly.

A good setup to start could be:

- 3 AGate Servers (4GB RAM). The productive ESS instance should have 3 AGate processes with 300 MaxSession and 20 MaxWorkthreads

=> that gives you 2700 (300 x 3 x 3) MaxSessions and 180 (20x3x3) MaxWorkthreads.

You need to have an ADM instance to monitor your environment and adapt to the amount of concurrent users. Also you need to consider certain peak usage times like Timesheet or Paystub (everybody does in on Fridays or everybody does it at the end of the month, etc.).

Another good 'just in case' strategy:

Since the WGate machines usually just need CPU Power and not much memory, you could always add AGate instances to those 2 machines too. If you don't need them you can always set the 'available'-flag in WGate configuration to 'no'.

best regards

Gerd

[Former Member · Accepted solution]

Thanks a lot Gerd, problem solved.

Best regards,

Alberto.