WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Resolving non-specific problems when using the WebSphere Message Broker Toolkit

Use the advice given here to help you to resolve some common problems that can occur when you use the WebSphere® Message Broker Toolkit that are not dealt with in previous categories.

Main menu entries missing on Linux on x86

  • Scenario: The main menu on Linux on x86 no longer contains items that relate to the WebSphere Message Broker Toolkit.
  • Explanation: If you have installed the WebSphere Message Broker Toolkit in more than one package group, and have now removed one of those installations, a known restriction causes the main menu items to be removed when the component is uninstalled.
  • Solution: Invoke the WebSphere Message Broker Toolkit from the command line. Navigate to the installation directory for the package group in which you have installed the WebSphere Message Broker Toolkit, and enter the following command:
    ./eclipse -product com.ibm.etools.msgbroker.tooling.ide

Editors do not update automatically when the same file is open in multiple windows

  • Scenario: You are working in the Broker Application Development perspective, and are using the associated editor to work with one or more resources; for example, you are editing a message flow in the message flow editor or an ESQL module in the ESQL editor. You have clicked Window > New Window to create a second Eclipse view, and have opened the same resource in the second window. Changes that you make to the resource in the first editor window are not reflected in the second editor window.
  • Explanation: The WebSphere Message Broker Toolkit editors do not automatically update multiple windows in which you have opened the same resource.
  • Solution: Save the contents of the resource file in the first editor window, then close and reopen additional windows. The reopened windows reflect the updated content.

Deleting or closing a project takes a long time

  • Scenario: Deleting or closing a project to save memory takes a long time.
  • Explanation: If a project is referenced by other projects, removing that project requires all the other projects, and the projects that refer to them recursively, to be built fully. This process occurs to keep the content-assist and validation models current.
  • Solution: To keep a project open in the workspace requires very little memory, therefore you do not need to close or delete projects.

You are experiencing poor performance when working with large or complex projects

  • Scenario: You are experiencing poor performance in the WebSphere Message Broker Toolkit when working with large or complex projects.
  • Explanation: Frequent project changes, such as adding and removing projects, or using Project > Clean, use large amounts of memory because of the size and number of files and the connections between them.
  • Solution: Increase your system memory.

You do not know how to return to the welcome page

  • Scenario: You do not know how to return to the welcome page that was displayed in the WebSphere Message Broker Toolkit when you first started using it.
  • Solution: To open the welcome page:
    1. From the Help menu, select Welcome. If only one welcome page is available, it is displayed. If more than one is available, a list is displayed.
    2. Select the welcome page that you want, for example, WebSphere Message Broker WebSphere Message Broker Toolkit.
    3. Click OK.
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:47:39


Task topicTask topic | Version 8.0.0.7 | au16604_