Enabling traces in WebSphere Application Server
Enable traces in IBM WebSphere Application Server so that we can access detailed information about the application server components, and use it to help troubleshoot the user life-cycle commands.
- Open the WebSphere Application Service WAS console.
- Expand Troubleshooting and select Logs and trace.
- Select the server to enable traces, and then select Diagnostic Trace.
- Click the Runtime tab.
- Click Change Log Detail Levels.
- Set the required trace level, select Save runtime changes to configuration as well, and click Apply.
Example
When a user is updated, a message is sent over the event infrastructure to other applications, and the log looks similar to the following.[28/04/10 19:01:24:053 IST] 00000032 JMSPublisher 3 com.ibm.lconn.events.internal.publish.impl.JMSPublisher publishEvent *************** Event data *************** _er_id: 26c21157-4d43-4534-ad07-d44f86832c91 _er_time: 1272477684021 _er_source: PROFILES _er_type: COMMAND _er_name: user.record.update _er_scope: PUBLIC _er_related_community: null _er_actor: null _er_actor_name: null _er_actor_email: null _er_properties: {"updated_directoryid":"S-1-401595654-2584217272-3161732908-1084554606-880431025-3930541184","_msg_id":"0","updated_email":"ajones141@myco.com","directoryid":"S-1-401595654-2584217272-3161732908-1084554606-880431025-3930541184","updated_logins":"[\"ajones141\",\"ajones141@myco.com\"]","updated_name":"Updated Sample Name"} Container: _er_container_id: null _er_container_name: null _er_container_html_path: null Item: _er_item_id: null _er_item_name: null _er_item_html_path: null _er_item_atom_path: null ***************The previous example shows the update that was triggered when the following command was issued:ProfilesService.updateUser("ajones141@myco.com", displayName="Updated Sample Name")
Parent topic:
Troubleshooting user data propagation
Related:
Verify the Profiles Worker is running correctly