What’s New In Transact 4.5?


Installer | Linux Installer Update

 

Prior to Ephesoft Transact v4.5.0.0, during silent installation on Linux environments, the user had to provide all the values for all the input variables in the config.properties file. For example, if the user wanted to install the application using Oracle, he had to make sure that details were provided for the MySQL database as well. This was required as the installer script validated all the parameters as soon as they were read from the silent installer configuration file and went into error whenever any parameter was missing.

In Ephesoft Transact v4.5.0.0, the installer script has been updated to read the complete file, fetch all the parameters and only then validate defined values on the basis of database selection. Now, if you want to install the application using an Oracle database, you can leave parameters dedicated to the MySQL database blank and vice versa.

The config.properties file also contains various “yes/no” switches which are used to define the parameters to be validated. The sets of governing and related parameters are given below:

Sr No Governing Parameters Related Parameters
1 input_run_application_as_non_root_user input_use_existing_user

input_application_user

input_application_user_group

2 input_run_application_as_non_root_user

input_application_user_password_required

input_application_user_password
3 input_change_server_name input_changed_server_name
4 input_change_shared_folder_path input_changed_shared_folder_path
5 input_existing_shared_folder input_existing_shared_folder_path
6 input_install_multiserver input_mounted_sharedfolder_path
7 input_database_type = 1(mysql) input_new_database_instance

input_system_ip_name

input_database_username

input_database_port_number

input_database_password

input_admin_database_username

input_admin_database_password

input_application_database_name

input_report_database_name

8 input_database_type = 2(oracle) input_new_database_schema

input_oracle_database_username

input_oracle_database_password

input_oracle_database_server_name

input_oracle_database_port_number

input_oracle_database_sid_service

input_oracle_database_application_db_schema

input_oracle_database_application_db_password

input_oracle_database_report_db_schema

input_oracle_database_report_db_password

input_oracle_database_report_archive_db_schema

input_oracle_database_report_archive_db_password

 

If the value of the governing parameter is “y”, then its related parameters will be validated. If the value is “n”, related parameters can be left empty or default.

 

Let’s consider the following example.

Suppose we are installing Ephesoft Transact using MariaDB in silent installation mode. To configure the parameters, let’s open the config.properties file, which is located in the Response-Files folder of the application installer.

C:\Users\Ephesoft\AppData\Local\Microsoft\Windows\INetCache\Content.Word\config2-1.png

Here, the value for input_database_type will be 1 as we are using MariaDB.

C:\Users\Ephesoft\AppData\Local\Microsoft\Windows\INetCache\Content.Word\config1.png

For database configuration, we provide required values only for MariaDB, leaving the Oracle parameters empty.

C:\Users\Ephesoft\AppData\Local\Microsoft\Windows\INetCache\Content.Word\config3.png

Let’s start the silent installation.

C:\Users\Ephesoft\AppData\Local\Microsoft\Windows\INetCache\Content.Word\console1.png

Ephesoft Transact is installed successfully.

C:\Users\Ephesoft\AppData\Local\Microsoft\Windows\INetCache\Content.Word\console2.jpg