| Sometimes, a race condition can occur when you install Operations Hub. Because of this, events may not work in the newly installed application. To resolve this issue, restart the IQP Tomcat service. | US385525 |
| When you export an application that contains an image widget, the images used in the widget are not exported. You must manually place the images in the target Operations Hub instance. | US383459 |
| When you save a favorite in a trend chart, if you include a special character in the name, the error message that appears does not specify the issue. | DE123967 |
| In a trend chart, if you add a tag that is identical to the one that is already plotted but the case of the tag name does not match the case of the tag name in Historian, a straight line appears in the trend chart. To resolve this issue, modify the tag name to match the case of the tag name in Historian. | DE123833 |
During Operations Hub installation, when you provide the tenant user ID, the following conditions apply:- If you are installing Operations Hub for the first time, do not provide StudioAdmin as the tenant user ID because it is used by Operations Hub.
- If you want to use a shared UAA to work with Operations Hub, do not provide the user ID of an existing user of the UAA instance. If you do so, the installation fails.
- If you are installing Operations Hub after uninstalling it without purge, do not provide a tenant user ID that matches any previously used user ID (including any previously used tenant ID). This is because after you uninstall Operations Hub without purge, previousOperations Hub users (along with tenant administrators, their groups, and privilege assignments) still exist in the database.
| DE123770 |
| You can create multiple data sources with the same URL. After you restart the services, the Data Distributor service uses the most recently saved System API authentication settings for the URL. Therefore, if the most recently saved credentials do not work, you cannot connect to the data source. To fix this issue, modify the data source to specify working credentials, and then test the data source. We recommend that you do not save the data sources that do not pass the test or data sources with the same URL. |
|
If you install Historian after installing Operations Hub on the same machine, sometimes, the Operations Hub login page does not appear. This is due to a conflict between the ports used by the two applications. To avoid this issue, perform one of the following workarounds:- Stop the Historian Tomcat instance, restart the IQP Tomcat instance, and then start the Historian Tomcat instance.
- While installing Operations Hub, provide a different port number for the IQP HTTP port so that it does not conflict with the port used by Historian.
| DE122500 |
| When you import an application, if an application with the same name exists, the new one is given a unique name. This is to avoid replacing the existing application with the new one. If, however, you want to replace the application with the new one, specify the same name for both the applications. This also applies to the queries and entities that are imported along with the application. However, in some scenarios, queries and entities are copied even if you wanted to replace. | DE120745 |
| Some widgets, such as a table, do not work as expected when used with a REST query. In particular, features which require additional queries to fetch more data (such as pagination), as well as features limiting data (such as row limits) may not work. | DE118883 |
| When you create a data source, you can provide a certificate only in the base-64-encoded format. A DER-encoded certificate is not supported. | DE116706 |
| Operations Hub uses Kafka, which generates a large number of logs in the following location: C:\tmp\kafka-logs\. To avoid consuming too much space for these logs, we recommend that you periodically delete the logs, especially if the system has low disk space. | N/A |