JaxView records copies of Web service request and response messages as a means or monitoring and reporting on service performance. By default, JaxView stores this data in the file system of the server where JaxView is running. This default configuration enables JaxView to be installed, configured, and begin monitoring the SOA environment quickly. For management of distributed environments over longer periods of time and to meet other operational or organizational requirements, JaxView can be configured to use external databases both to store data that it collects and its own configuration settings. This provides important enterprise-ready capabilities for deploying JaxView in distributed service environments.
JaxView has been tested with the following database systems:
When JaxView is configured to use a database, Web service message data being monitored by JaxView is recorded to the database. The database becomes JaxView's data repository instead of the local file system. JaxView is designed to share database for configuration and data reporting with other JaxView server installations. Any other JaxView connected to the same database has access to the same data. This includes both JaxView configuration properties and Web service message data. JaxView can use most databases that provide JDBC connection support. The following figure illustrates the use of an external database to share configuration data between a cluster of JaxView servers deployed as proxy servers behind a load balancer.
The following are some of the scenarios for which integrating an external database into your JaxView deployment will be essential or useful.
A JaxView cluster needs to be deployed behind a load balancer as a gateway to Web services. The individual JaxView servers need to record all metrics to one data repository to enable comprehensive performance reporting
A large amount of message traffic is being being monitored by JaxView and using the local file system for data storage could be problematic over time.
Data collected by JaxView needs to be available for much longer than the 30 day default data persistence period in JaxView.
A third-party report generation tool is used to create operational performance reports from data recorded to SQL databases. JaxView performance data needs to comply with this organizational process.
A JaxView cluster is installed behind a load balancer as a gateway to Web services. There is a need to minimize performance recording and report processing load on the JaxView proxy servers. Another JaxView installation needs to be assigned to perform the active monitoring and reporting tasks normal to JaxView.
Multiple JaxView installs are needed in a distributed environment in order to monitor and manage the entire infrastructure or due to operational restrictions.
A JaxView failover server needs to be configured to use the same configuration settings as a primary JaxView installation.
There are several steps to configuring JaxView to use an external database depending on the deployment objective you are trying to achieve. This section describes the step you use to integrate an initial JaxView installation with a database and then how to add another JaxView installation to the integration.
The following are prerequisites for things you need to know or do in order to configure JaxView to use an external database:
The database server installed and running.
The database server must be accessible to the JaxView server(s) using a JDBC connection.
A named database instance that JaxView will use is created on the database server.
A user name and password are configured for JaxView to write to the database. This account needs to be granted the rights to create, delete, insert, update, and select on the tables in the database.
The main.properties configuration file in the JaxView/Config directory has been backed up and modified with the SQL syntax statements specific to the database that you are using. See the section Modifying the JaxView Porperties File below for more information.
The database connection URL is defined for the server where JaxView is running.
At least one JaxView server has been configured with the Web service location information, monitor instances, event notification rule, event action alerts, governance policies, and other configuration options needed for SOA performance monitoring and management.
If you plan to use the option of having JaxView configurations and JaxView monitoring data stored in separate databases, you will need to provide database information for both databases as outlined above.
The following sections describe the steps you use to configure JaxView to use the database.
Currently, you must edit the main JaxView properties file to include the database command and query syntax for the database product you will be using. Database system vendors often use product-specific commands and syntax to interact with their database server. The database commands and query strings JaxView uses to manage external databases are stored in a configuration properties file. The following database command and SQL query files are available:
|
DBMS Product |
JaxView Properties Filename |
|---|---|
| MySQL | main.properties.mysqlprops |
| Oracle | main.properties.oracleprops |
| MS SQL | main.properties.mssqlprops |
| IBM DB2 | main.properties.db2props |
The following describes the steps to modify JaxView main properties for use of a specific database product.
To modify JaxView properties for a specific database product:
In this procedure, JaxView will create the database tables and populate them with configuration data. This assumes that JaxView has been installed in its intended location and that the applicable Web service definitions, monitors, transactions, rules, alerts and other configurations. Use the following steps to configure an initial JaxView server to use a the external database. See the section Working with Database Configuration Settings for more information about the properties in the Database Configuration form.
To configure the initial JaxView server and database:
After installing and configuring the JaxView server for Web service performance monitoring and management, log in to the JaxView application.
Select the Admin tab from the Main View navigation menu. The Admin page is displayed.
Click on the Database node in the Admin object tree on the left side of the Admin page. The Database Configuration form is displayed in the right side panel.
At the top of the form, check the Enable Database Configuration check box.
If you will be using a separate JaxView install to perform active monitoring and reporting tasks to reduce the processing load on the current JaxView install, check the Disable Active Monitors & Scheduled Reports check box. Select this option if the current JaxView is being used as a Web service proxy or gateway and there is a need to maximize throughput performance. Otherwise, leave this option unchecked.
Check the Copy Configuration check box to have this JaxView server send its service, monitor, rule, alert, policy, and other configuration data to the database.
Check the Restart Application Threads check box.
In the Configuration DB sub panel, check the Create Table in DB check box to have this JaxView create the tables to store the configuration data.
In the Configuration DB sub panel, enter the database connection properties as indicated including the Connection URL, database user name and password. See the section Working with Database Configuration Settings for more information.
If you will be using a separate database for JaxView data recording, enter the applicable database information in the Data Storage DB sub panel in the lower part of the page.
Once you have entered all the information, click the Save button at the bottom of the Database Configuration page. JaxView will attempt to connect to the database(s), create tables, and copy configuration data.
If the database initialization is successful, logout of JaxView and restart the JaxView service.
Log into JaxView to verify that it is operating as expected.
The following sections describe the options for integrating other JaxView servers with the same database created in the procedure above.
Use the following steps to configure one of more JaxView servers to operate “in parallel” to the initial JaxView server. The additional JaxView server(s) will use the same database as the initial JaxView server configured using the procedure in the previous section.
To add another JaxView server to a database option deployment:
Install the new JaxView server in the applicable location relative to any other JaxView servers previously installed. DO NOT configure any service definitions, monitors, transactions, rules, alerts or other configuration settings on this new JaxView server.
Select the Admin tab from the Main View navigation menu. The Admin page is displayed.
Click on the Database node in the Admin object tree on the left side of the Admin page. The Database Configuration form is displayed in the right side panel.
At the top of the form, check the Enable Database Configuration check box.
If you will be using a separate JaxView install to perform active monitoring and reporting tasks to reduce the processing load on the current JaxView install, check the Disable Active Monitors & Scheduled Reports check box. Select this option if the current JaxView is being used as a Web service proxy or gateway and there is a need to maximize throughput performance. Otherwise, leave this option unchecked.
DO NOT check the Copy Configuration check box; be sure this option is NOT selected.
In the Configuration DB sub panel, DO NOT check the Create Table in DB check box; be sure this option is NOT selected.
In the Configuration DB sub panel, enter the database connection properties as indicated for the same database as configured for the previous JaxView installation(s). You can log into the other JaxView installation(s) and copy the information from the Database Configuration page.
If you will be using a separate database for JaxView data recording, enter the applicable database information in the Data Storage DB sub panel for the same database as configured for the previous JaxView installation(s).
Once you have entered all the information, click the Save button at the bottom of the Database Configuration page. JaxView will attempt to connect to the database(s).
If the database connection is successful, logout of JaxView and restart the JaxView service.
Log into JaxView to verify that the configurations previously stored to the database are now in force in this new JaxView installation..
Repeat the steps of this procedure to add additional JaxView servers to this database deployment.
Use the steps in this section to add a new JaxView installation to be used as a metrics data processing server. This optional deployment is useful to maximize throughput performance of an existing JaxView cluster being used as a load-balanced proxy or gateway to Web services. The JaxView data processing server is the same JaxView package used for all other installations but with a simple configuration change. The JaxView to be used as the data processing server does not need to have direct access to the message bus for the Web services. It uses metrics data stored in the data storage database. The following figure illustrates the use of a data processing server as well as the concept of a shared database.
Use the following steps to configure a JaxView as a data processing server.
To add a JaxView data processing server to a database option deployment:
Install the new JaxView server in a location accessible to the data storage database being used by any other JaxView servers previously installed. DO NOT configure any service definitions, monitors, transactions, rules, alerts or other configuration settings on this new JaxView server.
Select the Admin tab from the Main View navigation menu. The Admin page is displayed.
Click on the Database node in the Admin object tree on the left side of the Admin page. The Database Configuration form is displayed in the right side panel.
At the top of the form, check the Enable Database Configuration check box.
DO NOT check the Disable Active Monitors & Scheduled Reports check box; be sure this option is NOT selected.
DO NOT check the Copy Configuration check box; be sure this option is NOT selected.
In the Configuration DB sub panel, DO NOT check the Create Table in DB check box; be sure this option is NOT selected.
In the Configuration DB sub panel, enter the database connection properties as indicated for the same database as configured for the other JaxView installation(s). You can log into the other JaxView installation(s) and copy the information from the Database Configuration page.
If you will be using a separate database for JaxView data recording, enter the applicable database information in the Data Storage DB sub panel for the same database as configured for the other JaxView installation(s).
Once you have entered all the information, click the Save button at the bottom of the Database Configuration page. JaxView will attempt to connect to the database(s).
If the database connection is successful, logout of JaxView and restart the JaxView service.
Log into JaxView to verify that the configurations stored to the database by the other JaxView servers are now in force in this new JaxView installation.
After successfully configuring the dedicated JaxView data processing server install, use the following steps to reconfigure JaxView servers acting as proxies or gateways to disable their data processing tasks.
To disable data processing task on a JaxView server:
Log into each of the JaxView installation that is not to be performing the data processing and reporting functions.
Select the Admin tab from the Main View navigation menu. The Admin page is displayed.
Click on the Database node in the Admin object tree on the left side of the Admin page. The Database Configuration form is displayed in the right side panel.
If you have configured a separate JaxView install to perform active monitoring and report processing tasks, check the Disable Active Monitors & Scheduled Reports check box.
Click the Save button at the bottom of the Database Configuration page.
There are two database configuration sections in the Database Configuration page. The first one is the Configuration DB. Completing the fields in this section and saving the settings will enable JaxView to store configuration settings and message data on a single database server. There may be several reasons that you will want to have JaxView store monitoring data on a separate database server. To enable this separation of data, you fill out both the Configuration DB section and the Data Storage DB section in the Database Configuration page, using the applicable connection information for the two database servers. The following figure illustrates the use of both a Configuration database and a Data Storage database in a case where multiple JaxView servers are deployed as proxy servers behind a load balancer.
JaxView database connection options and properties are set using the Database node in the Admin object tree in JaxView. Selecting the Database node displays the Database Configuration form in the right side panel. The form contains three sections. The top section includes a group of check box items that are used to control JaxView behavior relative to use of a database.
JaxView uses Hibernate (www.hibernate.org) . Hibernate supports most databases. To see sample configurations for a specific database you can look at the file: JaxView\tomcat\webapps\Hubble\WEB-INF\classes\hibernate.cfg.xml. If info on the database that you are using is not in this file, please visit the Hibernate Web site at http://www.hibernate.org/80.html for more information.
The following described the configuration settings in the database form
If you want to use a single database to store JaxView configuration properties and JaxView monitoring metrics,