Author |
Message
|
kumar.MBMQ |
Posted: Mon May 04, 2015 4:05 am Post subject: SOAP INPUT NODE -> compute ->SOAP REQUEST NODE -> |
|
|
Voyager
Joined: 06 May 2011 Posts: 93
|
I want to write a simple message flow , and I want to simply forward the request to SOAP Request node without modifying anyting .
the soapinput node contains the same wsdl as SOAP Request node.
except the soap:address location in the WSDL file.
SOAP Input node's soap:address location is localhost:7800/service3 where as
SOAP Request node's soap:address location is at 98.33.22.3/service3
SOAP INPUT NODE -> compute ->SOAP REQUEST NODE -> compute ->SOAP Reply node
can i dev a message flow as above ?
Please suggest |
|
Back to top |
|
 |
Vitor |
Posted: Mon May 04, 2015 4:53 am Post subject: Re: SOAP INPUT NODE -> compute ->SOAP REQUEST NODE -& |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
kumar.MBMQ wrote: |
can i dev a message flow as above ? |
Yes.
I struggle to imagine why you'd want to. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
mqjeff |
Posted: Mon May 04, 2015 4:56 am Post subject: Re: SOAP INPUT NODE -> compute ->SOAP REQUEST NODE -& |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
kumar.MBMQ wrote: |
soap:address location in the WSDL file. |
That really doesn't control much.
I can think of easier ways to provide a point of security or monitoring to a SOAP endpoint, but perhaps you have a solid business requirement. |
|
Back to top |
|
 |
kumar.MBMQ |
Posted: Mon May 04, 2015 5:57 am Post subject: |
|
|
Voyager
Joined: 06 May 2011 Posts: 93
|
But When i try to deploy below error is thrown,
BIP2087E: Broker 'Broker1' was unable to process the internal configuration message.
The entire internal configuration message failed to be processed successfully.
Use the messages following this message to determine the reasons for the failure. If the problem cannot be resolved after reviewing these messages, contact your IBM Support center. Enabling service trace may help determine the cause of the failure.
BIP4041E: Execution group 'eg1' received an administration request that encountered an exception.
While attempting to process an administration request, an exception was encountered. No updates have been made to the configuration of the execution group.
Review related error messages to determine why the administration request failed.
BIP5044E: A failure occurred while the execution group was preparing the XML and DFDL schema files that are contained in the application POC3.
A failure occurred while the execution group was preparing XML and DFDL schema files for use. The deployment of the named application has failed, and the deployment will be rolled back.
Review previous messages to find out why the error occurred. Be aware that DFDL schema files must also be valid XML Schema files, and that all DFDL schema files are prepared for use by the XMLNSC domain before being prepared for use by the DFDL domain.
BIP5047E: While checking the XML and DFDL schema files that are in the current deployment scope, the file IBMdefined\soap.xsd was found multiple times. Instances of this file were found to have the same path, but different content.
Files in the 'IBMdefined' and 'RemoteFiles' folders can exist multiple times within an application or execution group (when multiple libraries are deployed directly to the execution group), but all files that are contained in these folders, and have the same path, must be identical.
Locate all instances of the specified file and update them so that all instances that have the same path are identical.
BIP2871I: The request made by user 'ttJangitin' to 'deploy' the resource 'C:/Users/ttJangitiN/IBM/IntegrationToolkit90/Pocs/BARfiles/Barfilenet.bar' of type 'BAR' on parent 'eg1' of type 'ExecutionGroup' has the status of 'FAILED'. |
|
Back to top |
|
 |
Vitor |
Posted: Mon May 04, 2015 6:11 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
kumar.MBMQ wrote: |
But When i try to deploy below error is thrown, |
Yes because apparently
kumar.MBMQ wrote: |
BIP5047E: While checking the XML and DFDL schema files that are in the current deployment scope, the file IBMdefined\soap.xsd was found multiple times. Instances of this file were found to have the same path, but different content.
Files in the 'IBMdefined' and 'RemoteFiles' folders can exist multiple times within an application or execution group (when multiple libraries are deployed directly to the execution group), but all files that are contained in these folders, and have the same path, must be identical. |
and you have to
kumar.MBMQ wrote: |
Locate all instances of the specified file and update them so that all instances that have the same path are identical. |
This is nothing to do with the rather bizzare and unnecessary flow you're developing, and everything to do with how you've developed it.
Fix it like you'd fix any other flow that won't deploy. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
kumar.MBMQ |
Posted: Mon May 04, 2015 6:21 am Post subject: |
|
|
Voyager
Joined: 06 May 2011 Posts: 93
|
Thanks,
Last edited by kumar.MBMQ on Mon May 04, 2015 6:53 am; edited 1 time in total |
|
Back to top |
|
 |
mqjeff |
Posted: Mon May 04, 2015 6:21 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Also, upgrade your toolkit to the latest FP. |
|
Back to top |
|
 |
Vitor |
Posted: Mon May 04, 2015 6:28 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
kumar.MBMQ wrote: |
still error is thrown
XSD: There is no xmlns declaration for namespace 'http://vvvn.com/CDM/MRServiceRequest/1/0/1/14' |
And why would that be do you think?
It's also (as my most worthy associate points out) a good idea to stay current on maintenance. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
|