Configure Titan - Configure Titan - Perceptive Content - Titan - Perceptive-Content/Titan/Foundation-26.1/Titan-Installation-and-Setup-Guide/Configure-Titan - Foundation 26.1

Configure the app.config.json Configuration File

To configure the app.config.json configuration file, complete the following steps.

Navigate to the assets directory and open the app.config.json configuration file in a text editor.
Note: The default location for the configuration file is [drive:]\ Program Files\Apache Software Foundation\Tomcat 9.0\webapps\titan\assets\.
In the authConfig section, configure the following settings,where <app-host> specifies the application host you configured in the installation steps.
1. Update issuer with the URL for your identity provider’s issuer endpoint. Issuer refers to the identifier of the entity that issues security tokens. For example: https://server/oauth2/default/.well-known/openid-configuration. Typically, you can find the issuer by reviewing the discovery endpoint of your identity provider.
2. Update clientId to match the expected client ID defined by your identity provider. This value will be set by the identity provider and is required for Titan to leverage the identity provider for authentication.
3. Update scope to include the scopes that supply the username used for authentication.
```
  "authConfig": { 
  "issuer": "https://<idp-host>/identityprovider", 
  "clientId": "titan-app", 
  "scope": "openid profile profile.onbase", 
  "redirectUri": "https://<app-host>/view/authentication-confirmation", 
  "postLogoutRedirectUri": "https://titan/home", 
  "requireHttps": true 
  "strictDiscoveryDocumentValidation": false
},
```
In the appSettings section, update url and bearerLoginProfileName to specify the host location for Integration Server and the bearer token login profile name.
```
   "integrationServer": { 
  "url": "https://<is-host>/integrationserver", 
  "applicationId": "titan", "bearerLoginProfileName": "" 
},
```
Note: bearerLoginProfileName must match one of the values listed in the sso.bearer.profiles setting in the integrationserver.ini and inserver.ini configuration files.
Save the app.config.json configuration file and close the text editor.
Restart Tomcat.

Configure the inserver.ini File

To configure the inserver.ini configuration file, complete the following steps.

Navigate to the inserver\etc folder.
Open the inserver.ini configuration file in a text editor.
In the [Bearer Token Login Profiles] section, verify sso.bearer.profiles includes a value that matches the bearerLoginProfileName value you set in the app.config.json configuration file.
Save the inserver.ini configuration file and close the text editor.

Configure the integrationserver.ini File

To configure the integrationserver.ini configuration file, complete the following steps.

Navigate to the [path]/${TOMCAT_HOME}/webapps/integrationserver/WEB-INF folder.
Open the integrationserver.ini configuration file in a text editor.
In the [Forms] section, set forms.allowed.origins to the appropriate application origin URL.
In the [Bearer Token Login Profiles] section, verify sso.bearer.profiles includes a value that matches the bearerLoginProfileName value you set in the app.config.json configuration file.
Save the integrationserver.ini configuration file and close the text editor.

Configure Barcode Processing

During the capture process, indexing values can be read from barcodes. To assign indexing values from barcodes, complete the following steps.

In Management Console, in the External User Application Plan, click Modify Row or double-click the appropriate key. The system opens the <Key> Attributes dialog box.
Under General, from the Source list, select Barcode.
In the Value or Drawer field, enter a JavaScript regular expression pattern to locate a barcode match.
Note: The pattern should be enclosed with slashes, followed by an optional case insensitive flag, i. The first barcode on the page that matches is assigned to the key. The first regular expression capturing group is used to populate the key value. The capturing group allows sub-patterns of the barcode value to be used or can surround the pattern to use the entire barcode value.
Optional. Under Advanced, select any advanced option available for the Barcode source type.
Click OK.

Regular Expression Examples

The following table displays a list of regular expression examples.

Pattern	Barcode	Value
/^MRN(.+)$/	MRN123456	123456
/^(0+[1-9]+)/	001234 00005678 102346	001234 00005678 No match. Must start with one or more leading zeros.
/^DT(.+)$/i	DTABC dtIgnoreCase	ABC IgnoreCase
/^([A-Z0-9]{5})$/	A1234 12345 12p34 A12345	A1234 12345 No match. All letters must be uppercase. No match. Must be exactly 5 uppercase letters or numbers
/^(?:DT\|DocType)(.+)$/	DTHR DocType1099	HR 1099

For more information on developing and testing regular expressions, see the websites, https://regexr.com/ or https://regex101.com/. Ensure that the site is using ECMAScript or JavaScript for the regular expressions.

Configure Batch Header

The Batch Header Configuration feature in Titan enables users to customize and control the information displayed in the header section when viewing capture and indexing batches. This functionality provides flexibility in defining the layout, content, and appearance of batch headers to improve Capture and Indexing flow. To configure batch header, complete the following steps.

Navigate to Tomcat installation directory.
Open the app.config.json configuration file from the {titan_install_dir}/webapps/titan/asset folder.

Add batch header configuration under

"batchHeader": 
  { "batchNameLabel": "Batch ID", 
        "columnsPerRow": 6, 
        "propertyFields": 
        [ 
          { 
            "id": "batchContent", 
            "label": "Content" 
          }, 
          { 
            "customPropertyName": "Origin", 
            "label": "Origin CP", 
            "isEditable": true 
          } 
        ] 
   }