Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

IBM Exam C9510-401 Topic 4 Question 62 Discussion

Actual exam question for IBM's C9510-401 exam
Question #: 62
Topic #: 4
[All C9510-401 Questions]

A system administrator has created a wsadmin script with several steps to install and configure an application and some resources in a WebSphere Application Server process. The script executed but the application was not installed successfully. The administrator suspects that the script has problems.

How can the administrator test and debug the script?

Show Suggested Answer Hide Answer
Suggested Answer: C

The High Performance Extensible Logging (HPEL) facility writes to the log and trace repositories in a binary format. You can view, query and filter the repository using the LogViewer command.

logviewer.sh -monitor -includeLoggers Connection

-monitor [integer]Specifies that you want the logViewer to continuously monitor the repository and output new log record entries as they are created. You can provide an optional integer argument after this parameter to specify how often you want the LogViewer tool to query the repository for new records. By default the logViewer queries the repository for new records every 5 seconds. When used with other filtering options, only those new records that match the filter criteria are displayed.

References: https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/rtrb_logviewer.html


Contribute your Thoughts:

Derick
8 days ago
I think the best way to debug this script is to print out the entire thing, and then start rearranging the steps with a pencil and paper. That's how they did it back in the good old days!
upvoted 0 times
...
Lettie
9 days ago
Wow, using the --javaoption '-Xdebug' and the logViewer command sounds like a real geek-fest! I hope it works, but it seems a bit overkill for a simple script issue.
upvoted 0 times
...
Tayna
11 days ago
The debug perspective in Eclipse is the way to go! I can step through the script and see exactly where the issues are.
upvoted 0 times
...
Coleen
14 days ago
Executing the script with the --conntype NONE option and monitoring the log file could be useful, but I'm not sure if it will provide enough information to debug the script effectively.
upvoted 0 times
...
Dalene
19 days ago
The Validate option from the context menu seems like the easiest way to test the script. It should give me a good starting point to identify any issues.
upvoted 0 times
Josue
1 days ago
Option A) In WebSphere Application Server Developer Tools for Eclipse, right click on the script file and select Validate from context menu.
upvoted 0 times
...
...
Alisha
20 days ago
I prefer option B, executing the script with the --conntype NONE option and monitoring the log file. It's more straightforward for me.
upvoted 0 times
...
Tandra
21 days ago
I agree with Owen, using WebSphere Application Server Developer Tools for Eclipse in the debug perspective seems like the most efficient method.
upvoted 0 times
...
Owen
25 days ago
I think option C is the best way to test and debug the script.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77