Manage Bannerbear Data in DBArtisan as a JDBC Source
The CData JDBC Driver for Bannerbear seamlessly integrates Bannerbear data into database management tools like DBArtisan by enabling you to access Bannerbear data as a database. This article shows how to create a JDBC source for Bannerbear in DBArtisan. You can then edit data visually and execute standard SQL.
Integrate Bannerbear Data into DBArtisan Projects
Follow the steps below to register Bannerbear data as a database instance in your project:
- In DBArtisan, click Data Source -> Register Datasource.
- Select Generic JDBC.
- Click Manage.
- In the resulting dialog, click New. Enter a name for the driver and click Add. In the resulting dialog, navigate to the driver JAR. The driver JAR is located in the lib subfolder of the installation directory.
-
In the Connection URL box, enter credentials and other required connection properties in the JDBC URL.
Start by setting the Profile connection property to the location of the Bannerbear Profile on disk (e.g. C:\profiles\Bannerbear.apip). Next, set the ProfileSettings connection property to the connection string for Bannerbear (see below).
Bannerbear API Profile Settings
Retrieve your API keys from the Bannerbear dashboard. Specify the key type (Project or Master) via the KeyType property.
Built-in Connection String Designer
For assistance in constructing the JDBC URL, use the connection string designer built into the Bannerbear JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.
java -jar cdata.jdbc.api.jar
Fill in the connection properties and copy the connection string to the clipboard.
Below is a typical connection string:
jdbc:api:Profile=C:\profiles\Bannerbear.apip;ProfileSettings='APIKey=your_api_key';
- Finish the wizard to connect to Bannerbear data. Bannerbear entities are displayed in the Datasource Explorer.
You can now work with Bannerbear data as you work with any other database. See the driver help documentation for more information on the queries supported by the Bannerbear API.