IBM BOB Deployment & Connectivity Troubleshooting

Updated 14 November 2026 · Standard formula, shown below

This guide walks through the systematic troubleshooting of IBM Business Object Broker (BOB) deployment and connectivity issues. You will learn how to diagnose common failures, verify configurations, and restore service with clear, actionable steps. Before starting, ensure you have administrative access to the BOB server, the deployment manager, and the network infrastructure, as well as the ability to view logs.

What You’ll Need

Administrative access to the BOB server and the deployment manager console.
Network access to the BOB server’s ports (typically 1414 for MQ, 9443 for web console, and 22 for SSH).
Credentials for the BOB service account and the message broker.
A log viewer or text editor to inspect BOB logs (e.g., broker.log, deployment.log).
Optional: A copy of the deployment archive (BAR file) and the configuration files.

Step-by-Step

Verify the BOB service is running. On the server, check the service status. For Windows, use services.msc and look for the BOB service (e.g., “IBM Integration Bus” or “WebSphere Message Broker”). For Linux, use ps -ef | grep -i bob or systemctl status for the relevant daemon. If it is not running, start it and check the event logs for startup errors.
Check the deployment manager connection. Open the BOB web console (typically https://:9443/ibm/console). If the console is unreachable, verify that the deployment manager service is up and that the port is listening. Use netstat -an | grep 9443 on the server to confirm.
Inspect the deployment logs. Navigate to the BOB logs directory (often /var/mqsi/logs or C:\Program Files\IBM\MQSI\logs). Look for deployment.log and broker.log. Search for error codes like BIP (e.g., BIP2010, BIP2230). These codes give specific hints about the failure.
Test the message broker connection. Use the mqsilist command to list brokers. If the broker is not listed, run mqsistart to start it. Then test the connection with mqsipt or a simple ping to the queue manager using runmqsc.
Verify the queue manager is available. BOB typically connects to a queue manager (e.g., QMGR). Use dspmq to check the queue manager status. If it is not running, start it with strmqm. Ensure the BOB broker has the correct queue manager name in its configuration.
Check network connectivity and firewall rules. From the BOB server, use telnet 1414 or nc -zv 1414 to test the MQ port. Also test the deployment manager port (9443). If the port is blocked, work with your network team to open it.
Validate the BAR file and deployment artifacts. If deployment fails, check the BAR file integrity. Use mqsicreatebar to rebuild the BAR file if necessary. Ensure all dependent libraries and resources are included.
Review the broker’s execution group. In the web console, go to the broker and check the execution group status. If the execution group is stopped, start it. If it is in a “failed” state, check the execution group log for the specific error.
Restart the BOB components. As a last resort, restart the broker and the deployment manager. Use mqsistop and mqsistart for the broker, and restart the deployment manager service. This clears transient issues.

Common Mistakes

Ignoring the queue manager name case. Queue manager names are case-sensitive on Linux/Unix. A mismatch between the BOB configuration and the actual queue manager name will cause connection failures.
Using the wrong port. The default MQ port is 1414, but it can be changed. Always verify the port in the queue manager’s listener configuration.
Forgetting to start the execution group. Deploying a BAR file does not automatically start the execution group. You must start it manually in the console or via mqsistart.
Overlooking file permissions. The BOB service account must have read/write access to the logs and temporary directories. Permission errors often appear as generic “deployment failed” messages.
Not clearing the broker’s cache. After changing configuration, the broker may cache old settings. Use mqsireload to refresh the broker’s cache.

Tips

Enable verbose logging. In the BOB console, set the broker’s logging to “Debug” or “Trace” temporarily to capture detailed error messages. Remember to revert to normal logging after troubleshooting.
Use the mqsi commands. The command-line tools are powerful. mqsireportproperties can show the current broker configuration, and mqsichangeproperties can modify it without the console.
Keep a baseline. Document the working configuration (ports, queue manager names, execution group names) so you can compare when things break.
Test connectivity separately. Use a simple MQ client (like amqsput) to test the queue manager connection independently of BOB. This isolates whether the issue is with BOB or the MQ infrastructure.

Troubleshooting

If the steps above do not resolve the issue, consider the following:

Check the Windows Event Viewer or Linux syslog. BOB often writes critical errors to the system log that are not in the BOB-specific logs.
Review the deployment manager’s trace files. The deployment manager has its own logs, typically in /var/mqsi/registry or C:\ProgramData\IBM\MQSI. Look for deployment-manager.log.
Verify the Java environment. BOB’s web console requires a compatible Java version. If the console fails to load, check the Java version and reinstall the correct JRE if needed.
Check for port conflicts. Use netstat -an | grep to see if another process is using the BOB ports. This can cause silent failures.
Recreate the broker. If the broker is corrupted, you may need to delete and recreate it using mqsicreatebroker. This is a last resort, as it will lose all existing configuration.

Frequently Asked Questions

Why does my deployment fail with a BIP2230 error?

BIP2230 usually indicates a problem with the broker’s connection to the queue manager. Verify that the queue manager is running, the listener is active, and the connection details (host, port, channel) are correct in the BOB configuration.

How do I test if the BOB broker can reach the queue manager?

Use the amqsput and amqsget commands from the BOB server to put and get a test message. If this works, the network and MQ connection are fine, and the issue is likely in BOB’s configuration.

Can I deploy a BAR file without the web console?

Yes, you can use the mqsideploy command-line utility. For example: mqsideploy -i -e -a . This is useful for scripting and automation.

What should I do if the web console is not loading?

First, check if the deployment manager service is running. Then, verify that the port (9443) is open and not blocked by a firewall. Also, clear your browser cache and try a different browser. If it still fails, check the Java version and the deployment manager logs.

How do I reset the BOB broker to its default settings?

You can use mqsichangeproperties to reset specific properties, but for a full reset, you would need to delete and recreate the broker. This is not recommended unless you have a backup of your configuration.

Why does my message flow work sometimes but fail intermittently?

Intermittent issues often point to network instability, resource exhaustion (e.g., memory or threads), or queue manager backlogs. Check the system resource usage and the queue depths. Also, look for timeouts in the logs that might indicate network delays.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.