Author |
Message
|
Thripura Sundari |
Posted: Thu Jul 14, 2005 2:09 am Post subject: Importing XSD to create Message Defintion File |
|
|
Acolyte
Joined: 13 Jun 2005 Posts: 57 Location: Bangalore, India
|
Hi all,
I tried to import an xsd and create a message definition file. But it says namespace has no prefixes. I have validated the file, but still no change. Can some one please help?
Regards,
Thripura Sundari |
|
Back to top |
|
 |
damianharvey |
Posted: Thu Jul 14, 2005 8:20 pm Post subject: |
|
|
 Acolyte
Joined: 05 Aug 2003 Posts: 59 Location: Sydney, Australia
|
My contact admin hack (I'm sure someone with better knowledge of this will give you a better solution) is to put a colon ':' in the XSD before turning it into a Message Definition File.
eg. you might have :
Code: |
xmlns="http://www.opentravel.org/OTA/2003/05" |
so you change it to :
Code: |
xmlns:="http://www.opentravel.org/OTA/2003/05" |
As I said... contact admin. But it works.
Cheers,
D. |
|
Back to top |
|
 |
Thripura Sundari |
Posted: Thu Jul 14, 2005 10:35 pm Post subject: |
|
|
Acolyte
Joined: 13 Jun 2005 Posts: 57 Location: Bangalore, India
|
Hi,
Thanks for the reply. I had added a prefix to the namespace as requried, but I am stuck at the next step. The xsd does not have global elements. I cannot change it much as it is the format given to us. Trying to add global elements to it, but not got it yet. If you could help, (may be I am asking for too much, sorry..., but cant help it...), it would be great!
Regards,
Thripura Sundari |
|
Back to top |
|
 |
Maverik |
Posted: Fri Jul 15, 2005 10:16 am Post subject: |
|
|
Apprentice
Joined: 14 Jun 2005 Posts: 27
|
Ok i have been trying the same thing so i could tell you something.
Firstly, u dont need to change it to mxsd and import. Once creating the message set go to create new definition file and select "XML Schema file".
Now u can browse the xsd file(which should be already in the broker toolkit) and place it under the required message set.
If you get errors dont consider them until u have imported all the xsd's under the message set. If the errors persist even after this,then do not apply namespaces in the message set and try.
NOTE: About your global elements, it will ask you which global elements you want to import when you are trying to import the xsd's.
Good luck. |
|
Back to top |
|
 |
Thripura Sundari |
Posted: Fri Jul 15, 2005 11:16 pm Post subject: |
|
|
Acolyte
Joined: 13 Jun 2005 Posts: 57 Location: Bangalore, India
|
Hi Maverik,
Thanks for the wishes. Yes, as you had said, I had also tried to create a new message definition file by using the xml schema. When I select the xsd to be used to create the message definition file, i have to select the global elements, there are actually no global elements, so i cannot select anything and when i click on next, it doesnt go to the next step.
Again, Thanks for your response.
Regards,
Thripura Sundari. |
|
Back to top |
|
 |
Maverik |
Posted: Sat Jul 16, 2005 2:05 am Post subject: |
|
|
Apprentice
Joined: 14 Jun 2005 Posts: 27
|
Hi Thripura,
Not all the xsd's will show the global variables. I dont think that is an issue.
Also, after you get the page of global variables(which can be blank) you dont have any more pages, just a finish.
What you finally need to check is that no errors are present and that the root mxsd id now opening up to link all the other mxsd's.....i.e your entire message structure is available.
Can I know which company ur working for ??
Regards. |
|
Back to top |
|
 |
Thripura Sundari |
Posted: Sat Jul 16, 2005 4:31 am Post subject: |
|
|
Acolyte
Joined: 13 Jun 2005 Posts: 57 Location: Bangalore, India
|
Hi Maverik,
Thanks for the response. When I get the "select the global elements" option and when I dont have anything to select and so, i dont select, the
option is disabled. Also, when I click on
, nothing happens. I am left with just the option to
. Am I missing out something?
I am working for Cognizant. And I am new to WebSphere Business Integration. I get lots of information from this site.
Thanks to all of you.
Regards,
Thripura Sundari |
|
Back to top |
|
 |
Maverik |
Posted: Sun Jul 17, 2005 11:08 pm Post subject: |
|
|
Apprentice
Joined: 14 Jun 2005 Posts: 27
|
Hi Thripura,
R u trying to create an IDoc or something???
Let me know the name if its an Idoc, if i have it i'll forward it.or better let us have a look at the xsd's if they are custom made and we can think of something.
you can forward the files in a zip to elvis.ninan@patni.com
I dont promise anything but i'll try waiting for the files
Bye |
|
Back to top |
|
 |
Thripura Sundari |
Posted: Mon Jul 18, 2005 5:19 am Post subject: |
|
|
Acolyte
Joined: 13 Jun 2005 Posts: 57 Location: Bangalore, India
|
Hi,
I dont know what is an IDoc. By the way, the xsd I am trying to convert to a Message Definition file is
Code: |
<?xml version="1.0" encoding="utf-16"?>
<xs:schema xmlns="http://SupplierSwitchSchemas.CruiseAvailability_1_0_Response" xmlns:b="http://schemas.microsoft.com/BizTalk/2003" attributeFormDefault="unqualified" elementFormDefault="unqualified" targetNamespace="http://SupplierSwitchSchemas.CruiseAvailability_1_0_Response" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="CruiseAvailability_1_0">
<xs:complexType>
<xs:sequence>
<xs:element name="CruiseAvail">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="ErrText">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="Err" type="xs:string" />
<xs:element minOccurs="0" name="KlrInErr" type="xs:string" />
<xs:element minOccurs="0" name="InsertedTextAry">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="InsertedText">
<xs:complexType>
<xs:sequence>
<xs:element name="Offset" type="xs:int" />
<xs:element name="Len" type="xs:int" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element minOccurs="0" name="Text" type="xs:string" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element minOccurs="0" name="TextDisplay">
<xs:complexType>
<xs:sequence>
<xs:element name="TxtAry">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="Txt" type="xs:string" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element minOccurs="0" name="CabinCategory">
<xs:complexType>
<xs:sequence>
<xs:element name="CatAry">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="CatInfo">
<xs:complexType>
<xs:sequence>
<xs:element name="Cat" type="xs:string" />
<xs:element name="Status">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="SS" />
<xs:enumeration value="LL" />
<xs:enumeration value="CL" />
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="Rmk" type="xs:string" />
<xs:element name="Locn">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="I" />
<xs:enumeration value="O" />
<xs:enumeration value="M" />
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="NumUpperBerth" type="xs:int" />
<xs:element name="NumLowerBerth" type="xs:int" />
<xs:element name="Price" type="xs:integer" />
<xs:element name="Currency" type="xs:string" />
<xs:element name="DecPos" type="xs:int" />
<xs:element name="DescInd">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="Y" />
<xs:enumeration value="N" />
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element minOccurs="0" name="SailingRate">
<xs:complexType>
<xs:sequence>
<xs:element name="RateAry">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="RateInfo">
<xs:complexType>
<xs:sequence>
<xs:element name="Rate" type="xs:string" />
<xs:element name="Desc" type="xs:string" />
<xs:element name="Rmk" type="xs:string" />
<xs:element name="Rules">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="Y" />
<xs:enumeration value="N" />
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element minOccurs="0" name="SailingAvailability">
<xs:complexType>
<xs:sequence>
<xs:element name="SailingAry">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="Sailing">
<xs:complexType>
<xs:sequence>
<xs:element name="DayNightInd">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="D" />
<xs:enumeration value="N" />
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="InsuranceInd">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="W" />
<xs:enumeration value="I" />
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="ShipName" type="xs:string" />
<xs:element name="StartDt" type="xs:string" />
<xs:element name="StartDay">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="SU" />
<xs:enumeration value="MO" />
<xs:enumeration value="TU" />
<xs:enumeration value="WE" />
<xs:enumeration value="TH" />
<xs:enumeration value="FR" />
<xs:enumeration value="SA" />
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="StartPort" type="xs:string" />
<xs:element name="EndPort" type="xs:string" />
<xs:element name="Duration" type="xs:int" />
<xs:element name="Status">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="SS" />
<xs:enumeration value="LL" />
<xs:enumeration value="CL" />
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="PkgID" type="xs:string" />
<xs:element name="ItinInd">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="Y" />
<xs:enumeration value="N" />
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="DineStatus1">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="SS" />
<xs:enumeration value="LL" />
<xs:enumeration value="CL" />
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="DineStatus2">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="SS" />
<xs:enumeration value="LL" />
<xs:enumeration value="CL" />
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element minOccurs="0" name="CustomerIdentification">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="TextInd" type="xs:string" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element minOccurs="0" name="VendorChangedData">
<xs:complexType>
<xs:sequence>
<xs:element name="PkgID" type="xs:string" />
<xs:element name="CurrencyChgInd">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="" />
<xs:enumeration value="Y" />
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="Currency" type="xs:string" />
<xs:element default="0" name="DecPos" type="xs:int" />
<xs:element name="RateChgInd">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="" />
<xs:enumeration value="Y" />
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="Rate" type="xs:string" />
<xs:element name="CityChgInd">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="" />
<xs:enumeration value="Y" />
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="City" type="xs:string" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element minOccurs="0" name="TextMsg">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="Txt" type="xs:string" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
|
This was generated by Biztalk. So, there could be some internal issues. Not sure. I just created teh message defintion file manually and mapped it.  |
|
Back to top |
|
 |
Thripura Sundari |
Posted: Mon Jul 18, 2005 7:23 am Post subject: |
|
|
Acolyte
Joined: 13 Jun 2005 Posts: 57 Location: Bangalore, India
|
Hi all,
Sorry for sending the entire file to the site. I was in a hurry and didnt check the mail properly. My apologies.
Regards,
Thripura Sundari. |
|
Back to top |
|
 |
|