0

I'd like to create a simple server service that can perform the following tasks:

Retrieve presence info for specified user(s). Send message to specified user.

From what i've been reading, and because i'm siting server side I could choose to use UCMA 5.0? But i'm seeing a lot of push of the new UCWA SDK and working with the UCWA rest services. Is there any particular reason why i would use UCWA server side rather than just the UCMA API? I read that UCWA will, in the future, be support by Microsoft for Cloud --- Any input and experiences shared on this would be great.

Thanks, mike

Mike
  • 780
  • 1
  • 5
  • 26

2 Answers2

2

UCWA will be at some point be supported in Office 365 indeed. So if you create an application with UCWA you can expect it will run in the next future on your S4B On-Prem as well as on Office 365. I have to say anyway this support for UCWA on 365 is already long awaited, and still there's no official announcement about availability date.

A very good reason to choose UCWA instead of UCMA, also in case of server automation, is the much simpler deployment of UCWA (UCMA deployment is quite tough).

UCMA must run on a Windows Server OS which joins the S4B farm basically (thus sits in your DMZ) UCWA can run on any device that 'speaks' HTTP. Your UCWA App can run, for instance, on a Raspberry Pi

I think this is a huge difference, for sure it is for your system administrator

Massimo Prota
  • 1,226
  • 7
  • 14
  • Makes sense thanks. As I understand UCWA client components (.js) communicate with the REST services server side. Where can you get documentation on the these services? Everything i see UCWA is nothing more than a javascript library which is not something i want to use on the server. – Mike Jun 23 '15 at 16:54
  • Not really correct what you say. UCWA is a set of REST APIs, which can be called from JS, but from any code that can do HTTP requests as well. You can use UCWA also in a console application. Please have a look at these links for more information: 1. [About UCWA](https://msdn.microsoft.com/EN-US/library/office/dn323676(v=office.16).aspx) 2. [Documentation](http://ucwa.skype.com/documentation/getting-started) – Massimo Prota Jul 09 '15 at 08:01
2

Old thread, but in my experience, writing server-side code with UCMA is somewhat easier than trying to use UCWA - and all that UCWA really is is a UCMA application sitting on your Lync/S4B server with a REST wrapper.

For the fairly simple use-case you've described, you could write the service as a client-endpoint UCMA application, which avoids the rather irritating Lync/S4B topology changes and deployment headaches that Massimo alludes to for a TrustedApplication. In this configuration, you are essentially just a third-party client, and you provide the credentials to sign into Lync/S4B as a specified user. Under this scenario, the only requirements are that the server running your application needs to be joined to your domain, run a 64-bit Windows OS, and have the UCMA runtime installed.

Some sort of API support for Skype for Business on Office365 is badly needed. There was some promises of a UCMA-like SDK for Office 365, but it has been more than six months with no hints of an actual release.

EricRRichards
  • 474
  • 7
  • 20