Video: How do I enable configuration and runtime tracing in WAS?

Video: How do I enable configuration and runtime tracing in WAS?

The following transcript is for the "How do I enable configuration and runtime tracing in WebSphere Application Server?" video, which describes how to enable configuration and runtime tracing in WAS. This transcript is the video storyboard. Audio describes narration and captions. Onscreen Action describes the content that is shown in the video.

How do I enable configuration and runtime tracing in WAS?

Scene Audio Onscreen Action
1 Question: How do I enable configuration and runtime tracing in WAS? Show title, How do I enable configuration and runtime tracing in WAS?.
2 Log in to the administrative console. Show the user how to log in to the administrative console.
3
In the left panel, expand Troubleshooting then click Logs and Trace.
In the left panel, expand Troubleshooting then click Logs and Trace.

4
Select the application server that needs to be traced.
Show the user how to select the application server they want to trace.

5
Click the Diagnostic Trace link.
Click the Diagnostic Trace link.

6
Increase the maximum file size to 50 or 100 MB, and increase the maximum number of historical files to 10 to 20.

After we make the updates, click Apply.
Show the user how to increase the maximum file size to 50 or 100 MB, and increase the maximum number of historical files to 10 to 20.

After we make the updates, click Apply.

7
On the same panel, click Change Log Detail Levels.
Click Change log detail levels. on the right side of the panel.

8
Enter the trace string as requested by the support team or as outlined in the WAS MustGather document.

For example, to enable management tracing, append com.ibm.ws.management.*=all to *=info to the text Box.

To enable tracing on our own and if we are unsure about the trace string. Expand Components and Groups, click Groups, and select the component to trace.
Show the user where to enter the trace string.

For example, to enable management tracing, append com.ibm.ws.management.*=all to *=info in the text Box.

Show the user how to expand Components and Groups, click Groups, and select the component to trace.
Use this method to enable tracing on our own and we are unsure about the trace string.
9
Click Apply, save, and synchronize the changes.

Restart the server for the trace string to take effect.
Show the user how to apply, save, and synchronize the changes.
Click Apply.

Click save to synchronize the changes.

Click Ok to restart the server for the trace string to take effect.

10
The video now shows how dynamic tracing can be enabled.

Click Logs and Trace and select the server to enable the tracing on.
Show the user how dynamic tracing can be enabled.

Click Logs and Trace on the left menu in the panel and select the server to enable the tracing on.

11
Click Diagnostic Trace.

Click the Runtime Tab.

The server is already up and running for this tab to show up.
Click Diagnostic Trace.

Click the Runtime Tab.

The server is already up and running for this tab to show up.
12
Set the maximum file size to 50 or 100 MB, and set the maximum number historical files to 10 to 20.

Click Apply for the changes to take effect.
Show the user how to increase the maximum file size to 50 or 100 MB, and increase the maximum number of historical files to 10 to 20.

Click Apply for the changes to take effect.

13
Click Change log detail levels.
Click Change log detail levels in the right menu.

14
Enter the trace string to enable.

Click Apply.

It is not a requirement to save, synchronize, or restart the server when we enable tracing on runtime.

The trace files might fill up quickly, and it might override the trace. To avoid this issue, make sure disabling the trace string as soon as the problem is re-created.
Show the user how to enter the trace string to be enabled in the appropriate text Box.

Click Apply.

We are not required t to save, synchronize, or restart the server when we enable tracing on run time.

The trace files might fill up quickly, and it might override the trace.
To avoid this issue, make sure disabling the trace string as soon as the problem is re-created.

Scene	Audio	Onscreen Action
1	Question: How do I enable configuration and runtime tracing in WAS?	Show title, How do I enable configuration and runtime tracing in WAS?.
2	Log in to the administrative console.	Show the user how to log in to the administrative console.
3	In the left panel, expand Troubleshooting then click Logs and Trace.	In the left panel, expand Troubleshooting then click Logs and Trace.
4	Select the application server that needs to be traced.	Show the user how to select the application server they want to trace.
5	Click the Diagnostic Trace link.	Click the Diagnostic Trace link.
6	Increase the maximum file size to 50 or 100 MB, and increase the maximum number of historical files to 10 to 20. After we make the updates, click Apply.	Show the user how to increase the maximum file size to 50 or 100 MB, and increase the maximum number of historical files to 10 to 20. After we make the updates, click Apply.
7	On the same panel, click Change Log Detail Levels.	Click Change log detail levels. on the right side of the panel.
8	Enter the trace string as requested by the support team or as outlined in the WAS MustGather document. For example, to enable management tracing, append com.ibm.ws.management.=all to =info to the text Box. To enable tracing on our own and if we are unsure about the trace string. Expand Components and Groups, click Groups, and select the component to trace.	Show the user where to enter the trace string. For example, to enable management tracing, append com.ibm.ws.management.=all to =info in the text Box. Show the user how to expand Components and Groups, click Groups, and select the component to trace. Use this method to enable tracing on our own and we are unsure about the trace string.
9	Click Apply, save, and synchronize the changes. Restart the server for the trace string to take effect.	Show the user how to apply, save, and synchronize the changes. Click Apply. Click save to synchronize the changes. Click Ok to restart the server for the trace string to take effect.
10	The video now shows how dynamic tracing can be enabled. Click Logs and Trace and select the server to enable the tracing on.	Show the user how dynamic tracing can be enabled. Click Logs and Trace on the left menu in the panel and select the server to enable the tracing on.
11	Click Diagnostic Trace. Click the Runtime Tab. The server is already up and running for this tab to show up.	Click Diagnostic Trace. Click the Runtime Tab. The server is already up and running for this tab to show up.
12	Set the maximum file size to 50 or 100 MB, and set the maximum number historical files to 10 to 20. Click Apply for the changes to take effect.	Show the user how to increase the maximum file size to 50 or 100 MB, and increase the maximum number of historical files to 10 to 20. Click Apply for the changes to take effect.
13	Click Change log detail levels.	Click Change log detail levels in the right menu.
14	Enter the trace string to enable. Click Apply. It is not a requirement to save, synchronize, or restart the server when we enable tracing on runtime. The trace files might fill up quickly, and it might override the trace. To avoid this issue, make sure disabling the trace string as soon as the problem is re-created.	Show the user how to enter the trace string to be enabled in the appropriate text Box. Click Apply. We are not required t to save, synchronize, or restart the server when we enable tracing on run time. The trace files might fill up quickly, and it might override the trace. To avoid this issue, make sure disabling the trace string as soon as the problem is re-created.