ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Messageflow is not working due to restrictions in MRM

Post new topic  Reply to topic
 Messageflow is not working due to restrictions in MRM « View previous topic :: View next topic » 
Author Message
somjyoti
PostPosted: Tue Jan 29, 2008 5:24 am    Post subject: Messageflow is not working due to restrictions in MRM Reply with quote

Newbie

Joined: 10 Jan 2008
Posts: 9

Hi

I am using MessageBroker v6.1.

The scenario is something like, FileInput picks a comma separated flat file from a particular location, validates the message coming in using the Messagesets and put it in MQ.

For that I have created a Message Set in MRM domain. I have also created a Message definition(mxsd) file making each field of type Simple Type Restriction and added the value constraints for each field as well.
Now when I run the message flow, sometimes it is not picking the file or it flows through the message flow and fails to put it in MQ or the debug itself is getting terminated very immediately after the flow starts.

But when i make it a normal simple type without any restrictions it is working fine. Also here i couldnot validate my incoming file against restrictions.

Can anyone help me in sorting out this issue?

Also attached my mxsd file:


<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:complexType name="contactLoggingRecordsType">
<xsd:sequence>
<xsd:element name="CONTACT_REF_NO">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="12"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CONTACT_TYPE">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="WPRL"/>
<xsd:enumeration value="WNOW"/>
<xsd:enumeration value="WBLE"/>
<xsd:enumeration value="SDBC"/>
<xsd:enumeration value="SFIN"/>
<xsd:enumeration value="SFEX"/>
<xsd:enumeration value="WQGL"/>
<xsd:enumeration value="WFIN"/>
<xsd:enumeration value="WFEX"/>
<xsd:enumeration value="WPRH"/>
<xsd:enumeration value="SSME"/>
<xsd:enumeration value="POLR"/>
<xsd:enumeration value="POLS"/>
<xsd:enumeration value="POTH"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CONTACT_DATE" type="xsd:date">
</xsd:element>
<xsd:element name="CONTACT_TIME">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="\d\d:\d\d"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element minOccurs="0" name="BULLETIN_REF" nillable="true">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0"/>
<xsd:maxLength value="9"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element default="0" minOccurs="0" name="POINT_X" nillable="true" type="xsd:double"/>
<xsd:element default="0" minOccurs="0" name="POINT_Y" nillable="true" type="xsd:double"/>
<xsd:element minOccurs="0" name="OS_APR" nillable="true">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0"/>
<xsd:maxLength value="18"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element default="0" minOccurs="0" name="PROPERTY_NUM" nillable="true">
<xsd:simpleType>
<xsd:restriction base="xsd:int">
<xsd:totalDigits value="9"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element minOccurs="0" name="ADDRESS_1" nillable="true">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0"/>
<xsd:maxLength value="30"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element minOccurs="0" name="ADDRESS_2" nillable="true">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0"/>
<xsd:maxLength value="30"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element minOccurs="0" name="ADDRESS_3" nillable="true">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0"/>
<xsd:maxLength value="30"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element minOccurs="0" name="ADDRESS_4" nillable="true">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0"/>
<xsd:maxLength value="30"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element minOccurs="0" name="ADDRESS_5" nillable="true">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0"/>
<xsd:maxLength value="30"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element minOccurs="0" name="POSTCODE" nillable="true">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0"/>
<xsd:maxLength value="10"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="contactLoggingMessageType">
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<tdsStructRep delimiter="&lt;CR&gt;&lt;LF&gt;" messageSetDefaultRep="CSV"/>
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="contactLoggingRecords" type="contactLoggingRecordsType">
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<tdsElemRep messageSetDefaultRep="CSV" precision="-1"/>
<tdsInclRep messageSetDefaultRep="CSV" repeatingElementDelimiter="&lt;CR&gt;&lt;LF&gt;"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="contactLoggingMessage" type="contactLoggingMessageType">
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<MRMessage messageDefinition="/0/contactLoggingMessage;XSDElementDeclaration$MRObject"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:schema>



Regards
arunkarthik b
Back to top
View user's profile Send private message
AKARTHIK
PostPosted: Tue Feb 05, 2008 3:49 am    Post subject: Re: Messageflow is not working due to restrictions in MRM Reply with quote

Newbie

Joined: 29 Jan 2008
Posts: 3

I faced the same problem. You cannot have a date field with restriction in MRM domain.

akarthik
Back to top
View user's profile Send private message
kimbert
PostPosted: Tue Feb 05, 2008 7:57 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

AKARTHIK said:
Quote:
You cannot have a date field with restriction in MRM domain
Not true. There may be limitations, but you can certainly have enumerations, min and max inclusive facets etc. What did you mean to say?

somjyoti said:
Quote:
Now when I run the message flow, sometimes it is not picking the file or it flows through the message flow and fails to put it in MQ or the debug itself is getting terminated very immediately after the flow starts.
Please switch on user trace, and then describe your problem(s) with reference to actual error messages.

Quote:
Also here i could not validate my incoming file against restrictions.
I don't know what that means. Please explain.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Messageflow is not working due to restrictions in MRM
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.