Hi all,
I’ve seen this issue posted elsewhere, but I cannot locate an actual solution/workaround for this.
I am re-writing some of our integration solutions in BTS 2004 to replace the older ‘non-glamorous’ solutions we currently have. Since we used BTS 2002 with MSMQ, I required the folks who wrote the publishing adapters to use the ActiveXMessageFormatter when dropping their data to the queues. Our current rollout process will include that I have BTS 2002 & 2004 co-exist in the same framework until all applications are upgraded..long story on another project.
I installed the MSMQ Adapter 2.0 for use with BTS 2004 as to not disturb the source adapters and also as I do not have control over the actual code that delivers the message…plus, since I still need some of them to write out transactions for BTS 2002, I can’t afford to change the current publishing adapters from the applications.
Now I have some new solutions in BTS 2004 that are expecting messages that are submitted to MSMQ using the ActiveXMessageFormatter format, BTS 2004 is choking on the message thanks to the BOM wrapped into the messages. I have no qualms about writing a pipeline component if need be, so I’m looking for a stable solution to convert the incoming data to a readable format that is supported by BTS 2004.
Any ideas?
Thanks,
-Rich