| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ Integrator |
« View previous topic :: View next topic » |
| Author |
Message
|
| Jane |
 Posted: Thu Apr 22, 2004 1:25 pm Post subject: MQ Integrator |
 |
|
Newbie
Joined: 22 Apr 2004
Posts: 8
|
New to the MQ world and trying to learn the MQ Broker to create a message flow to take a XML file from the queue and insert into a DB2 table. It seems to be working since we are getting a successfull trace node but when we look at the DB2 table, only one field is being inserted,
not all of the fields. We mapped 10 fields to be inserted. Please help.
Jane |
|
| Back to top |
|
 |
| JT |
| Posted: Thu Apr 22, 2004 1:48 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
Jane,
Can you provide your ESQL code?
Have you debugged the code or turned on a debug trace?
Do the columns that are not populated, allow nulls?
Are you using v2.x or v5.x? |
|
| Back to top |
|
|
| Jane |
| Posted: Fri Apr 23, 2004 5:09 am Post subject: MQIntegrator |
|
|
Newbie
Joined: 22 Apr 2004
Posts: 8
|
JT,
We used the mapping feature between a XML file and the databases and only mapped ten of the fields. We did not create or change the ESQL. We did not try the debug steps since we were told that they were source hogs. We will give that a try. The columns in our DB2 tables are all 'not
nulls'. We are using V5.x version. We did set up two traces, one to the successfull node and one to the failure node. The successful node returns even though the data is not inserting correctly. We are not sure if it our message flow that is incorrect or if something in the MQ setup is incorrect.
We are looking in the Redbooks to find an answer but they are difficult to follow online.
Any help or direction would be greatly appreciated.
Thanks,
Jane |
|
| Back to top |
|
|
| fschofer |
| Posted: Fri Apr 23, 2004 5:36 am Post subject: |
|
|
Knight
Joined: 02 Jul 2001
Posts: 524
Location: Mainz, Germany
|
Hi Jane,
putting a trace node behind your nodes will give you only the actual state of your internal tree,
no information about errors in your mapping.
Best way to find errors is to run a debug trace (do not confuse this with the debugger).
Use the commands
mqsichangetrace <Broker> -u -e <Exec. Grp.> -f <Flow Name> -l debug -c 5000 -r
put a message to your flow
mqsireadlog <Broker> -u -e <Exec. Grp.> -o out.xml
mqsiformatlog -i out.xml -o out.txt
I hope that debug tracing also works for the mapping node
like on the compute node, never used it on mapping one.
Greetings
Frank |
|
| Back to top |
|
|
| Jane |
| Posted: Fri Apr 23, 2004 11:22 am Post subject: MQ Integrator |
|
|
Newbie
Joined: 22 Apr 2004
Posts: 8
|
A little more information on what we are trying to do. We are trying to use MQ Broker to receive an XML file in the MQInput node, then use the mapping feature in a DataInsert node to connect the XML parsed fields to the database fields and then do an insert. This sounds like a very simple process for the MQ Broker. The XML file was imported successfully and the database structure imported successfully. The mapping is very simple at this point, just connecting ten fields to insert. The data file is put to the queue using the RFHutil utility. The trace nodes seem to be working, atleast they are returning messages. But when we look at the DB2 table, the insert is incorrect. All the fields in the table seem to be initialized, spaces to character fields and zero to numeric fields except for one field, which inserted the correct data. The fields on our DB2 tables are not nullable. Is there a step in the setup of the messageflow incorrect? Has anyone else run into this same problem? Do we need to use a compute node instead of the datainsert node? Do we need a mapping node? We have to wait for production control to set a debug trace, but is there something else we need to look at?
Please help,
Jane |
|
| Back to top |
|
|
| Jane |
| Posted: Fri Apr 23, 2004 11:48 am Post subject: MQ Integrator |
|
|
Newbie
Joined: 22 Apr 2004
Posts: 8
|
Hi,
Does this code look correct? It is the code generated when we mapped the XML fields to the database fields. The sequence of numbers seems off to me.
<mappings xmi:id="TransformMapping_1">
<helper xmi:id="TransformMappingHelper_1">
<statement xmi:type="mfmap:InsertStatement" xmi:id="InsertStatement_1">
<assignments xmi:id="TableAssignment_1" expression="s_order_hhg.base_info.shipper_name.last">
<target xmi:id="TransformMappingItem_1" parentPath="TESTADDR" name="NAME_SHPR_LAST" esqlPath=""#T".NAME_SHPR_LAST"/>
</assignments>
</statement>
</helper>
<inputItems xmi:id="TransformMappingItem_2" parentPath="s_order_hhg.base_info.shipper_name" name="last" esqlPath="s_order_hhg.base_info.shipper_name.last"/>
</mappings>
<mappings xmi:id="TransformMapping_2">
<helper xmi:id="TransformMappingHelper_2">
<statement xmi:type="mfmap:InsertStatement" xmi:id="InsertStatement_2">
<assignments xmi:id="TableAssignment_2" expression="s_order_hhg.base_info.shipper_name.suffix">
<target xmi:id="TransformMappingItem_3" parentPath="TESTADDR" name="NAME_SHPR_SUF" esqlPath=""#T".NAME_SHPR_SUF"/>
</assignments>
</statement>
</helper>
<inputItems xmi:id="TransformMappingItem_4" parentPath="s_order_hhg.base_info.shipper_name" name="suffix" esqlPath="s_order_hhg.base_info.shipper_name.suffix"/>
</mappings>
Thanks,
Jane |
|
| 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
|
|
|
|
