MustGather: Read first For IBM FileNet Content Manager 5.2 - Process Engine Component

This background information is needed for opening a PMR, but is not gathered by the data collector:

• How often does this problem occur?
• Can the problem be reproduced? And if so, how is it reproduced?
• How many users are affected by this problem?
• Is the problem in newly exercised functionality? Or was this previously working and now it's stopped working?
• What, if anything, has been changed?
• What is the business impact of this problem?
• Is there a workaround?

• OS Version
• OS Environment Variables
• OS Kernel parameters
• OS running processes
• OS networking information
• OS locale information
• OS log files

Database Type and Version... For example, Oracle 11g 11.1.0.6 or SQL Server 2008 or DB2 LUW 9.5 FP2. Note that vwtool's configdetails command (collected above) will include this information in its output.

Is the database on the same server as the Content Manager Process Engine or on a remote database server?

Include the OS type and version information for database server if the database is remote.

In a web browser, go to your Content Engine's basic info pages:

http://cpehost:9080/wsi/FNCEWS40MTOM

In the above URLs, replace cpehost with the actual hostname of your Content Manager server, and, if necessary, replace 9080 with the actual port for your CE Server.

Include the returned HTML and XML pages.

Include the returned HTML page for these URLs as seen in a browser:

http://cpehost:9080/peengine/IOR/admin/help

In the above URLs, replace cpehost with the actual hostname of your FileNet Content Manager server, and, if necessary, replace 9080 with the actual port for your server.

In the response to the java_dump=true request, in the "Other message" area, you'll see the location of the java dump that was created. Look in that location and capture the *javacore.*.txt file.

Include the Content Manager Process Engine logs and traces from the last 7 days. The logs are in the "Log File Location" folder which is listed in the response to the IOR/ping page. This might be, for example, the C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\FileNet\server1 folder.

Also, collect the VWUpgrade_system.log and VWUpgrade_trace.log files if they exist. They'll be in the same "Log File location" as the other logs.
 

Include any javacore.* files that may have been created during the last seven days. These might be in C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01 for example.

Include the following information:

• Brand and model of load balancer
• Load Balancer settings and configuration information

The data collector does not automatically enable or create any tracing. But it will collect any traces that have already been created at the time the data collector is run.

If you will be collecting traces, it is easiest to generate the traces before running the data collector so that the traces are automatically included as part of the data collection.

If you have collected any traces, be sure to state the date and time when the problem has occurred.
 

The data collector does not automatically take or gather any screenshots. It may be appropriate to include screenshots of errors or other symptoms that will help us understand the problem.