Couple of suggestions

[gustafssone]

Hi! Couldn't resist investigating...

I am assuming this is tested on a local machine where there are lots of "leftovers", and plenty of work left, but perhaps this can add some insight.

A few things I noticed:

• Not clearly defined where to put the folders. "Should governanceCollector and Installer go straight into C:\Program Files\Qlik\Sense\EAPowerTools?"
• The Installers install.js requires plenty of node.js modules, which I guess can be added automatically, otherwise it would give an error on what modules are missing. It is quite easy to just add whatever "require" that it is missing though.
• Reference to Jeffs own computer at governanceCollector\webapp\config\settings.json.
• Not using HTTPS, which everything else does.
• governanceCollector\webapp\config\services.conf and governanceCollector\agent\config\services.conf references "ExePath=node\node.exe" and not "ExePath=node.exe". The C:\Program Files\Qlik\Sense\EAPowerTools\PowerToolsServiceDispatcher\services.conf thus needs to be updated.
• Ability to choose paths and folders to be used everywhere. Perhaps not a new library?
• Agent requires a reference to C:\Program Files\Qlik\Sense\EAPowerTools\governanceCollector\install however the installer is named InstallER, which then doesn't make the Agent starting. It is required to rename this folder so that the Agent can copy the apps.
• governanceCollector\agent\config\config.js refers to "c:/qvds" but Installer\install.js refers to "c:\qvdOutput". I am assuming this should be the same one.
• governanceCollector\agent\apps-info.js refers to a file called "apps-info-neo.js". This file is nowhere to be found. No errors AFAIK though.
• "undefined" in the Governance UI if no server is selected. You can press "Governance!" despite no server being added.
• "Error processing dimensions for app 1ef91bf6-779f-4aac-8b83-6a7fe4a6733c {"code":-1,"message":"Socket closed"}" in the console of the UI. On almost all of the files this is referenced: {"jsFile":"app-library-stories.js","level":"error","message":"{}","timestamp":"2017-08-11T12:38:23.973Z"} {"jsFile":"app-sheets.js","level":"error","message":"{\"code\":-1,\"message\":\"Socket closed\"}","timestamp":"2017-08-11T12:38:23.984Z"} {"jsFile":"app-sheets.js","level":"error","message":"{\"code\":-1,\"message\":\"Socket closed\"}","timestamp":"2017-08-11T12:38:23.984Z"} [THIS IS WHERE I GOT STUCK]
• This also makes the reload script for the QVD fail as qrsAccessControlMatrix.xml is not found: 2017-08-11 14:16:55 0161 FROM [lib://qsgc-metadata/qrsAccessControlMatrix.xml] 2017-08-11 14:16:55 0162 (XmlSimple, table is [qrsAccessControlMatrix/qrsAccessControlMatrix/App.Object/audit/access]) 2017-08-11 14:16:55 Error: Cannot open file: 'lib://qsgc-metadata/qrsAccessControlMatrix.xml' 2017-08-11 14:16:55 Execution Failed

Logfile attached.

2017-08-11.QlikSenseGovernance.log.zip

Prerequisites

• [X] Put an X between the brackets on this line

[gustafssone]

Seems that an upgrade was required. I was testing this for version 3.1.1. June patch 1 - got me past the error message above. Got stuck during the qvd load script but should be easier (KeyTables kept loading indefinitely). Will get back to you on that part.

Do you know if 3.2 SR3 would work? I have a customer environment where this version is used.

Parsing the logs gave the following error though, something is up there. {"jsFile":"parseScriptLogs.js","level":"info","message":"begin parsing","timestamp":"2017-08-11T14:18:02.409Z"} {"jsFile":"parseScriptLogs.js","level":"info","message":"Identifying files to parse in \\WIN2012R2\share\ArchivedLogs","timestamp":"2017-08-11T14:18:02.409Z"} {"jsFile":"parseScriptLogs.js","level":"info","message":"1 files to process","timestamp":"2017-08-11T14:18:02.424Z"} {"jsFile":"parseScriptLogs.js","level":"info","message":"Processing file number 0: win2012r2","timestamp":"2017-08-11T14:18:02.679Z"} {"jsFile":"parseScriptLogs.js","level":"error","message":"Error parsing win2012r2","timestamp":"2017-08-11T14:18:02.706Z"} {"jsFile":"parseScriptLogs.js","level":"info","message":"Parsing script log files complete","timestamp":"2017-08-11T14:18:02.707Z"}

All other suggestions are still valid :)