When something does not work, and you can't understand what, run the system health check and check log files.
The system Administrators can run the System Diagnostics and Download Server Logs from the Administration application homepage:
The "System Diagnostics" Action can be executed by Administrators from the Administration application → Home landing page by clicking on the corresponding button. A check for many system components will be executed, and in case the issue is present, this will be shown.
The following states are possible:
We highly recommend fixing issues and having the System Diagnostics pass all the validation rules with Success to be sure the system is working correctly:
In case of error or warning, click on the checked item and scroll down to the Details section for more information:
Fix the issues and re-run the System Diagnostics.
System Diagnostics checks the following items and system components:
|#||Verified component||Comments & Useful Links|
|1||Verify that windows service 'Matrix42 Engine Common' is running||System Components: Windows Services|
|2||Verify that windows service 'Matrix42 Engine Common X86' is running||System Components: Windows Services|
|3||Verify that windows service 'Matrix42 Engine Scheduler' is running||System Components: Windows Services|
|4||Verify that windows service 'Matrix42 Data Gateway' is running||System Components: Windows Services|
|5||Verify that windows service 'Message Queuing' is running||Windows Services|
|6||Verify that windows service 'Net.Msmq Listener Adapter' is running||Windows Services|
|7||Verify that windows service 'Net.Pipe Listener Adapter' is running||Windows Services|
|8||Verify that windows service 'Net.Tcp Listener Adapter' is running||Windows Services|
|9||Verify that windows service 'Net.Tcp Port Sharing Service' is running||Windows Services|
|10||Verify that any Matrix42 Worker is running||Matrix42 Worker Engine|
|11||Serious delays in processing Workflows operations||Matrix42 Worker Engine|
|12||Verify that the Email Engine is active||Email Engine and Designer|
|13||Verify that Workflow Engine on the Matrix42 Worker is running||Matrix42 Worker Engine: Matrix42 Workers & Workflows|
|14||Verify that all Compliance Rules uses the Email Engine for sending emails||
For warnings on this item, please consider adjusting the system as described on this page: Compliance Rules: switching to the new Email Engine
|15||Verify that the Data Gateway on the Matrix42 Worker is running||For warnings on this item, please consider adjusting the system as described on this page: Matrix42 Worker Engine: Using Matrix42 Workers as Data Gateway|
|16||Verify that windows service 'AppFabric Workflow Management Service' is running||Windows Services|
|17||Verify that windows service 'AppFabric Workflow Management Service' is running under account in AppFabric Security group||Windows Services|
|18||Verify that windows service 'AppFabric Event Collection Service' is running under account in AppFabric Security group||Windows Services|
|19||Verify that windows service 'AppFabric Event Collection Service' is running||Windows Services|
|20||Verify that AppFabric Security configured correctly||Workflow Engine: AppFabric|
Verify released Workflows compatible with the Worker
For warnings on this item, please consider adjusting the system as described on this page: Workflow Engine Migration Guide
See also Manage Workflows: Runs on AppFabric
|22||Verify connection to database 'Archive'||History Wizard|
|23||Verify connection to database 'Datawarehouse'||Data for license management reports|
|24||Verify connection to database 'Database File Storage'|
|25||Verify that windows service 'Web Deployment Agent Service' is running||Windows Services|
|26||Verify connection to database 'Workflow Monitoring'||Workflow Instances Activity Monitoring|
|27||Verify connection to database 'Workflow Persistence'||Workflow Engine: Persistence|
|28||Verify Workflow activations||Workflows: Publish action|
|29||Verify Workflow Engine to start workflow synchronously||Workflow Engine|
|30||Verify Workflow Engine to start workflow asynchronously||Workflow Engine|
|31||Verify Workflow Instance running on Matrix42 Worker||Workflow Instances Activity Monitoring: Runs on AppFabric|
|32||Verify that present Workflow Instances are valid||Workflow Instances Activity Monitoring|
|33||Verify connectors configurations||Connectors Overview: Connectors Delivered with Matrix42 products|
|34||Service Connections validation||Service Connections|
|35||Validating display expressions|
|36||Validating dynamic structures|
|37||Validating GDIE rules||Generic Data Import Export|
|38||Validating grid layouts|
|39||Validating quick filters||Quick Filters|
|40||Validating structures||Navigation Items: Structures|
|41||Verify that reports are accessible.||Reports|
Starting with DWP v.11.0 all system components check related to the Data Gateway, AppFabric, and legacy Alerting Engine for Compliance Rules (see items #14-20) will not be present in the System Diagnostics.
System Status dashboard is shown on the Administration home page.
System Status is run automatically when the home page of the Administration application is opened for the first time and is automatically refreshed every 3 hours after the last automatic check:
Click on the Run System Diagnostics action to update the System Status dashboard manually.
The dashboard shows when the last check has been run and a summary of the found issues of the following types:
For more details on the found issues, click on the checked item:
Download system logs
It is possible to download logs from the application, without directly accessing the Application Server. This can be done by clicking on the Administration application → Home → Download Server Logs button:
All Server Logs are downloaded locally to your device in a .zip archive.
You can also check specific logs from the Application Server. As a rule, in the default setup log files are located in
C:\Program Files\Matrix42\Matrix42 Workspace Management\Logs\ directory.
For more information on the log file types, see also System Components: Web Application section of the page.