Optional Setups

Below are some advanced optional configurations you can do for Digital Worker, such as key and salt, Neural Connect, and Home App configuration.

Advanced Configuration for Key and Salt

For Digital Worker setup, there is a provision to customize the source for salt and key used for encryption of the application credentials.

 

By default, Key-Salt combination for Digital Worker setup is retrieved from the database. This can be extended to a JSON file or Custom JS file API call. 

 

If you wish to change the default settings for Key and Salt, configure it immediately after installation of server-side components. The Key and Salt set up is used for application credential encryption for Digital Worker. Perform the configuration before you start the server-side components.

 

Caution:

 If you want to change the default values, make the required changes immediately after installation and before storing any credentials in the product. Once credentials are stored in the database, you cannot change the source key and salt configuration, including database entries, JSON files, custom JS files, or API calls.

 

NOTE:
  • Refer Customize Cryptography to know how to create the FILE/Custom JS API for Key-Salt combination.
  • If the chosen source is a JSON File or a Custom JS API, deleting or removing the JSON file/Custom JS file from the path post deployment may lead to server failure

 

Configuration of Digital Worker with Neural Connect
 

To use the copilot feature in the Admin module and Automation Studio, you must set up the Neural Connect URL in Digital Worker. For this, you need to update the <env->values.yaml.


To update the file:

  1. Open the <env->values.yaml file.
  2. Update the configs:/config.yml:/neuralconnect: as mentioned below to change the default values:
Name of Property Description
Tokenurl

Signifies the token URL used to connect the Neural Connect instance.
You can change the hostname and port number depending on which Neural Connect instance you want to connect. 
By default, it is set to

http(s)://<proxy_server_hostname>[:<port_number>]/<digital worker>/ auth/realms/xerealm/protocol/openid-connect/token
answerurlpart1 Signifies the service URL used to connect the Neural Connect instance.
You can change the hostname and port number depending on which Neural Connect instance you want to connect. 
By default, it is set to http(s)://<proxy_server_hostname>[:<port_number>]/<digital worker>/ neuralconnect/api/v1/expert
answerurlpart2

Signifies the service URL used to connect the Neural Connect instance.
By default, it is set to "/answer".

 

NOTE:

You are not allowed to change the default value of the answerurlpart2.
Clientid

Signifies the client ID used for authorizing the Neural Connect instance.
By default, it is set to "extraction".

 

NOTE:

You are not allowed to change the default value of the clientid.
Username  Signifies the username used to connect the Neural Connect instance.
Password Signifies the password used to connect to Neural Connect during the connection, if the HashiCorpVault is disabled. Otherwise, the password will be in plain text. For more information, see the Platform-Installation Guide.pdf.
Granttype

Signifies the type through which you can access the Neural Connect instance.
By default, it is set to "password".

 

NOTE:

You are not allowed to change the default value of the granttype.
Clientsecret Specifies the client secret ID used for authorizing the Neural Connect during the connection, if the HashiCorpVault is disabled. Otherwise, the client secret ID will be in plain text. For more information, see the Platform-Installation Guide.pdf.
Studioprojectid Specifies the ID used to connect to a specific Automation Studio project in the Neural Connect instance.
Adminprojectid Specifies the ID used to connect to a specific Admin module project in the Neural Connect instance.

 
    

The configuration of Digital Worker with Neural Connect is completed.

 

NOTE:

 If the <env->values.yaml file is updated after installing the DW, run the helm upgrade <release name ><repository name/chart_name>command to reflect the changes in the installed version.

 


Configuration of Digital Worker with HomeApp


To access the HomeApp, you must set up the home page URL in Digital Worker. For this, you need to update the <env->values.yaml.


To update the file:

  1. Open the <env->values.yaml file.
  2. Update the configs:/config.yml:/homeAppConfiguration: as mentioned below to change the default values:
Name of Property Description
baseurl

Signifies the base URL used to connect the HomeApp instance.
You can change the hostname and port number depending on which Homepp instance you want to connect.

 

NOTE:

 Update only the baseurl. The rest of the URL is automatically added by the code. For example: 
http://<baseurl>.com
platformId Signifies the platform ID used to connect the HomeApp instance.
partyId Signifies the party ID used to connect the HomeApp instance.
userId Signifies the user ID used for authorizing the HomeApp instance.
token Signifies the token used to connect the HomeApp instance.
appId Signifies the app ID used to connect the HomeApp instance.

  

 

NOTE:

 If the <env->values.yaml file is updated after installing the DW, run the helm upgrade <release name ><repository name/chart_name>command to reflect the changes in the installed version.