Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi there,
I have a job that looks like this :
when I deploy the job to de management console and configure a new task, I only can configure two connections.
The connections for DWH_manage and for DWH_TargetStaging are recognized, the connection for DataMart is not recognized. All three are in the context parameter list:
Why is this ??
Thanks in advance,
Jacco
Ah, I misunderstood. I thought you were saying you couldn't make the connection. I think that this is caused by your naming convention for the Datamart contexts. You have....
connection_DatamartDBUsername
...for example.
If you take a look at the documentation here (https://help.talend.com/r/en-US/Cloud/studio-user-guide-big-data-platform/naming-connection-parameters), you will see that it doesn't quite fit the required naming convention of....
connection_<application_name>_<parameter_name>
Give that a slight change and see what you get.
Where is the job running? Are you using a RemoteEngine to run this? If so, does the machine that hosts the RemoteEngine have access to connect to the Datamart environment?
@Richard Hall , yes the job is running using a RemoteEngine.
When configuring the task I'm able to configure the parameters :
after that I have to configure the connections. And there is one missing :
There should be something like Datamarts since the name of the connection parameters have the format connection_DataMartDB and so on.
So why isn't picked-up by the management console ?
Because when I configured an other task for the first time, all the connections needed in that task were recognized.
The connection for Datamart is not recognized, the way I see it.
Jacco
Ah, I misunderstood. I thought you were saying you couldn't make the connection. I think that this is caused by your naming convention for the Datamart contexts. You have....
connection_DatamartDBUsername
...for example.
If you take a look at the documentation here (https://help.talend.com/r/en-US/Cloud/studio-user-guide-big-data-platform/naming-connection-parameters), you will see that it doesn't quite fit the required naming convention of....
connection_<application_name>_<parameter_name>
Give that a slight change and see what you get.
rhall,
Thanks for pointing me in the right direction !
Got it fixed and it's working.
Thanks