on 10-13-2008 2:11 PM
Hi,
I need to use a generic user both for application data and metadata Jco destinations.(Because we need to avoid creating the users on R/3.)
This is for a web dynpro application accessing R/3 with an avg of 400 concurrent logins.
What are the considerations to be taken care in a production environment given the above requirements.
Many Thanks.
Hi,
Increase the pool size.
Regards
Ayyapparaj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Can you explain in little detail.
few sepcific question I have are like
- Can 400 users connect to r/3 concurrently with generic user id.How is it controlled.(will r/3 have any restrictions)
-How will it impact performance.How can performance be improved with pool size etc.
-Will using sso or generic user have the same performance levels..?? .. ..and using sso is just for application specific reason...
Many Thanks,
Ashok
-
Ashok,
check this document
Thanks
Bala Duvvuri
Hi,
Document is very useful. But I am not getting specific answer to my question...
Scenarion is : Using a generic user id to configure Jco for application data ...
Load : 400 concurrent users...
What is the difference between accesing r/3 using sso and accesing r/3 using generic user 400 times concurrently in terms of performance , efficiency etc...
Is it suggested given that I my appliocation can work with a generic user...
Any ideas?
Ashok
User | Count |
---|---|
81 | |
24 | |
11 | |
9 | |
7 | |
5 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.