Skip to content

Enabling traces in WebSphere Application Server

Enable traces in IBM® WebSphere® Application Server so that you can access detailed information about the application server components, and use it to help you troubleshoot the user lifecycle commands.

  1. Open the WebSphere Application Service Integrated Solutions Console.

  2. Expand Troubleshooting and select Logs and trace.

  3. Select the server on which you want to enable traces, and then select Diagnostic Trace.

  4. Click the Runtime tab.

  5. Click Change Log Detail Levels.

  6. Set a trace level, select Save runtime changes to configuration as well, and click Apply.

When a user is updated, a message is sent over the event infrastructure to the HCL Connections™ applications.

Note: The ProfilesService.updateUser("", displayName="Updated Sample Name") command updates the specified profile data in the Profiles database and then generates a JMS Message event. This message is received by the News application, which sends out separate messages to each application. For each message that is sent out, the News application receives an ACKmessage. To ensure that each update message is processed by each application, check the event data in the log.

The following sample log shows the update that was triggered when the following command ran:

ProfilesService.updateUser("", displayName="Updated Sample Name")
[28/04/14 19:01:24:053 IST] 00000032 JMSPublisher 3 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":"","directoryid":"S-1-401595654-2584217272-3161732908-1084554606-880431025-3930541184","updated_logins":"[\"ajones141\",\"\"]","updated_name":"Updated Sample Name"}

_er_container_id: null
_er_container_name: null
_er_container_html_path: null

_er_item_id: null
_er_item_name: null
_er_item_html_path: null
_er_item_atom_path: null

You can use a standard event tracing command that can be enabled at source and target applications:

Collecting from an application server, such as the Profiles application server: :*=all

Collecting from the News application server: :**=all

Parent topic:Troubleshooting user data propagation

Related information

Verifying that the Profiles Worker is running correctly

Checking events generated by the user life-cycle commands

Troubleshooting the user life-cycle SPI