Troubleshooting
Problem
FileNet Content Engine tracing in Administration Console for Content Platform Engine does not initiate new trace logging subsystems when enabled in ACCE. When trace logging is disabled it continues to log the one subsystem.
Symptom
Trace logging is "stuck" logging one subsystem and does not initiate new subsystems and does not disable all logging when disabled.
Cause
WebSphere cache is holding a previous setting.
Resolving The Problem
- Access WebSphere Administration Console
- Stop all WebSphere application server nodes, including the Deployment Manager node if one exists
- Remove the FileNetEngine directory where the application server cache data is stored. For example, the default Windows path for this directory is:
C:\Program Files\IBM\WebSphere\AppServer\profiles\profile_name\temp\node_name\serve
r_name\FileNetEngine\profile_name
- Restart all WebSphere nodes, including the Deployment Manager node if one exists.
- Clear the internet browser cache on all client computers that use Administration Console for Content Platform Engine (ACCE) for administering Content Platform Engine.
- Login to ACCE
- Enable logging
- Test to verify logging responds to changes
[{"Product":{"code":"SSNW2F","label":"FileNet P8 Platform"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Content Engine","Platform":[{"code":"PF033","label":"Windows"}],"Version":"5.2.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21968515