Troubleshooting
Problem
Customer-provided background information (also known as "MustGather" data) helps in problem determination and saves time when resolving Problem Management Records (PMRs). This technote provides a description of the background information IBM® Support will need for FileNet Content Engine LDAP issues.
Resolving The Problem
Tab navigation
- 1. Learning more
- 2. Troubleshooting
- 3. Collecting data- selected tab,
It is recommended to collect MustGather data before opening a PMR. This helps IBM® Support quickly determine the root cause of the problem. With this information, Support can determine if:
- This is a known problem (rediscovery).
- There is a non-defect problem that can be identified and resolved.
- This is a known defect for which a workaround has been developed.
- A new problem has been discovered and a fix is required.
If you have already contacted support, continue on to the LDAP MustGather information. Otherwise, please review this page: MustGather: Read first for FileNet Content Engine
LDAP MustGather information
The following information is required for troubleshooting LDAP problems.
1. All of the information described in MustGather: Read first for FileNet Content Engine, enabling the EJB and Security subsystem trace flags to show the exact error message being returned.
2. Provide details for each LDAP configuration listed in the domain.
In Administration Console for Content Engine (ACCE for P8 5.2 and later), click on the domain in the left navigation pane then click on the Directory Configuration tab in the right navigation display pane.
For each Directory Configuration listed, click through (ACCE) to get the details:
- In ACCE Take screen shots of all of the property Values listed.
Observe the lengths of the values and copy to a text file the values of any items that are not fully visible in the screen shots such as the Directory Service User, User Search Filter and Group Search Filter (whose values may exceed the display window width, especially in FEM).
3. Provide an LDIF export from the LDAP directory server for the problematic user account and that account's group memberships.
4. Provide the full text of the client side stack trace from the client application browser window (ICN, Records Manager). For this, please select all the text into the Windows clipboard and paste it into a text file rather than taking a screen shot so that the full content can be quickly reviewed.
5. Describe the type of LDAP server configured (Tivoli, Active Directory, etc.) and the application server being used (i.e. WebSphere standalone or Federated Repository).
6. Provide the application server's LDAP configuration information, for instance the security.xml from WebSphere, the login-config.xml from JBoss or screenshots from the WebLogic administrative console.
Related Information
[{"Product":{"code":"SSNVNV","label":"FileNet Content Manager"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Content Engine","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"4.0;4.0.1;4.1;4.5.0;4.5.1;5.0;5.1.0;5.2.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Was this topic helpful?
Document Information
Modified date:
26 September 2023
UID
swg21314043