Last Updated on

Transact 4.5.0.0 – Installation Guide – Silent

Overview

A step by step procedure for installing Ephesoft Transact 4.5.0.0 silently on a Microsoft® Windows machine. Windows 7 SP1, Windows 10, Windows Server 12, Windows Server 12 R2, and Windows Server 2016 are supported and applies to both a fresh install and an upgrade install. These instructions should be referred to when users want to install Transact silently using the Windows Installer package Ephesoft_4.5.0.0.

See Microsoft® Windows | Transact 4.5.0.0 Release Platform Support for more information.

What Is Silent Installation?

Silent-mode installation allows you to define an installation configuration only once and then use the configuration to duplicate the installation on many machines. During installation in silent mode, the installation program reads the settings from a properties file created before beginning the installation. The installation program does not display any configuration options during the installation process.

Prerequisites

In order to use Ephesoft Transact 4.5.0.0 silent installer, the user needs to install the following prerequisites:

  1. Microsoft Visual C++ 2010 Redistributable
  2. Microsoft Visual C++ 2012 Redistributable
  3. Microsoft Visual C++ 2013 Redistributable (x86 version)  – Download
  4. Microsoft Hotfix KB2919355 – Download
  5. Microsoft Visual C++ 2015 Redistributable (x64 version)
  6. Microsoft Visual C++ 2015 Redistributable (x86 version)  – Download
  7. Microsoft .Net Framework 4.5.1
  8. Windows OS should be updated with latest windows Update
  9. Microsoft® SQL Server® 2012 Native Client – QFE* (Version 11.4.7001.0)
  10. Microsoft® ODBC Driver 13.1 for SQL Server® – Windows, Linux, & macOS (Version 13.1.4413.46) – Download
  11. Microsoft® Command Line Utilities 13.1 for SQL Server® – Windows, Linux, & macOS (Version 13.811.168) – Download

*See Installing Ephesoft Transact v4.5.0.0 on Windows Server 2012 R2 – Windows 8 and Higher for more information on this specific installation.

Note: During a silent installation, the installer checks for the prerequisites on the system. If those are not already preinstalled, then the installer triggers their installation and proceeds. If the installation completes and some recostar.dll related issues are still observed, it may mean that the prerequisites have not been properly installed or are corrupted. The user needs to check if .Net Framework 4.5.1 (or higher), Microsoft Visual C++ 2013 Redistributable, and Microsoft Visual C++ 2015 Redistributable are installed or not. If all these prerequisites are installed, then Microsoft Visual C++ 2013 Redistributable and Microsoft Visual C++ 2015 Redistributable may be corrupt. You will need to reinstall these and make sure they are the 32-bit version. If redistributables are corrupt or installed incorrectly, Ephesoft Transact cannot detect it while installation. The user needs to ensure that they are installed properly.

Before starting the silent installation of Ephesoft Transact, make sure to:

  • Turn Windows User Account Control (UAC) OFF
  • Disable IPv6 (for more information, refer here)

Note: If your JAVA_HOME environment variable is already defined, it will be modified during the fresh installation of Ephesoft Transact.

Additionally, if the user wants to use Ephesoft silent installer with Microsoft® SQL Server, then the user can only configure an already installed instance of Microsoft® SQL Server.

Before beginning the installation, the user should have a properties file ready which contains all the required configuration.

You may download the current version here:

http://demoephesoft.com/products/ephesoft-transact/

The contents are in a zip file that MUST be extracted and includes the config.properties file as shown below:


<pre>#Placeholder for installation path.
installation_directory=C:\Ephesoft\

#Placeholder for whether to use existing shared folders or install new. It's 0 for new and 1 for use existing.
use_existing_shared_folders=0

#Placeholder for shared folders path.If configuring existing shared folders then give path of parent directory of existing shared folders else give path to install new shared folders.
shared_folder_path=C:\Ephesoft\

#Placeholder for operating system type.Input for this property should be in accordance with the customer’s system specification.It's 0 for 64 bit system and 1 for 32 bit system.
os_type=0

#Placeholders for user registration details.
user_registration_name=username
user_registration_company=companyname
user_registration_department=departmentname
user_registration_street=street
user_registration_city=city
user_registration_state=state
user_registration_country=country

#Placeholder for type of database that will be configured or installed. It is 1 for MariaDB and 2 for MS SQL 3 for Oracle.
database_type=1

#Placeholder for database name for mariadb and MS-SQL Server
#Placeholder for Application database name.
application_db_name=Ephesoft
#Placeholder for Report database name.
report_db_name=Report
#Placeholder for Report archive database name.
report_Archive_db_name=Report_Archive

#Placeholders for database login details. A login will be created and will be updated in configuration/properties files.
# Alphabets and digits are allowed and length must be from 1 to 16.
database_login_username=Demouser
# For MariaDB - Alphabets, digits and special characters[#@^$!%*?&amp;|;',./:?~`()&lt;&gt;{}+_-] are allowed and length must be from 6 to 12.
# For MSSQL Server - Alphabets, digits and special characters[#@^$!%*?&amp;|;',./:?~`()&lt;&gt;{}+_-] are allowed and length must be from 6 to 12 but there must be atleast one lowercase character, one uppercase character, one digit and one special character.
database_login_password=Demo@123
#It must be same as database_login_password property.
database_login_confirm_password=Demo@123


#Configuration for MariaDB Database
#Placeholder for whether to install new MariaDB or use existing.It's 1 for new and 2 for use existing.
configure_maria_db=1

#Placeholder for MariaDB password.
#There must be atleast one of these [!@#$%^&amp;*?] special characters ,[=\] are not allowed and length must be from 6 to 12.
mariadb_root_password=P@ssw0rd

#Placeholder for confirmation of MariaDB password.It must be same as root_password property.
mariadb_confirm_password=P@ssw0rd

#Placeholder for port number of MariaDB server.If not specified, by default it will be taken as 3306.
mariadb_port_number=3306

#Placeholders for details of existing MariaDB.
existing_maria_db_username=root
existing_maria_db_password=Passw0rd
existing_maria_db_servername=localhost

#Configuration for MS-SQL Server Database
#Placeholder for whether to install new MS SQL server or use existing.It's 1 for new and 2 for use existing.
configure_mssql_db=2

#Placeholders for details of existing MS SQL db.
existing_ms_db_username=sa
existing_ms_db_password=Passw0rd
existing_ms_db_servername=xx.xx.xx.xx

#Placeholder for port number of MS SQL server.
ms_sql_port_number=1433

#Placeholder for Instance name of MS SQL server(this is an optional field port no should be provided of instance).
instance_name_for_mssql=

#If using existing MS SQL server,this placeholder takes input for whether to enable always on feature or not.It's 1 for enable and 0 for disable.
#This is applicable for MS-SQL server 2012R2 and above
enable_always_on_feature=0

#Placeholder for Windows Authentication. It is 1 for Windows authentication and blank for sql authentication
windows_authentication_for_mssql=

#Configuration for ORACLE Database
#Placeholder for whether to create new oracle schema or use existing schema.It's 1 for new and 2 for use existing.
configure_oracle_db=1

#Placeholder for whether oracle is using 0 for SID and 1 for Service
existing_oracle_sid_or_service=0

#Placeholders for details of oracle database.
existing_oracle_servername=xx.xx.xx.xx
existing_oracle_sys_username=sys
existing_oracle_sys_password=P@ssw0rd
existing_oracle_sid_service=orcl

existing_oracle_applicationdbschema=Ephesoft
existing_oracle_applicationdbpassword=Passw0rd
existing_oracle_reportdbschema=Report
existing_oracle_reportdbpassword=Passw0rd
existing_oracle_reportarchivedbschema=Report_Archive
existing_oracle_reportarchivedbpassword=Passw0rd

#Placeholder for port number of oracle server.
oracle_port_number=1521

#Placeholder for whether to execute database patch or not. It's 1 for yes and 0 for no.This property is used in case of upgradation.
execute_patch=1

#Placeholder for whether database backup is taken or not. It's 1 for yes and 0 for no.Its value should be always 1 to continue to installation.
confirm_if_db_backup_taken=1

#Placeholder for open office port.
open_office_port_number=8100


#Placeholder for logon information for Ephesoft Transact service 0 for Local System User and 1 for other user 
service_logon_information_required=0
service_logon_username=
service_logon_password=


#Authentication mode 0 for normal Form Authentication(Default) and 1 for PIVCAC (PKI) authentication mode
pivcac_selected_mode=0

#Form Authentication Configuration 0 for HTTP 1 for HTTPS
form_authentication_http_or_https=0

#if HTTPS selected then please provide keystore file and its password
form_authentication_keystore_file_path=C:\\PIV\\sample-certificates\\servercert.jks
form_authentication_keystore_password=enter_servercert_password

#In case of PIV CAC(PKI authentication) please provide server certificate and ca certificate file path and its password 
pivcac_server_cert_path=C:\\PIV\\sample-certificates\\servercert.jks
pivcac_server_cert_password=enter_servercert_password
pivcac_ca_cert_path=C:\\PIV\\sample-certificates\\cacerts.jks
pivcac_ca_cert_password=enter_cacerts_password

#Realm settings for PIV CAC or HTTPS(Form authentication)
pivcac_realm_connection_url=ldap://localhost:389
pivcac_realm_connection_name=cn=Manager,dc=ephesoft,dc=com
pivcac_realm_connection_password=secret
pivcac_realm_user_base=ou=people,dc=ephesoft,dc=com
pivcac_realm_user_search=cn={0}
pivcac_realm_role_base=ou=groups,dc=ephesoft,dc=com
pivcac_realm_role_name=cn
pivcac_realm_role_search=uniqueMember={0}
pivcac_realm_userSubtree=true
pivcac_realm_roleSubtree=true

#Connector settings for PIV CAC configuration. In case of Form HTTPS authentication only pivcac_connector_port is required
pivcac_Connector_port=8443
pivcac_Connector_client_auth=want
pivcac_Connector_compression=on
pivcac_Connector_ssl_enabled=true
pivcac_Connector_secure=true
pivcac_Connector_ssl_protocol=TLS
pivcac_Connector_trust_store_file_path=C:\\Ephesoft\\certs\\trustore.jks
pivcac_Connector_trust_store_password=enter_truststore_password
pivcac_Connector_key_store_file_path=C:\\Ephesoft\\certs\\keystore.jks
pivcac_Connector_key_store_password=enter_keystore_password
pivcac_Connector_ssl_enabled_protocol=TLSv1,TLSv1.1,TLSv1.2
pivcac_Connector_ciphers_text=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA

#connectivity_user Configuration 0 for ldap mode, 1 for AD and 2 for tomcat
connectivity_user_connection=2
connectivity_url=ldap://localhost:389
connectivity_domain_name=ephesoft
connectivity_domain_org=com
connectivity_user_name=cn=Manager,dc=ephesoft,dc=com
connectivity_user_password=secret
connectivity_group_search_attribute_filter=cn
connectivity_user_search_attribute_filter=cn
connectivity_ldap_user_base=ou=people
connectivity_ldap_group_base=ou=groups
connectivity_msad_context_path=
connectivity_msad_group_search_filter=
connectivity_super_user_group=</pre>

Important Considerations for Silent-Mode Installation

When using silent mode, keep the following considerations in mind:

  • Silent-mode installation requires the same amount of temporary disk space (approximately 7 GB) and uses the same temporary storage directories as a standard installation. The installation program does not alert you if enough space is available in the temporary directory.
  • A silent-mode installation takes the same amount of time as a standard installation. At the beginning of a silent-mode installation, an installation program window is displayed, indicating that the installation has started. It remains throughout the installation process displaying the progress bar.
  • Incorrect entries in the properties file can cause installation failures. To help you determine the cause of a failure, a log file named “installation” is created in a sub directory named logs. This sub directory is created in the directory where properties file is placed.
  • Please do not use semi-colons or special characters in the properties file.
  • After installation is completed, a success message is displayed in the installation file created during installation.

Steps of execution

Following steps must be followed for fresh installation with Installer version 4.5.0.0

  1. Download zipped install package. Extract contents.
  2. Update the config.properties file as described above with required configuration.
  3. Install Prerequisites
  4. Run command prompt as administrator and execute following command:

msiexec /i <directory path of msi> /qb /norestart  USERINPUTSPATH=<directory path of properties file>

For example:

msiexec /i  “C:\Ephesoft_4.5.0.0.msi” /qb /norestart USERINPUTSPATH=C:\config.properties

The above command will initiate Ephesoft installer setup on machine.

Once the installation is prepared, the progress bar is displayed.

  • Note: When installation begins, a log file named installation is created in a sub directory named “logs”. This sub directory is created in the directory where properties file is placed.

If any error occurs during installation, error logs are created in this log file. Otherwise, a success message is shown.

After the installation is complete, the user manually restarts if needed or if user wants to restart, remove /restart tag from command line and use the following command:

msiexec /i “path where msi is copied” /qb  USERINPUTSPATH=path where properties file is copied

Post-Installation Instructions

There is a known issue with the expiration of the Logi license. See Known Issue: Logi License Expiration for more information.

  1. Download the new Logi license from http://download.ephesoft.com/Ephesoft_Product/lgx110102.zip.
  2. Extract the ZIP file.
  3. Create a back up of the existing lgx110102.lic file located in {Ephesoft Installation Directory}\EphesoftReports\.
  4. Rename the existing file and move it to another directory.
  5. Delete the expired license.
  6. Copy the downloaded lgx110102.lic to {Ephesoft Installation Directory}\EphesoftReports\.

Was this article helpful to you?

Rene Hernandez