Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Talend Cloud AWS EU Scheduled Outage: Starting Tues 26 May 21:00 CEST with expected completion Wed 27 May 01:00 CEST
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

migration problem 6.4.1 to 7.1.1

Hello,

 

We have jobs and routes in several projects in 6.4.1, we use a .properties file to store variables and context value.

This .properties files are stored in the same place (folder etc) with configuration in the studio for loading context from a file: "./etc/ProjectName.properties".

 

In 7.1.1, to reach the same folder etc, we have to put "../../../../../../../../../etc/ProjectName.properties".

Same case when exporting for Runtime. 

 

Is there a configuration in Studio 7.1.1 and Runtime 7.1.1 to set the base directory? (which seems to be no longer the studio or the container folder, but a lost folder at the end of the project).

 

Thank you for your help.

Labels (5)
7 Replies
Anonymous
Not applicable
Author

Hello,

Here is a KB article about:https://community.talend.com/t5/Architecture-Best-Practices-and/Migrating-a-Talend-ESB-product-from-...

Feel free to let us know if it is OK with you.

Best regards

Sabrina

Anonymous
Not applicable
Author

Hello,

Is there any update for your issue?

Best regards

Sabrina

Anonymous
Not applicable
Author

no new update, I'm still looking for the solution for now.

Anonymous
Not applicable
Author

I continue my research on the subject, it would seem to come from the difference of version of maven between 6.4 (maven 2) and 7.1 (maven 3).

Anonymous
Not applicable
Author

Hello,

Are you getting any error message when migrate your product from 6.4.1 to 7.1.1?

Best regards

Sabrina

Anonymous
Not applicable
Author

I do not remember, but I observe the same problem on a new project in 7.1

Anonymous
Not applicable
Author

new update: if I install the container as a service, a TALEND-CONTAINER-wrapper.conf file is created where the path of the properties file is correct (set.default.KARAF_ETC).

I do not have the problem on the server, but I still have not fixed the problem on the studio.

 

Il faut surement définir cette variable dans le studio, mais comment ?