Skip to main content



This installation guide is aimed at developers wishing to contribute to the engine, and thus contains more complex setup instructions. For developers simply wishing to use the DWCJ, select one of the other installation methods.


This walkthrough will cover installation on a Windows system - installation steps may vary for Mac/Linux OS devices.

Installation will be broken down into the following steps:

  1. Java and Maven download and configuration
  2. BBj download and installation
  3. Downloading DWCJ files and building the .jar file
  4. Configuring the application in the Enterprise Manager

1) Java and Maven Download and Configuration

In order to use the DWCJ, you must first have Java and Maven installed and properly configured. If you already have Java and Maven downloaded, please skip to Step 2. If you also have BBj installed on your system, please skip to Step 3.


Java OpenJDK17 can be found by following this link. It is recommended to allow the installation to handle setting the JAVA_HOME variable during installation, where applicable.


Maven should also be downloaded, and can be found at this link. It is recommended to configure your system environment variables with Maven - a guide for installation and configuration for Windows users can be found here.

2) BBj Download and Installation


While following this step, be sure to install BBj version 22.14 or newer

This video can help with the installation of BBj if you need assistance with setup. The installation section of the BASIS website can be found at this link


It is recommended to use the latest stable revision build of BBj, and to select "BBj" from the list of options, without "Barista" or "Addon".

Once BBj has been installed, it is also necessary to install the needed dependencies from the BBj library. This is done by navigating to the lib directory inside your bbx folder, and running the following commands:

mvn install:install-file "-Dfile=BBjStartup.jar" "-DgroupId=com.basis.lib" "-DartifactId=BBjStartup" "-Dversion=23.06-SNAPSHOT" "-Dpackaging=jar"
mvn install:install-file "-Dfile=BBj.jar" "-DgroupId=com.basis.lib" "-DartifactId=BBj" "-Dversion=23.06-SNAPSHOT" "-Dpackaging=jar"
mvn install:install-file "-Dfile=BBjUtil.jar" "-DgroupId=com.basis.lib" "-DartifactId=BBjUtil" "-Dversion=23.06-SNAPSHOT" "-Dpackaging=jar"
mvn install:install-file "-Dfile=BBjsp.jar" "-DgroupId=com.basis.lib" "-DartifactId=BBjsp" "-Dversion=23.06-SNAPSHOT" "-Dpackaging=jar"

After running these commands, make sure to perform an "install" using Maven in the engine directory.

3) Download/Clone and Package DWCJ

The following steps will explain downloading (or cloning) the files for the DWCJ from GitHub. We’ll assume that you already have Git and a command line tool, such as Git Bash installed. If not, please follow this link to set this up.

This tutorial will use Microsoft’s VS Code as the development IDE. Other IDEs may be used, and may come with other features or functionality. VS Code can be downloaded free of charge from this link.

Clone DWCJ Github Repo

Navigate to this link, which should take you to the engine section of the DWCJ on GitHub. Clone this folder onto your computer - this can be done using the command line and Git, or another Git tool.

To start, click on the green "Code" button and copy the address to your clipboard:

Cloning the repository

Once this has been done, navigate to a space on your computer where you'd like to clone the code to. This can be done in explorer, or using a command line tool such as GitBash.

GitBash directory

Clone the code into your chosen folder.

Cloning the repository

You should now have a folder named "engine" in the location you chose to clone the code to. This is where you'll find the files needed to add to the classpath later on in the tutorial, so make sure you take note of this location for future use.

Compile and Package Code

Now the code from GitHub must be compiled and packaged. To start this process, navigate to the "engine" folder that was just cloned from GitHub.

Opening a folder

Selecting a folder

Once the folder has been opened, you should see the various files and folders open in the panel on the left of your screen. First, navigate to the pom.xml file and open this in your editor.

pom.xml window

Notice the various profiles listed in this file, which specify default directories based on your operating system and BBj installation configuration. It may be necessary to change the default profile depending on which system and BBj naming convention you are operating with. Alternatively, you can change the profile you use by passing it to the maven command with the -P flag, such as “-P winbbjlib”.

POM items window

Now Maven will be used to package the engine and create a .jar file. Begin the process by running “mvn clean” in the engine directory - this can be done from any CLI, but this tutorial will use a VS Code bash terminal.

Maven clean command

If this runs properly, you should see “BUILD SUCCESS” in VS Code’s output console:

Maven clean output

Finally, we’ll package the code into a .jar file we can use. We’ll do this by running “mvn package” from the command line in the engine directory. If this runs correctly, a final “BUILD SUCCESS” message should display:

Maven compile command and output

After completing these steps, you should have a .jar file that you can use in the BASIS enterprise manager. The version of the .jar file will differ as releases are pushed to Github. This file should be found in “engine>target>lib”, as shown below:

Final packaged JAR

4) Configuration in the Enterprise Manager

The BBj Enterprise Manager will now be utilized to ensure we can run the DWCJ. First, we’ll add the necessary .jar file a custom classpath, and then create a web application from which we will launch an instance of a DWCJ app.

Login to the Enterprise Manager

To start, ensure that your BBjServices client is running. On Windows, we'll check this by seeing if it's listed in the processes tab at the bottom of our toolbar.

BBjServices location on the toolbar

NOTE: If this service isn’t running, you can restart BBj by restarting the application. On Windows, we’ll hit the Windows key, type “Admin” and select the program from the start menu:

Restarting Barista from the Windows start menu

Select “Start/Stop the BBjServices”

Stop/Start BBj services

Then select “Restart BBjServices”

Stop/Start BBj services

After ensuring that Barista is running, open the Enterprise Manager by navigating to http://localhost:8888/bbjem/emapp in a browser window. This will take you to a login screen, where the username is admin and the password is admin123.

Restarting Barista from the Windows start menu

Configuring Java Settings

After opening the Enterprise Manager, navigate to the Java Settings tab. To do so, double click on BBjServices on the lefthand toolbar, and then double click Java Settings.

Java settings sidebar option

On reaching the Java Settings tab, add a new custom classpath. This can be done by using the Classpath tab at the botton of the screen.

Classpath tab option

To add a new custom classpath, use the green "+" button near the middle of your Enterprise Manger window. Name your classpath something like "DWCJ".

Note that two classpaths need to be added: BBj's default classpath as well as the .jar file that was packaged in this step.

Adding a new classpath

The first classpath to add is BBj's default classpath. This can be done by selecting Existing Classpath, which will populate a list of the various classpaths already configured in the Enterprise Manager. Select bbj_default and press Add.

Selecting bbj_default

Select the same green "+" button on the right side of the acreen again. This time select "Jar File(s)". Navigate to the location you cloned the DWCJ code into. The folder will be called "engine". From there, select the "target" folder, and from there the "lib" folder. Inside this folder, you should see the "dwcj-X.XXX.jar" file, with the X's replaced by numeric values. The path may look similar to "C:\engine\target\lib". Select the .jar file and then click the "Open" button.

Opening the DWCJ .jar file

Once this is done, save your work by clikcing the save button near the top left of the Enterprise Manager window.

Saving new custom classpath

Create our DWCJ Application

The DWCJ application needs to be added into the Enterprise Manager. To do this, start by navigating to the Applications option on the left sidebar. Do this by double clicking the "Web" option, then double click "App Deployment", and finally "Applications".

Selecting the Application option

This should display a list of applications. Create a new application using the "+" button in the panel.

Adding a new application

Give your application a name - "dwcj" will be used for this example. The program file will be dwcj.bbj - don't worry if you're unfamiliar with the .bbj extension. The working directory will be the location where the files from GitHub were cloned, inside of the "\bbj" folder. The pathname may look something like "C:\engine\bbj\". Select the dwcj classpath that was created in the classpath section in the Classpath field. Finally, check the "DWC Web App Enabled" box.

Application configuration options

To complete the configuration needed in the Enterprise Manager, save your application using the save button towards the top left of your window.

Save your work in the application screen

After saving, click on the "Launch in Browser" button at the top right of the Enterprise Manager window.

Launch your application button

This will launch your application in a new, discrete browser window. You may want to copy the URL from this window and paste it into a browser. If you've successfully followed this guide, you should see the following welcome screen, unless additional configuration steps have been taken in the DWCJ code.

Launch your application button

Congratulations! You’ve successfully installed and launched the DWCJ. From here, you can explore the sample applications that are provided.

Continue to the next section to learn how to create your first application, and how to configure the DWCJ with various debug and default class options.