Configure the "Manage" Tenant - Fluid Topics - 3.9 - Reference Guides

Fluid Topics Installation Guide

Product
Fluid Topics
FT_Version
3.9
Platform
RHEL
Category
Reference Guides
language
English
audience
public

In a multi-portal environment, the conf.json file of "Manage" tenants must contain specific information to define the KHUB to manage and thus enable content management.

The khub parameter is added to define the fact that the portal manages a remote KHUB and the remote KHUB tenant.

Example

The following example shows the conf.json configuration file for the OleanDor "Manage" portal:

{
"ui": {
"languages": ["en-US"],
"supportMail": "support@oleandor.net"
},
"khub": {
"mode": "MANAGE",
"boProjectName": "OleanDor Technical Documentation",
"target": {
"id": 4,
"status": "stable"
},
"pafs": {
"connector": [
"Authorit",
"Dita",
"MapAttachments",
"UnstructuredDocuments"
],
"atict": false,
"dita-ot": "DITA-OT-2.1",
"related_links": "all"
}
}
}

Where:

  • mode:
    • MANAGE is the value to enable the KHUB management from the portal.
  • boProjectName: allows "Manage" tenants to interact with the Back Office.
  • target is the service ID and status of the tenant of the remote KHUB to manage from the portal.
  • pafs: configures PaFs installation to allow content upload on "Manage" tenants.