| Author | 
		  Message
		 | 
		
		  | vikas.bhu | 
		  
		    
			  
				 Posted: Mon Oct 04, 2010 10:07 pm    Post subject: problem calling webservice through mttprequest node.. | 
				     | 
			   
			 
		   | 
		
		
		   Disciple
 
 Joined: 17 May 2009 Posts: 159
  
  | 
		  
		    
			  
				Hi.
 
 
my flow is like Mqinput->compute->RCD->httprequest->tracenodde after the out,error and faliure terminal.
 
 
in the error terminal I am seeing folllowing error..
 
 
 (
 
  (0x01000000):Properties         = (
 
    (0x03000000):MessageSet      = ''
 
    (0x03000000):MessageType     = ''
 
    (0x03000000):MessageFormat   = ''
 
    (0x03000000):Encoding        = 546
 
    (0x03000000):CodedCharSetId  = 1208
 
    (0x03000000):Transactional   = FALSE
 
    (0x03000000):Persistence     = FALSE
 
    (0x03000000):CreationTime    = GMTTIMESTAMP '2010-10-05 05:45:30.620'
 
    (0x03000000):ExpirationTime  = -1
 
    (0x03000000):Priority        = 0
 
    (0x03000000):ReplyIdentifier = X'000000000000000000000000000000000000000000000000'
 
    (0x03000000):ReplyProtocol   = 'MQ'
 
    (0x03000000):Topic           = NULL
 
    (0x03000000):ContentType     = 'text/xml; charset=utf-8'
 
  )
 
  (0x01000000):HTTPRequestHeader  = (
 
    (0x03000000):Content-Length = '2206'
 
    (0x03000000):Host           = 'xww.xip-stage.world.xerox.com'
 
    (0x03000000):SOAPAction     = 'QueryDataUnit'
 
    (0x03000000):Content-Type   = 'text/xml; charset=utf-8'
 
  )
 
  (0x01000000):HTTPResponseHeader = (
 
    (0x03000000):X-Original-HTTP-Status-Line = 'HTTP/1.1 500 Internal Server Error'
 
    (0x03000000):X-Original-HTTP-Status-Code = 500
 
    (0x03000000):Connection                  = 'close'
 
    (0x03000000):Date                        = 'Tue, 05 Oct 2010 05:45:17 GMT'
 
    (0x03000000):Server                      = 'Microsoft-IIS/6.0, WebSphere Application Server/7.0'
 
    (0x03000000):Content-Type                = 'text/xml; charset=utf-8'
 
    (0x03000000):Content-Length              = '558'
 
    (0x03000000):Content-Language            = 'en-US'
 
    (0x03000000):Set-Cookie                  = 'JSESSIONID=00007VvVjJ2SJ2-psnbG0-m5xOi:-1; Path=/'
 
    (0x03000000):Expires                     = 'Thu, 01 Dec 1994 16:00:00 GMT'
 
    (0x03000000):Cache-Control               = 'no-cache="set-cookie, set-cookie2"'
 
  )
 
  (0x01000000):BLOB               = (
 
    (0x03000000):UnknownParserName = ''
 
    (0x03000000):BLOB              = X'3c3f786d6c2076657273696f6e3d27312e302720656e636f64696e673d275554462d38273f3e0d0a3c534f41502d454e563a456e76656c6f706520786d6c6e733a534f41502d454e563d22687474703a2f2f736368656d61732e786d6c736f61702e6f72672f736f61702f656e76656c6f70652f2220786d6c6e733a7873693d22687474703a2f2f7777772e77332e6f72672f323030312f584d4c536368656d612d696e7374616e63652220786d6c6e733a7873643d22687474703a2f2f7777772e77332e6f72672f323030312f584d4c536368656d61223e0d0a3c534f41502d454e563a426f64793e0d0a3c534f41502d454e563a4661756c743e0d0a3c6661756c74636f64653e534f41502d454e563a5365727665723c2f6661756c74636f64653e0d0a3c6661756c74737472696e673e73657276696365202661706f733b687474703a2f2f786d6c2e6e616d657370616365732e7865726f782e636f6d2f696d2f7869702f73657276696365732f65717569706d656e7441737365742f6d657373616765732f2661706f733b20756e6b6e6f776e3c2f6661756c74737472696e673e0d0a3c6661756c746163746f723e2f53303134335f496e7374616c6c65644571756970496e666f2f736572766c65742f6d657373616765726f757465723c2f6661756c746163746f723e0d0a3c2f534f41502d454e563a4661756c743e0d0a0d0a3c2f534f41502d454e563a426f64793e0d0a3c2f534f41502d454e563a456e76656c6f70653e0d0a'
 
  )
 
)
 
 
 
now I am not able to track that what is the problem..because the url which I am using in http request node is active(means using soapui I am getting folowing fault resonse 
 
 
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
 
   <SOAP-ENV:Body>
 
      <SOAP-ENV:Fault>
 
         <faultcode>SOAP-ENV:Server</faultcode>
 
         <faultstring>service 'http://xml.namespaces.xerox.com/im/xip/services/equipmentAsset/messages/' unknown</faultstring>
 
         <faultactor>/S0143_InstalledEquipInfo/servlet/messagerouter</faultactor>
 
      </SOAP-ENV:Fault>
 
   </SOAP-ENV:Body>
 
</SOAP-ENV:Envelope>
 
 )
 
 
I RCD message is properly being validated..and I have used WSDL and xsd to to create the message set.
 
 
what may be the problem? | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | mgk | 
		  
		    
			  
				 Posted: Tue Oct 05, 2010 12:30 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Padawan
 
 Joined: 31 Jul 2003 Posts: 1647
  
  | 
		  
		    
			  
				But the BLOB returned contains the same information returned as the SOAP UI did:
 
 
   
	| Code: | 
   
  
	<?xml version='1.0' encoding='UTF-8'?>
 
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchem
 
a-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
 
<SOAP-ENV:Body>
 
<SOAP-ENV:Fault>
 
<faultcode>SOAP-ENV:Server</faultcode>
 
<faultstring>service 'http://xml.namespaces.xerox.com/im/xip/services/equipmentAsset/messages/' unknown</fault
 
string>
 
<faultactor>/S0143_InstalledEquipInfo/servlet/messagerouter</faultactor>
 
</SOAP-ENV:Fault>
 
 
</SOAP-ENV:Body>
 
</SOAP-ENV:Envelope> | 
   
 
 
 
If you want this as XML have you tried setting the parser to XMLNSC on the node? _________________ MGK
 
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | WMBDEV1 | 
		  
		    
			  
				 Posted: Tue Oct 05, 2010 1:09 am    Post subject: Re: problem calling webservice through mttprequest node.. | 
				     | 
			   
			 
		   | 
		
		
		   Sentinel
 
 Joined: 05 Mar 2009 Posts: 888 Location: UK 
  | 
		  
		    
			  
				I think i'd be asking the WAS boys why they are returning the 500 error code:
 
   
	| Code: | 
   
  
	
 
  (0x01000000):HTTPResponseHeader = (
 
    (0x03000000):X-Original-HTTP-Status-Line = 'HTTP/1.1 500 Internal Server Error'
 
    (0x03000000):X-Original-HTTP-Status-Code = 500
 
 | 
   
 
 | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | mqjeff | 
		  
		    
			  
				 Posted: Tue Oct 05, 2010 2:21 am    Post subject: Re: problem calling webservice through mttprequest node.. | 
				     | 
			   
			 
		   | 
		
		
		   Grand Master
 
 Joined: 25 Jun 2008 Posts: 17447
  
  | 
		  
		    
			  
				
   
	| WMBDEV1 wrote: | 
   
  
	| I think i'd be asking the WAS boys why they are returning the 500 error code: | 
   
 
 
Because it's returning a SOAP Fault indicating that the SOAP Request did not match a known service.
 
 
Possibly because a namespace somewhere ends with a / when it shouldn't or vice versa, or otherwise because the request message is not correct. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | WMBDEV1 | 
		  
		    
			  
				 Posted: Tue Oct 05, 2010 2:42 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Sentinel
 
 Joined: 05 Mar 2009 Posts: 888 Location: UK 
  | 
		  
		    
			  
				| Quite, In asking the WAS boys as to why they could confirm the real value to use and that the service has been correctly deployed. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | vikas.bhu | 
		  
		    
			  
				 Posted: Tue Oct 05, 2010 10:11 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Disciple
 
 Joined: 17 May 2009 Posts: 159
  
  | 
		  
		    
			  
				I have tried with XMLNC option but the result is as..privious one
 
 
bhu Posted: Mon Oct 04, 2010 10:07 pm    Post subject: problem calling webservice through mttprequest node.. 
 
 
 
Hi. 
 
 
my flow is like Mqinput->compute->RCD->httprequest->tracenodde after the out,error and faliure terminal. 
 
 
in the error terminal I am seeing folllowing error.. 
 
 
( 
 
(0x01000000):Properties = ( 
 
(0x03000000):MessageSet = '' 
 
(0x03000000):MessageType = '' 
 
(0x03000000):MessageFormat = '' 
 
(0x03000000):Encoding = 546 
 
(0x03000000):CodedCharSetId = 1208 
 
(0x03000000):Transactional = FALSE 
 
(0x03000000):Persistence = FALSE 
 
(0x03000000):CreationTime = GMTTIMESTAMP '2010-10-05 05:45:30.620' 
 
(0x03000000):ExpirationTime = -1 
 
(0x03000000):Priority = 0 
 
(0x03000000):ReplyIdentifier = X'000000000000000000000000000000000000000000000000' 
 
(0x03000000):ReplyProtocol = 'MQ' 
 
(0x03000000):Topic = NULL 
 
(0x03000000):ContentType = 'text/xml; charset=utf-8' 
 
) 
 
(0x01000000):HTTPRequestHeader = ( 
 
(0x03000000):Content-Length = '2206' 
 
(0x03000000):Host = 'xww.xip-stage.world.xerox.com' 
 
(0x03000000):SOAPAction = 'QueryDataUnit' 
 
(0x03000000):Content-Type = 'text/xml; charset=utf-8' 
 
) 
 
(0x01000000):HTTPResponseHeader = ( 
 
(0x03000000):X-Original-HTTP-Status-Line = 'HTTP/1.1 500 Internal Server Error' 
 
(0x03000000):X-Original-HTTP-Status-Code = 500 
 
(0x03000000):Connection = 'close' 
 
(0x03000000):Date = 'Tue, 05 Oct 2010 05:45:17 GMT' 
 
(0x03000000):Server = 'Microsoft-IIS/6.0, WebSphere Application Server/7.0' 
 
(0x03000000):Content-Type = 'text/xml; charset=utf-8' 
 
(0x03000000):Content-Length = '558' 
 
(0x03000000):Content-Language = 'en-US' 
 
(0x03000000):Set-Cookie = 'JSESSIONID=00007VvVjJ2SJ2-psnbG0-m5xOi:-1; Path=/' 
 
(0x03000000):Expires = 'Thu, 01 Dec 1994 16:00:00 GMT' 
 
(0x03000000):Cache-Control = 'no-cache="set-cookie, set-cookie2"' 
 
) 
 
(0x01000000):BLOB = ( 
 
(0x03000000):UnknownParserName = '' 
 
(0x03000000):BLOB = X'3c3f786d6c2076657273696f6e3d27312e302720656e636f64696e673d275554462d38273f3e0d0a3c534f41502d454e563a456e76656c6f706520786d6c6e733a534f41502d454e563d22687474703a2f2f736368656d61732e786d6c736f61702e6f72672f736f61702f656e76656c6f70652f2220786d6c6e733a7873693d22687474703a2f2f7777772e77332e6f72672f323030312f584d4c536368656d612d696e7374616e63652220786d6c6e733a7873643d22687474703a2f2f7777772e77332e6f72672f323030312f584d4c536368656d61223e0d0a3c534f41502d454e563a426f64793e0d0a3c534f41502d454e563a4661756c743e0d0a3c6661756c74636f64653e534f41502d454e563a5365727665723c2f6661756c74636f64653e0d0a3c6661756c74737472696e673e73657276696365202661706f733b687474703a2f2f786d6c2e6e616d657370616365732e7865726f782e636f6d2f696d2f7869702f73657276696365732f65717569706d656e7441737365742f6d657373616765732f2661706f733b20756e6b6e6f776e3c2f6661756c74737472696e673e0d0a3c6661756c746163746f723e2f53303134335f496e7374616c6c65644571756970496e666f2f736572766c65742f6d657373616765726f757465723c2f6661756c746163746f723e0d0a3c2f534f41502d454e563a4661756c743e0d0a0d0a3c2f534f41502d454e563a426f64793e0d0a3c2f534f41502d454e563a456e76656c6f70653e0d0a' 
 
) 
 
)  
 
 
 
 
one more question why it is still saying unknown parser name..? | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | 
		    
		   |