Helloo everybody,
we have alot of parallel jobs that has basic transformers in it and also read and write to the same table in the same job and those basic transformers are causing problems all the time in development and test environment, I would like to replace all the basic transformers with the regular ones, as IBM doesnot advice to use basic transformers in parallel jobs.
is there any easy way to replace them with the regular ones, for example is it possible to export the job in xml format and modify the code and import the job by using modified xml file? or any other idess?
is there any easy way of replacing basic transformers with..
Moderators: chulett, rschirm, roy
is there any easy way of replacing basic transformers with..
Thanks,
Chad
__________________________________________________________________
"There are three kinds of people in this world; Ones who know how to count and the others who don't know how to count !"
Chad
__________________________________________________________________
"There are three kinds of people in this world; Ones who know how to count and the others who don't know how to count !"
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 3593
- Joined: Thu Jan 23, 2003 5:25 pm
- Location: Australia, Melbourne
- Contact:
I think you could write a server transformer to parallel transformer function that alters the export file.
Maybe as a search and replace macro in a text editing tool. You will need to build a simple job with a server routine, export it, replace it with a parallel routine, export it. Compare the files using a text file compare utility. Determine what you want to programmatically convert across, ie find out what functions you use a lot and what parallel functions they map to. Remember that any mapping code that you leave in there that is not valid in a parallel transformer will just show up as invalid red text and not do any real harm. You will just need to fix it when the post-conversion jobs are reviewed. As long as you get the core transformer conversion right the contents inside the derivation boxes are not a big deal and wont corrupt the job.
I would abandon all customer server routines and just map the field and make a note of it. Custom server routines will have to be handled on a case by case basis.[/img]
Maybe as a search and replace macro in a text editing tool. You will need to build a simple job with a server routine, export it, replace it with a parallel routine, export it. Compare the files using a text file compare utility. Determine what you want to programmatically convert across, ie find out what functions you use a lot and what parallel functions they map to. Remember that any mapping code that you leave in there that is not valid in a parallel transformer will just show up as invalid red text and not do any real harm. You will just need to fix it when the post-conversion jobs are reviewed. As long as you get the core transformer conversion right the contents inside the derivation boxes are not a big deal and wont corrupt the job.
I would abandon all customer server routines and just map the field and make a note of it. Custom server routines will have to be handled on a case by case basis.[/img]
Certus Solutions
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn