This will largely depend on the use and extent of implementation of your portal of course. I doubt anyone here will be able to make specific recommendations based on so little/vague information. Probably your best bet is to use the "Quick Sizer" tool from SAP. If you do not know where/how to use it, your BASIS folks should be able to direct you. Also, refer to the portal sizing documents that can be found on this site too. Some important things to keep in mind...
-will the portal be used for ESS only? (doubtful as others will see it's benefit as well and "want in on the action"...haha....It is best to clearly define your portal strategy up front)
-what exact services of ESS will be utilized? (using just basic personal info admin services versus a weekly timesheet will have a much different impace on load)
-Since you are doing ESS, will you be doing MSS as well? (one kinda leads to the other in many cases)
-will KM be implemented? (a big decision here....even if not implementing it now, you might want to plan for it later)
-what is the version of your backend source system? (versions of R/3 up till 4.7 will have some different requirments than ECC5.0 and up...for example, utlizing internal ITS on newer versions).
-what other applications/sources will utilize the portal? (see point#1 above)
-what will be the expected level of service? what agreements will be made with the business regarding uptime, maintenace, etc.
-how will access be handled? internal and/or external? This will have security implications what will also possibly have architecture considerations as well.
That's off the top of my head. Much more to consider I am sure. Good luck with it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.