Jco generic user
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.