1) Click on System > Support Features > Utility Node Resource Manager

2) Select the Appliance from the drop down.

a) For Traditional or DA select the master appliance
b) For standalone use Default.

3) Select "Resource List" from the drop down.  Click on Submit.  The available list of resources is displayed.

Typically, in a standalone appliance there should be only 1 entry for every resource.  As an example, the following shows the resource list for appliance CW51.cwlab.local.

Resources available for Resource Type: DOC
Node: CW51.cwlab.local:2595 | Count: 1 | Parent Appliance: CW51.cwlab.local:2595

Resources available for Resource Type: PDF
Node: CW51.cwlab.local:2595 | Count: 5 | Parent Appliance: CW51.cwlab.local:2595

Resources available for Resource Type: DRW
Node: CW51.cwlab.local:2595 | Count: 5 | Parent Appliance: CW51.cwlab.local:2595

Resources available for Resource Type: STELLENT
Node: CW51.cwlab.local:2595 | Count: 4 | Parent Appliance: CW51.cwlab.local:2595

Resources available for Resource Type: PST
Node: CW51.cwlab.local:2595 | Count: 10 | Parent Appliance: CW51.cwlab.local:2595

Resources available for Resource Type: NSF
Node: CW51.cwlab.local:2595 | Count: 10 | Parent Appliance: CW51.cwlab.local:2595

4) Resource Type: Doc - This is for IGC conversion of MSOffice documents including Outlook emails, msg files etc.
Count indicates the number of IGC threads for Doc Queue.  Here the count is 1, indicating only 1 MSOffice document is processed by IGC concurrently

5) Resource Type:PDF - This is for IGC conversion of PDF documents..
Count indicates the number of IGC threads for PDF Queue.  Here the count is 5, indicating 5 PDF conversions can be processed by IGC concurrently.

6) Resource Type:DRW - This is for IGC conversion of DRW (Drawing type) documents.
Count indicates the number of IGC threads for DRW Queue.  Here is the count is 5, indicating 5 DRW conversions can be processed by IGC concurrently.

7) Resource Type: STELLENT - This is for the STELLENT conversion threads available.
Count indicates the number of STELLENT threads for Queue.  Here is the count is 4, indicating 4 STELLENT conversions can be processed concurrently.

8) Resource Type: PST - This is for number of PST Resources available on the appliance.
Count indicates the number of PST threads for retrievals open at any given time.  Here the count is set to 10.

9) Resource Type: NSF - This is for number of NSF Resources available on the appliance.
Count indicates the number of NSF threads for retrievals open at any given time.  Here the count is set to 10.

Troubleshooting:

Common problems seen in Resource List

i)  Resource is Disabled on an appliance - text next to the Resource Type shows that the node is disabled.  Possible Reasons: 

a) D:\CWShared directory is not shared for all Clearwell (CW) accounts.  For utility Nodes or member nodes in DA environments, check if the CW account owner(s) are set to domain account.
b) Check the property browser for thread count of the particular resource type if it is set to '0' for some reason
c) Make sure IGCJobProcessorService and IGCBravaLicenseService are both up and running

ii) System Properties governing resource type (these are private to each appliance):

 a) esa.netit.processing.jpthreads.doc
 b) esa.netit.processing.jpthreads.pdf
 c) esa.netit.processing.jpthreads.drw
 d) esa.lf.dotmsg.parallel.crawling
 e) esa.processing.nsf.retrieval_parallelism
  f) esa.utility.stellent.resources
 g) esa.utility.igc.enabled (must be set to 'true' for IGC conversions to happen)
 h) esa.utility.stellent.enabled (must be set to 'true' for Stellent to function)
 i) esa.utility.retrieval.enabled (must be set to 'true' for all retrievals to function)

The above properties are self-explanatory.
 
iii) Check the JobProcessor.config file in D:\IGC\Brava! JobProcessor\  for the IGC Queue sizes

 b) thread.drw=10
 c) thread.pdf=10
 d) thread.doc=1

iv) PST and NSF are not mutually exclusive and should never be set to '0' on a standalone appliance.  For DA and traditional cluster, it is advised that only the cluster master be disabled.

v)  The 'tasklist' command should successfully execute from command line of the appliance.  If not, additional troubleshooting is necessary to resolve permission issues from Appliance to Utility Nodes and vice versa.  To test, RDP into Each appliance/utility node as the ESAApplicationService account owner, open a command prompt and run "tasklist /S ".  This should return all processes running on the remote system including the jpconsole.exe process without prompting for a password.

vi) Office 2013 should be installed and activated on Utility Nodes.  The Utility Node installer does not include   MS-Office license.

vii) Lotus Notes must be initialized on all nodes.  The EsaNSFCrawler/EsaNSFRetriever service account should be used to initialize notes.

viii) To check if each appliance/utility node is performing IGC conversions, RDP into each appliance/utility node, open a browser and point to https://.  The page displays the status of IGC as well as IGC file conversion at document level.  If the page does not display or shows errors make sure the CSFWriter (Printer) exists and it is configured properly and EsaIGCJobProcessorService is running.  The next step in troubleshooting is to check manual conversion on each appliance/utility node.  A sample pdf, tif, msg file should be used to test manual conversion.  The output can be set to jpeg format and viewed/verified using default program.
 
ix) If there is a need to reinstall IGC either as a local 'Administrator' account or a domain account,

a) The Windows Print Spooler service should be running.
b) The account must be a local admin account on the utility node/appliance.  It is required that the local 'Administrator' account have the same password on all appliances/utility nodes or a 'Domain account' be used as the IGC installation account.

Note: CSFWriter is used only for MSOffice documents.
 

Below is a screenshot of the Utility Node Resource Manager Support Feature

Applies To

Applies to all environments Clearwell v7.12 and above.

• Standalone Server
• Traditional Cluster
• Scale-out Cluster - Distributed Architecture (DA)
• Utility Nodes