What is JaxView?
What operating systems can JaxView be installed on?
How does JaxView monitor Web services?
How is JaxView licensed?
Can JaxView work with ESB's or Message Queues?
Can I use JaxView for Web service virtualization?
Can JaxView monitor Web services running on WebLogic, WebSphere, .NET, or other application servers?
Does JaxView require that I have a UDDI registry?
Can JaxView be used to automatically detect Web services?
Can JaxView handle encrypted XML messages or XML signatures?
Can JaxView work as a service gateway for client authentication?
Can JaxView modify service messages in runtime to satisfy different message schemas?
Does JaxView support transactions across multiple services?
What is JaxView agentless deployment?
Does JaxView save all message request and responses for auditing purposes?
How long is data stored by JaxView?
Can JaxView save monitoring data to an external database?
How can I manage more than one JaxView installation in my network?
Can I monitor Web services running on a cluster of servers with JaxView?
Can I control JaxView from another application?
How do I get regular expression matching to work in JaxView?
Why does JaxView fail to start after installation on Windows XP?
How do I apply a patch to JaxView?
How do I upgrade my version of JaxView
JaxView is an application for monitoring Web service transactions and providing a variety of runtime governance functions for service-oriented environments. JaxView gives IT operations teams important visibility into the SOA message space for managing system availability, performance, and policy compliance. JaxView also has many features that help enable policy enforcement in the SOA environment such as authentication, secure data exchanges, client usage metering, message modification, and other functions.
JaxView is built on platform-independent technology. It is currently supported on for installation on Windows, Linux, and Mac OS X platforms.
JaxView is designed to listen passively to request and response messages exchanged in the SOA environment. It can do this in a variety of ways. One is that it can be used as a service gateway or proxy where it can monitor message data that it passes between consumers and producers. Another way is to configure JaxView to use a network analyzer to listen to TCP packets and copy service message data from the network. JaxView can also receive copies of message data by subscribing to a service bus/message queue or from the use of agent stubs installed on application servers. Each of these is designed to have a minimal impact on network and service resources.
In addition to passive listening, JaxView can actively test Web service endpoints to verify availability with synthetic requests.
JaxView licensing information can be found here.
JaxView can integrate with an Enterprise Service Bus or Message Queue using the Java Message Service (JMS). You use the ESB node in the Admin tab in JaxView to define the connection parameters for each ESB or MQ to which you want to connect. You must also specify "topics" to which to subscribe in order to have JaxView receive the relevant Web service data.
JaxView can be used to virtualize services by deploying it as a service gateway or proxy between the clients and the service endpoints. In this deployment, JaxView creates a virtual URL for each of the services in its catalog. Clients can then be directed to the JaxView server address for all of the services to be virtualized and JaxView will forward the requests to the applicable service endpoint.
Can JaxView monitor Web services running on WebLogic, WebSphere, .NET, or other application servers?
JaxView's flexible deployment options allow it to monitor virtually any SOAP or REST type Web service. When used as a service gateway or integrated with a network analyzer, JaxView can monitor service message traffic regardless of what application server on which the services are run. Where an agent stub deployment is required, JaxView includes agent stubs for many commercial
JaxView does not require that a UDDI-compliant registry exist in the SOA infrastructure. While JaxView can be configured to use a UDDI registry, it is not central to the design or operation of the product. You use the Admin->Registries node to configure JaxView to connect to and query a UDDI registry.
Deploying JaxView as a network appliance is an alternative to having a UDDI in that it allows JaxView to automatically discover services in the environment.
JaxView can be configured to automatically discover services and automatically configure monitoring, alerting, and reporting for those services. One way that JaxView can do this is by integrating JaxView with a network analyzer and SPAN port enabled switch. In this configuration, JaxView will analyze TCP packets to detect service message exchanges. JaxView then adds service definitions based on information in the message traffic. It then can add monitor, alert, and report definitions that the user selected for newly discovered services. You use the Admin->Options node to configure JaxView network analyzer and auto discovery options.
JaxView supports decryption of XML data. When deployed as a service gateway, JaxView can decrypt incoming request messages before forwarding them onto service endpoints. It can also encrypt outgoing messages before sending them on to the client. JaxView can also handle messages signed with digital XML signatures or X509 certificates. You use the Policy forms attached to each service node in the JaxView Services view to configure encryption options. Select a service node in the Services tree and right-click to display the action menu. Select edit to access the Policy forms.
When deployed as a proxy between services and clients, JaxView can be used to enforce authentication of client service requests. This includes HTTP authentication against an LDAP directory or Active Directory database as well as a simple client access list native to JaxView. JaxView then only forwards requests that can be authenticated against these data sources. You use the Security Policy forms attached to each service node in the JaxView Services view to configure encryption options. Select a service node in the Services tree and right-click to display the action menu. Select edit to access the Policy forms.
When deployed as a service gateway or proxy, JaxView can be configured to modify incoming and outgoing messages. This is useful if the client or service producer application use different message schemas and could not otherwise interact correctly. Once a service definition has been added to JaxView, you can edit the service and configure a Request/Response Modification policy. This can be done using XPath or regular expression substitutions or by passing the messages to a customizable plugin module to perform more complicated modifications.
JaxView transaction monitoring allows you to define a transaction that involves multiple service endpoints. The service endpoint can be defined for each step of the transaction.
The Agentless deployment is when JaxView is connected to switch in your environment througha SPAN port or a TAP for monitoring all TCP protocol based services inclduing HTTP,SOAP, REST, JMS, JDBC, NET, JOLT....etc..
Yes JaxView stores all message data and all monitored data for reporting and auditing purposes.
JaxView maintains two primary data sets. The first is its own monitoring data logs. This data is JaxView specific information as calculated by the monitoring functions of the product. By default, this data will be kept for 30 days. You can change this value in the Admin->Master Settings node by modifying the _logKeepDays parameter. The second set of data stored by JaxView is service message data for the specific service operations being monitored. By default, this data is stored indefinitely. You can change how long this data is persisted by editing each service node in the Services tab and entering a number of days in the Days to Save Messages field under the Web Service General Policy section.
With the JaxView Enterprise license, service message and monitoring data can be exported to a JDBC-compliant database. JaxView has been tested with Oracle, MySQL, MS SQL Server 2005, and DB2 databases. More than one JaxView installation can use a single external database. This allows for deploying a cluster of JaxView servers as a service gateway or proxy. JaxView can even use the database as its own data repository for reporting functions.
If you have more than one installation of JaxView in your network environment, they can be managed individually or jointly by way of a shared database. JaxView servers deployed as a cluster or other distributed deployments can be configured to store their configuration data in an external database. If all of the JaxView installations use the same external database, they can then "see" the configurations of the other JaxView instances through the database. In the case of clustering, the JaxView servers can actually share the same configuration settings to where when a change is made to a configuration in one of the servers, the other servers will update their configurations by querying the shared database. These options are set using the Database and Master Settings nodes in the Admin tab. See the JaxView User Guide for more information.
Generally, a server cluster is implemented to provide load balancing and failover protection for a service. This usually means that client applications are unaware that the service is being served by a cluster of parallel machines. However, from an operations point of view, there may be a need to monitor each server in the cluster. You can do this in JaxView by adding each individual server address that provides the service as part of the service definition. You must do this at the time that you add the service to the Services tree.
JaxView includes a Web service interface that allows JaxView to be accessed and controlled remotely. This includes service interfaces for configuration of monitors, alerts, and reports. See the Advanced Options section of the JaxView User Guide for more information.
JaxView uses a Java library for regular expression support in the product. Due to the way this library is implemented, regular expression pattern need to account for any content preceding the target match and any content following the target match. Generally, this can be done by adding a .* pattern to the beginning of the expression and to the end of the expression. For example: .*JSESSI
If you are having difficulties getting the JaxView service to start on Windows XP, locate the VCRTArchive.zip file that is included with the JaxView download. Unzip the contents of the archive to the root directory (for example. C:). This will add a couple of missing DLL's into your system directory. Then try and restart the JaxView service again.
Unzip the patch in the directory above the installed directory for JaxView.
1)Download JaxView from our web site.
2)Rename your current JaxView directory to something else.
4)Copy the old JaxView/config direcotory into the new one and restart JaxView.