Advice for Dummy/Null Port Correlation Needs - KeithP

27-Mar-07 02:37:10
I have the need for correlation functionality within my
orchestration.  I am able to get everything working correctly, using a
send port to send a message to a folder and initialize my correlation
set.  However this acts as more of a "dummy" port, since I have no use
for the message in a folder.  This is to be a production system, so I
would like to have a clean way to do this without messages piling up
somewhere.

In doing some research I have come across two sites:
- http://www.gotdotnet.com/Workspaces/Workspace.aspx?id=76a1f074-07b9-4180-bbbb-c0ae934802d5

- http://www.winterdom.com/weblog/PermaLink,guid,475.aspx

Does anyone have any experience with these?  I would like to avoid
using a third party tool if possible, so can anyone give me some tips
or information on how to create a Dummy Adapter/Port??

Thanks for any help.
button
 
 

Advice for Dummy/Null Port Correlation Needs - Benny Mathew

27-Mar-07 11:31:47
Hi Keith,
Just a thought, not sure if it will work (don't see why it shouldn't
either), try it out and let me know.
In the send pipeline of your dummy port use a custom pipeline component that
will consume the outgoing message and return a null, so that no message is
outputted into the folder.
Returning a null from eh pipeline will indicate to the port / adapter that
there is no message.

HTH
--
Regards
Benny Mathew
Seamless Integration Solutions
BizTalk Consulting, Development, Training
Bangalore, India

Website: http://www.seamless.in
Blog: http://GeeksWithBlogs.net/benny
BizTalk Usergroup: http://groups.google.co.in/group/b-bug
button
 

Advice for Dummy/Null Port Correlation Needs - yossi.dahanREMOV

28-Mar-07 10:36:07
You could do a few things -
you could send the message out and have a consuming pipeline component
you could send the message out and use the community null adapter.
you could see if you can initalise the correlation set on a receive shape
instead
or you could (I think) call a receive pipeline with xmldisassembler from
your orchestration (if you're using BTS 2006)

--
Yossi Dahan
http://www.sabratech.co.uk/blogs/yossidahan
button
 

Advice for Dummy/Null Port Correlation Needs - KeithP

06-Apr-07 11:57:06
Thanks so much for the replies, after a break I am returning to this
issue now.  I like the first idea Yossi listed where a pipline
component could be created to return null.  This sounds like a simple
process, however I am not sure how to go about making it happen.  I am
familiar with creating a send or receive pipeline, but not with
creating a custom pipeline component.  Can anybody help me out with
how this compnonet would be created?
button
 

Advice for Dummy/Null Port Correlation Needs - Jan Eliasen

09-Apr-07 09:09:41
I have experience with the /dev/null adapter - take a look at this:
http://blog.eliasen.dk/Default.aspx#a528ae49c-ece6-4a47-b661-e3340172bfcd

It worked just fine!

--
eliasen, representing himself and not the company he works for.

Private blog: http://blog.eliasen.dk

Private email: jan@eliasen.dk
button
 

Advice for Dummy/Null Port Correlation Needs - Tomas Restrepo [MVP]

09-Apr-07 10:57:26
Hi Keith,


I'm the author of the second one and I've had good results with it. My
preference for using an adapter for this sort of thing instead of a pipeline
component is that in the latter case, you still have to configure an adapter
at the end of the pipeline, which makes the overall settings far harder to
discover (example: you configure the file adapter, but then you have to look
very carefully at the pipeline settings to realize no messages will be
produced).


--
Tomas Restrepo
http://www.winterdom.com/weblog/
button
 

Advice for Dummy/Null Port Correlation Needs - Jan Eliasen

09-Apr-07 01:19:32
On Mon, 09 Apr 2007 15:09:41 +0200, Jan Eliasen

Whoops -
http://blog.eliasen.dk/PermaLink,guid,528ae49c-ece6-4a47-b661-e3340172bfcd.aspx
is better.

--
eliasen, representing himself and not the company he works for.

Private blog: http://blog.eliasen.dk

Private email: jan@eliasen.dk
button
 
BizTalk 2006 R2 EDI Reporting Question