Hi,

Using MQseries Adapter for BizTalk Server 2006, we expirience the problem
that the Adapter places the messages as being of type "string" within the
MQseries queue. This leads to the problem that a recoding occurs as the
receiving system is of a different platform than the BizTalk machine.

How do we have to set up the message context in order to define the message
as being binary without any recoding taking place?

Thanks for any assistance.

Sincerely

Joerg Fischer

[ Post a follow-up to this message ]

Are you using an orchestration?  What is the type of the logical
(orchestration) port set to?

Scott Colestock
www.traceofthought.net

<Joerg Fischer> wrote in message
news:eBT1FZI5FHA.1864@TK2MSFTNGP12.phx.gbl...
> Hi,
>
> Using MQseries Adapter for BizTalk Server 2006, we expirience the problem
> that the Adapter places the messages as being of type "string" within the
> MQseries queue. This leads to the problem that a recoding occurs as the
> receiving system is of a different platform than the BizTalk machine.
>
> How do we have to set up the message context in order to define the
> message as being binary without any recoding taking place?
>
> Thanks for any assistance.
>
> Sincerely
>
> Joerg Fischer
>
>

[ Post a follow-up to this message ]

Hi,

The Port is a "Specify Later" port which sends an Multipart Message
consisting of an XML part and a binary part. Within our pipeline, we use an
ZIP component to build an archive consisting of the two message parts. This
all is sure to work with the FILE transport but fails with MQseries because
of the recoding.

I assume we have to set a specific combination of context properties on the
outgoing message; however, this is not clearly documented.

Sincerely

Joerg Fischer

"Scott Colestock" <scolestock@community.nospam> schrieb im Newsbeitrag
news:OLnKXMK5FHA.3540@TK2MSFTNGP10.phx.gbl...
> Are you using an orchestration?  What is the type of the logical
> (orchestration) port set to?
>
> Scott Colestock
> www.traceofthought.net
>
> <Joerg Fischer> wrote in message
> news:eBT1FZI5FHA.1864@TK2MSFTNGP12.phx.gbl... 
>
>

[ Post a follow-up to this message ]

But what is the message type for the port ?

<Joerg Fischer> wrote in message
news:uyfBZOf5FHA.2816@tk2msftngp13.phx.gbl...
> Hi,
>
> The Port is a "Specify Later" port which sends an Multipart Message
> consisting of an XML part and a binary part. Within our pipeline, we use
> an ZIP component to build an archive consisting of the two message parts.
> This all is sure to work with the FILE transport but fails with MQseries
> because of the recoding.
>
> I assume we have to set a specific combination of context properties on
> the outgoing message; however, this is not clearly documented.
>
> Sincerely
>
> Joerg Fischer
>
> "Scott Colestock" <scolestock@community.nospam> schrieb im Newsbeitrag
> news:OLnKXMK5FHA.3540@TK2MSFTNGP10.phx.gbl... 
>
>

[ Post a follow-up to this message ]

Hi,

The messagetype is a custom .NET class with a corresponding Serializer
specified for the Orchestration. It is sure to insert correct binary data to
the MessageBox as things work perfect when using FILE based communication.

Sincerely

Joerg Fischer


"Scott Colestock" <scolestock@community.nospam> schrieb im Newsbeitrag
news:OVaGhbi5FHA.4012@TK2MSFTNGP14.phx.gbl...
> But what is the message type for the port ?
>
> <Joerg Fischer> wrote in message
> news:uyfBZOf5FHA.2816@tk2msftngp13.phx.gbl... 
>
>

[ Post a follow-up to this message ]