Red Hat JBoss Data Virtualization

Red Hat JBoss Data Virtualization

About TrustRadius Scoring
Score 7.4 out of 100
Red Hat JBoss Data Virtualization


Recent Reviews

Video Reviews

Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of Red Hat JBoss Data Virtualization, and make your voice heard!


View all pricing

Sorry, this product's description is unavailable

Entry-level set up fee?

  • No setup fee


  • Free Trial
  • Free/Freemium Version
  • Premium Consulting / Integration Services

Would you like us to let the vendor know that you want pricing?

1 person want pricing too

Alternatives Pricing

What is Fivetran?

Fivetran replicates applications, databases, events and files into a high-performance data warehouse, after a five minute setup. The vendor says their standardized cloud pipelines are fully managed and zero-maintenance. The vendor says Fivetran began with a realization: For modern companies using…

Features Scorecard

No scorecards have been submitted for this product yet..

Product Details

What is Red Hat JBoss Data Virtualization?

Red Hat JBoss Data Virtualization Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo


View all alternatives

Reviews and Ratings



(1-1 of 1)
Companies can't remove reviews or game the system. Here's why
Score 7 out of 10
Vetted Review
Verified User
Review Source
We are using JDV to abstract the underlying data sources away from our applications. Currently the primary use is to allow us some flexibility while we retire an Informix based system.
  • Data source compatibility: since it is Java, it can connect to anything with a JDBC driver.
  • Flexibility: you can configure it however you want, we have it configured to use LDAPS for authentication and have all interfaces encrypted, and setting that up was pretty straight forward.
  • Documentation: hard to navigate, or missing entirely.
  • Integration with Windows: ODBC drivers are not great, don't support SSL.
  • Logging: troubleshooting issues is not straight forward, often requires logging changes.
I think it would work well in a Java/Linux environment. It is not as suited to Windows/.Net.