Monitoring and Maintaining Your Application
Congratulations on getting that application out there! Whether you have created a client or a web application, it’s very important to monitor its health.
You should log all the failed calls to the HealthVault web service. For additional debugging, the HealthVault SDK provides a tracing mechanism that you can use to log all the request responses. The mechanics of this are detailed at http://msdn.microsoft.com/en-us/library/ff803626.aspx. The HealthVault team monitors their development forums, available at http://www.msdn.com/healthvault, and you can use them to report any anomalies or failures in the service.
Each release of the HealthVault .NET SDK is supported for two years, and the team frequently adds enhancements and bug fixes to the newer releases. SDKs and libraries available in other language—Java, Python, etc.—are also updated by the community. As part of maintaining your application, you should make sure you monitor the underlying libraries so that you can upgrade your service to use the most robust offerings.
Another important aspect of maintaining a HealthVault application is to maintain its security artifacts, such as the application certificate and user tokens. HealthVault uses X509 certificates to authenticate web applications; you should make sure that the certificates you use for your application have the appropriate validity to function for a long time. HealthVault uses long-lived user tokens for client applications, and ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access