15 noviembre 2013

provider org.hibernate.ejb.HibernatePersistence provider
org.hibernate.ejb.HibernatePersistence java:/PruebasSeamDatasource

If you are not laughing at yourself, then you just didn't get the joke.

Enterprise Java Programming with IBM WebSphere







org.hibernate.transaction Class WebSphereExtendedJTATransactionLookup




java.lang.Object
  extended by org.hibernate.transaction.WebSphereExtendedJTATransactionLookup
All Implemented Interfaces:
TransactionManagerLookup

public class WebSphereExtendedJTATransactionLookup
extends Object
implements TransactionManagerLookup
TransactionManagerLookup implementation intended for use with WebSphere Application Server (WAS).
WAS, unlike every other app server on the planet, does not allow direct access to the JTS TransactionManager. Instead, for common transaction- related tasks users must utilize a proprietary API known as ExtendedJTATransaction.
Even more unfortunate, the exact TransactionManagerLookup to use inside of WAS is highly dependent upon (1) WAS version as well as (2) the WAS container in which Hibernate will be utilized.
WebSphereExtendedJTATransactionLookup is reported to work on WAS version 6 in any of the standard J2EE/JEE component containers.
Author:
Gavin King,





Nagios


With Nagios you can:
  • Monitor your entire IT infrastructure
  • Spot problems before they occur
  • Know immediately when problems arise
  • Share availability data with stakeholders
  • Detect security breaches
  • Plan and budget for IT upgrades
  • Reduce downtime and business losses

Nagios Support Wiki


information and helpful documentation on various Nagios products







14 noviembre 2013

Compuware APM Application Monitoring


http://www.compuware.com/en_us/application-performance-management.html

http://www.compuware.com/en_us/application-performance-management/products/application-monitoring.html







In today’s world, applications are the lifeblood of your business. When problems arise, reactive troubleshooting is no longer good enough. Compuware APM is a new generation of lightweight, always-on application monitoring that lets you move from reactive crisis mode to proactive management. Deliver faster applications, more quickly. Tame unruly applications before they become problems. And when problems arise, take control with 24/7 visibility into transactions and infrastructure, even in the most demanding environments. Powered by patented technologies, Compuware APM delivers all this with zero sampling, zero configuration and less than 2% overhead. Four solutions are purpose-built for today’s modern applications.




Java, .NET and PHP

Compuware APM for Java, .NET and PHP is the smartest and fastest time-to-value APM solution available for today’s modern Java, .NET and PHP applications. Powered by patented PureStack™ and PurePath Technology®, Compuware APM captures timing and code-level context for all transactions, end-to-end, from user click, across all tiers, to the database and back. With this exact, atomic-level detail across 100% of transactions and infrastructure, Compuware APM enables the fastest path to root cause on the market—one click to line of code.More >

- See more at: http://www.compuware.com/en_us/application-performance-management/products/application-monitoring.html#sthash.beoJAUSk.dpuf


Performance Monitoring Infrastructure (PMI)



http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=%2Fcom.ibm.websphere.nd.multiplatform.doc%2Finfo%2Fae%2Fae%2Fcprf_pmidata.html

Utilizando los datos PMI, se pueden identificar y solucionar los cuellos de botella de rendimiento en el servidor de aplicaciones. Por ejemplo, una de las estadísticas PMI en la agrupación de conexiones JDBC (Java DataBase Connectivity) es el número de sentencias descartadas de la memoria caché de sentencias preparadas. Esta estadística se puede utilizar para ajustar el tamaño de la memoria caché de sentencias preparadas, de forma que se minimicen los descartes y mejore el rendimiento de las consultas de la base de datos
Los datos PMI también se pueden utilizar para supervisar el buen funcionamiento del servidor de aplicaciones. Algunos de los indicadores del buen funcionamiento son el uso de la CPU, el tiempo de respuesta de los servlets y el tiempo de consulta JDBC. Las herramientas de gestión del rendimiento, como Tivoli Monitoring for Web Infrastructure u otras herramientas de terceros, pueden supervisar los datos PMI y generar alertas sobre algunos umbrales predefinidos.


¿Por qué debe utilizarse Request Metrics?

Request Metrics es una herramienta que permite realizar un seguimiento de transacciones individuales, registrando el tiempo de proceso en cada uno de los componentes principales de WebSphere Application Server.

Antes de empezar

La información rastreada por request metrics se puede guardar en archivos de anotaciones cronológicas para una recuperación y análisis posterior, ser enviar a los agentes ARM (Application Response Measurement), o ambas cosas.
A medida que la transacción fluye en el sistema, request metrics agrega información adicional, de modo que se puede establecer una correlación de los registros de anotaciones cronológicas de cada componente, creando una imagen completa de esa transacción. El resultado es similar al siguiente ejemplo:
HTTP request/trade/scenario ------------------------------> 172 ms
     Servlet/trade/scenario  -----------------------------> 130 ms
         EJB TradeEJB.getAccountData --------------------->  38 ms
              JDBC select -------------------------------->   7 ms 




Mkyong

Top 8 Java People You Should Know
http://www.mkyong.com/featured/top-8-java-people-you-should-know/