CloverDX Data Profiler Reporting Console supports the following web containers:
Basic installation is fairly simple.
Then place it to your web container’s
Deploy the Reporting Console:
Go to Integrated Solutions Console
Go toand follow the instructions on your screen.
Configure application class loading:
Go to Class loading mode select Classes loaded with local class loader first (parent last).. Here under
With default configuration, the Reporting Console will try start an internal Apache Derby database for storing the profiling results.
On WebSphere, this requires you to place
derbynet.jar drivers into your
You can download these drivers here.
Similarly to WebSphere, go to your server’s administration and deploy your copy of
Similarly to Tomcat, copy
The Reporting Console needs to communicate with a running CloverDX Server instance to check for user permissions.
By default, Reporting Console will try to contact CloverDX Server at the address
If your CloverDX Server instance is running at different location, please refer to Configuration to change this configuration.
By default, the Reporting Console will start an internal Apache Derby database for storing the profiling results. If you wish to store the profiling results into different database (which we recommend), please also refer to Configuration.
The easiest default installation and configuration is therefore the one when you deploy both CloverDX Server and the Reporting Console to the same web container on port 8080. This way both applications will successfully use their default configurations to communicate with each other. More on this in Configuration.