• Oracle TSAM monitors the major performance sensitive areas of a Tuxedo-supported enterprise computing environment. It can be used to monitor real-time performance bottlenecks and business data fluctuations, determine service models, and provide notification when pre-defined thresholds are violated.
• Real-time call path tree tracking of a monitored request is displayed and the performance metrics for each step are available.
• Oracle TSAM Framework: The framework is the data collection engine. It is an independent layer working between Tuxedo infrastructure and other TSAM components. This module is responsible for run time metrics collection, alert evaluation and monitoring policy enforcement.
• Oracle TSAM Plug-in: An extensible mechanism invoked by the Oracle TSAM Framework. The Oracle TSAM Agent provides default plug-ins to send data to the LMS (Local Monitor Server), and then to the Oracle TSAM Manager. The plug-in allows custom plug-in to be hooked to intercept the metrics. The default plug-in communicates with LMS with share memory. Application will not be blocked at metrics collection point.
• Local Monitor Server (LMS): The LMS is an Oracle Tuxedo system server. The Oracle TSAM default plug-in sends data to the LMS. The LMS then passes the data to the Oracle TSAM Manager in HTTP protocol. LMS is required on each Tuxedo machine if the node need to be monitored.
• Oracle TSAM Data Server: The data server is responsible for:
• Oracle TSAM Console: The Oracle TSAM presentation layer. It is a J2EE Web application and can be accessed via a compatible Web browser. After logging on to the Oracle TSAM Console, you have access to full Oracle TSAM functionality.Figure 1‑1 shows the Oracle TSAM architecture.Figure 1‑1 Oracle TSAM Architecture
• Call transportation. The edge (how information is sent and received) of a call path tree represents the transportation information from caller to service provider. It could be an IPC queue, BRIDGE connection or DOMAIN connection. The elapse time used for each transportation is also recorded.A "monitoring initiator" is a process that "initiates" tracking a call path tree. The process can be a Tuxedo client, application server, client proxy server (WSH/JSH), the Tuxedo domain gateway server or web services proxy serve GWWS. A typical scenario is when a tpcall/tpacall is invoked by the monitoring initiator; call path monitoring begins. All the back-end services involved in this call are displayed on the call path tree representation in the Oracle TSAM Console.
Note: Currently only tpcall/tpacall can trigger a call path monitoring. Other communication models are not supported.
• Monitoring Category. One monitoring policy can focus on one kind of monitoring, such as call path. It can also cover multiple interested areas.
• Enable or Disable. Oracle TSAM monitoring can be dynamically turned on or off. Monitoring policy can be predefined and enabled when the monitoring is needed. All enabled monitoring policy will be applied to Tuxedo applications automatically while application is running. Non-started application will get the policy while it is started.
• Interval-Based Monitoring. Monitoring is initiated based on specific time intervals. For example, call path monitoring. An interval-based monitoring policy can specify that the call path is tracked in 60-second intervals.
• Ratio-Based Monitoring. Monitoring is initiated by the number of executions. For example, service monitoring. A ratio that is set to 5 indicates that every 5 executed services are monitored. For call path monitoring, a ratio set to 5 indicates that every 5 tpcall/tpacall calls are monitored.
• Runtime Condition Filtering. TSAM monitoring policy supports some run time filters. Customer can monitor a particular service, a request from specific client and some kind of process type. The filter supports regular expression format.
• Flexibility to Reduce Monitoring Performance Impact. Oracle TSAM monitoring control enables you to configure the monitoring policy based on your application size, load and network activity. The monitoring policy can support only alert triggering without raw metrics storage.
• Correlation ID: A unique identifier that represents a call path tree. It is generated by the monitoring initiator plug-in. It uses the following format:Listing 1 shows an example of a Correlation ID. The monitored call is started by the program “bankclient” with process ID 8089 and thread ID 1 on machine “SITE1” on Tuxedo domain “TUXDOM1”. The master is “bjsol18” and IPCKEY in TUXCONFIG is “72854”.Listing 1 Correlation ID ExampleTUXDOM1:bjsol18:72854 SITE1 bankclient 8089 1 99 1259309025
• Service Name: The name of an Oracle Tuxedo Service.
• Location: The set of metrics to identify the process who sends out the performance metrics. It includes information about domain, machine, group and process name etc.
• IPC Queue Length: The message number in an IPC queue.
• IPC Queue ID: Oracle Tuxedo identifier of an IPC queue.
• Execution Time: The time used in an Oracle Tuxedo service or XA call execution in milliseconds.
• Wait Time: The time used of a message in the transportation stage.
• CPU Time: The CPU time consumed by the service request processing. It only applies to single threaded server.
• Message Size: The Oracle Tuxedo message size.
• Execution Status: The tpreturn service return code. It is defined by the Oracle Tuxedo ATMI interface.
•
•
• Elapse Time: The time elapsed time a call is monitored.
•
• Pending Message Number: The number of messages which are delivered to the Oracle Tuxedo network layer and waiting for being sent.
• Message Throughput: The total message number and volume accumulated in system server monitoring intervals.
• Waiting Reply Message Number: The number of requests in GWTDOMAIN awaiting a reply from the remote domain.
• XA Code: The XA call return code in transaction monitoring.
• XA Name: The XA call name.
• GWWS Metrics: A set of metrics used to measure GWWS throughput, including:Enabling call path monitoring for a Tuxedo client or application server allows you to find out all the information behind a simple tpcall/tpacall. The tracking points span multiple machines and multiple domains. You can clearly see the following information in the call path tree:Turn on call path monitoring with the proper monitoring policy and then use “tpgetcallinfo”. The following information is provided.The monitoring initiator process, tpgetcallinfo(), can also tell you the total time used.Install the Oracle TSAM Agent and the Oracle TSAM Manager. For more information, see the Oracle TSAM Installation Guide.Login to the Oracle TSAM Manager Console (for example: http://localhost:8080/tsam/faces).Your Oracle Tuxedo configuration can be found in the Oracle Tuxedo component tree panel. For more information, see the Oracle TSAM Console User Guide.• Monitor call path initiated from a particular client