| Author | 
		  Message
		 | 
		
		  | TBS | 
		  
		    
			  
				 Posted: Tue Jun 26, 2007 10:39 pm    Post subject: HTTPRequest and SSL | 
				     | 
			   
			 
		   | 
		
		
		   Centurion
 
 Joined: 29 Jan 2007 Posts: 143 Location: Hillerød / Denmark 
  | 
		  
		    
			  
				I have some problem regarding a SSL connection from the WMB that use HTTPRequest with SSL and I have some question about  HTTPRequest and SSL. on  WMB v.6 running on a Windows server.
 
 
I have put the keytrust and all the certs the file  %MQSI_FILEPATH%\jre\lib\security\cacerts. In the same file name "cacerts"  Ok ?   
 
The HTTPRequest is customized with the URL://
 
The HTTPRequest use JSSE implementation and the way off telling WMB where the keyStore and trustStore is  I have created a enviromentvariable IBM_JAVA_OPTIONS=
 
 -Djavax.net.ssl.keyStore=D:\WMB\jre\lib\security\cacerts -Djavax.net.ssl.keyStorePassword=changeit -Djavax.net.ssl.keyStoreType=JKS -Djavax.net.ssl.trustStore=D:\WMB\jre\lib\security\cacerts -Djavax.net.ssl.trustStorePassword=changeit -Djavax.net.ssl.trustStoreType=JKS
 
 
Is there a norther way of telling WMB where the keyStore, trustStore and password  is ?
 
 
Where do the debug information go when i  write IBM_JAVA_OPTIONS= -Djavax.net.debug=all   ?
 
 
 
From the Event log:  
 
 
( BKMQPWBI04.EKO ) An HTTP error occurred. The HTTP Request-Line was: ''POST /KMD.HW.EWSEarlyRetirementCitizenList.WS/Service.asmx HTTP/1.0
 
''.   
 
 
The HTTP Request Header bitstream (if any) to be used was: ''436f6e74656e742d4c656e6774683a203537300d0a534f4150416374696f6e3a2068747470733a2f2f696e74657773776c62732d776d2e6b6d642e646b2f4b4d442e48572e4557534561726c795265746972656d656e74436974697a656e4c6973742e57532f4765744c6973740d0a436f6e74656e742d547970653a20746578742f786d6c3b20636861727365743d7574662d380d0a486f73743a20696e74657773776c62732d776d2e6b6d642e646b0d0a0d0a''. The HTTP Request Message Body bitstream (if any) to be used was: ''3c3f786d6c2076657273696f6e3d22312e30223f3e3c746e733a456e76656c6f706520786d6c6e733a746e733d22687474703a2f2f736368656d61732e786d6c736f61702e6f72672f736f61702f656e76656c6f70652f2220786d6c6e733a6370723d22687474703a2f2f7265702e6f696f2e646b2f6370722e646b2f786d6c2f736368656d61732f636f72652f323030352f30332f31382f2220786d6c6e733a6b6d64313d22687474703a2f2f7265702e6f696f2e646b2f6b6d642e646b2f736f6369616c2f786d6c2f736368656d61732f323030352f30362f31332f2220786d6c6e733a6b6d64323d22687474703a2f2f7265702e6f696f2e646b2f6b6d642e646b2f736f6369616c2f786d6c2f736368656d61732f323030362f30312f31322f2220786d6c6e733a7873643d22687474703a2f2f7777772e77332e6f72672f323030312f584d4c536368656d612220786d6c6e733a4e53313d22687474703a2f2f7265702e6f696f2e646b2f6b6d642e646b2f736f6369616c2f786d6c2f7773646c2f323030362f30372f31332220786d6c6e733a7873693d22687474703a2f2f7777772e77332e6f72672f323030312f584d4c536368656d612d696e7374616e6365223e3c746e733a426f64793e3c6b6d64313a44617461437265617465644461746554696d653e323030372d30362d32365430303a30303a30302b30323a30303c2f6b6d64313a44617461437265617465644461746554696d653e3c2f746e733a426f64793e3c2f746e733a456e76656c6f70653e''. The HTTP Reply Header bitstream (if any) received from the server was: ''''. The HTTP Reply Message Body bitstream (if any) received from the server was: ''''. Ensure that the HTTP data is valid.   
 
 
 
( BKMQPWBI04.EKO ) Socket error detected whilst invoking Web service located at host 'intewswlbs-wm.kmd.dk', port '443', path '/KMD.HW.EWSEarlyRetirementCitizenList.WS/Service.asmx'.   
 
This may be a transient error, such as a server not responding, or a symptom of an invalid hostname or port number.   
 
Check that the hostname and port number are valid, and point to a functioning Web service. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | marcin.kasinski | 
		  
		    
			  
				 Posted: Tue Jun 26, 2007 10:58 pm    Post subject: Re: HTTPRequest and SSL | 
				     | 
			   
			 
		   | 
		
		
		   Sentinel
 
 Joined: 21 Dec 2004 Posts: 850 Location: Poland / Warsaw 
  | 
		  
		    
			  
				Have you checked it without SSL ?
 
Is your HTTPS service working ?
 
Can you test telnet 443 on service host ?
 
Have you set correct host and port ?
 
Can you see your request on service side ? _________________ Marcin | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | TBS | 
		  
		    
			  
				 Posted: Wed Jun 27, 2007 12:08 am    Post subject: HTTPRequest and SSL | 
				     | 
			   
			 
		   | 
		
		
		   Centurion
 
 Joined: 29 Jan 2007 Posts: 143 Location: Hillerød / Denmark 
  | 
		  
		    
			  
				Have you checked it without SSL ?  no
 
Is your HTTPS service working ?  Yes  with native Jave code
 
Can you test telnet 443 on service host ?  yes
 
Have you set correct host and port ? yes
 
Can you see your request on service side ? It's on a nother location and a nother company | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | marcin.kasinski | 
		  
		    
			  
				 Posted: Wed Jun 27, 2007 12:36 am    Post subject: Re: HTTPRequest and SSL | 
				     | 
			   
			 
		   | 
		
		
		   Sentinel
 
 Joined: 21 Dec 2004 Posts: 850 Location: Poland / Warsaw 
  | 
		  
		    
			  
				Have you checked system event log ? _________________ Marcin | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | TBS | 
		  
		    
			  
				 Posted: Wed Jun 27, 2007 1:17 am    Post subject: HTTPRequest and SSL | 
				     | 
			   
			 
		   | 
		
		
		   Centurion
 
 Joined: 29 Jan 2007 Posts: 143 Location: Hillerød / Denmark 
  | 
		  
		    
			  
				From the Event log: 
 
 
( BKMQPWBI04.EKO ) An HTTP error occurred. The HTTP Request-Line was: ''POST /KMD.HW.EWSEarlyRetirementCitizenList.WS/Service.asmx HTTP/1.0 
 
''. 
 
 
The HTTP Request Header bitstream (if any) to be used was: ''436f6e74656e742d4c656e6774683a203537300d0a534f4150416374696f6e3a2068747470733a2f2f696e74657773776c62732d776d2e6b6d642e646b2f4b4d442e48572e4557534561726c795265746972656d656e74436974697a656e4c6973742e57532f4765744c6973740d0a436f6e74656e742d547970653a20746578742f786d6c3b20636861727365743d7574662d380d0a486f73743a20696e74657773776c62732d776d2e6b6d642e646b0d0a0d0a''. The HTTP Request Message Body bitstream (if any) to be used was: ''3c3f786d6c2076657273696f6e3d22312e30223f3e3c746e733a456e76656c6f706520786d6c6e733a746e733d22687474703a2f2f736368656d61732e786d6c736f61702e6f72672f736f61702f656e76656c6f70652f2220786d6c6e733a6370723d22687474703a2f2f7265702e6f696f2e646b2f6370722e646b2f786d6c2f736368656d61732f636f72652f323030352f30332f31382f2220786d6c6e733a6b6d64313d22687474703a2f2f7265702e6f696f2e646b2f6b6d642e646b2f736f6369616c2f786d6c2f736368656d61732f323030352f30362f31332f2220786d6c6e733a6b6d64323d22687474703a2f2f7265702e6f696f2e646b2f6b6d642e646b2f736f6369616c2f786d6c2f736368656d61732f323030362f30312f31322f2220786d6c6e733a7873643d22687474703a2f2f7777772e77332e6f72672f323030312f584d4c536368656d612220786d6c6e733a4e53313d22687474703a2f2f7265702e6f696f2e646b2f6b6d642e646b2f736f6369616c2f786d6c2f7773646c2f323030362f30372f31332220786d6c6e733a7873693d22687474703a2f2f7777772e77332e6f72672f323030312f584d4c536368656d612d696e7374616e6365223e3c746e733a426f64793e3c6b6d64313a44617461437265617465644461746554696d653e323030372d30362d32365430303a30303a30302b30323a30303c2f6b6d64313a44617461437265617465644461746554696d653e3c2f746e733a426f64793e3c2f746e733a456e76656c6f70653e''. The HTTP Reply Header bitstream (if any) received from the server was: ''''. The HTTP Reply Message Body bitstream (if any) received from the server was: ''''. Ensure that the HTTP data is valid. 
 
 
 
( BKMQPWBI04.EKO ) Socket error detected whilst invoking Web service located at host 'intewswlbs-wm.kmd.dk', port '443', path '/KMD.HW.EWSEarlyRetirementCitizenList.WS/Service.asmx'. 
 
This may be a transient error, such as a server not responding, or a symptom of an invalid hostname or port number. 
 
Check that the hostname and port number are valid, and point to a functioning Web service. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | marcin.kasinski | 
		  
		    
			  
				 Posted: Wed Jun 27, 2007 1:32 am    Post subject: Re: HTTPRequest and SSL | 
				     | 
			   
			 
		   | 
		
		
		   Sentinel
 
 Joined: 21 Dec 2004 Posts: 850 Location: Poland / Warsaw 
  | 
		  
		    
			  
				You mentioned service works with your native JAVA client.
 
 
Is this client placed on broker machine ?
 
Can you compare JAVA client and broker request (HTTP headers and data) ? _________________ Marcin | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | 
		    
		   |