Skip to end of metadata
Go to start of metadata

Page Contents


Server Configuration

Administrators can update the section via its Edit button and ensuring to click Save Changes when finished. Note that any required passwords must be entered after saving changes. NOTE: Database updates require an EDG server restart.

Teamwork Platform Parameters

ParameterDefaultDescription
Repository projectRepositoriesSee the Application data storage section, below.
Comments activatedtrueAllows comments on data resources
Tasks activatedtrueAllows user tasks on data resources
Send task emailsfalseUsers with an email address receive email when a task is assigned to them
Metrics dashboards activatedfalseEDG only. This enables user viewing and administrator editing of metrics dashboards. For details, see Governance Model > Metrics Dashboards.
Application data storage<requires Admin choice>See the Application data storage section, below.
Default namespace suggestionhttp://example.org/{type}/new#This is the string used to pre-fill the Default namespace field for a new vocabulary/asset. The EDG default is http://example.org/{type}/new#, which an administrator can customize here. Note that the variable {type} produces the lowercase plural name of the vocabulary/asset type, e.g., "ontologies".
Teamwork Administrator Role 

This special teamwork role (cf. viewer, editor, and manager ) controls the ability to modify workflow types by downloading and uploading the Workflow Templates file.

Disable source code editingfalseSelecting true disables the source code editor in the full page editor.
Enable job titlesfalse

This allows the creation of job titles in the Organizational Structure under the Governance Model, and the ability to assign users to those job titles, instead of assigning them directly to the organization. If it's disabled the Party selection drop-down for governance role assignment shows Organizations instead of Job Titles (on Governance Areas page and Users tab).

NOTE: This feature is deprecated and is not recommended for new deployments; it might be removed in a future version.

Teamwork Platform Parameters: Application data storage

To create new asset collections, an EDG administrator must configure the Application data storage parameter for the collections' RDF graph data. The Repository project parameter should also be verified and updated if necessary.

If the Application data storage setting is ever incomplete (e.g., immediately after installation), EDG users will receive this notification:

To set the Repository project and Application data storage parameters, an administrator should open: EDG > ... > Server Administration > EDG Configuration Parameters > Server Configuration: Edit.

In the Teamwork Platform Parameters section, ensure that the Repository project setting is the name of EDG's own project (sub-)directory (default: Repositories) within the overall EDG workspace directory. NOTE: The Repository project name may not contain spaces. If the project does not exist, it will be created.

In the same Teamwork Platform Parameters section, the Application data storage parameter offers three types of persistence technology: (1) relational database, (2) Jena TDB files, or (3) MarkLogic's NoSQL database. This results in Application data storage having four options (with TDB having two choices):

App data storage typeDescription
In-memory + RDBMS persistenceChoice of relational DB: Oracle, Microsoft SQL Server, or MySQL, which requires further RDBMS Configuration, below.
TDB (One database per graph)Apache Jena TDB, configured for each graph to use its own TDB database
TDB (Shared graph database)Apache Jena TDB, configured for all graphs to share a single TDB database
In-memory + MarkLogic persistenceMarkLogic's NoSQL database, which requires further MarkLogic Configuration, below.

Because EDG's own system graphs also depend on the data storage type, changing the Application data storage should be considered as tantamount to a new installation, especially if the original installation used a non-TDB, remote data-store. Although existing graph data is not directly affected, changing the data storage type's remote store could entail the need to migrate data from the old source.

The TDB options require no additional setup or parameters. MarkLogic or RDBMS each have additional required configuration, as described below.

NOTE: After all Server Configuration sections have been completed, be sure to click Save Changes. Then supply any passwords as needed, clicking Save on each one.

MarkLogic or RDBMS Configuration Parameters (for Application data storage)

For the either of the MarkLogic or relational RDBMS parameters, the corresponding database must already exist before a user can use the web-based EDG interface to create a new vocabulary in that database. Changes to these settings require a restart of the EDG server. After restarting, the EDG Home page must be loaded to complete the installation, which occurs via the normal page-flow.

MarkLogic Configuration Parameters

Also see the Application data storage section, above.

ParameterDefaultDescription
MarkLogic URL 

ML database URL: marklogic://<host:port>/<databaseName> , e.g., marklogic://localhost:8000/mymldb, or marklogic://192.168.1.62:8000/tq

MarkLogic user name Login name for the database.
MarkLogic password This appears only if the other MarkLogic parameters are set, and it is set after Save Changes has completed.

NOTE: Changes to this section require a server restart.

RDBMS Configuration Parameters

Also see the Application data storage section, above.

ParameterDefaultDescription
RDBMS URL 

The URL of the relational database. For example, jdbc:oracle:thin:@localhost:1521:delphi, where delphi is the name of the instance, or jdbc:mysql://localhost:3306/myDatabase. The database with that name must already exist on the database server. (In the latter case, the myDatabase database must already exist on the MySQL system.)

Common formats for the RDBMS URL include:

jdbc:mysql://<server>/<database>
jdbc:oracle:thin:@//<server>:<port>/<service>
jdbc:oracle:thin:@<server>:<port>:<SID>
jdbc:sqlserver://<server>[:<port>][/database][;property=value]

NOTE for SQL Server: A single backslash "\" in the URL string may cause a problem in the secure storage file for the password. Alternatives are (1) to use double-backslashes "\\" or (2) store the password using Administration: Password Management or (3) replace the backslash "\" element by a keyword assignment, e.g., "...;instanceName=myInstance;..." instead of "...\myInstance;...".

RDBMS database type Select the supported type of relational database being used.
RDBMS user name Login name for the database.
RDBMS Update Batch Size1000OPTIONAL: This is the number of rows written to the SQL database in each batch. If unset, then 1000 is used. Adjusting it might improve bulk insert performance.
RDBMS Update Fetch Size 

OPTIONAL: The number of rows returned from the SQL database on each network round trip. Certain values have certain meaning to difference database types. Not all databases use this value.

NOTE: Leaving the Batch and Fetch sizes unset should generally yield acceptable loading/caching performance. Each can be fine-tuned for a particular application by adjusting it up or down and observing the performance changes.

RDBMS password This appears only if the other RDBMS parameters are set, and it is set after Save Changes has completed.

NOTE: Changes to this section require a server restart.

AutoClassifier Configuration Parameters

ParameterDefaultDescription
Maui Server URL The URL (with, if necessary, the port number and path) of the server running the Maui auto classifier, e.g., http://myserver.org:8080/mauiserver/
Maui Server user name Must be specified if Maui Server has been configured to require a user name and password (via the HTTP Basic Authentication protocol).

Maui password

 

This appears only if the other Maui parameters are set, and it is set after Save Changes has completed.

Data Platform Configuration Parameters

Note that changing Data Platform parameters requires a restart of the EDG server.

ParameterDefaultDescription
Enable Data Platform featurefalseWhen true, an EDG server restart will enable usage of the Data Platform server found at the given URL. See Data Platform documentation for details.
Data Platform server URLhttp://localhost:1066/The URL of the Data Platform server, which will will replicate data for selected asset collections between this and other connected EDG servers. See Data Platform documentation for details.

Explorer Parameters

ParameterDefaultDescription
Use legacy TopBraid Vocabulary Explorerfalse[Editor setting] Set to true on the Editor (source) server if and only if the Explorer server predates version 5.3.0.
Explorer users can view working copiesfalse[Explorer viewers setting] Set to true on the Explorer server if read-only users can also see the working copies of the published asset collections.
Explorer server 

[Editor] URL of an Explorer server that receives published versions of asset collections for read-only viewers.

NOTE: This must end with /tbl, e.g. http://myserver.org:8080/edg/tbl.

Explorer server user name [Editor] User name for authentication on the Explorer server (needs Administrator privileges)
Explorer server password This appears only if the other Explorer server parameters are set, and it is set after Save Changes has completed.
Editor server 

[ Explorer viewers ] URL of the EDG Editor (source) server, which can receive feedback from viewers of the published vocabularies.

NOTE: This must end with /swp, e.g. http://myserver.org:8080/edg/tbl/swp.

Editor server user name [ Explorer viewers] User name for authentication on the Editor (source) server ( Administrator privileges recommended)
Editor server password This appears only if the other Editor server parameters are set, and it is set after Save Changes has completed.

JIRA Integration Parameters

ParameterDefaultDescription
JIRA Server URL 

URL to access JIRA, e.g., https://mycompany.atlassian.net/ —NOTE: This URL must end with a slash "/"

JIRA User Name The JIRA login name to shared by all users (the password entry appears after the URL and username are set)
JIRA Password This appears only if the other JIRA parameters are set, and it is set after Save Changes has completed.

These JIRA settings enable the managers of each EDG asset collection to specify a JIRA project key, which in turn enables the asset collection's editors to launch from asset items in EDG to project items in JIRA. See any collection type's Manage > JIRA Project Key documentation for more information and related links. NOTE: If any of these settings—including the password—fail to match JIRA, then users might experience Server Interaction Errors, despite possibly seeing partial functionality.

EDG Asset Collection Singletons

Setup EDG Enumerations - Administrators can use this function to set values for built-in EDG properties to populate the selection boxes. 

Tagger Content Graphs

When licensed for EDG Tagger, this section lists all content graphs that can be used in the Tagger application. Content graphs contain resources that are tagged in EDG Tagger, i.e. the subjects of the subject-predicate-object tag triples. All RDF graphs in the workspace will appear here, except for those found in system projects, such as TopBraid, teamwork.topbraidlive.org, server.topbraidlive.org. When checked, the change is saved, and the graph will be available when creating new Content Tag Sets in the EDG Tagger application. Unlike the first section of this page, there is no Save button. For additional discussion of these settings, see the EDG Tagger User Guide: Configuring content and property graphs.

Tagger Properties Graphs

When licensed for EDG Tagger, this section lists potential graphs that can provide property types used for tags in Content Tag Sets, i.e. the predicates of the subject-predicate-object tag triples. When checked, the change is saved, and the graph will be available when creating new Content Tag Sets in the EDG Tagger application. Unlike the first section of this page, there is no Save button. For additional discussion of these settings, see the EDG Tagger User Guide: Configuring content and property graphs.

Configure Collections (Types)

For the asset collection types allowed by the installed TopBraid product license, these settings allow administrators to show or hide those types in the user interface. Administrators can also modify "default includes" for each asset collection type. Default includes are graphs that are automatically included when a new collection is created.

Default Notification Setup

These are the default notification settings that are used to initialize new collections. For each collection-related event, administrators can indicate default choices for the governance roles that should be notified of it. Each collection can override their initial default settings, and changes to these defaults do not affect existing collections. For information on associating governance roles with asset collections, see the Governance Model Overview. To manage a collection's notifications, see the Manage > Configure Notifications documentation of its collection type.

Governance Roles

A user who is assigned a governance role will have permissions on a collection in that subject area. This global setting determines whether the role can create workflows. Note that a user having one role disabled for workflow creation could still create a workflow if they also have another applicable enabled role (or a permission profile assignment).

For a general discussion of roles, see: Governance Areas > Governance roles.

Search the EDG Configuration

  • No labels