<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: How to Invoke Complex Web Services</title>
	<atom:link href="http://dsrealtime.wordpress.com/2008/04/12/how-to-invoke-complex-web-services/feed/" rel="self" type="application/rss+xml" />
	<link>http://dsrealtime.wordpress.com/2008/04/12/how-to-invoke-complex-web-services/</link>
	<description>thoughts about all things "real time" that revolve around "ETL" (Extract, Transform, Load) and Data Integration</description>
	<lastBuildDate>Thu, 29 Oct 2009 09:32:23 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: dsrealtime</title>
		<link>http://dsrealtime.wordpress.com/2008/04/12/how-to-invoke-complex-web-services/#comment-729</link>
		<dc:creator>dsrealtime</dc:creator>
		<pubDate>Fri, 31 Jul 2009 20:30:52 +0000</pubDate>
		<guid isPermaLink="false">http://dsrealtime.wordpress.com/2008/04/12/how-to-invoke-complex-web-services/#comment-729</guid>
		<description>It can be done, but it is not particularly easy.  The WSTransformer has the ability to pass a header, but it has to be in the absolutely correct format, and namespaces have to right..... the best way to approach it would be to use some separate testing tool (Actional, SOAPscope from Mindreef, etc.) and formally capture a &quot;working&quot; SOAP envelope and header.   Then you will be able to tell what you need to build and send.   It gets more difficult than that, because you may also have to custom craft the details of the SOAP body, and then do the same with the response and any other queries/commands you may be issuing.   WSTransformer is best for single row, stateless and no-session invocations that return a transformed result.  If you need to do complex processing it is best to put it together in a java client and invoke via the Java Transformer.  In the java client you will have all the control that you need, and can more easily unit test it outside of DS and then include in DS for integration testing once you know how Java Pack works.

Ernie</description>
		<content:encoded><![CDATA[<p>It can be done, but it is not particularly easy.  The WSTransformer has the ability to pass a header, but it has to be in the absolutely correct format, and namespaces have to right&#8230;.. the best way to approach it would be to use some separate testing tool (Actional, SOAPscope from Mindreef, etc.) and formally capture a &#8220;working&#8221; SOAP envelope and header.   Then you will be able to tell what you need to build and send.   It gets more difficult than that, because you may also have to custom craft the details of the SOAP body, and then do the same with the response and any other queries/commands you may be issuing.   WSTransformer is best for single row, stateless and no-session invocations that return a transformed result.  If you need to do complex processing it is best to put it together in a java client and invoke via the Java Transformer.  In the java client you will have all the control that you need, and can more easily unit test it outside of DS and then include in DS for integration testing once you know how Java Pack works.</p>
<p>Ernie</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anu</title>
		<link>http://dsrealtime.wordpress.com/2008/04/12/how-to-invoke-complex-web-services/#comment-728</link>
		<dc:creator>Anu</dc:creator>
		<pubDate>Fri, 31 Jul 2009 18:03:20 +0000</pubDate>
		<guid isPermaLink="false">http://dsrealtime.wordpress.com/2008/04/12/how-to-invoke-complex-web-services/#comment-728</guid>
		<description>Hi,
We have been reading your articles Datastage webservices and they have been very helpful. I have a doubt, was wondering if you can help us.
We need to connect Datastage 8.0 to an application via a URL by passing username and password in the HTTP headers. This application will return the cookie and a session Id within the cookie. This session Id should be captured for further transactions.
Now we imported the WSDL published by this application and created a Webservices Tranformer Stage but have not been able to figure out on how to pass the username and passwd in the HTTP header to connect with this app? Any help?</description>
		<content:encoded><![CDATA[<p>Hi,<br />
We have been reading your articles Datastage webservices and they have been very helpful. I have a doubt, was wondering if you can help us.<br />
We need to connect Datastage 8.0 to an application via a URL by passing username and password in the HTTP headers. This application will return the cookie and a session Id within the cookie. This session Id should be captured for further transactions.<br />
Now we imported the WSDL published by this application and created a Webservices Tranformer Stage but have not been able to figure out on how to pass the username and passwd in the HTTP header to connect with this app? Any help?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Heartburn Home Remedy</title>
		<link>http://dsrealtime.wordpress.com/2008/04/12/how-to-invoke-complex-web-services/#comment-640</link>
		<dc:creator>Heartburn Home Remedy</dc:creator>
		<pubDate>Wed, 15 Apr 2009 11:44:45 +0000</pubDate>
		<guid isPermaLink="false">http://dsrealtime.wordpress.com/2008/04/12/how-to-invoke-complex-web-services/#comment-640</guid>
		<description>Not that I&#039;m totally impressed, but this is   more than I expected for when I stumpled upon a link on Digg telling that the info   is quite decent. Thanks.</description>
		<content:encoded><![CDATA[<p>Not that I&#8217;m totally impressed, but this is   more than I expected for when I stumpled upon a link on Digg telling that the info   is quite decent. Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dsrealtime</title>
		<link>http://dsrealtime.wordpress.com/2008/04/12/how-to-invoke-complex-web-services/#comment-527</link>
		<dc:creator>dsrealtime</dc:creator>
		<pubDate>Wed, 10 Sep 2008 01:12:33 +0000</pubDate>
		<guid isPermaLink="false">http://dsrealtime.wordpress.com/2008/04/12/how-to-invoke-complex-web-services/#comment-527</guid>
		<description>Venu ...

You should have received the .dsx from me with the solution.   Not sure exactly what was thwarting you in your installation, but as we discussed, there are a variety of solutions.   For everyone else, it appeared to be a namespace issue.  In my 8.x with FP1, I was able to read the documents just fine, but if there are issues and you are reading XML to put into an rdbms or other target, there are lots of shortcuts to get you moving....the easiest is to just pass your xml string thru a Transformer and edit out the offending namespace prefixes.  You can&#039;t always do that, but very often, especially if you are just shredding the document anyway, it will be fine.   DataStage has rich text functions, especially in the BASIC Transformer or Server Jobs, that can manipulate lengthy text strings, with eReplace being one of my favorites.

Ernie</description>
		<content:encoded><![CDATA[<p>Venu &#8230;</p>
<p>You should have received the .dsx from me with the solution.   Not sure exactly what was thwarting you in your installation, but as we discussed, there are a variety of solutions.   For everyone else, it appeared to be a namespace issue.  In my 8.x with FP1, I was able to read the documents just fine, but if there are issues and you are reading XML to put into an rdbms or other target, there are lots of shortcuts to get you moving&#8230;.the easiest is to just pass your xml string thru a Transformer and edit out the offending namespace prefixes.  You can&#8217;t always do that, but very often, especially if you are just shredding the document anyway, it will be fine.   DataStage has rich text functions, especially in the BASIC Transformer or Server Jobs, that can manipulate lengthy text strings, with eReplace being one of my favorites.</p>
<p>Ernie</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: venu</title>
		<link>http://dsrealtime.wordpress.com/2008/04/12/how-to-invoke-complex-web-services/#comment-521</link>
		<dc:creator>venu</dc:creator>
		<pubDate>Sat, 23 Aug 2008 09:08:09 +0000</pubDate>
		<guid isPermaLink="false">http://dsrealtime.wordpress.com/2008/04/12/how-to-invoke-complex-web-services/#comment-521</guid>
		<description>My gmail id is : gopalopposite@gmail.com</description>
		<content:encoded><![CDATA[<p>My gmail id is : <a href="mailto:gopalopposite@gmail.com">gopalopposite@gmail.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: venu</title>
		<link>http://dsrealtime.wordpress.com/2008/04/12/how-to-invoke-complex-web-services/#comment-520</link>
		<dc:creator>venu</dc:creator>
		<pubDate>Sat, 23 Aug 2008 08:48:08 +0000</pubDate>
		<guid isPermaLink="false">http://dsrealtime.wordpress.com/2008/04/12/how-to-invoke-complex-web-services/#comment-520</guid>
		<description>Hi,
while  im process an  Embedded XML. A SOAP envelope  in datastage im getting below error please adivise
xml_job1..XML_Input_0: Xalan fatal error (publicId: , systemId: , line: 0, column: 0): An exception occurred! Type:NetAccessorException, Message:Could not connect to the socket for URL &#039;{0}&#039;. Error={1} 

xml_job1..XML_Input_0: Xalan fatal error (publicId: , systemId: , line: 1, column: 230): Fatal error encountered during schema scan</description>
		<content:encoded><![CDATA[<p>Hi,<br />
while  im process an  Embedded XML. A SOAP envelope  in datastage im getting below error please adivise<br />
xml_job1..XML_Input_0: Xalan fatal error (publicId: , systemId: , line: 0, column: 0): An exception occurred! Type:NetAccessorException, Message:Could not connect to the socket for URL &#8216;{0}&#8217;. Error={1} </p>
<p>xml_job1..XML_Input_0: Xalan fatal error (publicId: , systemId: , line: 1, column: 230): Fatal error encountered during schema scan</p>
]]></content:encoded>
	</item>
</channel>
</rss>
