| Author |
Message
|
| telus |
 Posted: Mon Nov 12, 2012 9:54 am Post subject: Import all the xsd's at once in message broker |
 |
|
Apprentice
Joined: 01 Nov 2012
Posts: 26
|
Hi
I need to import all the xsd at once .
One xsd is referrring the another xsd and the count is more than 50.
Used the toolkit but only able to do once at a time
Any other way to import all the xsd in the message set.
Thanks |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Nov 12, 2012 11:00 am Post subject: Re: Import all the xsd's at once in message broker |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| telus wrote: |
| Any other way to import all the xsd in the message set. |
I typed "import xsd" into the white box at the top left of the WMB InfoCenter and got a link to the mqsicreatemsgdef command.
The technical term for it is a "search facility". You might want to check it out.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| telus |
| Posted: Mon Nov 12, 2012 11:59 am Post subject: |
|
|
Apprentice
Joined: 01 Nov 2012
Posts: 26
|
I have got the following errors
Used the following command
mqsicreatemsgdefs -p NL_HL7_message_set -data "C:\Documents and Settings\user\IBM\wmbt70\workspace\MkOC\" -d "C:\Documents and Settings\tcsuser\Desktop\XSD\Schemas\"
Got lots of errors of the below type
IP0231E A problem was encountered importing file "C:\Documents and Settings\tcs
ser\Desktop\XSD\Schemas\QUQI_MT120008CA.xsd".
o message definition can be generated for this source file. Refer to the report
file for details of the problem. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Nov 12, 2012 12:08 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| telus wrote: |
| Refer to the report file for details of the problem. |
And when you referred to the report file what details did you find? 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| telus |
| Posted: Mon Nov 12, 2012 12:11 pm Post subject: |
|
|
Apprentice
Joined: 01 Nov 2012
Posts: 26
|
BIP0224W The message set has no XML Wire Format layer defined. Only the logical information will appear in the model.
BIP0235W The message set has no namespace support. The imported XML Schema will be modified to remove namespaces.
BIP0236E Error occurred while creating message definition.
PRPA_IN101202CA.xsd cannot be imported since it contains unsupported features.
The XML schema cannot be imported because the target namespace has no prefix.
Elapsed time processing this message definition file: 1.781 seconds |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Nov 12, 2012 12:33 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| telus wrote: |
| BIP0235W The message set has no namespace support. The imported XML Schema will be modified to remove namespaces. |
That's not going to help is it?
Especially given that:
| telus wrote: |
| The XML schema cannot be imported because the target namespace has no prefix. |
How much clearer do you need?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| telus |
| Posted: Mon Nov 12, 2012 1:48 pm Post subject: |
|
|
Apprentice
Joined: 01 Nov 2012
Posts: 26
|
Thanks I have imported succesfully by using the command.
Since I have created a message set project and I giving reference to the message set to which I have imported the files.
But in mapping node the attributes are not visible.But If i will do manually than it is visible in the mapping node.
Do I need to do something |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Nov 12, 2012 1:55 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| clean all projects and reopen the mapping node? |
|
| Back to top |
|
|
| telus |
| Posted: Mon Nov 12, 2012 1:57 pm Post subject: |
|
|
Apprentice
Joined: 01 Nov 2012
Posts: 26
|
| I had done so many times. But still the attributes not visible. |
|
| Back to top |
|
|
| telus |
| Posted: Fri Nov 16, 2012 4:25 am Post subject: |
|
|
Apprentice
Joined: 01 Nov 2012
Posts: 26
|
Thanks all.
I am able to do with the command tool provided by message broker.
But now the i come up with other problem.
1.I am using mapping node to map the two XSD's but after import the source and target XSD's I am getting the following error.
| Quote: |
This map is not callable from a node or another map. Correct the use of sources/targets and rebuild the file. |
2. I have checked the XSD in the altova tool and it is opening without any error .
I am not sure what to do know.Any pointer? |
|
| Back to top |
|
|
| kimbert |
| Posted: Fri Nov 16, 2012 5:30 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
|
| Back to top |
|
|
|
|
