Configure Datablau JDBC clients
Clients connect through the gateway using Datablau JDBC Driver. Direct database connections do not automatically apply gateway policies.
Connection parameters
| Parameter | Value |
|---|---|
| URL | jdbc:datablau://[host]:[port] |
| Driver class | com.datablau.jdbc.Driver |
| host | Deployed gateway address |
| port | Proxy source's gateway service port |
| Credentials | Match DAM or virtual-account mode |
Replace bracketed placeholders. Use administrator-provided packages and the Datablau class, not a native database class.
Connect database tools
- In DBeaver, open Database > Driver Manager and create a driver.
- Add the JAR and class.
- Create a connection with the gateway URL and credentials.
- Test and browse expected objects.
- Query known samples using Verification.
Check generated URLs even with driver templates. Match gateway detail links/login modes. Expand database/schema/tables/columns and test explicitly covered fields. Separate connection failures from masking problems.
Prepare FineBI integration
Deploy datablau-driver-jdbc-bridge.jar, the companion thread-context agent, and JDBC plugin from the approved package. Add companion agent parameters to actual startup configuration, start, then create the source.
The bridge passes the BI identity through thread context. Matching BI/DAM usernames use that DAM user's policies; passwords may differ. Nonmatching names use default permissions. Test real user results, not only administrator connections. Use deployment-specific paths/scripts and revalidate identity propagation after upgrades.
Troubleshoot
| Symptom | Checks |
|---|---|
| Class missing | Package loading and name |
| Refused | Enabled service, host, port, network |
| Authentication failure | Mode and credentials |
| Unexpected data | Actual route, identity, scope |
| Identical BI results for all users | Propagation, name mapping, defaults |