As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only. Moving forward, myibi is our community platform to learn, share, and collaborate. We have the same Focal Point forum categories in myibi, so you can continue to have all new conversations there. If you need access to myibi, contact us at firstname.lastname@example.org and provide your corporate email address, company, and name.
Clif, Thanks a lot for your suggestion. The example really helps me to get started. In my case, I need to query a SQL Server, format the output to XML then pass this XML to a web service. The web service will returns result as XML as well. I intend to: 1. Create a DBMS SQL flow to query output to XML 2. Create a data flow to pass the XML to web service. I'm still unclear on how to do this 2nd step & still playing with the data flow.
It does sound a bit roundabout. Does your web service takes an entire xml document as an input parameter? If so then create a synonym with a single A32767V or TX field to describe the xml file you created and join to it.
Posts: 397 | Location: New York City | Registered: May 03, 2007
Clif, Thank you so much for your advice. My webservice takes entire xml document as an input. Following your suggestion:
I'm not sure how to create the flat file synonym and add data to flat file manually. So I create a DBMS SQL flow that output to a flat file. Then I edit the synonym field to TEXT and paste my real XML data to the data file.
After that, I create the data flow to join the flat file and web service. After running, the returned message from webservice said that
"Processor Deserialize/Process Document failed. EXCEPTION details: Message: Value cannot be null. Parameter name: s Source: mscorlib Stack: at System.IO.StringReader..ctor(String s)"