I'm in front off a problem that I don't find how to solve to: I'm fetchning from an oracle database a field value. this value must be updated in an mysql database throw an update with two constants in a where row: UPDATE my_table SET my_field = oraclevalue WHERE field = 'firstField' AND secondField = 'secondField'; So my batch is based like the following one:
But from and to field are not variables but must be static values. How can I define their values ? Does I need to update the model? Does I need to update job to fetch the row matching from Mysql Database server and update it? Best
you can use a look up (small file delimited) with and dooble inner join
or create global variables in a tJava / tSetGloblavariable and use filter the output
or create two context variable and use filteron the output.
If you are using external image provider you may block out people from helping you. Some companies have extreme restrictive firewall rules. I can not get your picture if you don?t attach them to your post. If you need a constant value you can use a global variable. A global variable, you can set from any place in your job (like with tPrejob) and then use in your tMap. I?m usually using a context Variable for global Variables because I like the CTRL+Space functionality.
hello, thanks for yours feedback. So I have used them like this, but I'm not sure that syntax is wrong because CTRL+space doesn't give me my variables in list. The job contains now a t_SetGlobalVar which have two variables definitions.
In My Map, I have update the variables with CTRL+Space
But when I run job, I have an error that mapping fields cannot be null. So, My mapping is wrong, I suppose that my variables declarations is wrong, but I can't see why. Does someone can help a newbie? Best regards
When I was talking about the CTRL+Space I?m talking about variables declared in the Contexts (second tab, between Job and Component). Did you declare your variables there? Using context variables is only one way to deal with the situation but it is the way with the CTRL+Space.
in t_globalvar you define global variable for the job
in context you can create differente situation (prod,dev) with different value for the context variable. When you generate scriptjob you can choose the context (and the values of the context variable) to execute the job on the server.
After you can use "implicite tConextLoad" in the wiev job>extra : we load values of context variable from a files or data base (key;value)
For me, It's the unique interacrtion between user and job script on the server.