Development toolkit troubleshooting
These sections describe problems you might encounter while you are using the Business Monitor development toolkit.
You can find the latest troubleshooting tips as well as information about downloads and fixes at the following page: http://www.ibm.com/support/entry/portal/overview//software/websphere/websphere_business_monitor.
- Business Monitor server fails to start in the test environment
If you used a non-administrative ID to install an IBM Business Monitor server in a Windows installation of IBM Integration Designer, it is possible that the server will fail to start in the Servers view. - Java EE project generation results in an out-of-memory condition
When you generate Java EE projects for very large monitor models, you might experience an out-of-memory condition in the Eclipse workspace of IBM Integration Designer. - Server does not appear in the Servers view
After you have installed the IBM Business Monitor development toolkit, the IBM Business Monitor server should appear in the Servers view in Integration Designer. Verify the profile was created and restart Integration Designer using the -clean parameter. - Cannot find a business integration module when you are generating a monitor model
If you want to select a business integration module as an element to monitor when you are generating a monitor model, the name of the business integration module cannot be the same as the name of the process application. - Importing monitor models from a project interchange file
If you have a project interchange (PI) .zip file containing your monitor models from a previous release of Business Monitor development toolkit, you can import the monitor models into a workspace in Integration Designer. - Visual model testing returns unexpected results
When you are testing the visual model in the Monitor Model editor, you might get unexpected values if you use expressions containing user-defined XML Path Language (XPath) functions with certain dependencies. These functions might not evaluate as expected if they require database access, have dependencies on other JAR files, or are not capable of executing within a development environment for any other reason. - Deployed monitor models are not startable
A deployed monitor model does not show up as startable or started in the Integration Designer servers view or in the WebSphere® Application Server administrative console if the monitor model name or path name is too long. - Top-level monitoring context is not created
If you generated a monitor model from an Integration Designer application and your process is running and emitting events but a top-level monitoring context is not created when you think it should have been, you might not have created all the required events. This problem can also result in many No parent found exceptions. - Metrics are not being evaluated correctly
If you have a metric that you think is not being evaluated correctly at run time, and the metric receives its value from an expression that references itself or another metric, check that all reference metrics are being initialized correctly before they are used. - Integrated Test Client cannot process imported events
If an XML file of events begins with a blank line, the Integrated Test Client cannot read the file and therefore cannot emit the events. The only message that shows in the Integrated Test Client console is Emitting events. - Monitor model debugger (deprecated) terminates after model is changed
If you modify the monitor model and maintain the data from the previous debugging session, the debugger might terminate with an unrecoverable error in the SystemOut log. - Monitor model debugger (deprecated) fails to start with older monitor model
If you try to debug a monitor model that was created using an earlier version of the Monitor Model editor or using another tool, the monitor model debugger might fail to start. - Cannot re-create global monitoring context
If you want to re-create a global monitoring context that was previously deleted, you must delete the artifacts associated with the global monitoring context. - Reason codes
When you have an error in an expression, you might see the following reason codes as part of the error. Based on the first letter of the code, you can look up the reason for the error.
Parent topic: Troubleshooting
Related reference:
