Troubleshooting and support

If you are having problems with your IBM® Integration Bus Healthcare Pack applications, use the following techniques to help you to diagnose and solve the problems.

About this task

For information about the techniques that you can use to diagnose problems, see Troubleshooting and support in the IBM Integration Bus product documentation.

To view the solution to a problem that you encounter when you use IBM Integration Bus Healthcare Pack, select the corresponding problem from the following list:

IBM Integration Bus Healthcare Pack nodes and patterns not shown after installation

Procedure

  • Scenario: After you install IBM Integration Bus Healthcare Pack, you cannot see the healthcare patterns in the patterns explorer, and you cannot see the healthcare nodes in the node palette.
  • Solution: Start the IBM Integration Toolkit with the clean option:
    • On Windows, click Start > All Programs > Accessories, right-click Command Prompt, and click Run as administrator. Navigate to your IBM Integration Bus installation directory. Run iib toolkit -clean.
    • On Linux, open a terminal and navigate to your IBM Integration Bus installation directory. Run the command ./iib toolkit -clean.

Reverting to an earlier version of the IBM Integration Bus Healthcare Pack

Procedure

  • Scenario: You update IBM Integration Bus Healthcare Pack, by reverting to a version of the product you previously installed. However, when you open IBM Integration Toolkit, the contents are not updated to the reverted state.
  • Explanation: Some changes can result in the plug-in cache configuration becoming out of sync. Cleaning the cache can help to rectify this problem.
  • Solution: Start the IBM Integration Toolkit with the clean option:
    • On Windows, click Start > All Programs > Accessories, right-click Command Prompt, and click Run as administrator. Navigate to your IBM Integration Bus installation directory. Run iib toolkit -clean.
    • On Linux, open a terminal and navigate to your IBM Integration Bus installation directory. Run the command ./iib toolkit -clean.

Error messages when you deploy the MedicalDeviceInput node

Procedure

  • Scenario: When you try to deploy a message flow that contains the MedicalDeviceInput to an integration node, the deployment fails and an error message is shown.
  • Solution: Restart the integration server to which you want to deploy the message flow, and deploy the message flow.

Deploying a BAR file that contains the HL7 DFDL message model produces a BIP5043E error

Procedure

  • Scenario: You try to deploy a BAR file that contains the HL7 DFDL message model, but an error of type BIP5043E is produced.
  • Explanation: If you are deploying a BAR file that contains the full HL7 DFDL model (that is, including the HL7 chapters), the default maximum JVM heap size for the integration server (256 MB) might not be large enough for the deployment to complete successfully.
  • Solution:
    1. Increase the integration server maximum heap size to greater than 256 MB. A value of at least 512 MB is recommended. In the command console, type the following command: mqsichangeproperties integration_node -e integration_server -o ComIbmJVMManager -n jvmMaxHeapSize -v size_in_bytes where integration_node is the name of your integration node, integration_server is the name of your integration server, and size_in_bytes is the maximum heap size that you want to use.
    2. Restart the integration node, by entering the following commands: mqsistop integration_node, then mqsistart integration_node where integration_node is the name of your integration node.
    3. Set the maximum Java heap size to 536870912 bytes, by running the following command: mqsichangeproperties integration_node -e integration_server -o ComIbmJVMManager -n jvmMaxHeapSize -v 536870912, where integration_node is the name of your integration node, and integration_server is the name of your integration server.
    4. Restart the integration server by running the following command: mqsireload integration_node -e integration_server where integration_node is the name of your integration node, and integration_server is the name of your integration server.
    5. Deploy your BAR file.
    The BAR file deploys successfully.

The web-based monitoring web page cannot be opened

Procedure

  • Scenario: When you enter the URL for the web-based monitoring page, no page is displayed, or an HTTP 404 Not Found message is shown.
  • Explanation: This problem might exist because the URL for the web user interface server is incorrect, or the web user interface server is not running.
  • Solution: Check that you are using the correct URL to access the web-based monitoring web page; see Accessing web-based monitoring. Ensure that the web user interface server is running and is configured correctly; see Configuring the web user interface server and Enabling and disabling the web user interface in the IBM Integration Bus product documentation.

No pattern instances are available to select when you are viewing web-based monitoring

Procedure

  • Scenario: When you open the web page for web-based monitoring, the healthcare web-based monitoring page is shown, but no pattern instances are available to select. The message No pattern instances deployed is shown next to the pattern descriptions.
  • Explanation: This problem might exist because no pattern instances are deployed to the integration node that is running web-based monitoring.
  • Solution:
    1. Ensure that you deployed a pattern instance for the pattern that you want to monitor.
    2. Ensure that the integration node to which you deployed your pattern instance is the same integration node that is configured for web-based monitoring. You specify the integration node to use for web-based monitoring when you configure the web user interface server; see Configuring the web user interface server in the IBM Integration Bus product documentation.

Patterns from previous versions of IBM Integration Bus Healthcare Pack do not display in operational monitoring

Procedure

  • Scenario: You try to use operational monitoring to monitor a pattern that you created by using IBM WebSphere® Message Broker Connectivity Pack for Healthcare or IBM Integration Bus Healthcare Pack Version 3.0. Your patterns are not shown in the operational monitoring list. In the clinical application monitoring view, links from these patterns to operational monitoring do not work.
  • Explanation: You can use operational monitoring in IBM Integration Bus Healthcare Pack Version 4.0 to monitor all patterns that are generated in IBM Integration Bus Healthcare Pack Version 3.0, except for the Healthcare: HIPAA to XML pattern. You can monitor this pattern, and patterns that you created in IBM WebSphere Message Broker Connectivity Pack for Healthcare, but you must regenerate them in IBM Integration Bus Healthcare Pack Version 4.0.
  • Solution: Regenerate your pattern:
    • In the Application Development view, open Pattern Instances > pattern_instance_name > Pattern configuration > pattern_instance_name_configuration.xml, where pattern_instance_name is the name of your pattern instance.
    • In the Configure Pattern Parameters view, click Generate.
    Your pattern is regenerated, and can be used with operational monitoring.

When you are viewing web-based operational monitoring for a Healthcare pattern, no messages/second or last message information is shown

Procedure

  • Scenario: In the web-based operational monitoring page for a Healthcare pattern, in the Messages/second or Last message columns, no information is shown for one or more message flows.
  • Explanation: This problem might exist because of one of the following explanations:
    • Message flow statistics are turned off for this message flow
    • No messages have passed through the message flow since the monitoring session was started
    • The application or service that contains the message flow is stopped
  • Solution: Ensure that the application or service that contains the message flow you want to monitor is started and that data is passing through the message flow. Ensure that message flow statistics are turned on for the required message flows. You can turn on message flow statistics by clicking Enable statistics in the Change statistics state column of the monitoring table.

Error message when you deploy a DICOMInput node or a DICOMOutput node

Procedure

  • Scenario: On Linux® or UNIX systems, when you deploy a message flow that contains a DICOMInput node or a DICOMOutput node, you see the error trace text: 'java.lang.NullPointerException';
  • Explanation: The user that started the integration node to which the DICOM node was deployed does not have permission to read or write to the processing directory that is used by the node.
  • Solution: Check the node properties of the relevant DICOM node to determine the processing directory. Then ensure that this directory has the required permissions to allow files to be read from, or written to, by the user that is used to start the integration node.

When you create a pattern instance of the Healthcare: HL7 to HL7 DFDL pattern, you see an error message

Procedure

  • Scenario: When you create the Healthcare: HL7 to HL7 DFDL pattern, you see an error message and you cannot deploy the pattern.
  • Explanation: The HL7 DFDL model was imported after the pattern was deployed. You must include a reference to the HL7 DFDL library in your project so that the DFDL library is deployed together with the generated application.
  • Solution: Import the HL7 DFDL message model and clean the generated application; see Preparing the HL7 DFDL library in Managing a pattern instance. When the cleaning process completes successfully, the error message is removed.