This article covers setting up a duplicate YF environment.
It's something which can be used as a dev/test environment, for testing or backup purposes.
Before you begin, you'll want to ensure that you have:
- A backup of your Yellowfin repository/configuration database from the production environment
- Installer that matches version of Yellowfin currently in use on production
- Any custom styles/files used on production environment
- A valid licence for this new environment
Now it's time to set it all up
- Install the FULL version of Yellowfin that matches the production environment. Check the version and build number via System Information in the Administration Console.
- If you're installing on the same machine as the production instance, ensure you install Yellowfin into a different path. When it gets to create the database part of the installer, choose HSQL.
- Ensure the new instance is working correctly. Start the new instance, and ensure you can login and hit the 'browse' page.
- Stop Yellowfin.
- Restore the Yellowfin database backup you made from prod on this machine (or anywhere else that won't conflict with the production database).
- Open the web.xml and update the connection details to point to the restored database. You can refer to your prod web.xml to find the connection details but make sure to use the newly-restored database name (if it has changed).
- Start Yellowfin.
You should now be using a fresh install of Yellowfin, but looking at data which matches the current production data, though completely separate.
This is a perfect environment for testing changes/upgrades before rolling them onto prod.