| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Help with DocType tag, Adaptors, and Data handlers with WBI. |
« View previous topic :: View next topic » |
| Author |
Message
|
| Ulfinator |
 Posted: Tue Nov 14, 2006 12:49 pm Post subject: Help with DocType tag, Adaptors, and Data handlers with WBI. |
 |
|
Newbie
Joined: 14 Nov 2006
Posts: 2
|
First time poster here so be nice! 
So I am working on a project where we are having partners share metadata about documents, parts, etc in there PDM systems (TCE, Windchill, etc) so that we can have users of our system to reach back to those documents at a later time.
In architecting the solution (before my time) and trying to keep it as generic as possible so that any partner regardless of their PDM and/or Integration Broker (for instance we using Tibco) can communicate. In doing so it was decided that a JMS property should be uses to state what the transaction being performed was. Thus when we or a partner receive a request to create a doc, retrieve a docs content, etc one of the first things done is to look at the JMS property and figure out what transaction it is and what to do with it. So far we, plus 12 of our partners have been successful using this scheme for the last couple of years.
However now I have come across my first partner who is using WBI on there end. We started working with this new partner and they notified us that the out of the box adaptors and data handlers for XML require a DocType tag to be used for routing the transaction to the correct process. This has caused a problem for us as we are trying to get their connectivity set up rather quickly.
The only options that we know of are:
1) Make a change to our process and when we send messages to this partner we can modify the XML payload so that it includes the DocType tag. This is actually technically easy on our side but then introduces a specific special case in our communication architecture which is undesired.
2) Have the partner develop a custom adaptor and/or data handler that will use the JMS Property. This seems to be a viable option but might not satisfy the short term need to get this functional
3) I have also heard that we could us the root tag to provide the name of the transaction as well. Again from our side this is considered architectural undesirable.
Anybody have any other ideas than those listed above?
Thanks in advance for any help and or advice you might lend. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Nov 14, 2006 1:38 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Convert to using SOAP documents.
It's standard.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Ulfinator |
| Posted: Tue Nov 14, 2006 1:45 pm Post subject: |
|
|
Newbie
Joined: 14 Nov 2006
Posts: 2
|
| Quote: |
Convert to using SOAP documents.
It's standard. |
When you says it's standard do you mean SOAP is a standard, using JMS properties, etc is standard. Not real sure what you mean.
While SOAP is definitly a viable technical option it isn't a viable cost option for us. Too bad but the truth. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Nov 14, 2006 1:57 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I'm saying that SOAP is a standard for describing messages, and if you convert your processes to using it, then you won't run into issues with business partners where one or the other side has to conform to something that is not standard.
And if you already have an Integration Hub, then it should be relatively low cost to build something that will map between your internal format and a SOAP message that can be passed to this particular business partner - and the cost of that can be amortized over other business partners who may want to use a standard approach rather than your messaging.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
