Last Updated on

What’s New In Transact 4.5?


Installer | Database Type Matching in Server.xml and Windows Registry During Upgrade

In previous versions of Transact, the database details in the server.xml file and Windows registry were not matched during installation of an upgrade. Thus, the installation would proceed normally, but the user could face some difficulties later when he tried to use the updated application.

Whenever Transact is installed, database information is stored both in the server.xml file and Windows registry. If required, the user can change the database for Ephesoft Transact and update the database details in the server.xml configuration file. However, the Windows registry will still contain entries created at the time of installation. While this does not have any consequence for current system operation, it used to create problems after the application was upgraded. During the upgrade, the system picks up the details from the registry and automatically updates the server.xml file. As a result, the upgraded application could refer to a database that was no longer present and go into an error state.

In Ephesoft Transact v.4.5.0.0, the database details in server.xml are matched with the corresponding registry entries every time you upgrade the application. If these parameters match, the installation will proceed. If these parameters don’t match, the system will stop the installation with the error message “Installer has detected difference in selected database type in Windows Registry and Server.xml. Please update the configuration in registry to match the server.xml and re-try the installation”. At this stage, you can make the required changes either in the server.xml file or Windows registry to make sure the details point to the same database. After this, the upgrade must be restarted.

Let’s consider the following example.

When you install Ephesoft Transact, database entries are created both in the server.xml file (C:\Ephesoft\JavaAppServer\conf) and Windows registry. The database details in these entries are the same.

Database details in server.xml file

C:\Users\Ephesoft\AppData\Local\Microsoft\Windows\INetCache\Content.Word\server.xml-original.png

Database details in Windows registry

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

Note: The SelectedDb entry in the Windows registry will have one of the following values:

1 – MariaDB

2 – MS-SQL

3 – Oracle

Suppose you decide to use a different database and change the database details in the server.xml file accordingly.

C:\Users\Ephesoft\AppData\Local\Microsoft\Windows\INetCache\Content.Word\server.xml-changed.png

When you try to upgrade Transact you will receive the following error message:

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

Before restarting the upgrade, you’ll have to go back to the server.xml file or Windows registry and make the required changes so that database details match. After this, the upgrade can continue normally.