Introduction

As you troubleshoot problems with WebSphere Business Events V6.2.1 (hereafter called Business Events), you need to know where to find the product logs and how to interpret the information in those logs. Investigating the logs can often help understand the nature of the problem and determine the corrective course of action. This article describes the various logs generated by Business Events, where to find them, what information is provided in them, and how to analyze them. It also describes available logging mechanisms and troubleshooting techniques you can use to diagnose and resolve some of the common problems you may encounter with WebSphere Business Events V6.2.1.

This article assumes that you are familiar with Business Events components and configuration.

Before beginning the troubleshooting process, there are some diagnostic questions you should ask to determine whether there any obvious causes of a problem. Answering these questions first can save a lot of work by highlighting simple errors or by narrowing down the range of possible causes. These questions are covered in detail in the introduction section of Troubleshooting common problems with WebSphere Business Events V6.1; we recommend that you review that section before proceeding.

Back to top

Install and uninstall problems

This section describes the problems you may encounter when installing or uninstalling Business Events. The logs described in the following sections are generated by Business Events, and can help you diagnose the install/uninstall problems:

Install logs on Windows

Log files are generated in the operating system’s designated temporary directory. Unlike previous versions of Business Events, in V6.2.1 you aren't required to create a c:\tmp directory in order to generate logs. The following log files are produced:

• %temp%\wbe_install_debug.log
• %temp%\wbe_outputdebug.txt
• <WBE install_dir>\IBM_WebSphere_Business_Events_V6.2.1_InstallLog.log

The default temporary directory on Windows is C:\Documents and Settings\<userid>\Local Settings\Temp.

Install logs on UNIX

Log files are generated in the operating system’s /tmp directory. Unlike previous versions of Business Events, in V6.2.1, you aren't required to enable InstallAnywhere’s expanded debugging using the LAX_DEBUGenvironment variable in order to generate logs. The following log files are produced:

• /tmp/wbe_install_debug.log
• /tmp/wbe_outputdebug.txt
• <WBE install_dir>\IBM_WebSphere_Business_Events_V6.2.1_InstallLog.log

The log file wbe_install_debug.log captures any exceptions that occur during installation, while the wbe_outputdebug.txt and IBM_WebSphere_Business_Events_V6.2.1_InstallLog.log captures the installation environment and sequence of files being installed, along with the status (success or failure).

Listing 1 shows the a snippet from wbe_install_debug.log showing an exception message during installation.

Aug 4, 2009 2:51:55 PM com.ibm.wbe.dbconfig.DatabaseConnection 
get

SEVERE: BEEC0103E: An error occurred while connecting to the 
database using URL jdbc:db2j:net://localhost:50001/WBE621.
com.ibm.db2.jcc.b.gm: [jcc][t4][2057][11264][3.50.152] The 
application server rejected establishment of the connection.

An attempt was made to access a database, WBE621, which was 
either not found or does not support transactions. 
ERRORCODE=-4499, SQLSTATE=08004

$WBE_VALID_DB$: false

Connection information supplied is incorrect
            

Install logs on z/OS

Business Events on z/OS installation is performed via System Modification Program/Extended (SMP/E). Installation on z/OS is a two-stage process. Stage one is to write the files to the file system using SMP/E. Stage two is a manual process to configure Business Events in WebSphere Application Server (hereafter called Application Server) using the configuration scripts provided with the Business Events installation code.

Any errors or problems encountered in stage one are logged to the SMP/E joblog and any diagnostic messages for stage two are logged in the Application Server logs in the /<WAS_Home>/profiles/default/logs directory.

Uninstall logs on Windows

Log files are generated in the operating system’s desginated temporary directory. The following log files are produced:

• %temp%\wbe_uninstall_debug.txt
• %temp%\wbe_uninstall_outputdebug.txt

Uninstall logs on UNIX

Log files are generated in the operating system’s /tmp directory. The following log files are created:

• /tmp/wbe_uninstall_debug.txt
• /tmp/wbe_uninstall_outputdebug.txt

Uninstall logs on z/OS

Uninstallation of Business Events on z/OS is performed using SMP/E and any errors or problems encountered are logged in the SMP/E joblog.

Installation problem: Unsupported database

Problem: Business Events V6.2.1 is installed with Microsoft SQL Server database as the repository, and you see an unsupported database warning, as shown in Figure 1.

Problem analysis: This warning message is expected behavior, and occurs because the Microsoft SQL Server database is not a supported database for Business Events V6.2.1 dashboards.

Solution: Click OK and continue with the installation process. When using the Microsoft SQL Server database as the Business Events repository, the Business Space dashboards will need to be configured to use the Cloudscape database. For more information, refer to Configuring support for Business Space in the Business Events Information Center.

Installation problem: Current version already installed

Problem: When reinstalling Business Events V6.2.1 on a Windows machine after uninstalling it, you get the error: "Current version is already installed", as shown in Figure 2.

Problem analysis: This error message indicates that the uninstall of Business Events was not successful. Check to see if the Business Events install directory (for example, C:\Program Files\IBM\WBE621) is still present on the machine. If so, rerun the C:\Program Files\IBM\WBE621\uninstall\uninstaller.exe. If the uninstaller.exe has been deleted, you may have to manually clean-up the installation.

Solution: Follow the manual clean-up uninstall instructions described in the WebSphere Business Events V6.2.1 Information Center. Once you have verified that Business Events and Application Server (installed with Business Events) have been removed from the appropriate registry files, you can manually delete the Business Events directory, if it still exists.

Uninstallation problem: ObjectGrid and Application Server Feature Pack aren't uninstalled

Problem: When uninstalling Business Events, ObjectGrid and the Application Server feature pack fail to uninstall. The error messages shown in Figures 3 and 4 are displayed. If you click Next in the error message window, the uninstallation completes, leaving the Application Server directory behind.

Problem analysis: If you check C:\Program Files\IBM\WBE621\WAS\logs\objectgrid\uninstall\log.txt, you'll see the following error:

Failed to delete: 
file:/C:/Program%20Files/IBM/WBE621/WAS/lib/ogagent.jar
The file /C:/Program Files/IBM/WBE621/WAS/lib/ogagent.jar could 
not be removed.

If you check C:\Program Files\IBM\WBE621\WAS\logs\uninstall\webservices\log.txt, you'll see the following error:

CWUPI0032E: Running processes have been detected that may interfere 
with the current operation. Before installing or uninstalling maintenance 
package, stop all WebSphere and related processes.

This indicates that when the uninstall was performed, the Java™ process may have been running.

Solution: Since Business Events has been uninstalled, you may have to kill the Java processes and manually uninstall the ObjectGrid and Application Server feature pack by doing the following:

1. Go to C:\Program Files\IBM\WBE621\WAS\uninstall_objectgrid and run the command: java -cp og_install.jar run.
2. Continue to click Next until the uninstallation completes, as shown in Figure 5.
   
   Figure 5. ObjectGrid uninstallation
   
   
   
3. Go to C:\Program Files\IBM\WBE621\WAS\uninstall_websv and run Uninstaller.exe.
4. Continue to click Next until the uninstallation completes, as shown in Figure 6.
   
   Figure 6. Application Server uninstallation
   
   
   
5. Delete the C:\Program Files\IBM\WBE621\WAS directory.

You've now successfully uninstalled Business Events V6.2.1 and all its components.

Back to top

Configuration and runtime problems

When troubleshooting configuration or runtime problems, it's important to know which logs to review, where to find them, and how to analyze them. Business Events uses log4j for logging. Different logs are generated by the various Business Events components.

The Business Events runtime generates the log file WBERuntime.event.log, which is located in <WAS_HOME>\profiles\<PROFILE_NAME>\wbe\<NODE_NAME>\<SERVER_NAME>\logs.

You can control the level of logging with the log4j.logger.event property. The different logging levels are: debug, info, warn, error, fatal. The debug log level generates extensive information, whicl the fatal level records only fatal exceptions.

You can set this property from the Application Server administrative console, by selecting Resource environment entries => WbeSrv01 => Custom properties, as shown in Figure 7.

You can also set this property in Business Events by selecting Properties UI => Full Configurator => Logging. Under LOG4J settings, select log4j.logger.event and change the settings for the event log level from info to debug to write messages of all severities to the WBERuntime.event.log

For runtime troubleshooting, the WBERuntime.event.log is typically the first place to look. You can search for event name, or type= "event" in the logs. Any issued SQL or evaluated JavaScript is also shown in these event logs.

You can view WBERuntime.event.log from a Web browser using the Business Events administrative console. To make these log files easier to read, do the following:

1. Open the log file in a text editor, and add a unique tag to the very beginning of the file and a corresponding closing tag at the end of the file. For example: <l>event log text</l>
2. Save the file with a file type of .xml.
3. Open the saved file in a Web browser.

The Business Events connectors component has separate logging and generates information to the log file Connectors.log. By default this log file is located in <WBE Install>/director/logs. You can change the name and location of this log by configuring the properties file connectorsTrace.properties in <WBE Install>/config/wbe. Note that the connectors.log gets overwritten when the connectors are restarted.

Listing 2 shows a snippet of the Connectors.log file with an exception. The FFDC reported in the message below provides the exception stack which could help diagnose the problem.

[8/6/09 17:26:43:921 EDT] 00000012 jmsConnector  E   
BEER0402E: A JMS error occurred: javax.jms.JMSException: 
MQJMS2005: failed to create MQQueueManager for 'WBEQM'

8/6/09 17:26:44:125 EDT] 00000012 JSEFfdc       I   
BEER1852I: IBM WebSphere Business Events FFDC information 
has been written to C:\Program Files\IBM\WBE621
director\logs\wbe_40_09.08.06_17.26.43_1.txt
            

Although the above logs are specific to Business Events, you should also check the logs generated by Application Server, since the Business Events application wberuntimeear runs in the Application Server. The Application Server systemout.log shows the Business Events start-up and other informational messages which could be useful in troubleshooting problems.

You can manage the message logging levels and details in the Application Server systemout.log by configuring the message level. To do this, from the Application Server administrative console, select Troubleshooting => Logging and Tracing => server1 => Diagnostic Trace Service => Change log detail level, as shown Figure 8.

For example, changing the default value from info to detail would generate more detailed logs in the systemout.log. Figure 9 shows the logging and tracing levels that can be set for Business Events in Application Server.

Table 1 lists each Business Events component, its configuration, and which logs to check when troubleshooting.

Table 1. WebSphere Business Events components and logs

You can also view Business Events logs in real time, using a log viewer that is compatible with log4j. To display log message in the log viewer, do the following from the administrative console:

1. Select Resource environment entries => WbeSrv01 => Custom properties => New.
2. Add the following custom properties: log4j.appender.appender-name log4j.appender.appender-name.remoteHost log4j.appender.appender-name.port

For more information, refer to Viewing logs in real time in the WebSphere Business Events V6.2.1 Information Center.

Business Events tracing

If you can't get enough information about a problem from the logs described in the previous section, the next troubleshooting method to consider is using a trace. You can select the trace level and the components to be traced when you enable the trace; for example, fine, finer, finest, to enable you or IBM support to analyze the traces to determine the cause of the problem.

The information produced in the traces is sent to a log file, which is configured in the Application Server administrative console by selecting Troubleshooting => Logging and Tracing => server1 => Diagnostic Trace Service => <File Name>. Among other things, you can configure the file size and the number of historical files. By default, the log file is <WAS install dir>\profiles\WbeSrv01\logs\server1\trace.log.

The components associated with Business Events are listed under the group com.ibm.wbe.*. If a particular subcomponent within this group needs to be traced, you can select the trace level for the specific subcomponent instead of the entire group. For example, you can trace any connector-specific problems by setting the desired trace level on com.ibm.wbe.connectors.* subcomponent.

Runtime traces

To enable runtime tracing, do the following:

1. Select Logging and Tracing => server1 => Diagnostic Trace Service => Change Log Detail Levels and click the Runtime tab, as shown in Figure 10.
   
   Figure 10. Configure runtime logging and tracing
   
   
   
2. As shown in Figure 11, select All Messages and Traces or fine, finer, or finest.
   
   Figure 11. Select runtime tracing level
   
   
   
3. Save your changes.

Let's take a look at a runtime trace captured with the option of com.ibm.wbe.*=all.

Note:A sample runtime trace file, sample_runtime_trace.log, is provided for download, along with its project installValidation.xml, which explains the following in more detail.

• The first part of the trace displays "Start Display Current Environment," indicating the version information and install locations of WebSphere Application Server, WebSphere Business Events.
• JMSAccess shows the sending event message. Examine the contents of the event to determine whether the event contains the expected event objects and object fields, and to ensure that their names are spelled correctly (note that Business Events treats strings as case-sensitive). These names must exactly match corresponding definitions in Business Events, as defined in the Design Data tool.
• Scroll through the log to see how intermediate objects are instantiated. In particular, look to see whether intermediate object fields that should be populated are there or not.
• As you scroll further, you'll see messages that indicate whether a filter condition evaluates to true.
• Scrolling further, you'll see the actions produced by the "true" filter evaluation. You can examine the action to determine whether all the fields in the action objects contain expected values.

Start-up traces

Enable the wberuntimeear application start-up traces by doing the following:

1. Select Logging and Tracing => server1 => Diagnostic Trace Service => Change Log Detail Levels .
   
   Figure 12. Configure start-up logging and tracing
   
   
   
2. Click the Configuration tab, and select All Messages and Traces or fine, finer, or finest, as shown in Figure 13.
   
   Figure 13. Select start-up tracing level
   
   
   
3. Save the changes to the master configuration to enable the start-up traces and restart the server.

When the server is restarted, traces are logged by default in <WAS install dir>\profiles\WbeSrv01\logs\server1\trace.log. To ensure that the start-up traces have been enabled, check for the following in the start-up trace file: TRAS0017I: The startup trace state is *=info:com.ibm.wbe.*=all.

Security configuration problem: server initialization is slow and WBEruntimeear doesn't start

Problem: When security is enabled and Application Server is restarted, the server takes a long time to come up and wberuntimeear does not start.

Problem analysis: The following error is reported in the Application Server systemout.log,

com.ibm.wsspi.sib.core.exception.SINotAuthorizedException: 
CWSIP0302E: A user vgrover is not authorized to access the messaging engine 
Messaging.000-WbeBus on bus WbeBus.

This message indicates that the bus security is enabled and WBEruntimeear is unable to access the SIBus because it does not have authority to access it. With bus security enabled, you need to provide credentials so JMS can access the SIBus.

Solution:: Grant the user authority to access the JMS (SIBus, in this case) by doing the following:

1. Start the Application Server administrative console.
2. Select Resources => JMS =>Activation specifications => Activation specification name => JAAS - J2C authentication data.
3. Create a new alias under User ID; for example, vgrover, as shown in Figure 14.
   
   Figure 14. JAAS - J2C authentication data
   
   
   
4. Next select Resources => JMS =>Activation specifications => wbe_events.
5. Scroll to Additional => Authentication alias> and select the alias you created above, as shown in Figure 15.
   
   Figure 15. Authentication alias
   
   
   
6. Select Resources => JMS => Activation specifications => wbe_events => Buses => WbeBus => Security for bus WbeBus => Users and groups in the bus connector role, as shown in Figure 16.
   
   Figure 16. Add new user to the bus connector role
   
   
   
7. Click New to add the new user.
8. Restart the server and check the systemout.log to see whether WBEreuntimeear comes up.

Security configuration problem: connectors don't start

Problem: When security is enabled, the connectors don’t start.

Problem analysis: The connectors.log shows the following error:

BEER0402E: A JMS error occurred: javax.jms.JMSSecurityException: 
CWSIA0006E: The authorization for the supplied user name was not successful.  

This error indicates that the connectors are unable to access the SIBus due to authorization problems.

Solution:

1. Start the Application Server administrative console.
2. Select Resources => Resource Environment => Resource environment entries => WbeSrv01 => Custom properties.
3. Set the properties as.director.server.jms.username and as.director.server.jms.password to allow bus access, as shown in Figure 17. Make sure to remove the "!" character from the property names when you edit them.
   
   Figure 17. Set authorization properties
   
   
   

Back to top

Memory and performance problems

In all versions of Business Events, each time the Business Events runtime receives an event with a given context, a step is created in the in-memory least-recently-used (LRU) cache, and written to the steps table in the Business Events repository. This table could continue to grow, depending on the number of events received with contexts, ultimately resulting in poor performance.

This growth of the step table data for a context can consume runtime memory when that context is loaded.

In Business Events V6.1 and V6.2, users had to periodically clear up the step table in the Business Events repository. However, in V6.2.1, users can specify an expiration for a context and the system will remove contexts from the database that have not received an event for the specified time interval.

Two new properties are used to configure this feature:

• as.director.server.steptable.db.sweepInterval.minutes controls how often the system sweeps the database for possible contexts to expire (delete).
• as.director.server.steptable.db.contextExpiration.minutes specifies the number of minutes to use for the inactivity timeout period.

Note: It's important to review these properties periodically, particularly when deploying new or updated interaction sets.

To trace any problems with this feature not working properly, enable logging for the component com.ibm.wbe.server.engine.StepTableEngine=all from the Application Server administrative console, by selecting Troubleshooting => Logging and Tracing => server1 => Diagnostic Trace Service => Change Log Detail Levels.

Here are some basic guidelines for improving performance:

• Purge the history tables. If you're not using the dashboard, you can disable the recording of history. However, if you're using the dashboard for monitoring events, you should know that purging history may change or remove the ability to run the dashboard. This function is described in more detail in Purging history tables in the Business Events Information Center.
• Turn off logging. Refer to Managing log output for more information on this function.
• Only use connectors if they're needed. Send events directly to Business Events event destinations and receive actions directly from Business Events action destinations. For example, consider using Business Events destinations jms/eventTopic, jms/durableEventTopic, jms/actionTopic and jms/durableActionTopic.
• Use Application Server data sources for the Business Events repository.
• Set the Java heap size of the Application Server to manage memory efficiently: A small heap can cause frequent garbage collection, but a large heap can result in longer pause times. Change the Java heap size in the Application Server administrative console by selecting Application servers => server1 => Process Definition => Java Virtual Machine => Initial/Maximum heap size..
• Tune the JVM for WebSphere Application Server, as described in Tuning Java virtual machines in the Information Center.
• Tune the Business Events database. The Log File size and Buffer Pool size are important tuning parameters. See your database performance documentation for more information, as the parameters may vary depending on the database manager being used.
• If you're using Application Server default messaging as the JMS provider, you can use a lower reliability level to provide a higher throughput. The reliability level can be changed using the connection factories. From the Application Server administrative console, select Resources => JMS => TopicConnectionFactories => WbeTopicConnectionFactory.
• Deliver messages in batches from the input topic to Business Events. From the Application Server administrative console, select Resources => JMS => Activation specifications => wbe_events, and set the maximum batch size.
• If you are using MQ as the JMS provider, the key tuning parameters relate to queue manager logs, channels and listeners and queue buffer size. See Configuring and tuning WebSphere MQ for performance on Windows and UNIX for more information.

Back to top

Business Space and dashboard problems

The Business Space component in Business Events V6.2.1 enables users to monitor business event processing by defining and viewing charts and layouts using Business Space widgets supplied by Business Events. Three widgets are provided:

• Chart enables users to select and view charts displaying business events data processed by Business Events.
• Chart manager enables users to create and edit charts displaying business events data processed by Business Events.
• Layout (deprecated) enables users to select and view layouts created using the Design Dashboards tool from earlier versions of Business Events. It is not enabled by default.

You can access dashboards by opening a browser to the following URL: http://<server>:>port</BusinessSpace, where <server> is the name of the Application Server where Business Events is installed and <port> is the port number of the WC_defaulthost of this server (typically 9080).

Business Space database tables are configured in the Business Events repository as part of Business Events installation. They're used to store information relating to the widgets, spaces and pages created and used within the Business Space. The Business Events widgets are defined in xml files located in <WAS_HOME>\profiles\<PROFILE_NAME>\BusinessSpace\registryData

The chart definitions are stored in the Business Events repository. The Business Events runtime must be configured to record history in order for data to be available for the charts.

Only Internet Explorer V6 and above and Firefox V2 and above are supported. Recommended browsers for use with Business Space are Internet Explorer 7 and Firefox 3.

To determine the cause of problems with Business Space, do the following:

• Review the configuration steps in Configuring support for Business Space in the Business Events Information Center.
• Check <WAS install>/profiles/<server name>/logs/ffdc (for example, C:\Program Files\IBM\WBE621\WAS\profiles\WbeSrv01\logs\ffdc) to see if any errors are reported.
• If any error messages appear in the user interface, especially messages beginning with BEER, check the WBEruntime.event.log, the Application Server systemout.log, and the Application Server systemerr.log for details.

If the above logs do not show any information about the problem, run a trace by going to the Application Server administrative console, selecting Troubleshooting => Logging and Tracing => server1 => Diagnostic Trace Service => Change Log Detail Levels and specifying com.ibm.wbe.*=all for the trace string.

Business Space problem: Authorization fails at log in

Problem: When trying to log in to the Business Space on http://<server name>:9080/BusinessSpace/, you get the message HTTP 403 Authorization Failure errors occur on the Internet browser.

Problem analysis: Authorization failures can occur if the Business Events authentication method or Application Server security are note configured correctly.

Solution: To enable security for the dashboard using Application Server security, do the following:

• Make sure that the user who is starting Business Space is added to the WBEUsers and WBEDashboardUsers roles for the WBEruntime application in the administrative console under Enterprise Applications => wberuntimeear => Security role to user/group mapping..
• Ensure that the authentication method is set to AppServer in Resource environment entries => WbeSrv01 => Custom properties => as.director.common.authentication.method.

Back to top

Integration problems

Business Events V6.2.1 supports integration with the following IBM software products:

• WebSphere Process Server and WebSphere ESB: You can send events from WebSphere ESB to the Business Events runtime, and generate result events in response to actions sent by Business Events.
• WebSphere Message Broker: Your message flows can generate events that can be processed by Business Events, and can process actions that are received from Business Events.
• WebSphere Business Monitor: This integration enables you to get an up-to-date view of your business performance. WebSphere Business Monitor can generate events for and collect actions from Business Events to update the information it displays.
• WebSphere Application Adapters: This integration enables Business Events to receive events from a wide range of products like SAP, Siebel, and so on, through WebSphere Application Adapter schemas.
• WebSphere eXtreme Scale: You can use WebSphere eXtreme Scale to filter large volumes of events into smaller sets of events that can then be processed by Business Events.

Integration logs

Typically any problems with integration configuration with the Business Events runtime and the above products are reported in the Application Server systemout.log, Application Server systemerr.log, ffdcs, and WBEruntime.event.log. You should also check the product-specific logs for any errors. For example, broker syslogs for WebSphere Message Broker on UNIX or WebSphere ESB log file for WebSphere ESB.

Tracing can be enabled on the Business Events side and on the integrating product side if the logs don't provide sufficient information to determine the cause of a problem. On the Business Events side, you can set tracing from the administrative console, by selecting Troubleshooting => Logging and Tracing => server1 => Diagnostic Trace Service => Change Log Detail Levels => com.ibm.wbe.*. If you need to trace a specific component, such as JMS, to show the activity between Business Events and the SIBus, you should trace com.ibm.wbe.common*.

Back to top

Summary

In this article we addressed how to perform WebSphere Business Events troubleshooting, how to use the available logging mechanisms, and how to debug common problems you may encounter. Almost all of the problems and errors occurring in Business Events fit into one or more of the categories described in this article. The available logs described in this article can be extremely useful when troubleshooting and resolving problems. Additionally, you can check out the WebSphere Business Events Support page for the errors and problems you encounter that may have been reported in the past.

Back to top

Acknowledgements

The author would like to sincerely thank Denise Goldberg and Xiaoming Zhang for their valuable conributions to this article..

Back to top

Download

Information about download methods

Resources

• Troubleshooting common problems with WebSphere Business Events V6.1 (developerWorks 2009): Learn how to diagnose and resolve some common problems with WebSphere® Business Events V6.1 using troubleshooting techniques and available logging mechanisms. This introduction to this article provides a list of diagnostic questions that are good background for this article.
  
  
• WebSphere Business Events V6.2.1 Information Center: Get complete product documentation.
  
  
• WebSphere Business Events support page: Get product information, including features, benefits, demos and trial downloads.
  
  
• Troubleshooting common problems with WebSphere Business Events V6.1 (developerWorks 2009): This article describes how to diagnose and resolve some common problems with WebSphere Business Events V6.1 using troubleshooting techniques and available logging mechanisms.
  
  
• developerWorks BPM zone: Get the latest technical resources on IBM BPM solutions, including downloads, demos, articles, tutorials, events, webcasts, and more.
  
  

About the authors

Prasad Imandi is a Senior Software Engineer working in Level 2 Support in AIM in RTP, NC. He works on the WebSphere Message Broker, WebSphere Business Events and WebSphere Service Registry and Repository products, and leads product service teams. Prasad works with customers worldwide, focusing on product integration and troubleshooting issues. You can reach Prasad at imandi@us.ibm.com.

Vivek Grover is an Advisory Software Engineer in Level 2 Support for WebSphere Business Events and WebSphere Message Broker in RTP, NC. Vivek is also the e-Support team lead assisting knowledge engineers in designing and writing Technotes, DCFs (Document Control Facility), and quarterly e-mails to the customers describing technical issues.You can reach Vivek at vgrover@us.ibm.com.

Comments

Back to top

Trademarks  |  My developerWorks terms and conditions

Table of contents

• Introduction
• Install and uninstall problems
• Configuration and runtime problems
• Memory and performance problems
• Business Space and dashboard problems
• Integration problems
• Summary
• Acknowledgements
• Download
• Resources
• About the authors
• Comments

Next steps from IBM

• Try: WebSphere Business Events (in the SOA Sandbox: Process)
• Demo: Reduce business risk with WebSphere Business Events
• Briefing: WebSphere flexible business processes
• Buy: WebSphere Business Events (in the SOA Sandbox: Process)

My developerWorks community

Dig deeper into WebSphere on developerWorks

Cloud computing for developers

Virtual workshop: Learn how to build a cloud infrastructure and develop/deploy cloud-based applications. (6-8 Apr 2010)

Special offers