Oracle TSAM 10g Release 3 (10.3) Release Notes

Table 1 Revision History
Revision Date	Summary of Change
July 02, 2009	Updated “Oracle TSAM 10gR3 Supported Platform Data Sheets” in Installing tOracle TSAM with: HP-UX 11i v2 (32-bit) on Itanium
March 05, 2009	Updated “Oracle TSAM 10gR3 Supported Platform Data Sheets” in Installing tOracle TSAM with: Oracle Enterprise Linux 5.0 (32-bit)
January 15, 2009	Initial Release

About This Oracle TSAM Release

Oracle Tuxedo System and Application Monitor (TSAM) 10g Release 3 (10.3) provides comprehensive monitoring and reporting for the Oracle Tuxedo system and applications. It includes two components: Oracle TSAM Agent and Oracle TSAM Manager. For more information, see Oracle TSAM Agent and Oracle TSAM Manager in the Oracle TSAM Administration Guide.

The Oracle TSAM Agent enables collection of various performance metrics for applications, including call path, transactions, services, system servers. Oracle TSAM Manager provides a graphical user interface to correlate and aggregate performance metrics collected from one or more Tuxedo domains and display it in real time.

Call Path Monitoring and Analysis
Service Monitoring and Statistics
System Server Monitoring and Statistics
Transaction Monitoring
Event Alerts
Open Plug-in Framework
Dynamic Monitoring Policy Management
Web-based Reporting and Management

What's New and Improved

TSAM Manager: Oracle WebLogic Server and Oracle OC4J support
TSAM Agent: IPv6 support

Oracle TSAM Software Components

Oracle TSAM Agent

Oracle TSAM agent enables collection of various performance metrics for applications. It includes the following sub-components:

Oracle TSAM Framework
Oracle TSAM Default Plug-in
Local Monitor Server (LMS)

Oracle TSAM Manager

Oracle TSAM Manager provides a graphical user interface to correlate and aggregate performance metrics collected from one or more Tuxedo domains and displays them in real time. It includes the following sub-components:

Oracle TSAM Console
Oracle TSAM Data Server

Installation Notes

Oracle TSAM 10g Release 3 (10.3) includes two components: Oracle TSAM Agent for Tuxedo 10g Release 3 (10.3) and Oracle TSAM Manager. For more information, see the Oracle TSAM Installation Guide.

You must ensure that Oracle TSAM Agent is properly installed and configured on each monitored node in order to use in conjunction with Oracle TSAM Manager.

Upgrade Consideration

If you upgrade TSAM Manager from release TSAM 1.1 to 10g Release 3 (10.3), TSAM 10g Release 3 (10.3) Manager can reuse the database used in release 1.1.

Monitored policy sets defined in TSAM 1.1 can be exported to policy set definition files on the TSAM 1.1 Console, and then imported to TSAM 10g Release 3 (10.3)via TSAM Console.

Interoperability

TSAM 10g Release 3 (10.3) Manager can work with TSAM 1.1 Agent for Tuxedo 8.1, 9.1 and 10.0.

TSAM 10g Release 3 (10.3) Agent for Tuxedo 10g Release 3 (10.3) can work with TSAM 1.1 Agent in MP and Domain mode.

Oracle TSAM Platform Support

Oracle TSAM 10g Release 3 (10.3) supported platforms are listed in Oracle TSAM 10g Release 3 (10.3) Supported Platforms in the ‘Oracle TSAM Installation Guide.’

Known and Resolved Issues

Table 2 lists known Oracle TSAM 10g Release 3 (10.3) software limitations and includes recommended workarounds. The limitations are listed by bug number. Issues are listed by Change Request (CR) number.

Table 2 Know and Resolved Issues
CR767529	The Call Path monitoring status is always pending if a service call is timed out and RCVLEN is not initialized.
	Platform	All
	Workaround	Initialize the output buffer length of tpcall() or tpgetrply().
22806792	The Apache Commons Collections version embedded in TSAM 10.3 installer has security vulnerabilities.
	Platform	Generic
	Workaround	After installing TSAM 10.3, upgrade the embedded Apache Commons Collections version to 3.2.2 or later.

Table 3 lists problems that have been fixed in this release. Issues are listed by Change Request (CR) number.

Table 3 Problems Fixed in Oracle TSAM 10g Release 3 (10.3)
CR Number	Problem Description
CR340185	The Call Path monitoring status is always pending if a `tpacall()` service request is cancelled by `tpcancel()`.

Release Notes