Deployment and Export

Base URI Management

Displays all projects and all registered graphs in the TopBraid workspace. Each graph will have a base URI (the graph name) and the file name in the project’s workspace. If there is more than one file with the same graph name (base URI) a Warning icon will be displayed. Information icons indicate projects and graphs that import missing ontologies not registered in the workspace. These warnings normally need to be resolved.

Upload Project

This menu choice lets you add a project developed elsewhere (for example, a local copy of TopBraid Composer Maestro Edition) to run on this server. The Project Upload page gives you a field to identify the zip file of the project you’re uploading. To create the zip file, zip up the project folder within the development machine’s workspace, including the .project file created by Eclipse.

After uploading a project that contains any collection data, refresh the text indices to enable search.

Delete Project

This menu choice lets you delete projects from the server. Selecting it lists projects on your server, with Show buttons for each and Delete buttons for projects that are not part of the default installation of your server.

The Show button lists User Applications and User Sessions for that project, and Delete deletes the project.

Send Project to Another Server

This sends an EDG project, or its selected contents, from the current server to another EDG server. From the listed projects, an administrator can either send an entire project or its selected contents, such as an asset collection’s graph-pair (data and teamwork, .tch).

If the source is using a relational database (RDBMS), then the receiving server must have a compatible RDBMS configured, presumably to an independent location (optionally in the same database server). If the Also send database triples option is selected, the transfer will also copy the triples from the source data to the destination data. If it is not selected, the database connection files will be transferred but without the triples. This could cause the asset collection(s) to be empty, in which case they might not appear in the users’ listing of the corresponding asset collection type(s) (although an administrator could verify their presence via Base URI Management page). Keep in mind that the database type of the source files will remain the same and not be converted, regardless of the destination servers’ configured database.

If the Send UI configurations (etc.) option is selected, then it will send the UI configurations file from server.topbraid.org/dynamic/uiconfig; otherwise, the default uiconfig file will be used at that location.

Create TriG file of all EDG production graphs

Clicking this link will download a TriG file of the collections, not including working copies, in this EDG workspace. This file will be very large and include triples from EDG system graphs. The main purpose of this feature is to replicate an EDG workspace for testing/debugging. History (tch) and metadata such as permissions will not be retained.

Import TriG File

This page lets you create multiple asset collections at once by uploading a TriG file with multiple asset collections. This functions the same as the +New button in the header of EDG.

Refresh Workspace

Refresh Workspace rereads the workspace directory and re-registers any scripts, functions, templates and views.

Refresh Workspace also resets various caches related to permissions, roles and schema definitions. This should not normally have a visible effect.

Backup/Restore

Starting in EDG version 6.4.2, a new feature has been added for Administrators of EDG to take backups of the collections in the workspace and restore from a backup if needed. Restores should be reserved for disaster recovery purposes. Please test it in a development environment to get familiar with the process.

Note

This is memory intensive. If your server is low on memory, the restore could fail. We recommend manually running garbage collection prior to a restore through the memory management page. This feature should not replace any existing backup strategy you have for your organization, only supplement and enhance it.

Important details prior to using this feature:

Backups can be downloaded to local machine of user or stored in AWS S3 bucket. They are also stored in Tomcatwebappsedgconfigrestore folder upon doing a restore. This is in case of rollback. If you are doing frequent restores, please clear this folder out periodically to save disk space.
Everything in the workspace will be backed up/restored besides EDG system files and configurations. During the restore process, if there are any TDB databases (including new collections you have created) in the system that do not exist in the backup you are restoring, they will be cleared. Any other files in custom projects will remain, regardless of if they were in the backup or not.
This feature is only available for TDB backed data, not RDBMS or Data Platform. Data Platform backup and restore will be coming soon.
Once a restore is in progress do not navigate away from the page or shutdown the server. It may take time to do the restore, so please let it finish. If you get an error then you may have to restart Tomcat.