Mark Klein
asked on
Using Rules with WCF web service
I have a web service running with hard coded rules. See http://ArrowsDemo.loyaltyb uilders.co m for a working client site that uses the service.
I am in the process of changing the hard coded rules to rules coupled to the Microsoft WF rules engine. In fact, two of the apps on the demo site use that rules engine (see Next Best Offer or the Beacon app). Unfortunately I am getting unreliable results. When I access the service in debug mode from my local machine, the rules engine operates correctly. When I try to access the rules (which are stored in a sql server db as XML) from a web-based client such as ArrowsDemo, the results are inconsistent.
I have been careful about compilation and updating Service References from the applications. I believe the problem is connected to the targetObject of the rules, a C# file called Offers.cs residing in my VS solution for the web service. To build the rules properly, the Rules Editor needs to access the target Object during rule creation, and the service needs to apply the rules to the target object during rule execution.
My problem is exposing the targetObject on my remote IIS server. First I built rules running against the target Object on my local machine. But a web based app such as ArrowsDemo (or even my local sandbox C# app) should not access the target Object on my local machine. There is a place in the Rules Editor to specify the targetObject, but I can't get the syntax right to point this specification at the file and directory on the IIS server. That's where I need some help.
I am in the process of changing the hard coded rules to rules coupled to the Microsoft WF rules engine. In fact, two of the apps on the demo site use that rules engine (see Next Best Offer or the Beacon app). Unfortunately I am getting unreliable results. When I access the service in debug mode from my local machine, the rules engine operates correctly. When I try to access the rules (which are stored in a sql server db as XML) from a web-based client such as ArrowsDemo, the results are inconsistent.
I have been careful about compilation and updating Service References from the applications. I believe the problem is connected to the targetObject of the rules, a C# file called Offers.cs residing in my VS solution for the web service. To build the rules properly, the Rules Editor needs to access the target Object during rule creation, and the service needs to apply the rules to the target object during rule execution.
My problem is exposing the targetObject on my remote IIS server. First I built rules running against the target Object on my local machine. But a web based app such as ArrowsDemo (or even my local sandbox C# app) should not access the target Object on my local machine. There is a place in the Rules Editor to specify the targetObject, but I can't get the syntax right to point this specification at the file and directory on the IIS server. That's where I need some help.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER