System Utilities - EcoSys - 3.1 - Help - Hexagon

EcoSys Connect Help

Search by Category
EcoSys Version

The System Utilities page displays additional information such as dispatcher logs, system health (status of the connect components), and encrypting passwords. To view the System Utilities, click in the UI.

Dispatcher logs

The dispatcher logs can be accessed from the UI. This log contains information about actions taken within the UI, such as creating an agent, updating a repository, and kicking off a job (The log files does not contain details about job execution).

  1. To view the logs, click System Utilities and then click Logs tab.

  2. To download the logs, select the download format, and enter the required number of entries and click Download

System Health

The System Health page shows the status of the Connect components such as the ActiveMQ Broker, the dispatcher, and agents.

To view the system health, click System Utilities and then click System Health tab.

System Configuration

To view the system settings for all Connect components, click System Settings icon.

Encrypt Password

This page can be used to encrypt passwords to be used in the Connect property files.

  1. Click the ENCRYPT PASSWORD tab.

  2. Enter the password and click Encrypt.

    The encrypted password will be displayed in Encrypted Results section.

  3. Copy and paste the entire string in the property.

Logging Controls

This page controls the logging levels for Dispatcher, Agent, and LogAgent.

  1. Click the LOGGERS tab.

    No rows are displayed when you login initially.

  2. To change the logging, click the + button.

  3. Select the component from the list- All, Dispatcher, Agent, LogAgent.

  4. Select the log level- INFO, WARN, ERROR, DEBUG

  5. Click Apply.

    • Log levels are changed immediately on all components. No restart is required.

    • Log Levels are preserved during restarts and upgrades.

  6. To revert to the default logging level, either delete the row in the table or set the logging level to INFO. It does not enable logging of SOAP or OData request/response messages.

Using Self-Signed Certificates

When a SOAP end-point uses a self-signed certificate, the certificate need to be uploaded to Connect for the repository to be successfully created.

To add a certificate,

  1. Click the CERTIFICATES tab.

  2. Enter an alias name.

  3. Select the local certificate file to upload.

  4. Click OK.

    For some endpoints, hostnames might not match the certificate Common Name. In this case, the following error might be seen in the logs

    The https URL hostname does not match the Common Name (CN) on the server certificate in the client's truststore.  Make sure server certificate is correct, or to disable this check (NOT recommended for production) set the CXF client TLS configuration property "disableCNCheck" to true

    To resolve this error, the server setting connect.common.soap.disableCertificateCNCheck=true can be set in the dispatcher and agent properties files stored in GIT. This requires a restart of the dispatcher and agent.