Welcome to MSDN Blogs Sign in | Join | Help

Developer Environment Upgrade & URL Change

We are upgrading the HealthVault Developer Environment hardware so that its topology will mirror that of the HealthVault Consumer Environment.  The new development servers which will show up at a new domain – healthvault-ppe.com instead of microsofthealthbeta.com.  To minimize disruptions to any in-development apps, both sets of servers will be online concurrently for six weeks.  We will copy all data from the old servers to the new servers once, on 1/23.

·         On 1/23, the new servers will come online

·         On 1/23, we will take a snapshot of all data on the current HealthVault Developer servers – application configurations, user accounts, test data

·         The snapshot will be copied to the new servers later in the day on 1/23

·         The old servers will stay online until 3/8/2008 but any data added or changed after 1/23 will not be copied over to the new servers

 

To start using the new servers, you will need to change your web.config file as follows:

Old URLs:

    <add key="ShellUrl" value="https://www.microsofthealthbeta.com/" />

    <add key="HealthServiceUrl" value="https://platform.microsofthealthbeta.com/platform/" />

New URLs:

    <add key="ShellUrl" value="https://account.healthvault-ppe.com/" />

    <add key="HealthServiceUrl" value="https://platform.healthvault-ppe.com/platform/" />

 

We highly recommend that you make the change in your web.config files on 1/23 or 1/24 so that all of your data gets copied to the new environment. The old servers will continue to work until 3/8 but any new data that you add there after 1/23 will not be copied to the new servers.

 

For those of you with custom firewall settings that enable your communication with the HealthVault Developer Environment, here are the IP addresses of the old and new servers:

·         Old Shell (www.microsofthealthbeta.com): 207.46.177.34

·         Old Platform (platform.microsofthealthbeta.com): 207.46.177.32

·         New Shell (account.healthvault-ppe.com): 207.46.204.185

·         New Platform (platform.healthvault-ppe.com): 207.46.204.186

 

The next SDK update (23 Jan 07) will include the new URLs in its sample applications' web.config files.

 

Please comment below or use the forum if you have any questions about this.  These changes only affect the Developer environment.  The Consumer environment’s URLs are not changing.

 

-Chris

Published Thursday, January 10, 2008 5:22 PM by Tremonte

Comments

Thursday, January 10, 2008 9:09 PM by Noticias externas

# Developer Environment Upgrade & URL Change

We are upgrading the HealthVault Developer Environment hardware so that its topology will mirror that

Thursday, January 24, 2008 10:42 PM by Tim Thein

# re: Developer Environment Upgrade & URL Change

I'm getting a server error after switching to the new URLs.  When I swith back, my web application runs fine.  I suspect that not everything was copied to the new environment.  For now, I will continue to use the old URLs, until someone else verifies this problem and fixes it.  My cert was issued to WildcatApp-378C1FF8-BF49-4170-A2AD-3B56675849CD.  Here are the details of the error:

System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.

Stack Trace:

[AuthenticationException: The remote certificate is invalid according to the validation procedure.]

  System.Net.TlsStream.EndWrite(IAsyncResult asyncResult) +232

  System.Net.PooledStream.EndWrite(IAsyncResult asyncResult) +12

  System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar) +140

[WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.]

  Microsoft.Health.EasyWebRequest.WaitForCompletion() +438

  Microsoft.Health.EasyWebRequest.Fetch(Uri url) +317

  Microsoft.Health.EasyWebRequest.Fetch(Uri url, IEasyWebResponseHandler customHandler) +49

  Microsoft.Health.HealthServiceRequest.ExecuteInternal() +123

  Microsoft.Health.HealthServiceRequest.Execute() +75

  Microsoft.Health.Authentication.Credential.MakeCreateTokenCall(String methodName, HealthServiceConnection connection, Collection`1 appIdCollection) +507

  Microsoft.Health.Authentication.Credential.MakeCreateTokenCall(String methodName, HealthServiceConnection connection, Guid appId) +98

  Microsoft.Health.Authentication.Credential.CreateAuthenticatedSessionToken(HealthServiceConnection connection, Guid appId) +465

  Microsoft.Health.Web.Authentication.WebApplicationCredential.AuthenticateKeySetPair(AuthSessionKeySetPairs keySetPairs, HealthServiceConnection connection, Guid applicationId) +412

  Microsoft.Health.Web.Authentication.WebApplicationCredential.AuthenticateKeySetPair(HealthServiceConnection connection, Guid applicationId) +58

  Microsoft.Health.Web.Authentication.WebApplicationCredential.Authenticate(HealthServiceConnection connection, Guid applicationId) +55

  Microsoft.Health.Web.Authentication.WebApplicationCredential.AuthenticateIfRequired(HealthServiceConnection connection, Guid applicationId) +162

  Microsoft.Health.AuthenticatedConnection.Authenticate() +79

  Microsoft.Health.Web.HealthServicePage.GetPersonInfo(String authToken) +131

  Microsoft.Health.Web.HealthServicePage.HandleTokenOnUrl() +143

  Microsoft.Health.Web.HealthServicePage.InitializeUserData(Boolean logOnRequired) +32

  Microsoft.Health.Web.HealthServicePage.OnPreLoad(EventArgs e) +46

  System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1323

--------------------------------------------------------------------------------

Version Information: Microsoft .NET Framework Version:2.0.50727.1433; ASP.NET Version:2.0.50727.1433

New Comments to this post are disabled
 
Page view tracker