What are the process names involved in NuGenesis client and server components? - WKB124612

ENVIRONMENT

• NuGenesis 9
• NuGenesis 8
  • Note: The process names listed below are primarily from NuGenesis 9. The process names in NuGenesis 8 SDMS are similar but incorporate "80" in the name. For example, NGipvw.exe in NuGenesis 9 is named NG80ipvw.exe in NuGenesis 8.

ANSWER

• SDMS Transfer App:
  • NGipvw.exe - is the registered app for .NGX files.  When IE downloads and opens an NGX file from vision, it runs this program, and NGipvw reads the NGX file to determine whether the files should be opened in Preview (NGprev.exe) / Restore (NGrest.exe) / or quick restore (NGLApp.exe)
  • NGProv.exe - overlay viewer in NuGenesis Preview
  • Inspector.exe - viewer for JCAMP files and other scientific data formats.  Started by the transfer app when selecting a record for quick restore and the record has a JCAMP file associated with it (produced by the data converter during the file capture process)
• SDMS Administrator:
  • NGpm.exe
  • NGatbld.exe - archive template builder
  • NGtbld.exe - UNIFY/extraction template builder
  • NGsbld.exe - script builder
• UNIFY:
  • spoolsv.exe - Windows print spooler
  • splwow64.exe - print spooler for 32-bit apps on 64-bit Windows
  • NGedvo.exe - main UNIFY process for print job processing.  Also displays the UNIFY setup window and the tag dialog boxes before/after printing
  • NGprox.exe - proxy process.  Watches the UNIFY printer queues for jobs where the job owner = the owner of the ngprox.exe process and takes it out of the queue for processing by NGedvo.exe
  • The printing app process, such as winword.exe for Word
• LMS client:
  • eln.exe
  • slim.exe - Stability client
  • excel.exe - started when opening an Excel section
  • winword.exe - started when opening Word sections
  • powerpnt.exe - started when opening PowerPoint sections
• Smart Builder:
  • excel.exe - Smart Builder runs as a plug-in DLL inside Excel
• SDMS web server:
  • NGwvls.exe
  • NGwvpc.exe
  • w3wc.exe - WWW worker process, started by IIS when it receives an HTTP or HTTPS request
  • tomcat9.exe - Apache Tomcat server process for NuGenesis 9 SDMS
  • tomcat6.exe - Apache Tomcat server process for NuGenesis 8 SDMS
• NuGenesis RPC service:
  • NGRPCService.exe - main process for the NG RPC service.  Starts 2-4 NGRPCShadowServer.exe processes, depending upon the installed modules
  • NGRPCShadowServer.exe - worker process for the NG RPC service.  If NGRPCService.exe loses communication with a shadow server (for example, a process crash), the service will spawn a new shadow server process
• NuGenesis LMS JBOSS / WildFly server:
  • java.exe
  • Note: the LMS Job Manager and Scheduler services also run as java.exe.  In a fully-functional system there will be 3 java.exe processes running.  To link a java.exe process with a service, look at the end of the command line for the process, as seen in Procmon or task manager: ".CrJobManager" is the Job Manager, ".CrJobScheduler" is the LMS Job Scheduler, "-c eln" is the LMS Server
  • Java.exe is also used for the LMS server configuration tool
• NuGenesis Document Creator:
  • CreateDocumentService.exe
    • Excel.exe - started when the DCS starts; allows the DCS to read/write the contents of LMS document sections
    • Winword.exe - started when the DCS starts; allows the DCS to read/write the contents of LMS document sections
  • ConfigDocumentCreator.exe - configuration tool for the DCS

ADDITIONAL INFORMATION

This list is most useful when analyzing a Process Monitor trace of a NuGenesis software problem. Match the description of the problem (such as "UNIFY print is not working")  to the process list above, and look for those processes in the Process Tree view in procmon.

The client apps—primarily eln.exe, NGprox.exe, ngedvo.exe, ngipvw.exe/ngrest.exe/ngprev.exe, excel.exe/winword.exe—will often be seen multiple times in the process tree, particularly for Citrix systems where multiple user sessions are present. If a specific user reproduced the problem, ask for their user ID, and then find the matching client process in the tree where the owner is that user's ID.