UCMA vs UCWA - User Endpoint and Endpoint
I need to develop a chatbot with these properties:
Platform - Skype for Business On-Premise
Function - responds to user requests by browsing various knowledge bases (multiple platforms - databases, web interfaces, etc.)
Basic text conversation to start with and will gradually evolve to send attachments
No calls / videos, just chat
Will be hosted on an external VPN server
A simple sip will be created for the chat, which can be scanned by any user. I should be able to get this up to our IT department.
Limited development time
Scalability is an essential requirement, but the organization is pretty new to it, so they can be patient and let me make mistakes.
My research led me to these possible approaches:
-
SfB SDK - I rejected this approach because it requires the client to execute at all times and does not seem to be scalable
-
UCMA with Application Endpoint - did not reject this approach, but it looks like I will not do it because building Platforms applications seems tedious and requires me to make a lot of SfB server related IT requests
-
UCMA with User Endpoint - Excellent proximity to this . I've been experimenting with Tom Morgan (thinkstuff.co.uk) and it looks like I can start right away.
-
UCWA with application endpoint. Rejected this approach because UCWA (from my research) seems unsuitable for On-premise and the installation also seems time consuming.
-
UCWA with User Endpoint - Didn't reject this approach, but I'm not sure if the Web API method is really a good approach for the On-premise platform
I would like to ask how I do it, but it seems too vague.
What advice would you give is a good way to achieve this?
Also, someone might be patient enough to answer the disadvantages and advantages of each approach for my use case. I would like to make an informed decision and not reject any approach, simply because of a misunderstanding of the overhead
source to share
I ask in my organization and in other circles.
And since I am not getting quick answers, I will keep adding what I have learned. This way the person in the developer community will have a log of how I went with this.
UCWA is better suited for S4B online (versus parcel) and is typically used by people who are RESTful and have little knowledge of .NET development.
UCMA is apparently the WAY to go and for any bot server requirements, preferably with an application endpoint.
So for our development, we start with the UCMA user endpoint so that we can provide a base launch as version A in the meantime we will also contact the IT department and Lync administrators to create the application endpoints Once we get the same functionality as and we with the user endpoint will be copied to the application endpoint version
Keep browsing this space for further updates.
source to share