Troubleshooting and support

Solutions

To view the solution to a problem that you encounter when you use the IBM Integration Toolkit, see Troubleshooting and support in the IBM Integration Bus documentation.

Silent installation does not complete

Scenario

When you are installing IBM Integration Bus Manufacturing Pack by using the silent installer, the silent installer does not complete.

Explanation

The user ID might not have permission to write to the log file under the chosen installation directory, for example /opt/IBM/ManufacturingPack, which causes the thread to loop.

Solution

Complete the following steps:

1. Remove any IBM Integration Bus Manufacturing Pack directories and files that are still on your system, see Uninstalling manually.
2. Ensure that the user ID has the correct permissions, for example, root.
3. Install IBM Integration Bus Manufacturing Pack by using a user ID that has the correct permissions.

You receive an error when you are uninstalling, or the uninstallation does not complete

Scenario

When you are uninstalling IBM Integration Bus Manufacturing Pack in graphical mode, you receive an error, for example, an InvocationTargetException due to a StackOverflowError, or the uninstallation does not complete.

Explanation

The uninstallation did not complete successfully. After an incomplete uninstallation, IBM Integration Bus Manufacturing Pack directories and files might remain on your computer.

Solution

Remove any IBM Integration Bus Manufacturing Pack directories and files that are still on your system, see Uninstalling manually.

IBM Integration Bus Manufacturing Pack nodes and the pattern are not shown after installation

Scenario

On Windows and Linux, after you install the "Pattern and nodes for the IBM Integration Toolkit" component of IBM Integration Bus Manufacturing Pack, you cannot see the Manufacturing pattern in the Patterns Explorer view or the Manufacturing nodes in the palette.

Explanation

The Eclipse cache was not refreshed in your IBM Integration Toolkit.

Solution

Clean the launcher:

On Windows:

1. Click Start > All Programs > IBM Integration Toolkit > IBM Integration Toolkit version, where version is the version number of the IBM Integration Toolkit.
2. Right-click Start IBM Integration Toolkit version. The Integration Toolkit Properties window opens.
3. On the Shortcut tab, in the Target field, at the end of the target name, type - clean, click OK.
4. Right-click Start IBM Integration Toolkit version, click Run as administrator.
5. After the IBM Integration Toolkit loads, close the IBM Integration Toolkit, remove - clean from the Target field.
6. Start the IBM Integration Toolkit.

On Linux:

1. Open a terminal and navigate to your IBM Integration Toolkit installation directory. By default, this directory is /opt/IBM/IntegrationToolkit90.
2. Run the command ./launcher -clean.
3. If the nodes and pattern are still not showing, run the command by using sudo.

The web user interface page does not open

Scenario

When you enter the URL for the web user interface, no page is displayed, or an HTTP 404 Not Found message is shown.

Explanation 1

The URL for the web user interface server is incorrect.

Solution 1

Check that you are using the correct URL to access the web user interface for the appropriate integration node; see Accessing the web user interface.

Explanation 2

The web user interface server is not running.

Solution 2

Ensure that the web user interface server is running and is configured correctly; see Accessing the web user interface in the IBM Integration Bus documentation.

Explanation 3

The web user interface component might not be installed.

An error message might look like the following example:

May 19 09:19:47 host_name IIB[1068]: IBM Integration Bus v9002 (integration_node) [Thread 1133] (Msg 1/1) 
BIP3836E: An exception occurred when applying the MQSI_ADDITIONAL_CONTEXT_ROOTS environment variable 
because web UI extension '/opt/IBM/ManufacturingPack/1.0.0.0/webui/manufacturing' does not exist.

A success message might look like the following example:

May 19 09:19:47 host_name IIB[1068]: IBM Integration Bus v9002 (integration_node) [Thread 1133] (Msg 1/1) 
BIP3835I: The web UI extension '/opt/IBM/ManufacturingPack/1.0.0.0/webui/manufacturing' 
is installed and is available at 'http://localhost:4414/manufacturing'.

where integration_node is name of your integration node and host_name is the host name.

Solution 3

Use the information in the error message to resolve the problem.

Information in the Manufacturing Integration view is not up-to-date

Scenario

After you change message flows that are shown in the Manufacturing Integration view, the information in the view is not up-to-date.

Explanation

The Manufacturing Integration view does not automatically update, so any changes since the page was last loaded are not shown.

Solution

In your browser, reload the web page for the Manufacturing Integration view.

Data for a newly created tag is not showing on the server

Scenario

After you add a tag to a PI-Input or OPC-UA-Input node, you cannot see any data for that tag on the server.

Explanation

If a tag does not exist when a subscription is created, those tags are not subscribed to.

Solution

Stop and restart the server so that you can see data for this tag in your output message.

You receive the message: (integration_node) Failed to start input node called 'PITest.PI-Input.PIServerNotifyInput'.

Scenario

You receive the following message when you try to deploy a PI-Input node:

(integration_node) 
A ''System.IO.FileNotFoundException'' was thrown from the .NET AppDomain ''PITest'' 
to the broker from the source ''Manufacturing_Nodes'' with the message 
''Could not load file or assembly 'OSIsoft.AFSDK, Version=4.0.0.0, 
Culture=neutral, PublicKeyToken=6238be57836698e6' or one of its dependencies. 
The system cannot find the file specified.''.

where integration_node is name of your integration node.

Explanation

The PI AF SDK is not installed.

Solution

Install the PI AF SDK.

Two basic property tabs are shown in the Properties view for the PI-Input node

Scenario

After installing a new version of IBM Integration Bus Manufacturing Pack, in the IBM Integration Toolkit, the Properties view for your PI-Input nodes contains a Basic tab and a basic tab. You added the PI-Input nodes to message flows in IBM Integration Bus Manufacturing Pack Version 1.0.0.0.

Explanation

The Update rate property for the PI-Input node was removed in IBM Integration Bus Manufacturing Pack Version 1.0.0.1. If you added a PI-Input node to a message flow in Version 1.0.0.0, when the node is shown in later versions of IBM Integration Bus Manufacturing Pack, the Update rate property appears in the Properties view on the basic tab.

Solution

The node works correctly, and the Update rate property has no effect, so no action is required. You can update the node to remove the basic tab. To update the node if it was generated by using the "Manufacturing: Factory Publication" pattern, regenerate the pattern. To update the node if it was not generated by using the pattern, add a new PI-Input node to the message flow and then delete the node that contains the basic tab.

When you deploy a message flow that contains an MQTT node, you receive a BIP3845E error message

Scenario

You receive a BIP3845E error message when you try to deploy a message flow that contains an MQTTPublish node or an MQTTSubscribe node.

Explanation

To use the MQTT nodes, you must first install the MQTT connector by installing the mqttNode configurable service. If the connector is not installed, or references a previous installation of IBM Integration Bus Manufacturing Pack, the BIP3845E error message is shown.

Solution

Install the MQTT connector by completing one of the following options:

• In the IBM Integration Explorer, under your integration node, right-click Configurable Services and select Import *.configurableservice. Then navigate to installation_directory/runtime/MQTTConnector/mqttNode.configurableservice and click Open, where installation_directory is your IBM Integration Bus Manufacturing Pack installation directory.
  Note: If you do not see a Configurable Services option, ensure that your integration node is connected by right-clicking the integration node and selecting Connect.
• In the command line, run the following command:

  mqsicreateconfigurableservice integration_node_name -c ConnectorProviders -o MQTTNode 
  -n connectorClassName,jarsURL,nativeLibs  
  -v "com.ibm.broker.connector.mqtt.MQTTConnectorFactory","installation_directory/runtime/MQTTConnector","default_Path"

  where integration_node_name is the name of your integration node and installation_directory is your IBM Integration Bus Manufacturing Pack installation directory.

When you start an integration node that has a message flow deployed that contains an MQTT node, you receive a BIP3847E error message

Scenario

You deploy a message flow that contains an MQTTPublish node or an MQTTSubscribe node to an integration node and then stop the integration node. You uninstall and then reinstall IBM Integration Bus Manufacturing Pack to a different installation directory. You receive a BIP3847E error message when you try to restart the integration node.

Explanation

To use the MQTT nodes, you must first install the MQTT connector by installing the mqttNode configurable service. This configurable service references the installation directory of IBM Integration Bus Manufacturing Pack. If IBM Integration Bus Manufacturing Pack is reinstalled to a different directory, the reference in the configurable service is incorrect and you receive the BIP3847E error message when you start your integration node.

Solution

Replace the existing MQTT connector by completing one of the following options:

• In the IBM Integration Explorer, under your integration node, right-click Configurable Services and select Import *.configurableservice. Then navigate to installation_directory/runtime/MQTTConnector/mqttNode.configurableservice and click Open, where installation_directory is your IBM Integration Bus Manufacturing Pack installation directory.
  Note: If you do not see a Configurable Services option, ensure that your integration node is connected by right-clicking the integration node and selecting Connect.
• In the command line, run the following command:

  mqsicreateconfigurableservice integration_node_name -c ConnectorProviders -o MQTTNode 
  -n connectorClassName,jarsURL,nativeLibs  
  -v "com.ibm.broker.connector.mqtt.MQTTConnectorFactory","installation_directory/runtime/MQTTConnector","default_Path"

  where integration_node_name is the name of your integration node and installation_directory is your IBM Integration Bus Manufacturing Pack installation directory.