widgetBackend

The "widgetBackend" setting controls the behavior of database-driven widget and file upload/download requests when the Profound.js application is running inside a Profound UI / Genie session.

There are two valid values:

• "pui": This value causes database-driven widget and file upload/download requests to be processed by the Profound UI / Genie backend. Queries will run against the local IBM i database where PUI / Genie is running. This setting does not allow for running queries against the databases defined in databaseConnections. The Profound UI version of the file upload and file download exit programs will be called, and files will be uploaded/downloaded to/from the IBM i system where PUI / Genie is running.
  
  
  

• "pjs": This value causes database-driven widget and file upload/download requests to be processed by the Profound.js backend. Queries will run against the databases defined in databaseConnections. The Profound.js version of the file upload and file download exit programs will be called, and files will be uploaded/downloaded to/from the system where Profound.js is running.
  
  This option requires configuring the Profound UI / Genie HTTP server instance to proxy the requests to the Profound.js server, using these directives:

  # If the PJS server is running on a different system than PUI / Genie, # replace "localhost" with the host name or IP address of the system. LoadModule proxy_module /QSYS.LIB/QHTTPSVR.LIB/QZSRCORE.SRVPGM LoadModule proxy_http_module /QSYS.LIB/QHTTPSVR.LIB/QZSRCORE.SRVPGM LoadModule proxy_connect_module /QSYS.LIB/QHTTPSVR.LIB/QZSRCORE.SRVPGM ProxyPassMatch "^/(profoundjs/(auth/)?PUI00091(01|02|03|04|07|09|10|19)\.PGM)$" "http://localhost:8081/$1" ProxyPassReverse /profoundjs http://localhost:8081/profoundjs

  This setting has no effect when the application is not running inside a Profound UI / Genie session. In that case, the behavior is always like "pjs".

Click here for information on how to modify this setting.

Example