Frequently Asked Question

Migrate Need4Viz infrastructure during a SAPBI migration (ex. 4.2 to 4.3) - ON THE SAME SERVER
Dernière mise à jour il y a 3 ans

Symptom

  • The SAPBI environnement will be upgraded from a 4.2 version to a 4.3 version WITHOUT CHANGING SERVER
  • Need4Viz is already installed and configured on the SAPBI server

Environment

  • Windows/Unix Server
  • Need4Viz : all versions

Resolution

  1. Before upgrading SAPBI version, make a backup of the  full /tomcat/webapp/N4VCustomElements folder.
  2. Open the CMC / Applications / Web Intelligence / Custom Elementsimage
  3. For each service, click on "Configure..." and copy/paste the Service Name & Service URL values in a text file to backup the exact names and URL of each service :image
  4. Make your SAPBI upgrade to the final version (ex. 4.3SP2)
  5. After the upgrade, check the /tomcat/webapp/N4VCustomElements folder and, if it doesn't exist anymore, copy the previous backuped version (step 1)
  6. Open a PowerShell window and run "pm2 list" to check all N4V services are up and running : image
  7. Open the CMC / Applications / Web Intelligence / Custom Elements and check all the N4V services are configured. If no service is defined, recreate all the services with exactly the same name & URL as backuped in the text fil in step 3 (be careful to previously whitelist the URLs if necessary)
  8. Once the services are configured in the CMC, you could open a Webi report including existing N4V charts and chek it is correctly displayed.
  9. At these step, if your N4V version is prior to 2021.12.4, the navigation components and native Webi Linking Element will not work on the SAPBI 4.3SP2 version, goto the next paragraph to update your N4V version.

Update N4V version for 4.3SP2

Once your SAPBI version is updated and your N4V version is prior to 2021.12.4, you have to update your N4V version to enable the navigation (components and Webi linking elements) in Webi :

  1. Open Need4Viz\nodejs\node_modules\custom_element\ce_libs\config.js file 
  2. Change the “SAPBI_ver” setting from “42” to “43”
  3. Open a PowerShell command and run “pm2 stop all” then “pm2 start all”

Veuillez patienter!

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