Page Contents


Installation of the TopBraid Live Server

The TopBraid Live Enterprise (TBL) Server is designed using Java servlet technology and deployed using a Web Application Server, also known as a Servlet Container, such as Apache Tomcat or Oracle WebLogic. Installation consists of deploying the WAR (Web Application Archive) file in the application server.

The WAR file is obtained by contacting TopQuadrant sales to receive the login/password for downloading the Enterprise Vocabulary Net install files. The install files consist of the WAR file for TopBraid Live (tbl.war) and the TBL Installation Guide (this document).

The installation of TopBraid Live (TBL) is slightly different depending on both the operating system and Web Application Server. Detailed instructions for Tomcat Installation InstructionsInstallation Instructions for Linux  and Installation Instructions for Windows Server  are provided in the sections below. In general, installation consists of:

  1. Deploy the TopBraid Live tbl.war file to the Tomcat server by either using Tomcat Manager or manually copying it to Tomcat's webapps directory.

  2. (Optional) Setting the location of the TBL workspace. By default, the workspace is set to /var/lib/ontologies. Upon deployment of the (TBL) application, library files will be written to this folder, including TopBraid (system library for TopBraid Suite features), server.topbraidlive.org (TBL server files for sessions, etc.), and other TopBraid Suite features. This folder will also contain all projects uploaded to the server. See Methods to Deploy Projects to Server .

    The location of the workspace can be changed by editing the init-param element in $APP_HOME/webapps/tbl/tbl/WEB-INF/web.xml, where $APP_HOME is the home directory of the application server.

    If permissions for the user running the application server are insufficient to write to the /var/lib/ontologies folder, full deployment of TopBraid Live will not succeed. Edit the web.xml to a folder with write permissions and re-start the application server.

  3. (Optional) Setting authentication and role-based access control through Tomcat or a LDAP server. These are explained in more detail throughout this document.

Additional Integration