Hi Bassant,
Based on our emails and other HH threads, you seem to have an unclear picture of how things fit together.
MDWS is web services for talking to your VistA system. It communicates via RPC (much like CPRS) to VistA. Want to write an app that pulls meds out of VistA? If you were using the RPC Broker, you'd need to figure out which RPCs to call, the arguments, how to parse the results, how to connect and login to VistA, etc. etc. MDWS aims to dramatically simplify all that by giving you meaningful APIs to work with. Need to connect to VistA? Well, that's the "connect" web service. Need to authenticate your user? That's the "login" service. Need to pick a patient? "match" and "select" services. Get meds... you guess it: the getAllMeds service.
The demo project I linked to 6/5/2014 is just a simple C# client application of MDWS. It's purpose was to illustrate everything I just highlighted above, the simple session management, a UI to show how one might display the data, etc. Since the demo project is a client of MDWS, it needs to know *where* MDWS is hosted so that it can construct the correct web service requests. As you saw, "
mdws.vistaehr.com" does not exist any more. I don't know of any publicly hosted MDWS installations for you to bang against. However, you also seem to be standing up your own MDWS server so why not point the demo there?
Good luck!