Collecting MustGather data for LDAP issues
Prepare the following MustGather information before you call IBM Support to help with LDAP issues.
Procedure
- Configure the following trace string in the Transaction server Docker container.
*=info: com.ibm.websphere.commerce.WC_USER=all: com.ibm.websphere.commerce.WC_SERVER=all : com.ibm.websphere.commerce.WC_TRANSPORT_ADAPTER=allFor information about how to set trace strings, see Configure logging for the Transaction Server.
- Reproduce the problem.
Record the specific steps that we used to reproduce the problem and any details that might be relevant.
- Collect the following files from the Transaction server Docker container.
- /opt/WebSphere/AppServer/profiles/default/config/cells/localhost/wim/config/wimconfig.xml
- /opt/WebSphere/AppServer/profiles/default/installedApps/localhost/ts.ear/xml/ldap/ldapentry.xml
- /opt/WebSphere/AppServer/profiles/default/installedApps/localhost/ts.ear/xml/config/wc-server.xml
- /opt/WebSphere/AppServer/profiles/default/logs/server1/trace*.log
- Run the following database queries to collect the necessary information from the database (output results in CSV format).
select orgentity_id, dn from orgentity where orgentity_id in (-2001, -2000) select users_id, logonid from userreg where logonid like '%wcsadmin%' select users_id, dn from users where users_id = -1000 select * from wmmmap where member_id in (-2001,-2000, -1000)