Best Practices and Techniques for the “New” XML Stage

Hi Everyone…

It’s been awhile since I’ve posted anything.   A certain amount of “blog” fatigue is to blame, but also because I like to post things that are (as much as possible) proven, time-honored (and not release dependent).   Many/most of the techniques I write about here are ones that I’ve spent many hours helping customers and colleagues implement in real situations.

It’s time I write about the XML Stage.  It is not-so-new anymore, but still feels new as it has had some very important xsd handling features added to it in the last few releases.   This week I will start posting suggestions and tips for using the XML Stage to read and write xml documents using DataStage.  

I’ll start with a pointer to a valuable RedBook that came out last year regarding the XML Stage.  I had the pleasure of reviewing the material as the authors put it together.  It is a great place to start when learning to work with this important Information Server capability.

XML Stage Redbook


…and a link to the first “New” XML Stage post…

Establish Meaningful Link Names when using the XML Stage!

Posted in XML. 5 Comments »

5 Responses to “Best Practices and Techniques for the “New” XML Stage”

  1. craighulett Says:

    Awesome, thanks Ernie. Looking forwards to reading them!

  2. DsGuy Says:

    Look forward to some great material! Thanks!

  3. mahender Says:

    Thanks Ernie , Nice e-Book !!!!!!
    As per my understanding real time integration can be done only with TIBCO types of product. got to know that it can be done with DataStage as well ? How about Informatica ????

    • dsrealtime Says:

      Hi! and thanks…

      At this time, I think you will find that every viable ETL tool on the market can do “some” degree of real-time, whether it means reading and writing message queues, performing with accepted standard protocols of SOAP, REST, etc., and working with the typical payloads (XML, JSON, etc.). The lines between classic EAI and ETL offerings continue to blur, although there are still subtle and important differences that remain, mostly related to the characteristics of the required solution and the team(s) implementing it. [more here: ].

      Beyond that, consider what the tools can “do” in that real-time arena. Can they process messages in parallel? …across a grid? …do they support a true XA transaction for two-phase commit (ensure that a message is not deleted from a queue until it is written into (say) DB2 or Oracle?) …can they write to multiple rdbms tables in the same unit of work? …can they parse complex, multi-path xml, and also create it? Do they generate WSDL automatically, and can they support JSON and REST in addition to SOAP for web services payloads? DataStage can do all of that and more….. ; )

  4. mahender Says:

    Thanks ,,,,,

    Love this ,,, True insight of lot of real time capabilities !!!!!!!!!

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: