The BMC Helix Innovation Suite product is now renamed to BMC Helix Platform. To view the latest documentation, see BMC Helix Platform.

If you have bookmarked these pages, you should update them with the new links.

Updating centralized tenant configuration settings

Centralized tenant configuration refers to storing the tenant's configuration data at a common location that can be accessed across multiple servers. The Centralized Tenant Configuration ensures consistency by communicating changes to the global properties across all the servers in a cluster. When a tenant-specific property is modified on one server, the Centralized Tenant Configuration automatically sends the notification to other servers that have the same tenant added, so that these configuration changes are also synchronized by each server in the same cluster.

The Centralized Tenant Configuration contains the configuration settings for the following components:

  • Approval
  • Assignment
  • Shared

To configure centralized tenant configuration settings

  1. Log in to BMC Helix Innovation Studio and navigate to the Administration tab. 
  2. Select Configure My Server > Centralized Configuration Settings > Centralized Tenant Configuration
  3. From Component Type, select the component for which you want to configure the setting.

    • To configure a new setting, click Add Setting.
    • To edit a setting, select the checkbox that corresponds to the setting you want to edit, and click Edit
  4. From the Setting Name list, select the setting to be configured.
  5. In the Setting Value, provide the appropriate value for the selected setting.
  6. Click Save

Centralized Tenant Configuration settings

The following table describes the centralized tenant configuration settings in BMC Helix Innovation Studio and provides example values for each setting:


  • If you cannot view all the columns, click Full screen in the upper-right corner of the page or press F to open the page in full screen mode. Alternatively, use the scroll bar at the bottom of the table. Press Esc to exit full screen mode.
  • To easily search for a specific parameter in the table, select the parameter from the Setting Name list. Alternatively, type the name of the parameter in the Setting Name text box.
    For example, to search for the Full-Text-Case-Option parameter, select it from the Setting Name list, or type the parameter name in the Setting Name text box.

Start adding filters for your table either in the macro settings or on the filtration pane.

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...

Setting NameDescriptionValues


Defines the maximum combined size limit for all attachments in an outgoing email.Example: 5000000 bytes


Defines the maximum number of attachments that can be added to an outgoing email.Example: 5

Indicates whether full-text searching is case sensitive. This setting affects all the FTS-enabled fields. Changes to this setting trigger an automatic re-indexing.

0—Case sensitive (Default)

1—not case sensitive


Provides the location of the directory where the FTS index files are stored.

Default location: <install directory>/arsystem/tenant/<tenant name> /ftsconfiguration/collection


Provides the location of the directory where the FTS configuration files are stored.

Example, configuration files for the words-to-ignore and synonyms list.

Default location: <install directory>/arsystem/tenant/<tenant name> /ftsconfiguration/conf


Indicates whether the FTS server processes pending indexing tasks.

F— Do not disable indexing (Default).

T—Disable indexing. Pending indexing tasks are processed after indexing is enabled.


Indicates whether the BMC Helix Innovation Suite server uses the full-text search engine. 

F— Use the full-text search engine (Default).

T—Disable the full-text search engine. 

Note: The database search capability continues to work even after the full-text search engine is disabled.

Full-Text-Exclude-ListContains the extensions of files that must be excluded from full-text search.

Example: .pdf, .xml, .png, and so on.

Full-Text-Ignore-Word-ListContains words to be ignored during FTS. Search results will not contain the words that are added in this list.

Articles (a, an, the), prepositions (in, on, from, front, beside), and so on.

Press Enter to add a new word in this list. 

Full-Text-Indexer-Log-FileGives the location of the directory where the FTS index log files are stored.Default location: <install directory>/arsystem/tenant/<tenant name>/db
Full-Text-ReindexInitiates the re-indexing of all FTS-enabled fields.

0Re-indexing is not performed (Default).

1Starts re-indexing.


Indicates how the FTS server modifies search queries.

0—Force leading and trailing wildcards.

1—Ignore leading and force trailing wildcards.

2—Ignore leading wildcards.

3—Remove leading and trailing wildcards.

4—Leave query unchanged (Default).


Contains synonyms so that when the end user searches for any of these words, resources related to its synonyms also appear in the search results. 

PC workstation laptop desktop computer

slow sluggish

bright shiny

Type a word followed by its synonyms separated by a space. Press Enter to add a new list of synonyms.


Defines the relevancy weight for the Environment Field. This setting relates to the fields for which the application business analyst has defined the relevancy when Enabling full-text search in an application.

Default value: 1

MFS-Keywords-Field-WeightDefines the relevancy weight for the Keyword Field. This setting relates to the fields for which the application business analyst has defined the relevancy when Enabling full-text search in an application.

Default value: 2

MFS-Title-Field-WeightDefines the relevancy weight for the Title Field. This setting relates to the fields for which the application business analyst has defined the relevancy when Enabling full-text search in an application.

Default value: 4


Specifies whether the password policy must be enforced.

BMC Helix Innovation Suite ensures that passwords are always encrypted. To ensure that the passwords are validated and encrypted, a password policy is enforced and forces the users to set a password that cannot be blank. For information about the password policy, see Enforcing a password policy.

T: Enforces the password policy, and you must create users and define the password according to the guidelines defined in the password policy. By default, the value is set to T.

F: Does not enforce the password policy, and you can create users without a password.

Was this page helpful? Yes No Submitting... Thank you