JaxView has multiple deployment options that can help provide visibility, policy enforcement and control to services deployed on JBoss application server. With many open API’s for customization JaxView is a clear choice for the open source community

JaxView deployed in agent-less mode can provide visibility into all transaction in- and out of JBoss application server by sniffing on the net work that the traffic is flowing through. In this deployment option JaxView can provide visibility into not only HTTP based traffic by also JMS, JMX, RMI or any other TCP based protocols. This agent less visibility into JBoss through a port mirror or TAP is the only one in the SOA runtime governance space.

This deployment can be used to perform transaction tracking, consumer SLA’s and metering and monitoring, alerting and auditing of all transaction within the JBoss SOA platform.

To enforce policies JaxView can be deployed in the gateway mode to add additional control to the service installed on JBoss platform. In this mode JaxView can enforce security, routing, throttling, and virtualization of the services.

If looking to gain visibility into intra-container call within services that are deployed on the same JaxView server then you can use the JaxView agent based deployment. JaxView JBoss agent is light weight and monitors all calls being made within services that are installed on the same container.

By deploying JaxView in different fashion the user can provide end-end visibility and control over the JBoss deployed services in their environment including multiple protocols used by those services.