TopBraid Explorer and TopBraid Tagger and AutoClassifier

TopBraid Explorer and TopBraid Tagger and AutoClassifier are optional, separately licensed add-on modules for the EDG product. Each module entails some additional server installation. AutoClassifier has a Maui Indexer webapp, which can either run on the main EDG server or a separate server. Explorer has an EDG-like webapp for viewers, which should run on a separate (app-) server from the main EDG server where the source content is edited.

TopBraid Explorer Server

The Explorer server provides users with read-only access to versions of vocabularies or asset collections that have been published from a separate EDG Editor (source) server.

Please Note: There is no separate module or war file for the explorer server, you’ll use the same edg.war file for both your editor and explorer servers.


Explorer setup

The Explorer server is installed similarly to any EDG server (see EDG Server Installation), with the following differences.

1. Explorer installation prerequisites (differences)

  • Verify database compatibility between the Editor server and the Explorer server. Explorer server requires an independent, but compatible, database installation and RDBMS configuration.
  • Via either Tomcat or LDAP, assign all Explorer users to a single, read-only role and no other roles.

2. Explorer initial administration (differences)

3. Editor (source) EDG administration

For the reverse relationship, configure the Editor-source server’s Explorer server (URL), user name and password in: Server Administration > Setup – EDG Configuration Parameters > Explorer Parameters.

Publishing to Explorer

After both servers are installed and configured, authorized users can publish edited source asset collections to the Explorer server and manage viewable versions. For details, see an appropriate asset collection type (e.g., taxonomy, ontology, etc.): Export > Publish for Explorer Users.

Installing the Maui Indexer for Tagger AutoClassifier

The TopBraid Tagger AutoClassifier component requires the Maui Indexer server. Like the TopBraid EDG server, the Maui server is a Java WAR-file application deployed to a Tomcat webapp server. Thus, installation involves copying the maui.war file to the Tomcat webapps directory or using Tomcat Manager to deploy maui.war. It can be installed on the same server where you are running TopBraid EDG.

Once the Tomcat server is restarted, no further configuration of the Maui server is necessary, however, we do recommend explicitly defining the data directory where Maui Server keeps its data. See the  Maui server documentation  for details. Most users should probably define the data directory by setting the MAUI_SERVER_DATA_DIR environment variable.  If the data directory is not explicitly defined, then it will default to the current directory from where the Tomcat webapp server was started, which can be a somewhat   random and undesirable location.

You may also use the servlet container’s authentication features to protect the Maui Server web application with a username and password of your choice, using the HTTP Basic Authentication protocol.  In this case, the same credentials need to be specified in the AutoClassifier configuration in EDG.

Finally, an EDG administrator must configure EDG to point to Maui as described in Server Administration > Setup – EDG Configuration Parameters. For example, if you are running both EDG and Maui Server on the  server at port 8080, the Maui Server URL entered under the AutoClassifier Configuration Parameters section would be: .