WCF-Oracle and Oracle Advanced Queing (AQ) – tips

If you use the WCF-Oracle adapter to communicate with Oracle Advanced Queing you are in for a treat. We followed the steps suggested in a very good MSDN post. There are however some caveats;

  • Username is case sensitive
  • The generated schemas have a reference to the package, and Database schema, make sure this is consistent throughout the environments
  • The generated schemas are slightly different then what the WCF-Oracle adapter expects in some cases (more on that below)
  • Use a count procedure to determine if there are messages

Generated the schemas is done by following the standard ‘Add Generated items’ wizard so that should not be hard to do. When you generate schemas for Oracle they will typically have the targetnamespace:

/Package/http://Microsoft.LobServices.OracleDB/2007/03/<DATABASESCHEMA>/Package/<PACKAGENAME>

Where the <DATABASESCHEMA> could be something like ‘DBOWNER’ and the packagename could be whatever.

When you implement this everything seems ok, until you start testing, receiving messages won’t work (not supported exception stating that the action is invalid;

image

This is because the WCF-Oracle adapter expects a different targetnamespace!!

See the namespace below with the subtile change from ‘Package’ to ‘PollingPackage’ ;

 

http://Microsoft.LobServices.OracleDB/2007/03/<DATABASESCHEMA>/PollingPackage/<PACKAGENAME>

  • I therefore strongly recommend to generate a separate schema for each receiving procedure (this allows you to alter the targetnamespace), as it works fine for non receiving procedures which can be generated into a single schema.

 

Another thing that will get in the way is that the generated schema is somehow now in lign with the message returned;

The message structure is pretty logical;

clip_image001

The generated items wizard however generates somewhat different;

clip_image002

  • Take this into account when receiving the message in my case I had to extract the message body out of an envelope so I used the WCF feature to extract this body out using XPath

/*[local-name()='DEQUEUE']/*[local-name()='DEQUEUEResult']

 

To be sure to only receive messages when there are messages on the queue, define a stored procedures that checks for messages.

The adapter can then be configured like this:

Property

Configuration

PolledDataAvailable Statement

SELECT <DATABASESCHEMA>.<PACKAGE>.<PROCEDURE> FROM DUAL

PollingAction

http://Microsoft.LobServices.OracleDB/2007/03/<DATABASESCHEMA>/PollingPackage/<PACKAGENAME>/<PROCEDURE>

PollingStatement

<ns0:DEQUEUE xmlns:ns0=/Package/">http://Microsoft.LobServices.OracleDB/2007/03/<DATABASESCHEMA>//Package/">Package/Package/">/<PROCEDURE> />

 

This should get you right on track!

 

Sander

Comments

Post a Comment

Popular posts from this blog

Azure implementation guidelines

In My post ‘ Service Bus Management ’ I pointed out a way of implementing a DTAP strategy for managing the Service Bus environment. There’s now a great post available from Microsoft which goes into more detail about other aspects of managing the Azure subscriptions and other artefacts which is quite useful when setting up your Azure environments. Follow this link to the ‘Azure Implementation Guidelines’ HTH, Sander
Read more

Focus and innovation - recap of the last 2 years

It's been a long time since my last post. Hereby a partial explanation for that, with the note that this blog will remain active for the purpose of being a resource for historical references. My IT career started with programming, and adventures within holland, as well as overseas. When I realised programming is something you can specify, I figured that providing added value is crucial for a long term career and decided to focus on process centric roles. I started with webservice integration and eventually from that to process integration using BizTalk. The great feeling when discussing high level processes and implementing solutions within days, even highly scalable and interfacing with LOB systems is great. After several years of implementing solutions like these, I started questioning if all of this work was justified by the business case, if the solution was actually contributing, if the choices had been valid. In other words, I needed to understand the choices made. When...
Read more

BizTalk Pub/sub vs Topics based routing–discussion

My colleagues and I had a brief discussion about the subject ‘Topics’ and what it brings… Do you all agree/disagree with the following statement: topic-based pub-sub messaging doesn’t really exist in BizTalk “In my opinion; I disagree, as BizTalk offers the following 'out-of-the-box' • Message Routing (f.e build in context properties like message type, trading partner, operation etc) • Content Routing (f.e. promoted properties, message inspection in orchestrations/pipelines icw orchestration logic)” My colleague Rene Brauwers Here my 2 cents…. I agree that it exists...however the current offerings in BizTalk are tightly coupled, making the usage far from perfect. When doing content based routing on custom fields (promoted properties), you will be making the solution message-coupled; Your custom message property schema is deployed, and the message filter on these fields have a direct relationship with this property schema. Making any change to this schema will g...
Read more