After the release of K2 1370, there have been some small updates to the K2HostServer.config file for your SmartObject Services configuration.
The basics is pretty simple, KB1370 added the ability to change binding and binding configuration on the REST and WCF endpoints separately. Because the binding configuration also defines the authentication mechanism, this means that REST endpoints could use basicHttpBinding with Basic authentication, while the WCF endpoint uses wsHttpBinding with Windows authentication. It also allows us to run either one endpoint on HTTPS while the other is not.
In my previous post on the K2 Services I showed you how to create a static endpoint, this simplifies the URL and allows you to rename or update the SMO without the endpoint changing. The configuration sections shown in those posts are now outdated and won’t work anymore. Since the KB article describing the change doesn’t have all the parameters, this post is also a note-to-self.
With the release of K2 Services in the 1290 release, we’re able to get all sorts of data using RESTful services. These services provide output in 3 formats:
In the 1200 series, a few new web services are available out of the box. In this article I’ll tell you what they are for, how you can use them and give some insight on the technical details behind the services to make you understand them better.
There are two services new to K2 in the 1200 series:
- K2 Services
- K2 SmartObject Services
The K2 Services were first introduced in the KB001200 Update which contains a WS and WCF endpoint. A later release will bring REST-enabled endpoints for the K2 Services. The SmartObject Services are released in KB001230.