Unknown macro: {next_previous_link3}
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

The WSO2 IoTS client sends requests to the WSO2 IoTS server through a Proxy Server. The Windows WSO2 IoTS protocol constructs a URI that uses the host name by appending the domain of the email address to the subdomain, enterpriseenrollment for the each device request. Therefore, you can either purchase a domain name or create a DNS entry in the  http://enterpriseenrollment.<EMAIL_DOMAIN> format.

For example, discover the WSO2 IoT server by sending a request through: http://enterpriseenrollment.<EMAIL_DOMAIN>/EnrollmentServer/Discovery.svc.

As the WSO2 IoT server can not create Windows service endpoints it is advisable to use a proxy server between the device and the WSO2 IoT server. 

When using a proxy server, it redirects the device requests to the WSO2 IoT server endpoints. As the proxy directly contacts the WSO2 IoT server you need to configure the SSL Configuration to maintain a secure message flow.

Please refer the Windows Device Enrolment Process Message Flow to identify the message flow from a Windows mobile device to the WSO2 IoT server through the Proxy Server.

The following subsections will guide you on how to configure the server settings on WSO2 IoTS for Windows. We recommend that you NGINX as the proxy server but if required you can use the Apache2 HTTP Server as the Proxy Server.

You do not need to perform any additional steps to configure the Windows client.

  • No labels