How to add more VISION daemons to a NuGenesis SDMS web server - WKB61834

OBJECTIVE or GOAL

Have more than one local or remote VISION daemon running on a NuGenesis web server so as to share the processing load between processes and/or servers.

ENVIRONMENT

• NuGenesis 8 SDMS
• NuGenesis 9 SDMS

PROCEDURE

To add more local VISION daemons:

1. No additional installations are necessary for multiple local VISION daemons. The only changes needed are in the WebVision.ini configuration file.
   • NuGenesis 8: Drive:\Program Files (x86)\apache-tomcat-6.0.29\webapps\WebVision\ngvisionWebVision.ini
   • NuGenesis 9: Drive:\Program Files (x86)\Waters\apache-tomcat-9.0.8\webapps\WebVision\ngvision\WebVision.ini
2. Edit WebVision.ini in Notepad. Look for the following line:
   • // servers
3. The line immediately below "// servers" is the configuration line for the local NuGenesis VISION daemon. Each line packs a lot of parameters. For a local daemon, only the second parameter needs to be changed.
4. Copy the line that begins with "local='localhost',1,12020,..." and paste it on a new line below the first one. On the new line, change the second parameter to a 2. This parameter is the serial number for each VISION daemon known by the SDMS web/app server. The number must be incremented for each daemon added to the server. All other parameters can stay the same. Example lines:
   • local='localhost',1,12020,100,100,'C:\\Program Files (x86)\\NuGenesis 8.0\\Application Server\\','','','','NuGenesis RPC Service V8.0','WIN2008-64-MM1',2505
   • local='localhost',2,12020,100,100,'C:\\Program Files (x86)\\NuGenesis 8.0\\Application Server\\','','','','NuGenesis RPC Service V8.0','WIN2008-64-MM1',2505
5. Save and close WebVision.ini.
6. Restart the following services, in this order, or restart the entire server:
   1. Restart Apache Tomcat
   2. Stop World Wide Web Publishing.
   3. Restart NuGenesis VISION Server.
   4. Start Word Wide Web Publishing.

To add more remote VISION daemons:

Note: Remote WebVision daemons are NOT supported in NuGenesis 9.

After installing the "Remote WebVision Daemon" components on a separate server, go back to the SDMS web/app server, edit WebVision.ini, and look for the "//remote=..." line in the file. This line is commented out in the file, so it doesn't have any effect on the operation of the Vision listener and daemons, but it does serve as an example line. Copy and paste this line into the file, edit the new copy to remove the comment characters "//", and replace the placeholder text with the following:

REMOTE_HOST=hostname of the remote VISION daemon server

REMOTE_PATH=Install path of the VISION daemon components on the remote server

NGRPC_NAME=should be NuGenesis RPC Service v8.0 unless customized

NGRPC_ADDR=should be the same as the local daemons as the remote daemons do not have the NuGenesis RPC service installed

Follow the procedure above under local daemons to make the change go into effect.

ADDITIONAL INFORMATION

Local daemons: the effect of this change is that the NuGenesis VISION listener process will spawn two daemon processes and will pass user requests onto the the daemons in a round-robin fashion. The additional process will allow the VISION processing to make more effective use of CPU time on a multi-core processor. A single process in Windows is limited to 100% usage of a single core, which is actually just a percentage of the total CPU usage (25% of a four-core CPU). Multiple daemons will share the load and use more CPU time to process user requests more efficiently.

Remote daemons: This type of daemon differs from the local variety in that the NG80wvpc.exe or NGwvpc.exe process runs on a separate machine from the VISION listener and other local daemon(s). It requires a separate machine that doesn't have any NuGenesis software installed or the installation of the VISION daemon components. The VISION daemon components installer can be found on the NuGenesis Base media kit. Follow the setup program prompts to install the daemon components.

The NuGenesis VISION listener communicates with the daemons via port 12020 by default, so make sure that this port is opened through the firewall on the SDMS web/app server and the remote daemon servers, if any.