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

Announcements
Join us in NYC Sept 4th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
PSteinberg1604504662
Contributor
Contributor

ext_resources

I have an xml file that is loaded from a custom library. In 6.2.2 I was able to put this in the studio folder. With 7.1 and 7.3 I need to put it in the ext_resources folder. I have multiple jobs that use this file and I now need to make copies of it.

The worst part is that it keeps disappearing from the folder randomly. Then I have to copy it in again.

Is there a way to change this default folder for the jobs?

Labels (2)
3 Replies
Anonymous
Not applicable

Hi

Is this folder created by yourself or studio? I don't see this folder under <studio installation directory>.

It seems you are using relative path on the component which read the XML file. This is not officially supported. We usually set the file path as a context variable, for example: context.file_directory+"filename.xml". In the future, we only need to change the value of the variable no matter which directory the file is placed in, without opening the job to modify it.

 

Regards

Shong

PSteinberg1604504662
Contributor
Contributor
Author

The ext_resource path is under the workspace for the job:

F:\TOS_BD7.3.1\workspace\REDSHIFTLOADER\poms\jobs\process\EXCELA3\Prod\prod_mediation_prep_main_0.1\src\main\ext-resources

I do not create it, it is part of the workspace.

The path itself is not specified. I have a tjavaflex component calling a java program. This java program needs this XML file and I believe it looks in the default directory of whatever program it is run from. In 6.2.2 I was able to put the file in the Studio folder and all of my jobs that used it were able to get to it.

 

 

PSteinberg1604504662
Contributor
Contributor
Author

I was able to resolve this. I had to put my XML file in the workspace\REDSHIFTLOADER\temp\lib directory. This is the location the external jar file was loaded to when I imported it.