| Author |
Message
|
| smeunier |
 Posted: Thu Jan 12, 2006 10:03 am Post subject: |
 |
|
Partisan
Joined: 19 Aug 2002
Posts: 305
Location: Green Mountains of Vermont
|
I did not have a Message type specified on the MQInput node Message Type property(I assume this is where you meant it to be) So I specified it to be the first Message in the Message Definition(Z2200MM_UPIX_DELIVERY000). I then ran a test. Same results. I checked the XML name properties and that matches the Message Type. No the message type, this is: MD_SAP_BO_z_200mm_upix_pick01 as specified in the RFH2 Header, which should also be the root tag. See above post with all the data. I think I'm reading this right............
No my understanding, is that the properties specified on the MQInput node override the RFH2 properties. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Jan 12, 2006 10:05 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Actually, it's the other way around.
Properties in the MQRFH2 override the properties on the MQInput node.
So the properties in the message need to be correct or non-existent.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu Jan 12, 2006 10:10 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| Quote: |
| Properties in the MQRFH2 override the properties on the MQInput node. |
Which is why it is on the "default" tab on the MQInput node ... 
_________________
-wayne |
|
| Back to top |
|
|
| smeunier |
| Posted: Thu Jan 12, 2006 6:55 pm Post subject: |
|
|
Partisan
Joined: 19 Aug 2002
Posts: 305
Location: Green Mountains of Vermont
|
Still looking for a solution to this problem and ran into this section in the documentation which perhaps you eluded to a little. Currently I have one message set and one Message Definition file. The MDF contains both a CwXML and CWF physical format. This reference in the book seems to frown on that. Could this perhaps be the problem. Incompatible types in the same Message Definon file?
| Quote: |
You can have as many message definition files as you want within one message set. But you are recommended to limit your message sets to a few related message definition files that share the same physical formats. There are several reasons for this:
Generation of a message dictionary and other representations is quicker.
Generated documentation is more manageable.
Physical formats apply to all objects within the message set.
So for example, if you have an XML message and an unrelated CWF message in the same message set, then both XML and CWF physical format properties will be present for all objects. But the XML properties are of no interest to the CWF message and so will take default values in that message. (Similarly, the CWF properties are not of interest to the XML message.) This can result in unwanted task list warnings.
|
|
|
| Back to top |
|
|
| kimbert |
| Posted: Fri Jan 13, 2006 4:41 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
| That section in the docs is a statement about how to avoid lots of unnecessary warnings in the task list of the Message Set editor. Having more than one physical format does not affect the runtime in any way, and it certainly does not explain your problem. |
|
| Back to top |
|
|
| kimbert |
| Posted: Fri Jan 13, 2006 5:11 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
OK - going back to the main problem...
1. Can you post the first few lines of your input message
2. Check that your message set is using namespaces. To do this, go to the Message Set properties and confirm that the 'Use Namespaces' check box is ticked.
3. You did not actually confirm that you had checked the namespaces in your message set against the namespaces in your message. That's a really important check. Apologies if you did that already and just didn't mention it. |
|
| Back to top |
|
|
| smeunier |
| Posted: Fri Jan 13, 2006 5:38 am Post subject: |
|
|
Partisan
Joined: 19 Aug 2002
Posts: 305
Location: Green Mountains of Vermont
|
First few lines of XML input message:
| Code: |
<?xml version="1.0" encoding="UTF-8"?>
<MD_SAP_BO_z_200mm_upix_pick01:MD_SAP_BO_z_200mm_upix_pick01 xmlns:MD_SAP_BO_z_200mm_upix_pick01="http://www.ibm.com/websphere/crossworlds/2002/BOSchema/MD_SAP_BO_z_200mm_upix_pick01" xmlns:MD_SAP_BO_sap_idoccontrol="http://www.ibm.com/websphere/crossworlds/2002/BOSchema/MD_SAP_BO_sap_idoccontrol" xmlns:MD_SAP_BO_z_200mm_upix_pick01_z2200mm_upix_item000="http://www.ibm.com/websphere/crossworlds/2002/BOSchema/MD_SAP_BO_z_200mm_upix_pick01_z2200mm_upix_item000" xmlns:MD_SAP_BO_z_200mm_upix_pick01_z2200mm_upix_delivery000="http://www.ibm.com/websphere/crossworlds/2002/BOSchema/MD_SAP_BO_z_200mm_upix_pick01_z2200mm_upix_delivery000" xmlns:MD_SAP_BO_z_200mm_upix_pick01_cwdata="http://www.ibm.com/websphere/crossworlds/2002/BOSchema/MD_SAP_BO_z_200mm_upix_pick01_cwdata" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.ibm.com/websphere/crossworlds/2002/BOSchema/MD_SAP_BO_z_200mm_upix_pick01 file:MD_SAP_BO_z_200mm_upix_pick01.xsd" version="3.0.0" verb="Create" locale="en_US" delta="false">
<MD_SAP_BO_z_200mm_upix_pick01:Control_record>
<MD_SAP_BO_sap_idoccontrol:MD_SAP_BO_sap_idoccontrol version="1.0.0" verb="" locale="en_US" delta="false">
<MD_SAP_BO_sap_idoccontrol:Name_of_table_structure>EDI_DC40</MD_SAP_BO_sap_idoccontrol:Name_of_table_structure>
<MD_SAP_BO_sap_idoccontrol:Client>017</MD_SAP_BO_sap_idoccontrol:Client>
|
Message Set "Use namespaces" is checked
On Item 3, not sure how you mean check. The Namespace URI's in the message set (CwXML hysical format) are correct against the namespaces in the message, or i would not be able to reference them in the ESQL(or output messages using Namespace prefixes). Do you mean check so other way. |
|
| Back to top |
|
|
| smeunier |
| Posted: Fri Jan 13, 2006 5:53 am Post subject: |
|
|
Partisan
Joined: 19 Aug 2002
Posts: 305
Location: Green Mountains of Vermont
|
Just to add to the last:
In the Message Definition(mxsd) Root Tag Name is blank
Under Field Identification:
Render = XMLElement
XML Name - Z2200MM_UPIX_DELIVERY000
Other values grayed out |
|
| Back to top |
|
|
| kimbert |
| Posted: Fri Jan 13, 2006 6:10 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
| Quote: |
| The Namespace URI's in the message set (CwXML physical format) are correct against the namespaces in the message, or i would not be able to reference them in the ESQL(or output messages using Namespace prefixes) |
1. The statement about ESQL field access is incorrect ( as long as the ESQL path matches the tree the reference will succeed )
2. You are correct about outputting of namespace prefixes - the prefixes would be output as 'ns1', 'ns2' etc if the namespaces in the cwXML physical format did not match
however...
3. I'm more interested in the namespaces in the logical model. You need to open your message set in the Message Set Editor and check that the namespace hierarchy shown in the Navigator view exactly matches the namespaces in the input XML document.
4. While the message set is open. do a quick visual check that each level in the message definition for 'MD_SAP_BO_z_200mm_upix_pick01' matches the tags in the input document. |
|
| Back to top |
|
|
| smeunier |
| Posted: Fri Jan 13, 2006 8:28 am Post subject: |
|
|
Partisan
Joined: 19 Aug 2002
Posts: 305
Location: Green Mountains of Vermont
|
We may be having a communcation breakdown. And I apologize...... just to be clear on what you are asking. The Logical model exists in the .mxsd file of the message set, opened by the Message Definition Editor. The .mset does not contain a Logical model under Properties Hierarchy opened by the Message Set Editor. When you talk about navigator are you refering to the Resource Navigator on left panel(guess it would depend on the perspective).
[/img] |
|
| Back to top |
|
|
| kimbert |
| Posted: Fri Jan 13, 2006 8:45 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
It's OK - you're on roughly the right lines. If you open the Message Set project in the Broker Application Development perspective, the Navigator view (top left pane) will show the .mxsd file within a folder. The name of that folder should be
| Code: |
| www.ibm.com.websphere.crossworlds.2002.BOSchema.MD_SAP_BO_z_200mm_upix_pick01 |
|
|
| Back to top |
|
|
| smeunier |
| Posted: Fri Jan 13, 2006 9:00 am Post subject: |
|
|
Partisan
Joined: 19 Aug 2002
Posts: 305
Location: Green Mountains of Vermont
|
Ahhh, and that is where I thought you were going with this........... The Message Set was built using the System Manager for the mySAP.com adapter. Not really an issue. I like the integrated tool features.......
Normally when building a message set from a Business object, it creates a BOSchema file for each namespave level. I had not noticed that those were missing until just now and because everything else worked ok(other than blank values( hadn't paid much credence to it. Are you eluding to that those files need to be there in order for this to work? I will rebuild the Message Set, since I'm not sure how to add then independantly. Perhaps I just need to import those schema files in |
|
| Back to top |
|
|
| kimbert |
| Posted: Fri Jan 13, 2006 9:14 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
Not at all. When the message broker converts a message set to a dictionary its inputs are:
- the messageSet.mset file
- the .mxsd file(s)
Any other files which happen to exist with the message set project are ignored.
My question was a very simple one really - does the namespace of your .mxsd file match the namespace in the input document? Apparently the answer is 'yes'.
I must admit I'm stumped at this point. I know this scenario works - it's a perfectly straightforward use of the MRM. I also know roughly where the fault lies - it's either a fault with the message set or an error in the message properties ( Message Set, Message Type, Message Format ).
I can only suggest that you recreate the message set using the System Manager and see whether it all springs into life. |
|
| Back to top |
|
|
| smeunier |
| Posted: Fri Jan 13, 2006 11:58 am Post subject: |
|
|
Partisan
Joined: 19 Aug 2002
Posts: 305
Location: Green Mountains of Vermont
|
So to answer you question:
| Quote: |
does the namespace of your .mxsd file match the namespace in the input document? |
The answer is: in the Details section, under the Namespace section, all fields are greyed out. Prefix:blank Target Namespace:blank
Default namespaces for local objects: < no target namspace>
Help? |
|
| Back to top |
|
|
| kimbert |
| Posted: Sat Jan 14, 2006 12:20 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
In that case we've finally diagnosed the problem. Your .mxsd file is in the noTargetNamespace. Presumably, in the Navigator view, it appears under a folder called 'default', whereas it should appear under a folder called 'www.ibm.com.websphere.crossworlds.2002.BOSchema.MD_SAP_BO_z_200mm_upix_pick01'.
The solution should be straightforward. Recreate your message set, this time ensuring that the .mxsd file is in the correct target namespace. Sorry I can't tell you exactly how, because I've never used the mySAP.com adapter myself. |
|
| Back to top |
|
|
|
|
