DSXchange

Why are you using the xml stage? Just send the output link to the ISDoutput stage and then pick one of the REST bindings in ISD and choose JSON (or xml if that's what you really need inside the payload).

Ernie

It's possible that it is MQ header information. If you are receiving a file and not actually reading from MQ, see if the application that is reading MQ and writing the file can just capture the "message content" and leave out the header, so that you don't have to deal with it. I can't reme...

....but there isn't any overhead to a job with the "potential" to be run multi-instance or the "potential" to be deployed under ISD. It's merely a setting for capability that "could" be exploited but is (apparently) not.

Ernie

Hard to say. I've seen things like this before when the higher level repeating node is not easily unique (meaning --- you have to go to its 3rd or 4th element before noticing that the next instance of demand is indeed unique from the prior one). ...in this case you have to go to tasklistname before ...

Personally, I try to avoid special characters, and usually go to a CamelCase format when possible ...either way, see if the importer will let you choose your own column name (with or without one or more underscores) prior to saving. You can edit the column name in the grid at the bottom after you &q...

This is the other reason that it is ABSOLUTELY MANDATORY that you get yourself a testing tool to test THIS web service outside of DataStage. SOAPui and Actional's Soap tester are two free ones that a lot of people like, but there are others... Use that tool to see if the service works, if it is avai...

A key question here is the syncronous nature (or not) of the web service you are putting together. Is the calling client going to be "waiting" for a response? If so, you could use a single Job, probably a simple Server Job, and inside of a Transformer, use the DSUtilityRunJob function to c...

There are various things that could be going on here. 1. the importer in the release that you are using might not be capable of handling the "import" or "include" statements. Usually that gives you a more fatal error, so that's probably not your issue, but it's possible. 2. the m...

Use the JSON option in the REST binding ---- it will deliver JSON directly. It won't be deeply hierarchical ---- just a single repeating node in JSON for your final output link to the ISDoutput Stage. You'll have it working in minutes. Doing custom deeper hierarchicak JSON in the current release wil...

It's not necessarily that simple. Those "special" characters might be critical binary values. You need to speak with whoever authored that file and understand what is truly stored in each of its bytes.

Ernie

Do a lot of searching and reading of this forum and of the formal documentation...MQ is not something you enter into lightly....lots of things to consider and potentially things to install and configure......on the DataStage side and on the mq side, depending on your application variables for perfor...

There is a lot more to this than just the classpath.... First, have you coded your Employee.java along with the JavaPack API? DataStage works very closely with the java code that you write, invoking various pre-defined methods that you include in your code. In those methods you place your own logic ...

That's fine. Provided that you aren't getting other errors, rejections, or invalid documents, then something is different ....check the xpaths, check the namespaces ...see if the namespace declarations at the top are different between the documents....... Something is different. Maybe it is being re...

+ 1 and also, why the XML Transformer? If you exclusively are doing things in xslt, that makes sense, but it shouldn't be necessary if you are using xmlOutput. As for duplicated root elements, that generally happens when things aren't aggregating correctly. Check things like: a) your aggregation set...

I would suggest using JavaPack ...find a Java developer who knows how to access LDAP and then introduce them to the Java Pack (lots of threads here on it and the doc is very good)....it won't be difficult for them to adapt their code to a Stage implementation so that LDAP records can be delivered to...