You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Gert Vanthienen <ge...@skynet.be> on 2007/06/01 11:58:16 UTC
Re: Simple JBI App
rb2399,
Do you want to forward the contents of the messages all the way through your
message flow (as in the Message History pattern) because you need it further
down the road for your processing or do you need it for logging/auditing
purposes?
If you need the contents of the previous messages for processing, I don't
think that there is an out of the box component that does so. Feel free to
add it to the servicemix-eip component and let us know if you need any help
implementing it...
In the latter case, you can write your own Auditor implementation and plug
it into the container. Starting with version 3.2 (which you'll have to
build from source yourself for now), there is an additional correlation ID
that is sent with every message exchange to link subsequent messages
together. This allows you to write an Auditor that logs the entire message
history (I've recently done something similar, it works really well)
Gert
rb2399 wrote:
>
> Hi Gert,
> thanks for your reply.On a sidenote I wanted to know if we have a "out of
> the box" component that implements the "Message History" pattern from EIP.
> If not,what is the best way to implement the same ?
> Is it using wiretap ?
>
> Thanks,
> rb2399
>
>
> rb2399 wrote:
>>
>> Hi All,
>> I am new to JBI and SM world.I am trying to run a sample example like:
>> HTTP BC --> SE1 (Just appends the payload received from HTTP BC) -- >SE 2
>> (receives the msg & displays it)
>>
>> I've defined SE 1 as in-only & so is SE2 also.I'm having problems with
>> exception "ould not find route for exchange" when SM routes it from SE1
>> to SE2. I've followed the hello world SE example for defining
>> xbean.xml.Do I need to update the servicemix.xml also with
>> activationspec.
>>
>> Sorry if I've repeated the question,but I'm totally lost here.
>>
>> Thanks in advance,
>> rb2399
>>
>
>
--
View this message in context: http://www.nabble.com/Simple-JBI-App-tf3839777s12049.html#a10910007
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: Simple JBI App
Posted by Gert Vanthienen <ge...@skynet.be>.
Arif,
I'm unsure what you mean with the jsessionid question. The overall goal of
the correlation ID is to help you determine which MessageExchanges happen
together in a single message flow.
You can get this correlation ID using
MessageExchange.getProperty(JbiConstants.CORRELATION_ID). This should allow
you to keep all information of a single request (spanning multiple
MessageExchanges) in a single file for logging purposes.
Gert
Arif Mohd wrote:
>
> Gert,
>
> You are talking about correlation ID,
>
> will it be unique for every message if so can we compare this id
> with jsessionid ?
>
> I want to implement logging in such a way that i should be able to
> keep all the information related to a request in a file(Name of the file
> same as correlation id) so that i can use this file later for monitoring
> purpose for what happened for a request along the way.
>
> Is it possible to achieve this? if so how?
>
> My message flow in ESB will be Consumer queue --> Content base
> router,....--> http BC -->out put queue
>
>
> Gert Vanthienen wrote:
>>
>> rb2399,
>>
>> Do you want to forward the contents of the messages all the way through
>> your message flow (as in the Message History pattern) because you need it
>> further down the road for your processing or do you need it for
>> logging/auditing purposes?
>>
>> If you need the contents of the previous messages for processing, I don't
>> think that there is an out of the box component that does so. Feel free
>> to add it to the servicemix-eip component and let us know if you need any
>> help implementing it...
>>
>> In the latter case, you can write your own Auditor implementation and
>> plug it into the container. Starting with version 3.2 (which you'll have
>> to build from source yourself for now), there is an additional
>> correlation ID that is sent with every message exchange to link
>> subsequent messages together. This allows you to write an Auditor that
>> logs the entire message history (I've recently done something similar, it
>> works really well)
>>
>>
>> Gert
>>
>>
>> rb2399 wrote:
>>>
>>> Hi Gert,
>>> thanks for your reply.On a sidenote I wanted to know if we have a "out
>>> of the box" component that implements the "Message History" pattern from
>>> EIP.
>>> If not,what is the best way to implement the same ?
>>> Is it using wiretap ?
>>>
>>> Thanks,
>>> rb2399
>>>
>>>
>>> rb2399 wrote:
>>>>
>>>> Hi All,
>>>> I am new to JBI and SM world.I am trying to run a sample example like:
>>>> HTTP BC --> SE1 (Just appends the payload received from HTTP BC) -- >SE
>>>> 2 (receives the msg & displays it)
>>>>
>>>> I've defined SE 1 as in-only & so is SE2 also.I'm having problems with
>>>> exception "ould not find route for exchange" when SM routes it from SE1
>>>> to SE2. I've followed the hello world SE example for defining
>>>> xbean.xml.Do I need to update the servicemix.xml also with
>>>> activationspec.
>>>>
>>>> Sorry if I've repeated the question,but I'm totally lost here.
>>>>
>>>> Thanks in advance,
>>>> rb2399
>>>>
>>>
>>>
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Simple-JBI-App-tf3839777s12049.html#a10944080
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: Simple JBI App
Posted by Arif Mohd <ar...@wipro.com>.
Gert,
You are talking about correlation ID,
will it be unique for every message if so can we compare this id with
jsessionid ?
I want to implement logging in such a way that i should be able to
keep all the information related to a request in a file(Name of the file
same as correlation id) so that i can use this file later for monitoring
purpose for what happened for a request along the way.
Is it possible to achieve this? if so how?
My message flow in ESB will be Consumer queue --> Content base
router,....--> http BC -->out put queue
Gert Vanthienen wrote:
>
> rb2399,
>
> Do you want to forward the contents of the messages all the way through
> your message flow (as in the Message History pattern) because you need it
> further down the road for your processing or do you need it for
> logging/auditing purposes?
>
> If you need the contents of the previous messages for processing, I don't
> think that there is an out of the box component that does so. Feel free
> to add it to the servicemix-eip component and let us know if you need any
> help implementing it...
>
> In the latter case, you can write your own Auditor implementation and plug
> it into the container. Starting with version 3.2 (which you'll have to
> build from source yourself for now), there is an additional correlation ID
> that is sent with every message exchange to link subsequent messages
> together. This allows you to write an Auditor that logs the entire
> message history (I've recently done something similar, it works really
> well)
>
>
> Gert
>
>
> rb2399 wrote:
>>
>> Hi Gert,
>> thanks for your reply.On a sidenote I wanted to know if we have a "out of
>> the box" component that implements the "Message History" pattern from
>> EIP.
>> If not,what is the best way to implement the same ?
>> Is it using wiretap ?
>>
>> Thanks,
>> rb2399
>>
>>
>> rb2399 wrote:
>>>
>>> Hi All,
>>> I am new to JBI and SM world.I am trying to run a sample example like:
>>> HTTP BC --> SE1 (Just appends the payload received from HTTP BC) -- >SE
>>> 2 (receives the msg & displays it)
>>>
>>> I've defined SE 1 as in-only & so is SE2 also.I'm having problems with
>>> exception "ould not find route for exchange" when SM routes it from SE1
>>> to SE2. I've followed the hello world SE example for defining
>>> xbean.xml.Do I need to update the servicemix.xml also with
>>> activationspec.
>>>
>>> Sorry if I've repeated the question,but I'm totally lost here.
>>>
>>> Thanks in advance,
>>> rb2399
>>>
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Simple-JBI-App-tf3839777s12049.html#a10912524
Sent from the ServiceMix - User mailing list archive at Nabble.com.