Additional configurations

This section discusses some additional configurations that you may want to make in the general-config.yaml file available in the vars folder in the Adeptia Rancher package.

The following table describes the variables you may want to configure based on your requirement before you deploy the Adeptia Rancher package.

Variable	Variable	Description
rke2_custom_path	A custom path for RKE2 installation.
coredns_hosts	Configure mapping between IP and hostnames in CoreDNS.
override_edi_schema	Set it to trueif you want to override the value for "EDISchemas based on property" while deploying the accelerators, else set it to false.
rabbitmqWatcher_enabled	Set it to false if you want to deploy the application with RabbitMQ in HA mode, else set it to true.
delete_db_migration_job_after_execution	Set it to falseif you don't want to delete the databasemigration pod after the job execution completes, else set it to true.
delete_migration_job_after_execution	Set it to falseif you don't want to delete the migration pod after the job execution completes, else set it to true.
delete_static_job_after_execution	Set it to falseif you don't want to delete the static pod after the job execution completes, else set it to true.
delete_cleanup_job_after_execution	Set it to false if you don't want to delete the cleanup pod after the job execution completes, else set it to true.
ac_ha_mode	Variable to enable or disable the deployment of Adeptia Automate in High Availability (HA) mode. The possible values for this property are true and false (default). • When set to true, the application is deployed in HA mode with all the microservices having at least two replicas. As autoscaling is by default enabled, replica count may go up to the value you set for the property maxReplicas in the default_vars_ha.yaml file in the default folder in the package. The default value for the property maxReplicas is 3. Any changes to this property is subject to your Adeptia Automate license. • When set to false, all microservices have only one replica (default).
ac_redeploy	Set it totrue to skip the execution of databasemigration, migration, cleanup, and static jobs, thereby making the redeployment quicker. Else, set it tofalse.
rabbitmq_ha_mode	Variable to deploy Adeptia Automate with RabbitMQ in HA mode. If you want to deploy Adeptia Automate with RabbitMQ in HA mode, set the value for this variable to true, else set it to false.
lan_pv	The variable containing the parameters to define, mount, and enable the use of multiple LAN volumes for reading and writing folders/files in your transactions/process flows. For more details, refer to this page.
hostAliases	This variable contains the mapping between IP and hostnames that you need to add as an entry in the pod's host file.
Variables for enabling distributed execution of the Child Process Flows
redis_stream_enabled	Set this variable to trueto enable distributed execution of the Child Process Flows. The default value for this variable is false.
redis_ha_mode	Setting this variable to true enables the deployment of Redis in HA mode. The default value for this variable is true.
rabbitmq_child_concurrency	This variable sets the concurrency of Child Process Flows in runtime deployments. The default value for this variable is 10**.**
Variable for enabling SAP integration
sapservice_enabled	This variable controls the deployment of the SAP service, which enables the application to communicate with SAP systems. Set it to trueif you use SAP and want to enable SAP integration.
Variables for SAML configuration
saml_sso_enable	Enable or disable SAML SSO.
saml_sso_mappings_0_name	Variable for mapping SAML assertion attributes to Adeptia user fields. Enter the Adeptia user field. For more details, refer to  this page.
saml_sso_mappings_0_mappedattribute	Variable for mapping SAML assertion attributes to Adeptia user fields. Enter the SAML assertion attribute. For more details, refer to this page.
saml_sso_mappings_0_ignorecase	Variable for mappingSAML assertion attributes to Adeptia user fields. Set the fields' value comparison to be case-sensitive. Setting its value to false makes the fields' value comparison case-sensitive. For more details, refer to  this page.
saml_sso_metadata_generator_entity_base_url	Enter a URL to redirect Adeptia Automate after successful SAML authentication. It needs to be a URL with protocol, server, port, and context path. If you are communicating over SSL protocol, provide the protocol name as https and port number on which Adeptia Automate is running in the URL. For more details, refer to this page.
saml_sso_idps_configuration_0_metadata_location	Variable to expose IdP metadata to Adeptia Automate. For more details, refer to this page.
saml_sso_idps_configuration_0_registration_id	Name of the IdP.
Variables for integrating with HashiCorp Vault (For more details, refer to this page)
config_management_enabled	Variable to enable or disable the Config Management feature. The possible values are trueand false. • true – enables the Config Management feature • false – disables the Config Management feature
profile	The Profilein Hashicorp Vault that you want to use for fetching the secrets. A Profile in Vault is used for grouping the secrets based on the type of environment, for example, Dev, QA, or Prod. This ensures that the secrets associated with the specified Profile, and thus with the specific environment, are fetched.
config_management_segregation_criteria	The variable to define the basis for the segregation of your secrets. The value for this variable is either project(in case of project based segregation) or it can be left blank.
hashicorp_vault_enabled	Set this variable to trueto fetch the secrets from HashiCorp Vault.
hashicorp_vault_kv_version	The variable to define the version of the kv secret engine. The possible values are v1and v2.
hashicorp_vault_secret_path_pattern	The pattern of the path for the secrets stored in the Vault. The default value for this variable is: $PROJECT_VAULT_MAPPING$/$PROFILE$ /$PROJECT_NAME$ Where, • $PROJECT_VAULT_MAPPING$ must be included in the pattern if you have used project mapping. • $PROFILE$ must be included in the pattern if you have used profiles in Vault for grouping the secrets based on the type of environment. • $PROJECT_NAME$ must be included in the pattern if you have used project folders in the Vault.
hashicorp_vault_url	Access URL (endpoint) of the HashiCorp Vault.
hashicorp_vault_secret_base_path	Enter the complete path to the base folder that contains secrets.
hashicorp_vault_authentication	Enter the type of authentication to be used by AC application to authenticate to the Vault. The possible values are KUBERNETESand TOKEN.
hashicorp_vault_token	Enter the Vault token.
hashicorp_vault_kubernetes_role	Enter the name of the role associated with the Kubernetes authentication method you have defined in the Vault.
hashicorp_vault_kubernetes_service_acc_token_path	Enter the path where the Service Account token is stored within the pod. The default value for this variable is /var/run/secrets/kubernetes.io/ serviceaccount/token.
hashicorp_vault_kubernetes_path	Enter the name of the Kubernetes authentication method defined in the Vault.

Custom installation of Adeptia Rancher

If you want to custom-install the application in a different partition other than the default, follow the steps below to attach a separate disk before starting the RKE2 installation.

1. Add a new disk (Data disk) in existing VM (Recommended)

Attach a separate disk with sufficient capacity and mount it to a permanent location (For example, /data/rke2).

Confirm the new disk is visible

Code

lsblk

or

Code

sudo fdisk -l

You should see a new disk like:

Code

/dev/sdb

(No partitions yet)

Partition the disk (Recommended)

Use fdisk (MBR) or parted (GPT, preferred for disks >2TB).

Using fdisk (Common case)

Code

sudo fdisk /dev/sdb

Inside fdisk:

Code

n   → new partition 
p   → primary 
1   → partition number 
Enter → default start 
Enter → default end (Use full disk) 
w   → write changes

Verify:

Code

lsblk

You should now see:

Code

/dev/sdb1

Format the partition

Use ext4 (Most common for Ubuntu):

Code

sudo mkfs.ext4 /dev/sdb1

Warning: This erases all data on that disk.

Create a mount point

Code

sudo mkdir /data/rke2

(You can choose any path: /mnt/data, /appdata, etc.)

Mount the disk

Code

sudo mount /dev/sdb1 /data/rke2

Verify:

Code

df -h

Make the mount persistent

Get the disk UUID:

Code

sudo blkid /dev/sdb1

Example output:

Code

UUID="1234abcd-56ef-78gh-90ij-klmnopqrst"

Edit /etc/fstab:

Code

sudo nano /etc/fstab

Add this line:

Code

UUID=1234abcd-56ef-78gh-90ij-klmnopqrst  /data/rke2  ext4  defaults,nofail  0  2

✔ nofail prevents boot failure if the disk is missing.

Test fstab

Code

sudo mount -a

If no errors → configuration is correct.

Set permissions (Optional)

Code

sudo chown -R root:root /data/rke2

Or for shared access:

Code

sudo chmod 775 /data/rke2

Final verification checklist

Code

lsblk 
df -h 
mount | grep sdb

2. RKE2 configuration using general-config.yaml

Create or edit the RKE2 configuration file:

Code

sudo mkdir -p /etc/rancher/rke2 
sudo vi Rancher-Package/vars/general-config.yaml

Configuration example

Code

## RKE2 configuration ## 
rke2_custom_path: /data/rke2

Verify disk space before installation

Code

df -h /data/rke2

Confirm that the directory has at least 100 GB available.