Release Notes
Getting Started with Operations Hub
User Guide
- Overview
- Operations Hub (New Layout)
- Applications
- Entities
- Queries
- Plug-ins
- Events
- Email Templates
- Parameters
- Users
- Roles
- Administration
- Data Sources
- Pages
- Navigation
- Explorer
- Themes
- Settings
- Widgets
- General Reference
- APIs
- Troubleshooting
  - Basic Troubleshooting
    This topic contains information to help you troubleshoot issues.
  - Error Codes
  - Error Messages
    A list of connection errors, their cause, and action to be taken.
  - Configure Logs to Troubleshoot Licensing Issue
    With Operations Hub licensing enforcement, you may be asked to purchase a license even when you have a valid license activated on your license client.
  - Configuration of Logging for Services
  - Modify Registry for TLS 1.2
    This topic describes how to modify the registry setting on the Operations Hub server to allow for TLS 1.2.
  - Scalable Vector Graphic (SVG) Editor Tools
    Scalable Vector Graphic (SVG) is a vector image file type. The SVG images are scalable, that is, you can modify the shapes, lines, curves, and so on or, resize the SVG images without affecting the image quality.
  - Addressing Import Errors: Invalid Application/Page Name
    With Operations Hub 2024 release, restrictions have been imposed on the use of special characters for both application and page names.

Configuration of Logging for Services

You can find log configuration for every service at the following location.

WebHMI Services: <Directory where Operations Hub is installed>\webhmi-tomcat\webapps\<Service>\WEB-INF\classes\logback.xml
IQP Apps: <<Directory where Operations Hub is installed>\iqp-tomcat\webapps\<site/app/eventengine>\WEB-INF\classes\ logback.xml

Important Configurations

MaxHistory: https://logback.qos.ch/manual/appenders.html#tbrpMaxHistory. For more information, refer to https://logback.qos.ch/manual/appenders.html#SizeAndTimeBasedRollingPolicy.

To configure package level logging or any changes on the logging configuration that do not require restart of the tomcat container.

(http://logback.qos.ch/manual/configuration.html#autoScan scan=true) which detects runtime changes on log level without need to restart the service. But currently it is kept disabled, as it has runtime impact.

You can configure package level logger highlighted as below:

https://logback.qos.ch/manual/configuration.html#loggerElement

UAA Services

<Directory where Operations Hub is
               installed>\uaa-tomcat\webapps\uaa\WEB-INF\classes\log4j2.properties