Step-by-Step Liquibase Deployment
1. Deploy latest Liquibase windows installer Silently
Executed with a PowerShell script as Admin User A.
2. InstallShield Database Application
Installed by Admin User B, performing the following:
○ Moves required Liquibase files to enable the Liquibase call command.
○ Sets the global environment path variable to the Liquibase installation folder.
3. Generate SQL Output
Liquibase is called to create an output SQL file containing the database changes that need to be applied.
The Problem
When Admin User A installs Liquibase, Admin User B is unable to run Liquibase, despite the global environment path variable being set. For User B to execute Liquibase, User A must first run Liquibase after installation.
Troubleshooting Steps Tried
1. Restarting the Machine
After setting the global environment path through the installer, we restarted the machine but were still unable to run the Liquibase command.
2. Manual Command Execution
○ As User B, opened the Command Prompt and manually ran the Liquibase call command that our installer was trying to run, which generated the necessary files. No log files indicating what potentially failed were outputted. These log files are generated in call command syntax.
○ However, attempting to run Liquibase via the InstallShield-installed application still failed.
Observation: Liquibase runs successfully for User B only after User A has executed it once via the installer.
Key Question
Has anyone else encountered this issue?
We’ve thoroughly reviewed discussions on Stack Overflow and Liquibase community forums but haven’t found a similar case. Based on our investigation, we do not believe this is related to our InstallShield application.
We’re seeking insights or potential resolutions for this behavior. Any guidance would be greatly appreciated!