Issues Setting up BOS on IIS

 

An EntityServer is created for each data source extension used.  You use a data source extension when you construct an EntityManager - by default the extension is null (none).   I see that we've unfortunately omitted the discussion of data source keys and extensions from our current documentation, but in brief an extension allows you to target an alternate set of EdmKeys at runtime; DevForce uses both the data source key name associated with each Entity and the data source extension provided with the EntityManager to resolve the actual EdmKey used to access the data source.

 

2) I am not sure what EntityService*.svc is. What does the * represent. I assume Data Extension Name. Where is that found and how can I configure that. The /IIS Files has samples but they are not clear at least to me. Is the final file name supposed to be EntityServiceMYAPP.svc or just MYAPP.svc?

 

You should always just have one EntityService.svc file - the EntityService is kind of a gateway to the EntityServers.  You'll need an EntityServer_XXX.svc for each of the data source extensions used.  If you don't use any extensions, then only EntityServer.svc is needed.  If you use an extension of "Dev" for example, then you'll need an EntityServer_Dev.svc.

 

3) Unable to connect to http://domain.com/EntityService

 

Since you're hosting the BOS in IIS, the client URL should be resolved to something like http://domain.com/EntityService.svc or http://domain.com/MyVRoot/EntityService.svc.  The URL is formed using information from the client's <objectServer> element in the ideaBlade.v4 configuration section.  The client log file should also indicate how it determined that address - i.e., using the ideaBlade configuration or serviceModel configuration.

 

 

 

 

Here's an example:

        <objectServer isDistributed="true"

            remoteBaseURL="http://localhost"

            serverPort="80"
            serviceName="MyApp/EntityService.svc" 

        />

Also, are you using https or is that a typo?  I would first try getting standard http communications working without adding SSL to the mix.   If using SSL, you may also need to use a client-side serviceModel configuration to ensure communications are configured correctly.  But again, first try the out-of-the-box configuration to get these other problems worked out.