Release Notes
Release 12.1.0.2.4
E29596-01
April 2012
Oracle Business Transaction Management allows you to define and monitor transactions, and understand the business context of each transaction, including the transaction's consumers and business payload. You can also set performance targets for each transaction and monitor performance relative to those targets. You can trigger alert notifications when performance targets are breached or unusual conditions are met.
This document provides information about the changes introduced with release 12.1.0.2.4 of Business Transaction Management. It is recommended that you review this document before installing the product or upgrading to this version of the product. This document contains the following sections:
The following sections describe new capabilities introduced with Release 12.1.0.2.4.
The fApps observer enables monitoring of the principal technologies that make up the infrastructure of Oracle Fusion 11g RUP1 Applications. The fApps observer package includes the following:
The SOA observer (including new probe for EDN)
The Java EE observer (except the JDBC probe)
New probes for ESS (Enterprise Scheduler Service) and ORA-WS (Oracle Infrastructure Web Services)
Depending on the technology, some messages flow directly from a client to a service, others flow through a host of intermediate endpoints before they reach their actual destination. Such intermediate endpoints might comprise the implementation of a messaging system, a job scheduling system, a distributed system, and so on. When installing probes for technologies that use intermediate endpoints, Business Transaction Management allows you to specify whether you want to monitor all endpoints or just the endpoints at the edge of such systems; often these are the endpoints that directly represent the business services of interest. Turning off the monitoring of intermediary endpoints can improve monitoring performance and eliminate data that is not essential to monitoring your distributed applications.
The observer communication policy gives you the option of controlling the monitoring of intermediate endpoints for SOA and EJB probes. For additional information, see Business Transaction Management Installation Guide.
The following problems have been observed:
Coexistence with ADP agent
CR 13895330: The ADP agent and BTM observer cannot coexist in a single container until the planned ADP agent update to 12.1.0.2. This is targeted for availability in mid-April 2012.
SOA Suite 11g PS5 bug impacting observer
CR 13895209: INCORRECT WSDL FOR SOA PS5 WEB SERVICES. User Description: In SOA PS5, if WSDLs of different SOA web services import the same parent WSDL, a query WSDL of individual service might contain all endpoints from different services with the same address location. This affects BTM in that SOA web services importing the same parent WSDL might show more endpoints than they are supposed to have.
The following bugs were fixed in this release.
CR 13577313: BTM JAVA EE OBSERVER GIVES SERVER FAULT RESPONSE TO CUST CLIENT
User Description: When deployed in WebLogic 10.3.5, the JAXWS probe might generate a SOAPFault when an observed message contains an invalid WS-Addressing header (e.g. wsa:From at the wrong position).
CR 13804251: EJB2.1 Session Bean Client Outbound Missing
User Description: If an EJB session bean is created using a facade pattern, which means that the remote bean interface (implementing EJBObject) is extended from a base interface (that does not implement EJBObject), then if calls to the remote EJB are made through the base interface, outbound measurements between EJB client and remote EJB are missed.
CR 13780025: ERROR CREATING MESSAGE PROPERTY - ERROR: COULD NOT FIND THE BUILT IN PARENT TYPE
User Description: When creating a Message Property on a managed object (server, endpoint, or operation), an IllegalStateException appears in the UI and the message property is not created. The error occurs on the screen that comes up when you select the menu option "Create->Message property on <object>". Also, the message "could not find the built in parent type ..." shows up in the server log. The problem occurs when you have nested restrictions of Simple types in the XSD describing the message for the operation.
CR 13800185: EXCESSIVE BTM ROUTER LOOKUPS IN DTA (INCORRECT LOG MESSAGE: CREATING ROUTER FOR
User Description: The BTM system automatically detects routers in a monitored environment. It adds a newly discovered router to the Sphere model. However the router existence information is not cached in memory. This causes excessive calls between the Monitor and Sphere.
CR 13805446: HEADER MESSAGE PROPERTIES CANNOT BE USED FOR TRANSACTION CONSUMER SEGMENTATION
User Description: Selecting a header property as the property to be used for segmentation does not work. The problem is that the code in the transaction server treats header and non-header properties differently and does not account for the possibility that a header could be used as a value for a segment.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Oracle Business Transaction Management Release Notes, Release 12.1.0.2.4 for all platforms
E29596-01
Copyright © 2012 Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.