DSXchange

...apologies not needed! These things are procedural...and part of the learning curve. Tutorials...others on this site may have better suggestions than I.... as for other sources --- this site itself, of course is a great resource "as is", many professionals on this site do videos and trai...

Yes..."contact method" is a repeating element....so you would need a separate row for the email, and another for the phone details. Alternatively, "if" these are the only two columns, you might just consider having a transformer upstream that builds the "contact method"...

...ok....that just means that the environment hasn't been configured as you require it... you or someone needs to define an ODBC System DSN with all the requisite connection details, at the Windows level, that correctly points to the Database in the remote SQL Server system that you are looking for....

: ) use the import method to get the "metadata" into DS.... now you have to write your DS jobs to move the actual "contents" of those tables...

How does this contrast with the first entry in the thread? (you noted that things deployed succesfully)? Second, your comment is interesting that it works from the Director....a job with WISDInput makes no sense running directly from the Director, I would expect that one to abort strangely. Sounds l...

Look in your 8.1 doc set...there is a dedicated pdf for MQ. It includes both the Plugin and the new Connector options. lstsaur nailed the big enhancements. It also has a few other goodies, like end-of-wave support, better functionality with reply-to functions and other esoteric bits of MQ. It (at 8....

Windows XP and Windows Server? You should be able to make that connection directly thru various Windows protocols..... Did I mis-read? is there a DataStage "unix" platform involved? If so, then yes, as Ray notes, you'll need a gateway of some type....DataDirect is the one we often see peop...

; ) Yes, indeed.... a valuable discussion. The use case for a simple topology, or "batch job as a service" [for instance a basic normal job that reads from a flat file and goes to db2] is to provide the simplest way possible for a .NET or java programmer to put a button on a page somewhere...

An alternative is to avoid the general setting and instead use the IPC Stages to do "inter-process" row buffering only where you designate. Wherever you put these stages you will then create a process boundary. ...be careful, because now you are actually creating additional processes on th...

SOA and ISD is not for this type of requirement. What you are looking for is some type of Changed Data Capture. Do some searches here in this forum and all around....tools like InfoSphere Changed Data Capture will "watch" your relational logs and move data the instant it is committed to th...

The metadata for your "data" in SQL Server is probably best/easiest imported using ODBC. This can be done from within DataStage (import...table definitions....ODBC... or via the Import Connector Wizard)....and/or also from within FastTrack and/or Info Analyzer. This will be for the tables ...

It will help if we start higher and understand your goals. ISD is best used when there is a portal application, with java, .NET or other such clients, and you would like to share a certain Transformation, lookup, QualityStage, or other such DataStage/QualityStage logic with them. What are you trying...

...this performance feature is great...but always be sure to do your testing, and don't just "turn it on" and blindly re-roll the job into production. One of the options (for example), "inter-process" row buffering, can make subtle changes to the behavior of your jobs. There are ...

Hi... Tell us a little bit more about your environment and what you are trying to do... Do you only have Metadata Workbench, or do you also have DataStage/QualityStage, and/or FastTrack, and/or Information Analyzer? Do you have the Import/Export Manager installed? Are you looking to import the table...

Hi.... Great job so far. You've created a wISD job and deployed it via SOAP, and have the WSDL. You now have an always on Job for performing Transformations.... Let's look at your questions. (1). It already is 24 by 7. Having wISDInput automatically means that it will be "always on". Check...