Print Page | Close Window

WCF and Persistence Manager

Printed From: IdeaBlade
Category: DevForce
Forum Name: DevForce Classic
Forum Discription: For .NET 2.0
URL: http://www.ideablade.com/forum/forum_posts.asp?TID=828
Printed Date: 11-Jun-2026 at 3:07am


Topic: WCF and Persistence Manager
Posted By: antalakas
Subject: WCF and Persistence Manager
Date Posted: 06-Jun-2008 at 1:59am
Hello,

Apart from the use of BOS, i had success in the past using a Persistence Manager with direct access to database (not using BOS), inside a WCF service hosted under IIS 6.

The service simply asks the db and returns results to the user.

Later i decided to port the WCF service to Windows 2008 and IIS 7. After this the service went mad. Every now and then returns irrelevant results.

Is it possible to use a standalone Persistence Manager in this scenario?

Thank you

Andreas


-------------
Andreas Ntalakas


Replies:
Posted By: kimj
Date Posted: 06-Jun-2008 at 10:22am

It sounds like you're not using a BOS right now, and a "standalone" Persistence Manager does not use WCF at all, so I'm not sure what your question is.  If your service is not the BOS yet it's gone "mad" after a port, how can we help?  If your service is the BOS or is talking to a BOS, then maybe we can help diagnose the problems you're seeing.

A "standalone" Persistence Manager - ie, a PM which does not communicate with a BOS, but instead directly accesses the database - does not use WCF.   With one exception, if the CommunicationsTechnology setting in your ibconfig is "WCF" the trace file logging will use WCF for communications between the app and the tracing service.  If this is causing problems, you can change the CommunicationsTechnology to the default of "Remoting". 


Print Page | Close Window