| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Warehouse Node difference v5 <-> v6 |
« View previous topic :: View next topic » |
| Author |
Message
|
| PieterV |
 Posted: Thu Jul 06, 2006 4:27 am Post subject: Warehouse Node difference v5 <-> v6 |
 |
|
Disciple
Joined: 04 Jan 2006
Posts: 164
Location: Belgium
|
I notice that the way you configure the warehouse node in version 6 is totaly different then in v5.
In v5 i only had to make a JDBC connection to a DB, have a table with a TIMESTAMP(varchar20) and a MESSAGE(hugeblob) and in the mapping give the TIMESTAMP as value 'CURRENT_TIMESTAMP' and MESSAGE as value 'BITSTREAM(MsgRoot)'.
When i try to do this in v6, the toolkit gives error on the values...
What do i need to do to acclompisch the same thing as in version 5?
in other words, i want a DB table with the current timestamp and the message in BLOB format. |
|
| Back to top |
|
 |
| PieterV |
| Posted: Tue Jul 11, 2006 12:14 am Post subject: |
|
|
Disciple
Joined: 04 Jan 2006
Posts: 164
Location: Belgium
|
* kick *
is there nobody who has tried to use the Warehouse node in version 6 like the way it is used in version 5.
In the samples of the toolkit i can only find a sample who does "almost" the same thing as the warehouse node did in version 5, but in fact the warehouse node is not used in that sample. All is done based on ESQL in compute nodes.
Even importing a version 5 msgflow containing a warehouse-node fails in version 6 toolkit; it fails on the mapping file that is in version 6 of a different extension... |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Jul 11, 2006 2:43 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Well, I guess you didn't post the errors the toolkit gives.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| PieterV |
| Posted: Tue Jul 11, 2006 5:24 am Post subject: |
|
|
Disciple
Joined: 04 Jan 2006
Posts: 164
Location: Belgium
|
true,
well i accepted that i could migrate from a version 5 msgflow.
now my mapping looks as follows:
Table TIMESTAMP mapped to esql:current_timestamp()
Table MESSAGE mapped to esql:asbitstream($source)
and it seems to work.
I must say that it was much more easier in version 5, but version 5 was also limited in use as you could only map to TIMESTAMP and MESSAGE with fixed values CURRENT_TIMESTAMP and BITSTREAM(MsgRoot).
It looks like in version 6 you can map to whatever you want and that was confusing to me since i expected a similar approach like in version 5.
But now it seems to work.
But i'm experiencing another problem using the mapping editor.
If i have a source that is a message ( < message definition < message set < message set project) and the message is a MRM based XML with namespaces in it, then the mapping editor gives an error that i cannot find the message.
Error: Unable to find message "purchaseOrder" in message set "A640XMLIn".
Message XSD (xsd from a Sample Project):
| Code: |
<?xml version="1.0" encoding="UTF-8"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.ibm.com"
xmlns:po="http://www.ibm.com">
<annotation>
<documentation xml:lang="en">
Purchase order schema example from XML Schema Part 0: Primer
Copyright 2001, IBM Corp. All rights reserved
Copyright 2001, World Wide Web Consortium,
(Massachusetts Institute of Technology, Institut National de Recherche en Informatiqueet en Automatique, Keio University).
All Rights Reserved.
</documentation>
</annotation>
<element name="purchaseOrder" type="po:PurchaseOrderType"/>
<element name="comment" type="string"/>
<complexType name="PurchaseOrderType">
<sequence>
<element name="shipTo" type="po:USAddress"/>
<element name="billTo" type="po:USAddress"/>
<element ref="po:comment" minOccurs="0"/>
<element name="items" type="po:Items"/>
</sequence>
<attribute name="orderDate" type="date"/>
</complexType>
<complexType name="USAddress">
<sequence>
<element name="name" type="string"/>
<element name="street" type="string"/>
<element name="city" type="string"/>
<element name="state" type="po:USState"/>
<element name="zip" type="decimal"/>
</sequence>
<attribute name="country" type="NMTOKEN" fixed="US"/>
</complexType>
<complexType name="Items">
<sequence>
<element name="item" minOccurs="0" maxOccurs="unbounded">
<complexType>
<sequence>
<element name="productName" type="string"/>
<element name="quantity">
<simpleType>
<restriction base="positiveInteger">
<maxExclusive value="100"/>
</restriction>
</simpleType>
</element>
<element name="USPrice" type="decimal"/>
<element ref="po:comment" minOccurs="0"/>
<element name="shipDate" type="date" minOccurs="0"/>
</sequence>
<attribute name="partNum" type="po:SKU" use="required"/>
</complexType>
</element>
</sequence>
</complexType>
<simpleType name="SKU">
<restriction base="string">
<pattern value="\d{3}-[A-Z]{2}"/>
</restriction>
</simpleType>
<simpleType name="USState">
<restriction base="string">
<enumeration value="CA"></enumeration>
<enumeration value="PA"></enumeration>
<enumeration value="AR"></enumeration>
</restriction>
</simpleType>
</schema>
|
when i change line 3 to targetNamespace="" he does not create a schema com.ibm.www and he place the mxsd file in the default schema.
when i do this he doesnt give me an error in the mapping editor.
This was only a test, but there might be cases where i cannot change the xsd file that is the foundation for a message definition file.
Does anybody has an explanation for this and perhaps a workaround?
Perhaps you can try it, you find the xsd file in the sample project PurchaseOrder (Technology Samples -> XML -> Editing and validating XML files )
When you create a message definition file with it and then you use that message in your warehouse node you will receive an error in the mapping editor. |
|
| 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
|
|
|
|
