| Author |
Message
|
| kotagiriaashish |
 Posted: Sat Aug 06, 2011 12:39 pm Post subject: WSDL Generation Help [Solved] |
 |
|
Disciple
Joined: 06 Aug 2011
Posts: 165
|
Hi guys!!
i am having issues with generation and usage of wsdl files in MB7, these are the steps i am following to generate a wsdl file.
1: New message set project
2: New message definition file from > IBM supplied messages > soap1.1Envilope
3: Ne message definition >Emp_def, added some elements to it.
4: Right click on the message definition and select Generate>WSDL
5: Generate wsdl definition from existing message definitions.
6: generate wsdl as single file.
7: next next .... finish
Wsdl file is being created but the problem i am facing is, when i try to set the SOAP node properties, this wsdl never shows up on the listing, insted i get a "generate new/import" option, OK i generate a new one again!! this time i can see the wsdl in the listing too, if i select it, all the properties get populated correctly, but when i try to run the flow, All hell breaks loose and this exception shows up
"Unable to locate message definition "Emp_def"
Please Please Please Help me, im very stuck at this point this is the same case even if i use a MESSAGE CATALOG file and generate a wsdl...... Even a slightest push will be very appreciated 
Last edited by kotagiriaashish on Tue Aug 09, 2011 5:29 am; edited 1 time in total |
|
| Back to top |
|
 |
| WGerstma |
| Posted: Sat Aug 06, 2011 2:51 pm Post subject: |
|
|
Acolyte
Joined: 18 Jul 2011
Posts: 55
|
Have you added a Project Reference from your Message Flow Project to the MessageSet?
Have you deployed your MessageSet/message Definition with your BAR File? |
|
| Back to top |
|
|
| kotagiriaashish |
| Posted: Sun Aug 07, 2011 3:22 am Post subject: yes i did |
|
|
Disciple
Joined: 06 Aug 2011
Posts: 165
|
| The same error shows up in the test client and on the broker too....is there any thing wrong with the process i am doing? |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sun Aug 07, 2011 3:56 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
How about you post the relevant lines from your event log?
This will give us a lot more detail than the tiny amount you have so far.
For example,
What exactly does
| Quote: |
All hell breaks loose and this exception shows up
|
Mean?
Did the Sky fall in? Did the floor move? Was there a Flood, a Plague of Locusts? What exactly do you mean?
My fortune telling equipment is in for service today...
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| kotagiriaashish |
| Posted: Sun Aug 07, 2011 8:53 am Post subject: smdavies99 Thanks for the reply |
|
|
Disciple
Joined: 06 Aug 2011
Posts: 165
|
Exception Message: Could not find element or attribute "Request".
Exception
| Code: |
Trace:com.ibm.etools.mft.unittest.generator.value.serializer.ValueStructureSerializerException: Could not find element or attribute "Request".
at com.ibm.etools.mft.unittest.generator.value.serializer.XMLValueStructureSerializer.serialize(Unknown Source)
at com.ibm.etools.mft.unittest.generator.utils.XMLValueStructureSerializerHelper.xmlValueElementToString(Unknown Source)
at com.ibm.etools.mft.unittest.core.commchannel.mb.AbstractSendMessageDelegate.sendValueElements(Unknown Source)
at com.ibm.etools.mft.unittest.core.commchannel.mb.AbstractSendMessageDelegate.sendMessage(Unknown Source)
at com.ibm.etools.mft.unittest.core.transport.soap.SOAPHandler.send(Unknown Source)
at com.ibm.etools.mft.unittest.core.commchannel.mb.SendMessageOperation.sendMessage(Unknown Source)
at com.ibm.etools.mft.unittest.core.commchannel.jobs.SendMessageOperationJob.doRun(Unknown Source)
at com.ibm.etools.mft.unittest.core.commchannel.jobs.SendMessageOperationJob.run(Unknown Source)
at org.eclipse.core.internal.jobs.Worker.run(Unknown Source)
Caused by: com.ibm.etools.mft.unittest.generator.value.serializer.ValueStructureSerializerRuntimeException: Could not find element or attribute "Request".
at com.ibm.etools.mft.unittest.generator.value.serializer.XMLValueStructureSerializer.handleChildValueElements(Unknown Source)
at com.ibm.etools.mft.unittest.generator.value.serializer.XMLValueStructureSerializer.handleValueStructure(Unknown Source)
at com.ibm.etools.mft.unittest.generator.value.serializer.XMLValueStructureSerializer.handleChildValueElements(Unknown Source)
at com.ibm.etools.mft.unittest.generator.value.serializer.XMLValueStructureSerializer.handleValueStructure(Unknown Source)
... 9 more |
this is the complete WSDL :
| Code: |
<?xml version="1.0" encoding="UTF-8"?><wsdl:definitions name="SOAP_Msset" targetNamespace="http://tempuri.org/SOAP_Msset" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://tempuri.org/SOAP_Msset" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<xsd:schema targetNamespace="http://tempuri.org/SOAP_Msset" xmlns:mrm="http://tempuri.org/SOAP_Msset">
<xsd:include schemaLocation="Serv.xsd"/>
</xsd:schema>
</wsdl:types>
<wsdl:message name="Operation1_in">
<wsdl:part element="tns:Request" name="Request"/>
</wsdl:message>
<wsdl:message name="Operation1_out">
<wsdl:part element="tns:Resp" name="Resp"/>
</wsdl:message>
<wsdl:message name="Operation1_fault1">
<wsdl:part element="tns:Request" name="Request"/>
</wsdl:message>
<wsdl:portType name="SOAP_MssetPortType">
<wsdl:operation name="Operation1">
<wsdl:input message="tns:Operation1_in" name="Operation1_Input"/>
<wsdl:output message="tns:Operation1_out" name="Operation1_Output"/>
<wsdl:fault message="tns:Operation1_fault1" name="Operation1_Fault"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="SOAP_MssetSOAP_HTTP_Binding" type="tns:SOAP_MssetPortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="Operation1">
<soap:operation soapAction=""""/>
<wsdl:input name="Operation1_Input">
<soap:body parts="Request" use="literal"/>
</wsdl:input>
<wsdl:output name="Operation1_Output">
<soap:body parts="Resp" use="literal"/>
</wsdl:output>
<wsdl:fault name="Operation1_Fault">
<soap:fault name="Operation1_Fault" use="literal"/>
</wsdl:fault>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="SOAP_MssetSOAP_HTTP_Service">
<wsdl:port binding="tns:SOAP_MssetSOAP_HTTP_Binding" name="SOAP_HTTP_Port">
<soap:address location="http://localhost:7800/SOAP_MssetSOAP_HTTP_Service"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
|
this is the XSD SCHEMA of Serv.mxsd
| Code: |
<?xml version="1.0" encoding="UTF-8"?><xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:complexType name="Request">
<xsd:sequence>
<xsd:element name="EmpId" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="Request" type="Request">
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<MRMessage messageDefinition="/0/Request;XSDElementDeclaration$MRObject"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="Resp">
<xsd:sequence>
<xsd:element name="Salary" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="Resp" type="Resp">
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<MRMessage messageDefinition="/0/Resp;XSDElementDeclaration=1$MRObject"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:schema> |
Every thing looks intact.... is there something wrong with my process? please throw some light on this. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sun Aug 07, 2011 10:05 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Please:-
1) Answer my questions (what do you mean by all hell broke loose)
2) Post the eventlog
3) Please, please use CODE Tags around output. It makes things a whole lot easier to read and importantly understand.
you can go back and edit your last post you know.
Until you post the error messages (part of the 'All hell broke loose') we really can't help very much I'm sad to say.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Aug 07, 2011 1:58 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
I put the code tags around for your stuff.
It looks like you may be missing some import statement of some qualifying namespace for the "Request", also note that "Request" is not the same as "Request "...
I'd go in graphical mode for the wsdl editor and try and assign the Request via the drop down...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| kotagiriaashish |
| Posted: Sun Aug 07, 2011 5:57 pm Post subject: |
|
|
Disciple
Joined: 06 Aug 2011
Posts: 165
|
Thanks guys.. this fourm feels like home.....every one is really trying to help.... ill post the log ASASP  |
|
| Back to top |
|
|
| kotagiriaashish |
| Posted: Mon Aug 08, 2011 6:43 am Post subject: |
|
|
Disciple
Joined: 06 Aug 2011
Posts: 165
|
In case this is not the log you are looking for, i got this log by getting the user trace the code is below...
I fairly cant make head or tail of it  is this what you really want smdavies99/fjb_saper??
| Code: |
mqsichangetrace WBRK61_DEFAULT_BROKER -u -e default -l debug -r
mqsireadlog WBRK61_DEFAULT_BROKER -u -e default -o C:\Books\Trace.xml
mqsiformatlog -i C:\Books\Trace.xml -o C:\Books\Trace.xml
|
| Code: |
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<UserTraceLog uuid="UserTraceLog" userTraceLevel="none" traceLevel="none" userTraceFilter="debugTrace" traceFilter="none" fileSize="4194304" bufferSize="0" fileMode="safe">
<UserTrace timestamp="2011-08-08 14:37:07.576629" thread="2608" function="ImbConfigurationNode::evaluate" type="ComIbmConfigurationNode" name="ConfigurationNode" label="ConfigurationMessageFlow.ConfigurationNode" text="'Configuration changed successfully and committed to persistent store'" catalog="BIPv610" number="4040" file="F:\build\S610_P\src\DataFlowEngine\ImbConfigurationNode.cpp" line="371">
<Insert type="string">'default'</Insert>
<Insert type="string">'98c0a152-3001-0000-0080-f4102838f1d2'</Insert>
<Insert type="string">ConfigurationMessageFlow.ConfigurationNode</Insert>
</UserTrace>
<UserTrace timestamp="2011-08-08 14:37:07.577366" thread="2608" function="ImbMqOutputNode::putMessage" type="ComIbmMQOutputNode" name="OutputNode" label="ConfigurationMessageFlow.outputNode" text="'MQPUT issued to put message to the specified output queue'" catalog="BIPv610" number="2638" file="F:\build\S610_P\src\DataFlowEngine\ImbMqOutputNode.cpp" line="2229">
<Insert type="string">'WBRK61_DEFAULT_QUEUE_MANAGER'</Insert>
<Insert type="string">'SYSTEM.BROKER.EXECUTIONGROUP.REPLY'</Insert>
<Insert type="integer">0</Insert>
<Insert type="integer">0</Insert>
<Insert type="string">ConfigurationMessageFlow.outputNode</Insert>
</UserTrace>
<UserTrace timestamp="2011-08-08 14:37:07.577447" thread="2608" function="ImbMqOutputNode::putMessage" type="ComIbmMQOutputNode" name="OutputNode" label="ConfigurationMessageFlow.outputNode" text="'Message received and queued successfully'" catalog="BIPv610" number="2622" file="F:\build\S610_P\src\DataFlowEngine\ImbMqOutputNode.cpp" line="2342">
<Insert type="string">'WBRK61_DEFAULT_QUEUE_MANAGER'</Insert>
<Insert type="string">'SYSTEM.BROKER.EXECUTIONGROUP.REPLY'</Insert>
<Insert type="string">ConfigurationMessageFlow.outputNode</Insert>
</UserTrace>
<Information timestamp="2011-08-08 14:37:07.577761" thread="2608" function="ImbConfigurationNode::evaluate" text="'Execution Group finished with administration message.'" catalog="BIPv610" number="2154" file="F:\build\S610_P\src\DataFlowEngine\ImbConfigurationNode.cpp" line="493"/>
<UserTrace timestamp="2011-08-08 14:37:24.184787" thread="2608" function="ImbCommonInputNode::run" type="ComIbmMQInputNode" name="InputNode" label="ConfigurationMessageFlow.InputNode" text="'Dequeued message and propagating to output terminal'" catalog="BIPv610" number="2632" file="F:\build\S610_P\src\DataFlowEngine\ImbCommonInputNode.cpp" line="1609">
<Insert type="string">ConfigurationMessageFlow.InputNode</Insert>
</UserTrace>
<UserTrace timestamp="2011-08-08 14:37:24.184936" thread="2608" function="ImbRootParser::parseNextItem" type="ComIbmMQInputNode" name="InputNode" label="ConfigurationMessageFlow.InputNode" text="'Created parser'" catalog="BIPv610" number="6060" file="F:\build\S610_P\src\DataFlowEngine\ImbRootParser.cpp" line="429">
<Insert type="string">'Properties'</Insert>
<Insert type="integer">0</Insert>
<Insert type="integer">0</Insert>
<Insert type="string">ConfigurationMessageFlow.InputNode</Insert>
</UserTrace>
<UserTrace timestamp="2011-08-08 14:37:24.184978" thread="2608" function="ImbRootParser::parseNextItem" type="ComIbmMQInputNode" name="InputNode" label="ConfigurationMessageFlow.InputNode" text="'Created parser'" catalog="BIPv610" number="6061" file="F:\build\S610_P\src\DataFlowEngine\ImbRootParser.cpp" line="571">
<Insert type="string">'MQMD'</Insert>
<Insert type="integer">0</Insert>
<Insert type="integer">364</Insert>
<Insert type="string">'MQHMD'</Insert>
<Insert type="string">ConfigurationMessageFlow.InputNode</Insert>
</UserTrace>
<UserTrace timestamp="2011-08-08 14:37:24.185062" thread="2608" function="ImbRootParser::parseNextItem" type="ComIbmMQInputNode" name="InputNode" label="ConfigurationMessageFlow.InputNode" text="'Created parser'" catalog="BIPv610" number="6061" file="F:\build\S610_P\src\DataFlowEngine\ImbRootParser.cpp" line="571">
<Insert type="string">'XMLS'</Insert>
<Insert type="integer">364</Insert>
<Insert type="integer">244</Insert>
<Insert type="string">'XMLS'</Insert>
<Insert type="string">ConfigurationMessageFlow.InputNode</Insert>
</UserTrace>
</UserTraceLog> |
|
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Aug 08, 2011 6:54 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| kotagiriaashish wrote: |
| In case this is not the log you are looking for, i got this log by getting the user trace the code is below... |
I'd try:
| Code: |
mqsichangetrace WBRK61_DEFAULT_BROKER -u -e default -l debug -r
mqsireadlog WBRK61_DEFAULT_BROKER -u -e default -o C:\Books\Trace.xml
mqsiformatlog -i C:\Books\Trace.xml -o C:\Books\Trace.txt
|
and post the txt file. This should give you something a bit more readable.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| kotagiriaashish |
| Posted: Mon Aug 08, 2011 8:48 am Post subject: |
|
|
Disciple
Joined: 06 Aug 2011
Posts: 165
|
Guys Guys Guys...... the problem raises when i try to test the flow in the test client and when i use another flow to consume the services provided by first flow which has[soap input > compute > soap reply] that works fine, and no one is concentrating on my first problem.....
i am unable to browse the wsdl file in the soap input properties when i generate it using the [Generatewsdl > from message set].
secondly the flow fails when i generate WSDL from the soap input node options[import/generate new] and test it using the test client....
and Vitor....
| Code: |
Timestamps are formatted in local time, 420 minutes before GMT.
Trace written by version ; formatter version 6105
2011-08-08 08:20:47.086471 2608 UserTrace BIP4040I: The Execution Group ''default'' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
2011-08-08 08:20:47.086982 2608 UserTrace BIP2638I: The MQ output node 'ConfigurationMessageFlow.outputNode' attempted to write a message to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' connected to queue manager ''WBRK61_DEFAULT_QUEUE_MANAGER''. The MQCC was '0' and the MQRC was '0'.
2011-08-08 08:20:47.087032 2608 UserTrace BIP2622I: Message successfully output by output node 'ConfigurationMessageFlow.outputNode' to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' on queue manager ''WBRK61_DEFAULT_QUEUE_MANAGER''.
2011-08-08 08:20:47.087356 2608 Information BIP2154I: Execution group finished with Configuration message.
A command response will be sent to the broker.
No user action required.
2011-08-08 08:21:00.135730 2608 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'ConfigurationMessageFlow.InputNode'.
2011-08-08 08:21:00.135899 2608 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2011-08-08 08:21:00.135949 2608 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
2011-08-08 08:21:00.136133 2608 UserTrace BIP6061I: Parser type ''XMLS'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '244' bytes beginning at offset '364'. Parser type selected based on value ''XMLS'' from previous parser.
Threads encountered in this trace:
2608
|
|
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Aug 08, 2011 8:57 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| kotagiriaashish wrote: |
| Guys Guys Guys...... the problem raises when i try to test the flow in the test client and when i use another flow to consume the services provided by first flow which has[soap input > compute > soap reply] that works fine, and no one is concentrating on my first problem..... |
Breathe.
| kotagiriaashish wrote: |
| i am unable to browse the wsdl file in the soap input properties when i generate it using the [Generatewsdl > from message set]. |
There was a suggestion about that earlier. How did that work out?
| kotagiriaashish wrote: |
| secondly the flow fails when i generate WSDL from the soap input node options[import/generate new] and test it using the test client.... |
Yes, but fails how? With what error messages? Just the one you posted earlier? If so, how did the previous suggestion work out?
| kotagiriaashish wrote: |
and Vitor....
| Code: |
Timestamps are formatted in local time, 420 minutes before GMT.
Trace written by version ; formatter version 6105
2011-08-08 08:20:47.086471 2608 UserTrace BIP4040I: The Execution Group ''default'' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
2011-08-08 08:20:47.086982 2608 UserTrace BIP2638I: The MQ output node 'ConfigurationMessageFlow.outputNode' attempted to write a message to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' connected to queue manager ''WBRK61_DEFAULT_QUEUE_MANAGER''. The MQCC was '0' and the MQRC was '0'.
2011-08-08 08:20:47.087032 2608 UserTrace BIP2622I: Message successfully output by output node 'ConfigurationMessageFlow.outputNode' to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' on queue manager ''WBRK61_DEFAULT_QUEUE_MANAGER''.
2011-08-08 08:20:47.087356 2608 Information BIP2154I: Execution group finished with Configuration message.
A command response will be sent to the broker.
No user action required.
2011-08-08 08:21:00.135730 2608 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'ConfigurationMessageFlow.InputNode'.
2011-08-08 08:21:00.135899 2608 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2011-08-08 08:21:00.135949 2608 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
2011-08-08 08:21:00.136133 2608 UserTrace BIP6061I: Parser type ''XMLS'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '244' bytes beginning at offset '364'. Parser type selected based on value ''XMLS'' from previous parser.
Threads encountered in this trace:
2608
|
|
Now isn't that better? Easier to read?
It also shows the default execution group receiving a deploy and something called ConfigurationMessageFlow reading a message off a queue. It doesn't show a SOAPInput node, or any abends, or indeed anything else of any use to us in helping identify your problem.
Use the same technique to trace the problem flow, and post that.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Aug 08, 2011 9:05 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
And the OP still has not explained what they meant by 'All hell broke loose'.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| kotagiriaashish |
| Posted: Mon Aug 08, 2011 9:14 am Post subject: |
|
|
Disciple
Joined: 06 Aug 2011
Posts: 165
|
| All hell broke loose -> Exception throws up stopping the flow and the input message vanishes, half completed files are written and processed by scripts resulting in a unstable database..... this is a very big flow the results i am showing you is a sample wsdl and sample soap input.....hope that explains hell breaking loose.... |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Aug 08, 2011 9:23 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
This is on a test system isn't it?
If so then this is a risk with any system.
If not then I'm glad that I don't work at your place.
Some basic questions
1) Do you not have DB backups?
2) What are your backout plans.
and so much more but this is getting well off the immediate topic.
It sound like you are trying to run before you can walk. The key to any systems integration project is to take 'small steps'. I learnt this 30+ years ago and is very good advice.
If you have lost your input message then that is a 'feature' of your design and choice of components. It can be overcome but being honest, from what I've seen so far I don't think you have the skills/training to do it.
Is there a 'broker expert' in your shop that you can turn to for help. We (in this forum) can only do so much.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
|
|
