Troubleshooting and support

If you are having problems with your WebSphere® Message Broker or IBM® WebSphere Message Broker Connectivity Pack for Healthcare applications, use the techniques described to help you to diagnose and solve the problems.

For information about the techniques that you can use to diagnose problems, see Troubleshooting and support in the WebSphere Message Broker documentation.

The following list describes typical problems, with a corresponding solution or workaround:

IBM WebSphere Message Broker Connectivity Pack for Healthcare nodes and patterns not shown after installation

Toolkit component on Windows 7 or Windows Server 2008:
  • Scenario: After you install IBM WebSphere Message Broker Connectivity Pack for Healthcare, you cannot see the healthcare patterns in the patterns explorer and you cannot see the healthcare nodes in the node palette.
  • Solution: Run the IBM WebSphere Message Broker Toolkit with a user ID that has root or administrator authority:
    • On Windows, click Start > All Programs > Accessories, right-click Command Prompt, and click Run as administrator. Navigate to your WebSphere Message Broker Toolkit installation directory. By default, this directory is C:\Program Files\IBM\WMBT800. Run launcher.bat -clean.
    • On Linux, open a terminal and navigate to your WebSphere Message Broker Toolkit installation directory. By default, this directory is /opt/IBM/WMBT800. Run the command ./launcher -clean. If the nodes and patterns are still not showing, run the command by using sudo, sudo ./launcher -clean.
    You need to complete this step only the first time that you open the IBM WebSphere Message Broker Toolkit after installing the IBM WebSphere Message Broker Toolkit component of IBM WebSphere Message Broker Connectivity Pack for Healthcare.

Error messages when deploying the MedicalDeviceInput node

Runtime component on Windows and Linux:
  • Scenario: When you try to deploy a message flow containing the MedicalDeviceInput to a broker, the deployment fails and an error message is shown.
  • Solution: Restart the execution group to which you want to deploy the message flow and deploy the message flow.
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 2011, 2014Copyright IBM Corporation 2011, 2014.

        
        Last updated
        
        Last updated : 2015-12-07 14:51:55


Task topicTask topic | Version 8.0.0.0 | ha00200