Wondering about what impact scaling up the number of BlueWorx users will have? The answer is it depends. Here's why:
Firstly, more users will make no difference to the BlueWorx mobile application when it's in normal use. That's because, except for a few online interactions with SAP or when you're syncing, BlueWorx is running separately from the SAP system. So the application performance is based on your device performance, the data volumes you have, etc, and not on the number of other BlueWorx users.
The move to BlueWorx may shift users away from SAP GUI, if they previously had access, or it might increase SAP access for BlueWorx net new users. If you're shifting users from SAP GUI then that will decrease the SAP dialog sessions used, and in its place there will be more intensive but far shorter bursts of stateless connectivity coming from the sync between the application and SAP.
Moving from desktop SAP GUI to BlueWorx mobility could also spread the connectivity load, because users sync when they need to based on the completion of a task. Conversely if connectivity is restricted to WiFi in certain areas, accessed periodically and with regularity, like rest breaks, then it might concentrate the load.
In any roll out out here' a few ideas that may help:
In conclusion there's are magic numbers around scaling BlueWorx users. The answers depend on too many variables. There are however things you can do to understand and mitigate the risk. If you have any questions on this topic then please come back with them on the forum, raise a support ticket or contact me.
Product Development Manager
+64 27 230 2678