topic Re: Integrate Management console with studio context variable in Talend Studio

Integrate Management console with studio context variable

Anonymous — Sat, 16 Nov 2024 05:56:25 GMT

Hi all,

I want to setup context variable from management console. I thought, I'm able to get this by setting connection parameters with the same name in management console as in the studio context variable, but this is not working.

The behaviour:
* First I added three fields in studio: new1, new2, new3 > they are logged

* I add connection parameter in management console > it is not loged

* I add connection parameter with the same name as context variable in studio > studio value is logged

So, how can I setup management console connection parameter to connect to studio context variable? Is it possibile at all?

Thanks!

best regards,
Viktor

Re: Integrate Management console with studio context variable

Anonymous — Mon, 06 May 2019 10:08:55 GMT

Hello,

Talend Studio supports the use of context connection parameters in Artifacts.

Connection parameters enable you to share configuration settings with web users by allowing them to select the connection to use when running Tasks in Talend Cloud Management Console.

For more information, please refer to this online user guide about:TalendHelpCenter:Talend Cloud context parameters.

Best regards

Sabrina

Re: Integrate Management console with studio context variable

Anonymous — Mon, 13 May 2019 12:22:24 GMT

Hello Sabrina,

Thanks for your response!
I have retested the variables and I can give a more detailed description of my problem. My goal was to log the context vaiables and values with tcontextDump component and tLogRow.
Steps:

1. I have added fields to a repo context descriptor: new1, new2, new2

2. I have added them to a job (all of them) >> I could logged them

3. I have modified one field name in the context view of tContextDump component (new1 >> new1_modified)> I could see in the log new1 and new1_modified as well.

So it seems, the old variable somehow stucked somewhere.

I have got this behaviour in an on premise runtime.

best regards,
Viktor