| Author |
Message
|
| aaron_blade |
 Posted: Tue Feb 02, 2010 4:00 pm Post subject: Using .mxsd in WTX for Type Tree creation |
 |
|
Apprentice
Joined: 21 Dec 2009
Posts: 29
|
Hi,
We are trying to integrate SAP with legecy systems. We are using WMB for routing and WTX for mapping purposes.
WMB is using SAP adapter to connect to SAP and giving IDoc structure in format of .mxsd for WTX. WTX needs to sue this .mxsd file and make type trees and use for mapping purposes.
As a POC I am trying to do a SAP to SAP direct mapping using WTX.
But I am running into some namespace issues.
Can anybody plese help me out, how can we use .mxsd to make a type tree?
-Thanks,
AAron. |
|
| Back to top |
|
 |
| Amitha |
| Posted: Tue Feb 02, 2010 5:32 pm Post subject: |
|
|
Voyager
Joined: 20 Nov 2009
Posts: 80
Location: Newyork
|
Hi Aaron,
You can import Schema xsd file to create type tree. You can generate xsd from .mxsd file. Right click on message set project file and generate xsd file.
But, What is the format of the message sent by SAP? How did you create .mxsd file? |
|
| Back to top |
|
|
| aaron_blade |
| Posted: Tue Feb 02, 2010 7:21 pm Post subject: |
|
|
Apprentice
Joined: 21 Dec 2009
Posts: 29
|
When the message comes to WTX it is in XML format.
.mxsd file is formed when WMB uses SAP Adapter and imports the IDoc into WMB.
Thing is WMB is done by a different team and we are taking care of WTX part. So when they give us they are giving .mxsd file.
So want to know is there any way we can do this?? |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Tue Feb 02, 2010 9:40 pm Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
mxsd wont work out in WTx.
get a XSD file from SAP Side or do what Amitha asked you to do
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Feb 03, 2010 2:35 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| mxsd wont work out in WTx. |
Why not? A .msxsd is simply an xsd with some WMB annotations. It's a valid xsd, so technically WTX should cope with it OK ( might need to change the extension).
Having made that point, I agree that the correct approach is to generate the .xsd from the .mxsd as Amitha suggests.
| Quote: |
| But I am running into some namespace issues. |
Maybe this is the real problem. But 'namespace issues' doesn't really explain the problem. Please describe your 'issues'. |
|
| Back to top |
|
|
|
|
