Skip to main content
Blackboard Help


This tool updates the configuration according to the settings in the file.

Running this command restarts the services and redeploys all of the properties files. If any customizations have been made to the properties files, they will be lost.

The first operation replaces the existing template files and copies the original template files to a time-stamped sub-directory of blackboard_home/backups/templates/time_stamped. You can use these files to retrieve and re-apply any local customizations.

The second operation is Tomcat-specific and requires that Custom Authentication Types be disabled. The .jar files from apps/tomcat/server/lib/directories will be loaded instead of from blackboard_home/systemlib/. Be aware that any .jar file found in the directory will be loaded at Tomcat startup. This operation is controlled by the .classpath files located in config/tomcat/classpath. Any changes to the Tomcat configuration files or startup scripts must be made to the templates in config/tomcat/. In particular this applies to additional MIME types added to the web.xml file. Touch points are files such as web.xml, server.xml, startup scripts, and configuration files used in clustered Tomcat environments.

Tomcat Clustering is deprecated for Blackboard Learn 9.1 Service Pack 6, and has been removed from Blackboard Learn 9.1 Service Pack 8. For alternative solutions, see Optimizing Performance.

The third operation updates the BBLEARN.SYSTEM_REGISTRY (legacy: BB_BB60.SYSTEM_REGISTRY) database table with the configuration changes. The current performance parameters for the application server are recorded in the BBLEARN_ADMIN.CONFIG.REGISTRY (legacy: BBADMIN.CONFIG.REGISTRY) database table. It automatically pushes any changes to the database hostname and port, instance name, and externally visible Web server hostname to the database.

The final operation configures content management, which includes verifying the license, updating connection information, and then pushing the new information to the database. It then check the version of each database schema and updates if necessary.

Windows Example:


When using the PushConfigUpdates tool in Windows, it is very important to run the tool from the command line instead of double-clicking the file from Windows Explorer. The command line executes the tool in verbose mode, displaying important messages.

UNIX Example: