Managing web service user for multiple client request

[RandyB]

Hello, 

we are planning to create a “master” repository of HOPEX (in an installation instance) to which multiple “clients” HOPEX installation instances (each having multiple users) will be connected to subscribe to content via webservices. Does it make sense to have one “Webservice-user” used for all of the clients, or a separate “Webservice-user” for each client, or should each user have a “webservice-user”? (We are concerned with considerations of conflicting, or coinciding requests from the various users of the various clients.)

Additional Question: Can any problems occur when there are multiple clients simultaneously pulling data from one source of HOPEX?

Thank you, 

Randy

[oguimard]

If you are talking of "system to system" type of interaction you can :

• Have only one technical user
• Have a technical user for each system (client) that connect to the API

One technical user account

If you are doing "query" only there is no risk.

If you are doing "update" then it is recommended that each system that is doing it's request has its own user account. Otherwise you can encountered issue when doing dispatch of the update.

Several technical user account

Is the most safe but you need to have enough license for it.