PointBase Schemas, Embedded or Server, One Tool

PointBase is the compact pure-Java database that early Java EE application servers, BEA WebLogic among them, bundled for development and testing. DbSchema connects over the PointBase JDBC driver and gives those inherited databases an ER diagram, a SQL editor, and documentation.

One tool for embedded and network server mode
See what the JPA provider generated, as a diagram
Query the data without a dedicated PointBase client
Export a schema reference for audits and handovers

available for

ISO-27001 certified

Free Community Edition No signup required 15-day Architect trial included

Free Download

DbSchema rendering a PointBase database schema as an ER diagram

Trusted by teams at

The Development Environment Is Gone
The PointBase Database Is Still Here

Teams maintaining older Java EE applications keep finding PointBase underneath: a test or configuration database the JPA layer generated years ago, with no documentation and no graphical tooling left to open it.

DbSchema reads the PointBase catalog — tables, column types, and foreign keys — and turns it into a model you can browse, query, and document today.

Inspect, Query & Document
PointBase from One Desktop Tool

What a legacy database needs most: visibility.

Reverse engineer a PointBase catalog into an ER diagram

Recover the Schema Nobody Documented

Connect once and DbSchema draws the tables, types, and foreign-key relationships the JPA provider or Hibernate created — no archaeology in system catalogs.

Run SQL against PointBase in the DbSchema SQL editor

SQL for Both PointBase Modes

Inspect application data, run DDL, and validate a change before it reaches the application server — against embedded and server-mode databases alike.

Generate HTML documentation for a PointBase schema

A Reference That Outlasts the Project

Produce a structured HTML report of table definitions, column metadata, and relationship diagrams — the durable artifact audits and handovers ask for.

The Model File Outlasts
the Original Dev Environment

DbSchema keeps the PointBase schema in a design model file of its own. Open it years later, with or without a running database, and the structure is still there to read, version, and build on.

Open the PointBase model without a connection

Browse Without the App Server

The model opens on its own — no WebLogic instance, no live database required.

Keep the PointBase schema model in version control

Version It with the Project

Commit the model next to the legacy code, so schema and application history stay together.

Read generated SQL before running it on PointBase

Read Changes as SQL

Review the statements a schema edit produces before anything runs against the database.

Design a migration target schema in DbSchema

Design the Successor

Plan the move off PointBase by modeling the target schema in the same tool.

Embedded or Server: Connection Facts

The two PointBase modes differ only in driver JAR and URL. Embedded mode uses pbembedded.jar from your PointBase installation with a URL of the form jdbc:pointbase:embedded:dbname; server mode uses pbclient.jar with jdbc:pointbase:server://host/dbname. Register the matching JAR in DbSchema's driver manager and the connection wizard picks it up.

For embedded mode, the database files must be reachable from the machine running DbSchema, and no other process may hold a lock on them during the session. Setup details are on the PointBase JDBC driver page.