DSXchange

Glad it worked.....it's very odd though, that it failed...CRLFs and blanks are "noise" for XML...and most valid parsers should ignore them.....

Either way, the removal of formatting is a best practice that everyone should follow, and it has been well documented in this forum.

Ernie

shut off all formatting. The xml should go out as one big giant string, which is what you want anyway....it saves bytes on the wire or wherever else you might be sending the xml.

I suspect that it will be very close. The xml Stages use xslt and the WSTransformer also uses a lot of that..... SOAP and XML is slow. You aren't going to get screaming performance from a Web Service like this. Perhaps you can partition it and spread the work around, but your problems may not even b...

It's hard to tell exactly (suggest you do a trace like suggested up above), but it looks like it is working perfectly!! Odds are that the error in workflow is coming back from the web service that you are calling......it obviously isn't displaying any error in a nice way, but something is dying insi...

this is fairly poorly designed xml. The better design is where the metadata is truly the names of the tags, as in your first example. What happens here is that the structure of the xml is totally different. The whole "contact name" is no longer the repeating element....instead, contactFiel...

then something must different about the values as they are being passed when you hard code them vs the db....maybe leading or trailing spaces, the datatypes, etc..... One thing you might want to try... use the trace function (you may have to write it as a server job to try this)......go to the trace...

The WSTransformer can only handle one row in and one row out by default. Run this desired web service from some other testing tool, such as SOAP UI...... If it returns multiple rows then you will have to unpack them yourself. Put one giant column on your output link, such as "soapOutput" (...

Worst case, you will most likely be able to connect to it just fine by using JavaPack, and then invoking your own Java class to talk to "Web View"...

Ernie

What exact release are you on? I recall times in the past when lineage dead-ended on certain Containers, but I thought most of those had been corrected...

Ernie

That's a very good question, and is being answered by engineering as we evolve into 8.7 and beyond with InfoSphere Metadata Asset Manager. The Metadata Asset Manager is a central location for performing imports, assessing whether they are correct, and then accepting them for xmeta or rejecting them....

follow lstsaur's steps.....indeed, you should get a LOT of table defintions...the WS Transformation Stage knows what to do with them when you "Load" the message details on the input and output links....

Ernie

did it really import? do you remember seeing and selecting the exact desired operation on the right hand side of the importer? Open up the whole tree -- select each operation individually and then click "import".....it should go thru two steps and tell you about it......

Ernie

Not that I am aware of.....i haven't tried this, but see if the workflow comments exist in the .csv that you can send to disk when you look at the list of items that is in a particular state ---- like "all draft".....or "all approved"...check them all and then there's an option o...

did you complete all the information in the config file? (runimport.cfg).

They are viewable as "part" of the editing and workflow process. You will see the comment, for example, when you look at the terms sitting in "Approved" after they are approved.

Ernie