## 1. How to monitor GWWS server status (down/active/unhealthy) via TSAM? To monitor GWWS server status (active/down/unhealthy) in Oracle TSAM Plus, use the Console’s **Component Tree** and **Availability** views (these show “status” as active/inactive). Optionally, enable a **GWWS monitoring policy** for metrics/alerts. ### 1) View GWWS “up/down” status in the Component Tree (status colors) In the TSAM Plus Console, the **Tuxedo Domains Component Tree** uses icon colors to indicate node status: - **Green** = domain/components active - **Yellow** = at least one child node inactive or unhealthy - **Red** = domain/component inactive (“down”) You may need to **Refresh** the tree to reflect current status. ### 2) Use the Domain Dashboard “Availability” to spot inactive items From the **Domains Dashboard** (or an individual domain dashboard), use the **Availability** section. It shows availability of servers in the domain; clicking the inactive (**red**) portion of the chart pops up a window listing the inactive items in detail. ## 2. How to monitor the status of a server in a monitored Tuxedo domain (up/down/crashed) To monitor whether a server is **up / down / crashed** in a monitored Tuxedo domain using Oracle TSAM Plus, use the **Component Tree** status indicators and the **Availability** view in the dashboards. ### 1) Use the Tuxedo Domains Component Tree (primary “up/down” indicator) In the TSAM Plus Console, the **Tuxedo Domains component tree** shows the hierarchy: - domain → machine → group → server Each node’s icon color reflects status: - **Green**: the domain (and all components under it) are active - **Yellow**: at least one child under the node is inactive or unhealthy - **Red**: the domain/component is inactive (effectively “down”; commonly what you see after a crash) **What to do:** - In the left Component Tree, expand to **Domain → Machine → Group → Server** - Check the server node color (**green/yellow/red**) - Click **Refresh** in the component tree to pull the current structure/status (the tree does not automatically change unless you refresh / enable auto-refresh) Also, make sure the domain is actually being discovered/updated: the FAQ notes the component tree shows automatically once LMS is correctly configured and the domain is booted. ### 2) Use “Availability” in the domain (or group) dashboard (fast way to list down items) On the domain dashboard, TSAM Plus provides an **Availability** view that summarizes server availability; clicking the inactive (**red**) portion shows the inactive items in detail. This is a quick way to see which servers are down without expanding the full tree. ## 3. How to get notified if a Tuxedo server is down or crashed TSAM Plus Manager does not notify users if a Tuxedo servier is down or crashed. Users need to check the status of a server in the Domain/Component Tree pane. If a server is down, its status will be in Red. ## 4. Are there any issues related to database, such as connection issue? TSAM Plus Manager does not have any metrics for database connections so unable to notify users if there are any database related issues. Please check TSAM log to check if any database related issues happen ## 5. What percent defines red, yellow and green in Dashboard? Sometimes, chatbot can answer the question. The answer is fine. The provided knowledge context does not explicitly define the percentage values for red, yellow, and green in the Dashboard. It mentions that the Domains Dashboard presents an aggregated view of all domains components availability, with a pie chart that shows inactive items in red. For more precise details, please provide additional context about the specific dashboard or metric you're referring to. ## 6. Does running TSAM has any impact on Tuxedo services? There might be performance impact to Tuxedo applications. There are several ways to tune performance impact to Tuxedo applications: 1) Call Path: Ratio/Interval: can reduce network traffic, TSAM database resource usage, and CPU usage. 2) Conditional Filter: can reduce network and database resources and allows administrators to focus on exceptional cases. 3) Alert Only: Specifies alert evaluation only. No metrics are sent to manager. ## 7. Can we Archive TSAM's data and restore it back if needed? TSAM Plus Manger provides a way to export policy definitions and alert definitions, and the exported definitions can be imported later. TSAM Plus Manager does not provide a way to archive metrics data or restore it back. Users need to use Oracle database tool to export/import metrics data. ## 8. From where can we download the new TSAM patch? Sometimes, chatbot can answer the question. Either of answers below works. 1) To download an Oracle TSAM patch from Oracle Support, you must have a valid Oracle Support Identifier (CSI). With your CSI, you can access My Oracle Support (MOS) at https://support.oracle.com. Log in with your CSI credentials, navigate to the Patches & Updates section, and search for the specific TSAM patch by its patch number or description. Once located, download the patch to your local machine. Ensure you review the README file included with the patch for installation instructions. 2) The provided knowledge context does not contain information about where to download the new TSAM patch. The context information appears to be related to the configuration and usage of Oracle TSAM Plus, but it does not mention patch downloads. ## 9. What are the known issues/bugs in current version? The answer is dependent on the release notes. If no known issues are mentioned in release notes, chatbot should answer following: There are no known issues mentioned in this release. chatbot should list the known issue list mentioned in 22c release notes. ## 10. Can TSAM Plus Manager be scaled? Yes, TSAM Plus Manager can be scaled. Oracle TSAM Plus Manager is built on J2EE technology and runs in a Java application server. ## 11. How to increase LMS agent queue depth as several messages are getting dropped? In what all circumstances messages are dropped by LMS? What all possible solutions? LMS message drops usually mean the Agent-side shared-memory ring buffer is being overrun. The first setting to review is -m, because it controls how much burst data LMS can absorb before old unread records are overwritten. Messages may also be lost when LMS cannot forward data to TSAM Manager fast enough due to network issues, Manager slowness, or Manager-driven throttling. The right solution is usually to increase -m first, then tune -n and -T if needed, and also tune TSAM Manager persistence threads, queue threshold, sleep interval, and JVM protection settings so the whole pipeline can keep up. ## 12. Can we create a cluster of TSAM Managers? Yes, we can create a cluster of TSAM Managers. This is mentioned in TSAM Plus Manager documentation. ## 13. How to check DB related settings, such as DB username, connection string, etc. TSAM Plus Manager leverages the DataSource in WebLogic Server. Refer to WebLogic Server documentation for details. ## 14: If there is any DB connectivity issue in TSAM, which log file to refer? In TSAM, there is no specific log file directly mentioned for DB connectivity issues. However, you can control the log level for JPA SQL, which defaults to Warn. To troubleshoot DB connectivity issues, adjust the log level to a more detailed setting like Debug or Trace to capture relevant information. Log level modifications take effect immediately without needing to reboot the application server.