How we solved few issues we had while deploying the reference implementation

Dec 23, 2008 at 1:39 PM
Hello, 
    we buillt version 18637 and here are few hints on how we got around some bumps that we found on the road.
I hope that you might benefit from it ( and save time! ). Giuseppe

Q:  My reference solution compiles and installs but I cannot browse to the services. 

 

AIn the directory….. \Version1\WindowsServices\XDSRegistryServiceHost  edit App.config

Browse for the following content and make sure that the part in red is commented out.

If not insert   <!--  and --> before and after the block .

        <behaviors>
            <serviceBehaviors>
                <behavior name="XDSRegistry_ServiceBehavior" >

                    <serviceDebug includeExceptionDetailInFaults="false" />

                    <!--<serviceMetadata httpsGetEnabled="true" />-->

                    <!-- HTTP ONLY -->
                    <serviceMetadata httpGetEnabled="true" httpsGetEnabled="true" />
                    <!-- HTTP ONLY -->

                   
<!--                            

          <serviceCredentials>

<serviceCertificate findValue="824aced4b7600d8547eceec02c3c86ea6d23cb2f"

              storeLocation="LocalMachine"

        storeName="Root"

        x509FindType="FindByThumbprint" />

              </serviceCredentials>

          -->
                </behavior>

            </serviceBehaviors>

        </behaviors>



Also make sure that IIS is stopped when using the services.

 You can achieve that with  typing the following command in the command line  : 

                                iisreset  /stop

 

 

Database connection

 

If using SQLexpress the connection string for the database is similar to this :  MYMACHINE\SQLEXPRESS

If you are using SQL server is : MYMACHINE.
If you are not sure open the

make sure the app.config files have the correct connection setting.

 

Use the Microsoft SQL – Surface Area Configuration  and  make sure that you allow for remote connections

 

 

 
Q: When I use the TestHarness the Query to the registry fails.

A:  Make sure the the Registry server and the clients configurations are matching.

The services offered by the Registry can be used by the Repository or Document Consumer.

 

In the App.config for the Registry make sure that the  bindings look like the following : ( note the messge encoding “text” ).

 

<binding name="XDSRegistry_HTTP" closeTimeout="00:10:00"

        openTimeout="00:10:00" receiveTimeout="00:10:00" sendTimeout="00:10:00"

        bypassProxyOnLocal="false" hostNameComparisonMode="StrongWildcard"

        maxBufferPoolSize="524288" maxReceivedMessageSize="65536"

        messageEncoding="Text" textEncoding="utf-8" useDefaultWebProxy="true"

        allowCookies="false">

 

 

in the repository App.config  AND test harness  App.config the matching endpoint as a client should look like the following :

  <binding name="XDSRegistry_HTTP_Endpoint" closeTimeout="00:01:00"

     openTimeout="00:01:00" receiveTimeout="00:10:00" sendTimeout="00:01:00"

     bypassProxyOnLocal="false" transactionFlow="false" hostNameComparisonMode="StrongWildcard"

     maxBufferPoolSize="524288" maxReceivedMessageSize="65536" messageEncoding="Text"

     textEncoding="utf-8" useDefaultWebProxy="true" allowCookies="false">

     <readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384"

      maxBytesPerRead="4096" maxNameTableCharCount="16384" />

     <reliableSession ordered="true" inactivityTimeout="00:10:00"

      enabled="false" />

     <security mode="None">

One last hint.  When you deployed my solution I had to copy everything in a subdir closer to the root to shorten the filepath length.
The install script was failing because of it . My path looks like c:\IHE-18637\Version1\..and it works fine now.
 

Hope this helps.