07-09-04 08:31 PM
the envelope can be in the send pipeline and then this pipeline can be
applied to your send port. the map can and should happen on the receive
port to get it to the format you want.
You can promote properties into the context and then use those without
having to get them into the envelope.
Matt
"Matt" <mattjgilbert@yahoo.co.uk> wrote in message
news:3fb4ee63.0407061257.5a912cf1@posting.google.com...
> Hi,
> Looking for some advice as to whether this is feasible/technically
> possible in bts2004.
> I am looking to develop a pub/sub architecture where applications can
> submit files to bts and a standard envelope is applied (to ALL
> messages) for routing and tracking. The inbound files could be flat
> files or xml. The ideal solution would also allow different message
> types to be submitted to the same receive locations (e.g. all iDocs
> (flatfiles) from SAP get directed to one place). The trick here is:
> how do you receive a flat file, map to its xml representation and
> apply a standard envelope to the message ready to be pushed to
> subscribers?
> Could you include the envelope information in the switch to xml -
> effectively killing two birds with one stone?
> And if all that is possible, you could throw these into the
> equation...
> 1. Make the process generic - only one 1 pipeline say for SAP files of
> any type/schema
> 2. Promote data from the original file into the generic envelope for
> routing and subscriptions
> Only just started to scratch the 2004 surface but feeling like the
> deep end has a vast amount of water (as no doubt many people are...).
> Hoping someone more ahead of the game has some cool ideas!
> Thanks
> Matt :o)
[ Post a follow-up to this message ]
| 
