TIBCO Spotfire Analyst client loads modules which are not part of the deployment area
Article ID: KB0074468
Updated On:
| Products | Versions |
|---|---|
| Spotfire Analyst | All Versions |
Description
When connecting TIBCO Spotfire Analyst to a deployment area it loads modules that are currently deployed within the deployment area but there might be a case where you see a module or a custom extension loaded into the client that is not currently part of the deployment area
This is caused if the "loadallmodules" argument is present in the Spotfire.Dxp.exe.config file .
This is caused if the "loadallmodules" argument is present in the Spotfire.Dxp.exe.config file .
Issue/Introduction
This article explains why an Analyst client loads all the modules including any custom extensions that are not present in the deployment area
Resolution
1. Open the Spotfire.Dxp.exe.config file which can be found in either of the following location,
2. Check the arguments section in the config file. It would be as below
<arguments>
<argument name="loadAllModules" />
</arguments>
If this argument is present in the configuration file then the client will load all the modules available in the Modules folder defined the config file. If the unwanted module/custom extension has been previously deployed and downloaded then the client will load these module(s) though they are not part of the deployment area.
a. C:\Program Files (x86)\TIBCO\Spotfire\10.10.3\
b. C:\Users\<uname>\AppData\Local\TIBCO\Spotfire\10.10.3\
2. Check the arguments section in the config file. It would be as below
<arguments>
<argument name="loadAllModules" />
</arguments>
If this argument is present in the configuration file then the client will load all the modules available in the Modules folder defined the config file. If the unwanted module/custom extension has been previously deployed and downloaded then the client will load these module(s) though they are not part of the deployment area.
Feedback
Yes
No
Powered by
