How can system properties be utilized during troubleshooting in Maximo? (Choose Three)

Question

Options

• ATo define log file paths
• BTo set logging levels dynamically
• CTo specify database connection details
• DTo control session timeouts
• ETo manage the application server cache

• A
  80% (24)
• C
  13% (4)
• E
  7% (2)

Explanation

In Maximo, system properties (accessed via the System Properties application) directly support troubleshooting by allowing administrators to define log file paths (A), adjust logging verbosity levels dynamically without restarting the server (B), and control session timeout durations (D) - all of which help diagnose issues in a live environment.

C is wrong because database connection details (JDBC URLs, credentials, pool sizes) are configured at the application server level (e.g., WebSphere or WebLogic data sources), not within Maximo's System Properties application.

E is wrong because application server cache management is also handled at the server infrastructure layer, not through Maximo system properties - Maximo does have its own cache refresh mechanism, but it's accessed via tools like the Caches application or MXServer, not System Properties.

Memory tip: Think "LLS" - Logs, Levels, Sessions. These three are things Maximo itself controls and exposes via system properties for real-time troubleshooting. Database connections and app server cache live outside Maximo's control boundary, so they're not tunable from within.

No community discussion yet for this question.