Frequently Asked Question

Configuration of N4V for printing components (PDF/XLS export from Webi)
Dernière mise à jour il y a 10 mois

Symptom

  • When printing a Webi report in PDF/XLS format, N4V components may not be correctly printed (a puzzle may appear) or there is a very long delay to print the report.

Environment

  • Linux/Windows Server
  • Need4Viz : all versions. New settings available in 2024.3.0.

Resolution

To print a PNG of a N4V component (used when printing a Webi report in PDF/XLS), N4V server needs to access the N4VCustomElements webapp (generally deployed on your SAPBI Tomcat). The URL used to access this webapp may not be available from the N4V server (URL only available from the user's browser).

In version 2024.3.0, new settings have been created to dynamicaly change the URL of the N4V webapp when the component is print on the N4V server.

For instance, if Tomcat is installed on the same server as the N4V server (and accessible on port 8080), you can change the settings in the \Need4Viz\nodejs\node_modules\custom_element\ce_libs\config.js file as following :

var use_internal_webapp_PRINT = true;
var URL_PORT_WebApp_int_PRINT = "http://localhost:8080";

Another example, if Tomcat is deployed on a second server accessible from the N4V server by its name (and accessible on port 80), you can set the \Need4Viz\nodejs\node_modules\custom_element\ce_libs\config.js file as following :

var use_internal_webapp_PRINT = true;
var URL_PORT_WebApp_int_PRINT = "http://server_name";

One the config.js file is updated, save it and restart all N4V services (run a "pm2 start all" command in a PowerShell window run as administrator) and try to print again your report.

Veuillez patienter!

S'il vous plaît patienter... il faudra une seconde !