Downloading & Registering FAQ
If you're having any problems with the Registration Form, here are some tips:
- Make sure you've checked the "I have read and agree to the Best Of BI forum terms and conditions" box near the bottom
- Make sure you've entered a value for "Province/State/Region" (this field reverts to blank every time the page refreshes)
If you're having trouble downloading Best Of BI Open Source Software, here are the more common reasons and solutions:
- Cookies not enabled
- For apps which require registration before download, your browser must have cookies enabled to recognize that you have registered.
- File HAS downloaded, but you haven't found it
- Have you checked your browser's default download location? Maybe it DID download after all!
- The file downloads, but won't open
- All Best Of BI downloads are tested before release, so if your download seems to be "corrupt", just try again.
- When all else fails...
If you're having any problems logging in and suspect you have forgotten your password:
- Go to the login page at https://bestofbi.com/page/login
- Click the 'Forgot your password?' link
- In the 'Email' field, enter the email address of your account
- Double check it: is that the correct email address?
- Click the 'Enter email & click here to reset password' button
- Check your email for a new password from Best Of BI
If you don't receive an email from Best Of BI...
- Check your 'Junk' or 'Spam' folder
- If you still don't have an email from Best Of BI, you have entered an incorrect/invalid email address somewhere in the process. Please create a new account with the correct email address.
If you wish to delete your Best Of BI member account for any reason, please email your request to email@example.com.
Installing SQL Power Software
All of our products include the SQL Power Database Connection Manager. This practical tool allows you to create, modify and delete connections that are shared between all of our products. Our products are compatible with any JDBC or ODBC-accessible database.
To create a new database connection:
- Open the file menu and select 'Database Connection Manager...'
- Click the Add... button, and then select 'Database connection...'
|In this field...
|Enter a unique name for the database connection.
|Select the database platform you want to connect to.
Note: This list contains the database types you previously defined. For more information, see the section called 'How do I set up database types'.
|Connect Options and JDBC URL
|Enter the connection options for the database driver. (Theses options are based on the database type you select.)
If you are using one of the fully-supported drivers, the connection option parameters are added into the JDBC URL field in the order that the Java driver expects to see them (this string is sometimes called a "db URL" in Java terminology). In the following example:
|Username and Password
|If necessary, enter the username and password to connect to the database.
3. Click OK. The new connection is added to the list of available connections.
You must define general settings for the database platforms you plan to work with (such as SQL Server, MySQL, Oracle, DB2, etc.). These settings will be used by our products when you set up a connection to a specific database server. The most common database types are predefined by default. If you plan to work with one of these database platforms, all you need to do is define the location of the JDBC driver. For more information, see How do I add JDBC drivers.
Keep in mind that at this point you are configuring general settings only and are not connecting to a specific database. For more information on connecting to a database, see How do I connect to my database.
To add a new database type:
- Go to the Database Connection Manager, which is embedded in all of our products.
- Click the 'JDBC Drivers...' button
- Click '+' below the list of database types.
- Enter the following information on the General tab:
|In this field...
|...enter the following information.
|Name for the database type (for example, PostgreSQL or SQL Server).
|Java class name of the driver. This is the driver class within the JDBC driver JAR file that will be used for database connections.
|Connection String Template
|General format of the JDBC URL for the database platform.
Important: You are not creating a connection for a specific database - you are entering a generic connection string that applies to the database platform. Later on, when you set up a connection to a specific database, the Database Connection Manager will use this template to create the URL to connect to the database. The connection string template must conform to a specific pattern that includes literals and variables.
Each variable you define is shown below the Connection String Template field. This provides you with a preview of the values you will be able to modify when creating a database connection.
For example, the connection string template to connect to a Microsoft SQL Server database might look like this:
When you create a connection to a specific SQL Server database, the Database Connection Manager will use this template to create the connection URL. In this example, the template will create the URL 'jdbc:sqlserver://:1433', where 1433 is the default port value. Since SQL Server databases listen to port 1433 by default, it makes sense to include this value in the template. When you're creating the actual database connection, you can change the port value if the database you're connecting to is configured differently.
- Next, you must define the location of the JDBC driver for the database type. For more information, see How do I add JDBC drivers.
- Click OK.
Whether you are adding a new database platform to one of our products or want to use one of the pre-configured platforms, the last step in setting up a database type is to locate the JAR file (or files) that contain the JDBC drivers for the database platform. Remember, at this point you are just telling our products where the drivers are. You must set up a database connection in order to connect to a specific database server (for more information, see How do I connect to my database).
Unlike most applications, which need a distinct driver program to communicate with each type of database, our products use Java-based drivers. These drivers normally come from the database vendor in the form of JAR (Java Archive) files. JAR files are an extension to the file format used by PKZip/WinZip archives.
Most database platforms provide drivers that are fully backward compatible. This means that it is best to use the newest driver available, regardless of the software version on the specific database server you intend to connect to. One exception to this is the Oracle database. It is important to match the major version number of your JDBC driver with the major version number of the Oracle database server you connect to. For example, if you are connecting to an Oracle 10g database, use the latest Oracle 10g driver. If you are connecting to an Oracle 9i database, use the Oracle 9i driver.
Note for Oracle 11 users:
Although Oracle 11 is not officially supported yet, you can still connect to Oracle 11 databases using the Oracle 10 driver.
To define the JDBC driver for a database type:
- If you do not have the JDBC driver for a specific database platform, you can usually obtain one from the database vendor. (For example, you can find Oracle JDBC Drivers on the Oracle site.) If that fails, you can find a directory of databases drivers on Sun's website. There is also a permanent thread in the SQL Power Architect user support forum, where you can share information with other Best Of BI tool users about finding and configuring drivers for a particular database platform.
- Decide on a permanent location to store your JDBC drivers. A good strategy is to create a JDBC folder under your Documents folder and collect all of you JDBC driver files there.
- Save the JDBC driver (it will usually be one or more JAR files) in the location you've chosen.
- Go to the Database Connection Manager, which is embeded in all of our products.
- Click on the 'JDBC Drivers...' button.
- On the 'JDBC Drivers' window, select a database type.
- Click 'Add JAR'.
- Locate the JAR file and click 'Open'. If there is a valid driver class in the JAR file, a file tree will appear showing the JDBC driver classes within the JAR file.
- Select the driver you want to use by selecting it from the list.
- Click OK.
Since SQL Power Software uses JDBC and MS Access uses ODBC, you will need to use a JDBC-ODBC bridge - such as the one included in your JDK.
For more information, refer to this article.
SQL Power Software doesn't support flat file access out of the box. However, since we use JDBC, you can access any file/database that you have a working JDBC driver for. So if you have the corresponding JDBC driver for your file/database type, all you need to do is install the JDBC driver.
Follow these steps to enable connecting to a SQL Server with your Windows domain credentials.
- Copy the file named 'sqljdbc_auth.dll' which comes with the Microsoft JDBC driver to the Windows system directory.
- Create a new database type and call it something like 'SQL Server Domain Security'.
- Use the following JDBC URL template:
- Notice the added 'integratedSecurity=true' part.
- Create a new database connection using the newly defined type.
Make sure you have Java installed on the computer.
This is related to a known bug. A simple fix is to change the server-startup.sh file permissions manually from the terminal:
chmod a+x server-startup.sh
Make sure you're using Sun JRE/JDK 6, not Gcj+classpath.
Using Best of BI Software
Best Of BI Developers communicate with the developer community using Google Groups. You can contact us at the following Google Groups for each project:
SQL Power Architect Developers:
SQL Power DQguru Developers:
SQL Power Wabit Developers:
You can use Java's built in proxy support. To do this, you have to set a few system properties:
How you accomplish this depends on which operating system you're using (Windows, OS X, or some form of Unix).
Please note: for clarity, the following examples refer to SQL Power Wabit, but the instructions will work for all of our apps. If you are not using SQL Power Wabit, just substitute the name of the app you're using.
On Windows, you can provide additional command-line parameters in a file called appname.l4j.ini. To do so, follow these steps:
- In Windows Explorer, locate the application's .exe file (for example, C:Program FilesWabitwabit.exe)
- In the application's folder, create a new text file called wabit.l4j.ini. An easy way to accomplish this is to right-click on the folder window's background, the select New > Text Document from the popup menu.
Note: if you are using SQL Power Architect, call the file architect.l4j.ini; for DQguru, call the file dqguru.l4j.ini
- Open the newly-created file in Notepad
- Paste the following contents into the file, and edit the settings as necessary for your environment:
# SQL Power Wabit runtime configuration
- Save the file, then relaunch Wabit.
Mac OS X
On Mac, you will need to edit the application's info.plist file. To do so, follow these steps:
- In the Finder, locate the application's icon
(for example, /Applications/SQL Power Wabit.app.)
- While holding down the Ctrl key, click the application's icon.
- Select "Show Package Contents" from the popup menu. A new finder window will appear.
- In the new finder window, open the Contents folder.
- Open the Info.plist file in TextEdit. (Once TextEdit is running, you can do this by dragging the Info.plist file onto the TextEdit icon in the dock.)
- Locate the following lines near the bottom of the file:
- Change them to:
- Save the file and re-launch the application.
Linux and other Unix-like Platforms
If you are using the Unix distribution, simply include the appropriate command-line parameters when launching the application. For example:
prompt% java -Xmx600m -Dhttp.proxyHost=myproxyserver.com -Dhttp.proxyPort=80 -jar wabit.jar
Note that as of SQL Power Wabit version 1.3.4, Parameters are still experimental and only recommended for advanced users.
There are two places where you can use parameters: in a report, and in a where clause on a query.
- Report Parameters
To create a report parameter:
- Click on the + button in the lower right parameters panel.
- You can create a date picker, a text field or a drop down list.
- Query Parameters
Once you have parameters defined in a report, you can also use them in a query.
- On a report, once a table is in the play pen, select the where field beside a column, then hold "ctrl" and press the space bar. This brings up a Parameters window which allows you to select a field out of the project as a parameter.
- Select the variable using the "..." box in the top right. The box will display a menu of all objects in the tree. Hovering over one will display all possible parameters in that object that can be used as a variable, including titles of objects and Java preferences for Wabit.
- Once a variable is selected, you can define a default value.
- Note that once you press "Insert" to add the variable, you can't return to the editor for the parameter. (To change the parameter at this point, you would have to delete all of the inserts and make a new parameter.)
Developing with SQL Power Software
The source code for all of our open source projects are hosted on Google Code. You will need to use Subversion to access the source code repositories.
Instructions for how to checkout the source code are available at each of the project's Google Code page:
SQL Power Architect:
SQL Power DQguru:
SQL Power Wabit:
But before you try to compile it, make sure you read the FAQ below.
All Best Of BI Community Edition projects include valid Eclipse project configurations and Apache Ant build.xml scripts. After checking out the code for the first time, Eclipse will complain about some missing Java source files. These sources need to be generated by the Ant build using apt, the Annotation Processing Tool. Executing the default Ant target and then refreshing the Eclipse workspace should be enough to get the whole project to compile without any errors.
Note: All our products now compile and run on Java 6 or newer. If you had been developing in any of our code bases prior to July 2010, you would have been compiling against Java 5.
Yes: please refer to http://code.google.com/p/power-architect/wiki/JavaFormattingConventions for details.
If you submit patches that don't more-or-less adhere to these conventions, we will ask you to reformat and send in a new patch.
Other Frequently Asked Questions
Here's how Community/Enterprise projects are handled in SQL Power Architect and SQL Power Wabit:
- Architect/Wabit Projects created in the Community Edition can be migrated to Enterprise Edition.
- Architect/Wabit Projects created/saved in Enterprise Edition are stored in the Enterprise server database and cannot be accessed by the Community Edition.
- When an Architect/Wabit Enterprise license (or free trial period) expires, the Enterprise server database and any projects therein are "locked out" (they are still there, but not accessible) until a license is obtained/renewed.
For SQL Power DQguru, all Projects can be created by/accessed by either Community or Enterprise version.
Best Of BI Software user limit restrictions are based on the number of named users, not the number of concurrent users. In other words, if you purchase a 10-user SQL Power Wabit subscription, that means you can define up to 10 named Wabit users, each with unique privileges, settings, etc.
Also note that in regards to SQL Power Wabit thin-client web access, the user limit does not restrict people from viewing Wabit Reports that are published to public domains. The user limit would apply only to the report editors (i.e. those using Wabit application to edit the reports) and not the report viewers (i.e. those using their web browser to access publicly published Wabit Reports).
Community Edition refers to the standalone app you can download for free; Client Edition refers to the client component that interacts with the server component of the Enterprise Edition.
Prior to June 2010, our Open Source free downloads were known as "Client" Editions. But with the introduction of our Enterprise Server components, the term "Client" is now reserved for the Client component of the Enterprise Server offering. Therefore as of June 2010, the Open Source free downloads are now more aptly named "Community" editions.
Also note that as of July 27 2010, Premium Support is no longer offered for Community Edition software. Going forward, Premium Support is only included with Enterprise subscriptions.
Best Of BI Open Source Software is licensed under GPL version 3. In short, you are allowed to download, install and use our software on as many computers as you need, without having to pay any licensing fees.
As of July 2012, Best Of BI Software is no longer offering new subscriptions for Enterprise versions of SQL Power DQguru or SQL Power Wabit. SQL Power Architect Enterprise is also no longer available. Current subscriptions are still being maintained and support is still available for current subscribers. Open Source Community Editions are still available for free download.
As of September 2012, SQL Power Software is no longer offering an online version of the User Guides.
While the SQL Power Wiki is no longer available, please note that the content of the Wiki is identical to the User Guide content - so if you have purchased a User Guide, please refer to your User Guide PDF instead of the online Wiki for Best Of BI Software documentation.