This file provides important information you should read before installing and using webMethods Monitor 6.5.1 Service Pack 2.
For release information about webMethods Monitor and other components of webMethods Fabric, see webMethods Fabric Release Notes 6.5. For information about technical support, see the General Support Statement for webMethods Fabric.
2.0 Known Issues
3.0 Usage Notes
5.0 Deprecated Items
7.0 Platform Support
The following list describes the critical issues that were known when this readme was published.
- webMethods Monitor 6.5.2 SP2 requires that you have My webMethods Server 6.5.2 with MWS_6-5-2_Fix1 or a later version installed.
- All of the My webMethods connection parameters have been removed from the webMethods Monitor configuration. You must now configure these parameters using the Common Authorization Package (WmComauth). As a result, you must have the WmComauth package installed and configured before using webMethods Monitor.
For late-breaking critical information, refer to theon the .
When the Japanese Language Packs are installed for the webMethods Monitor and My webMethods Server user interface, Monitor displays some system-defined strings for Process, Status, Filter By, and Range in Japanese even if the Preferred Locale is set to English in the User Profile.
When editing a pipeline, you cannot edit fields that have the data type of String Table.
On the Business Monitoring > Processes > Process Instances page, Monitor disables the check boxes for BAM process instances (i.e., displays them grayed out) because BAM process instances are not eligible for resubmission. Users cannot select these check boxes individually. However, when you click the "Select All" icon, Monitor selects the BAM process instances and enables the Resubmit button.
As a workaround, when the Process Instances page includes a mix of BPM and BAM process instances, select the process instances you want to resubmit one by one rather than use the "Select All" icon.
You can only export data for the Start step on the Step Report page. You access the Step Report page by clicking "Total Steps" from the Business Monitoring > Process Reports, Instances page. The Step Report page contains details about steps in processes. When you export the data for any step on the Step Report page, Monitor always exports the data for the Start step regardless of the step you select.
When searching for process models, if process description search criterion is used, the search fails; Monitor returns an empty result set. This issue affects the following:
- For BAM models, a full description search does not work in the Keyword search or "Process Description" field.
- For BPM models, partial and full description searches work in the Key Word search field. However, neither partial nor full description searches work in the "Process Description" field.
The Data Management > Archiving > Archive page in My webMethods does not function properly. You cannot archive data using the My webMethods user interface. As a workaround, you can archive data by either:
- Executing services in the pub.monitor.archive folder, which is in the WmMonitor package
- Running stored procedures directly on the logging databases
For more information about these alternative methods, see the webMethods Monitor User's Guide.
For other known issues and troubleshooting information relating to webMethods Monitor, see theon the .
Viewing images in SVG format is the default setting in Monitor. When using an SVG viewer in multi-byte OS environments, users need to download the local version of the Adobe SVG plug-in.
webMethods Monitor 6.5.1 SP2 includes the following fixes and service packs that were shipped since the last release.
You cannot resubmit services from the My webMethods Integration Monitoring > Services page; "No services were eligible for resubmission" error is issued.
Using the My webMethods Integration Monitoring > Services task, use the search panel to search for services. In the search results, select the services that you want to resubmit, then click Resubmit. Monitor invokes a resubmit service passing it the list of services to resubmit. However, the resubmit fails, and Monitor issues the message "No services were eligible for resubmission". The Monitor resubmit services were not handling a list of services to resubmit.
This issue has been resolved by updating the Monitor resubmit services to handle a list of services as input.
Using My webMethods to search for services, webMethods Monitor returns old search results that do not include information about recent services.
Using the My webMethods Integration Monitoring > Services task, you can use the search panel to search for services. After performing a search, webMethods Monitor displays the search results and also caches the results. If additional services are executed, and you click Go to re‑execute your search, Monitor re-displays the cached search results. Monitor does not display information for the recent services that meet your search criteria.
This issue has been resolved so that Monitor now displays the correct search results.
webMethods Monitor does not retain the values you change in a service pipeline when the pipeline has nested fields or documents.
Using the My webMethods Integration Monitoring > Services task, you can view the Service Detail page for a service. From the Service Detail page, you can use the Edit Pipeline button to view and alter the pipeline data for the service. If the pipeline data contains nested fields or documents, you can update field values and save as normal. It appears that Monitor saved the updated values. However, if you click Edit Pipeline again, you will see that the fields have their original value and that the updated values were not saved.
This issue has been resolved by updating webMethods Monitor so it retains the modified values when there are nested fields and documents.
When editing pipelines, only the first line of multi-line data is displayed, and Internet Explorer might become unresponsive when attempting to display pipeline data.
When attempting to edit pipelines (for both services and process steps), the following can occur:
- If a field in the pipeline contains multi-line data, only the first line of the data is displayed.
- When using Internet Explorer 6.0 to display pipeline data that contains a nested document, the Web browser becomes unresponsive.
Monitor was not properly encoding the Carriage Return/Line Feed (CRLF) characters in the pipeline data. As a result, My webMethods Server was handling the characters as end of data indicators.
This issue has been resolved by updating Monitor to properly encode the CRLF characters. Additionally, Monitor no longer automatically expands all nested sections of the documents within the pipeline when displaying data on the Edit Pipeline page. Nested sections are now only expanded on demand. This prevents Internet Explorer from becoming unresponsive when attempting to expand a large, complex nested set of documents.
webMethods Monitor does not display the complete pipeline data if the data contains a Carriage Return/Line Feed character (CRLF).
Using the My webMethods Business Monitoring > Processes > Process Instances task, you can view the Process Instance Detail for a process and also the Step Instance Detail for each step in the process. From the Step Instance Detail page, you can use the Edit Pipeline button to view, and optionally alter, the pipeline data for the step. If the pipeline data for the step contains a CRLF, webMethods Monitor only shows the pipeline data up to the CRLF character and does not show the remaining pipeline data.
This issue has been resolved by correctly handling the CRLF character so that all pipeline data is displayed when a CRLF character is in the pipeline data.
The error "[POP.012.9002.wm_bam_instance_list] Remote Exception caught: electric.util.WrappedException: java.rmi.ConnectException: url = http://<ipaddress>:5555/soap/rpc" is received when resubmitting a process.
Using the My webMethods Business Monitoring > Processes > Process Instances task, you can resubmit a process. If the process is resubmitted to a server that is not localhost:5555, the error described above occurs. The error occurs because webMethods Monitor used a hardcoded port of 5555.
This issue has been resolved by updating Monitor so that it does not use a hardcoded value for the port; as a result, processes can now be resubmitted to servers that use any port and host.
For detailed information regarding these fixes and services packs, see theon the Web site.
A new configuration screen has been added to the WmMonitor package. On this screen
- The field previously labeled "Administrator" is now labeled "Data Level Security Administrator" to better clarify its purpose.
- All of the My webMethods connection parameters have been removed from the Monitor configuration. You now configure these parameters through Common Authorization Package (WmComauth).
Additionally, this screen allows you to set properties that you previously had to set by editing text files. To access the new screen:
2. In the row for the WmMonitor package, click the icon in the Home column.
Parent context ID, root context ID, and context ID search criteria are not available when searching for services.
webMethods Monitor versions 6.5 through 6.5.1 SP1 do not include fields to search for services using the parent context ID, root context ID, or context ID of a service.
This issue has been resolved by adding fields to the Advanced tab of the Integration Monitoring > Services page for the parent context ID, root context ID, or context ID.
If you resubmit a process instance and then reload the page with the Web browser, the process instance is resubmitted again.
From the Business Monitoring > Processes > Process Instances page you can view the details for a process instance and then the details for a step within the process instance. From the Process Step Detail page, when you click Resubmit, the process is resubmitted starting at the step. If you then use the Web browser's reload button to reload the page, the process is resubmitted again.
This issue has been resolved so that a process is not resubmitted when using the browser to reload the Process Step Detail page.
Monitor displays blank service information when you attempt to view Parent Service or Child Services information from the Service Detail page.
On the Integration Monitoring > Services > Service Detail page, when a service has a parent service, Monitor displays its name in the "Parent Service" field. Similarly, if the service has child services, Monitor displays the service names in the "Child Services" field. The service names are hyperlinked, so you can click on them to view the details for the corresponding service. However, when you click on a service name in the "Parent Service" or "Child Services" fields, Monitor displays blank information.
This issue has been resolved.
Parent context ID, root context ID, and context ID are not displayed in the service detail information.
webMethods Monitor versions 6.5 through 6.5.1 SP1 do not include fields for the parent context ID, root context ID, or context ID of a service on the Integration Monitoring > Services > Service Detail page.
This issue has been resolved by adding these fields to the Service Detail page.
Several time fields on the Process Instance Detail and Process Step Detail pages do not include milliseconds in the time value.
You access the Process Instance Detail and Process Step Detail pages from the Business Monitoring > Processes > Process Instances page. Monitor does not include milliseconds when displaying:
- On the Process Instance Detail page, the "Start Date/Time" on the Step Summary tab and the "Date/Time" field on the Logged Fields and Process Errors tabs
- On the Process Step Detail page, the "Date/Time" fields on the Step History, Logged Fields, and Step Errors tabs
This issue has been resolved. Monitor now includes the milliseconds when displaying the fields listed above.
Monitor displays commas incorrectly in pipeline data for a service.
You can view the pipeline for a service from the Integration Monitoring > Services > Service Detail page. When the pipeline data contains commas, Monitor converts the commas to their URLEncoded equivalent and all other data is left as is. If the pipeline data already contains URLEncoded commas, the resulting data is incorrect. For example, if the pipeline data contains "1, 2, 3", after Monitor converts the commas to their URLEncoded equivalent, it might look like "1%2C 2%2C 3".
This issue has been resolved.
The message "[POP.004.0002] The Message Key 'table.column.errorMessage' was not found in the Resource Bundle 'com.webmethods.bpo.portlet.wm_mon_service_details.resources.Mon_service_detailsResources' appears for Failed services.
You can view the details for services on the Integration Monitoring > Services > Service Detail page. For services in a Failed status, the error message listed above is listed in the service detail information rather than the actual error message for the service due to an error in the resource bundle.
This issue has been resolved.
This service pack requires that you have My webMethods Server 6.5.2 with MWS_6-5-2_Fix1 or a later version installed.
webMethods Monitor 6.5.1 SP2 is supported on the same platforms as webMethods Monitor 6.5.1.
To install this service pack, follow the procedure described in the webMethods Installation Guide.
This service pack conforms to the internationalization standards of webMethods and includes support for operation in any country, locale or language. It was tested with non-English configurations and non-ASCII data.
Language packs containing support for other languages, when available, can be installed at any time using webMethods Installer.
For webMethods Monitor 6.5.1 technical documentation, go to the webMethods6\IntegrationServer\packages\WmMonitor\doc directory or the. The following manuals are provided as PDF files:
- webMethods Monitor User's Guide
To view the documentation, you must have.
webMethods Access, webMethods Administrator, webMethods Broker, webMethods Dashboard, webMethods Developer, webMethods Fabric, webMethods Glue, webMethods Installer, webMethods Integration Server, webMethods Mainframe, webMethods Manager, webMethods Modeler, webMethods Monitor, webMethods Optimize, webMethods Portal, webMethods Servicenet, webMethods Trading Networks, and webMethods Workflow are trademarks of webMethods, Inc. webMethods and the webMethods logo are registered trademarks of webMethods, Inc.
All other marks are the property of their respective owners. Copyright (c) 2006 by webMethods, Inc. All rights reserved, including the right of reproduction in whole or in part in any form.
This product includes software developed by the.
This product includes software developed by.
Authorized technical support contacts can reach webMethods Customer Care for support via:
Web: webMethods online support center
Japan 0120-979-762 (Toll Free in
In addition, self-service support is available in theand in the .
To view information about the previous release of webMethods Monitor, see the.