This section lists any critical issues for the current release that were known when this readme was published. For critical information found later, go to the Knowledge Center on the Empower website.

webMethods Monitor 10.15 requires that the program files and user interface are the same version.

When installing webMethods Monitor 10.15, you must install webMethods Monitor 10.15 Program Files along with the 10.15 version of the Monitor User Interface located under My webMethods Server User Interfaces on the install tree.

webMethods Monitor 10.15 requires My webMethods Server 10.15.

Before you can use webMethods Monitor, you must configure My webMethods connection parameters from the WmMonitor Home page. To access the configuration page, on the Package Management page in Integration Server Administrator, click the Home icon for the WmMonitor package. For complete information about configuring My webMethods connection parameters, see webMethods Monitor User's Guide.

webMethods Monitor 10.15 is compatible only with the 10.15 version of Optimize for Process and Optimize for Infrastructure.

webMethods Monitor 10.15 lists process instances from the current day’s activity by default.

When you use Monitor to view process instances, Monitor lists only process instances from the current day’s activity. To retrieve other process instances, you can specify an alternate date range in the Advanced tab on the Process Instances page.

When you use Microsoft SQL Server and you create Process Audit Log database objects, a warning message is displayed stating that the index is too large. You can ignore this message.

To use the archive feature, the schema for the archive tables should exist on the same database instance as the schemas for Process Audit Log and IS Core Audit Log.