Print Page | Close Window

Can BOS use an DevForce Entity Manager as the data source?

Printed From: IdeaBlade
Category: DevForce
Forum Name: DevForce 2010
Forum Discription: For .NET 4.0
URL: http://www.ideablade.com/forum/forum_posts.asp?TID=2231
Printed Date: 29-Jul-2026 at 11:17am


Topic: Can BOS use an DevForce Entity Manager as the data source?
Posted By: sgillbee
Subject: Can BOS use an DevForce Entity Manager as the data source?
Date Posted: 15-Oct-2010 at 11:00am

I'm researching the possibility of chaining multiple BOS's where the actual data source may exist several BOS hops away from the client.

Machine A: Custom Entity Framework DataContext (over non SQL data) wrapped by DevForce Entity Manager.
Machine A: BOS service layer allowing remote clients to connect to data source on Machine A.
Machine B: DevForce Entity Manager connecting to BOS on machine A.
Machine B: BOS service layer allowing remote clients to connect to data source on Machine B (which is really a proxied data source from machine A).
Machine C: DevFoce Entity Manager connecting to BOS on machine B.

Is this possible?

If so, it is possible to remove the need for an Entity Manager on Machine B? Can I directly connect the BOS on machine B with the BOS on machine A? That way the BOS on machine B doesn't need to know about the actual entity model but just acts as a pass=through.

Am I even asking the right questions? ;)


Replies:
Posted By: ting
Date Posted: 18-Oct-2010 at 3:54pm
If I understand your case correctly, yes, this is not a problem.  The DevForce BOS uses standard web protocols to communicate, so you can set up a proxy in front of it.  One approach is to use the Microsoft Application Request Router (ARR) extension for IIS and use that to pass requests through a DMZ.

I see that you're talking with one of our sales engineers tomorrow, so we can chat more about this then.

Posted By: sgillbee
Date Posted: 19-Oct-2010 at 7:49am
Actually, that's not quite what I'm asking.
 
I want to know if you can chain multiple BOS services together... so Client -> BOS 1 -> BOS 2 -> SQL
The entity model would exist at Client, BOS 1 and BOS 2 but only BOS 2 would have an actual SQL connection string... Client and BOS 1 would have <object server> config entries.
 
I'll clarify this use case when I talk with the SE later today.

Posted By: eniben
Date Posted: 18-Dec-2010 at 9:25am
Hi,

We didn't get an update on the meeting discussing this use-case.

Might we know the resolution for those of us interested in it?

Thank you.

Posted By: ting
Date Posted: 22-Dec-2010 at 1:55pm
Eniben - I believe they discussed an approach that did not involve chaining multiple BOS services together.  So far, we haven't seen a use case where chaining would be preferable to a simpler alternative.

Posted By: eniben
Date Posted: 24-Dec-2010 at 2:46am
Hmmm.

Might I ask what approach was agreed on?  Just curious.


Print Page | Close Window