Category
Installation & Upgrades
Product Version
7.3
Yellowfin 7.3 and 7.4 parallel upgrade
Answered
Hi,
We have existing YF 7.3 running in an old server sharing with another applications and it is in operation, we would like to changed the environment and do a separate installation of YF 7.4 on another server dedicated to Yellowfin only. The plan is to continue the use of YF 7.3 until we have fully migrated all content and tested everything on the new server and finally switch users to use the new YF 7.4. Is there a best practice to this or has this been already discussed here in the community? If yes, could anyone provide the link please? How will the license work for this type of upgrade?
Any help is highly appreciated.
Thanks,
Pearlsia.
The same question
Hi Pearlsia,
Thanks for reaching out with your question. It looks like you're already headed in the right direction!
In order to accomplish this, the best answer is to start by:
A) Restore a full backup of your 7.3 Yellowfin Configuration Database onto the target server.
B) Perform a fresh install of the SAME 7.3 version on the target server into a temporary or DUMMY Database.
C) Edit line 112 in the <YellowfinInstall>/appserver/webapps/ROOT/WEB-INF/web.xml file to point to your RESTORED Database.
D) Restart Yellowfin.
From this point you will have a replica of your production 7.3 server, with all settings intact. The caveat here is that the license will be tied to your hostname. You may have to reach out to your Account Manager to discuss options for licensing here to finalize this process.
Once you have a license working for your target server, you can then begin your upgrade testing.
Let me know if this helps or if you have any further questions.
Thanks,
Ryan
Hi Pearlsia,
Thanks for reaching out with your question. It looks like you're already headed in the right direction!
In order to accomplish this, the best answer is to start by:
A) Restore a full backup of your 7.3 Yellowfin Configuration Database onto the target server.
B) Perform a fresh install of the SAME 7.3 version on the target server into a temporary or DUMMY Database.
C) Edit line 112 in the <YellowfinInstall>/appserver/webapps/ROOT/WEB-INF/web.xml file to point to your RESTORED Database.
D) Restart Yellowfin.
From this point you will have a replica of your production 7.3 server, with all settings intact. The caveat here is that the license will be tied to your hostname. You may have to reach out to your Account Manager to discuss options for licensing here to finalize this process.
Once you have a license working for your target server, you can then begin your upgrade testing.
Let me know if this helps or if you have any further questions.
Thanks,
Ryan
Okay so I searched further and found these links:
https://community.yellowfinbi.com/knowledge-base/article/%E2%80%8Bbest-practice-for-performing-a-yellowfin-upgrade
https://community.yellowfinbi.com/knowledge-base/article/replicating-your-yellowfin-environment?_ga=2.38058467.1310391533.1534894879-1554337166.1532491985&_gac=1.249168179.1533254302.EAIaIQobChMI-8Ob5MjP3AIVE6qWCh3H1AguEAAYASAAEgIUO_D_BwE
This is what we are going to do, to mirror the YF 7.3 production environment on the new server .
Goal is to make it identical to the existing environment.
Okay so I searched further and found these links:
https://community.yellowfinbi.com/knowledge-base/article/%E2%80%8Bbest-practice-for-performing-a-yellowfin-upgrade
https://community.yellowfinbi.com/knowledge-base/article/replicating-your-yellowfin-environment?_ga=2.38058467.1310391533.1534894879-1554337166.1532491985&_gac=1.249168179.1533254302.EAIaIQobChMI-8Ob5MjP3AIVE6qWCh3H1AguEAAYASAAEgIUO_D_BwE
This is what we are going to do, to mirror the YF 7.3 production environment on the new server .
Goal is to make it identical to the existing environment.
Hi Pearlsia,
Thanks for reaching out with your question. It looks like you're already headed in the right direction!
In order to accomplish this, the best answer is to start by:
A) Restore a full backup of your 7.3 Yellowfin Configuration Database onto the target server.
B) Perform a fresh install of the SAME 7.3 version on the target server into a temporary or DUMMY Database.
C) Edit line 112 in the <YellowfinInstall>/appserver/webapps/ROOT/WEB-INF/web.xml file to point to your RESTORED Database.
D) Restart Yellowfin.
From this point you will have a replica of your production 7.3 server, with all settings intact. The caveat here is that the license will be tied to your hostname. You may have to reach out to your Account Manager to discuss options for licensing here to finalize this process.
Once you have a license working for your target server, you can then begin your upgrade testing.
Let me know if this helps or if you have any further questions.
Thanks,
Ryan
Hi Pearlsia,
Thanks for reaching out with your question. It looks like you're already headed in the right direction!
In order to accomplish this, the best answer is to start by:
A) Restore a full backup of your 7.3 Yellowfin Configuration Database onto the target server.
B) Perform a fresh install of the SAME 7.3 version on the target server into a temporary or DUMMY Database.
C) Edit line 112 in the <YellowfinInstall>/appserver/webapps/ROOT/WEB-INF/web.xml file to point to your RESTORED Database.
D) Restart Yellowfin.
From this point you will have a replica of your production 7.3 server, with all settings intact. The caveat here is that the license will be tied to your hostname. You may have to reach out to your Account Manager to discuss options for licensing here to finalize this process.
Once you have a license working for your target server, you can then begin your upgrade testing.
Let me know if this helps or if you have any further questions.
Thanks,
Ryan
Hello Ryan,
Thank you for your response.
So just on the license part, is it possible to install another YF 7.3 on the new server during upgrade and testing while we keep the existing Yellowfin7.3 operational on the old server till we can confirm that everything is perfectly working on the new server and we can decommission/uninstall it from the old one?
What are the options for us to achieve this?
Thank you so much!
Kindest regards,
Pearlsia.
Hello Ryan,
Thank you for your response.
So just on the license part, is it possible to install another YF 7.3 on the new server during upgrade and testing while we keep the existing Yellowfin7.3 operational on the old server till we can confirm that everything is perfectly working on the new server and we can decommission/uninstall it from the old one?
What are the options for us to achieve this?
Thank you so much!
Kindest regards,
Pearlsia.
Hi Pearlsia,
Yes it is possible to host two instances of Yellowfin on one server, provided there are adequate resources available to do so.
The caveat here is that you will have to set your NEW Instance to a different port number than the existing instance. This can be done during install per the process highlighted above.
You will also have to manually install this as a service (if on Windows) instead of doing so in the installer. To do this, after installation you will want to open a command line prompt in the <YellowfinInstall>/appserver/bin folder and execute the following command as Administrator:
This allows you to name the service uniquely so as to not cause problems with your existing service.
I would encourage you to reach out briefly to discuss this with your Account Manager, as they are often willing to work with clients who are performing operations such as this.
Please let me know if you have further questions on the process.
Thanks,
Ryan
Hi Pearlsia,
Yes it is possible to host two instances of Yellowfin on one server, provided there are adequate resources available to do so.
The caveat here is that you will have to set your NEW Instance to a different port number than the existing instance. This can be done during install per the process highlighted above.
You will also have to manually install this as a service (if on Windows) instead of doing so in the installer. To do this, after installation you will want to open a command line prompt in the <YellowfinInstall>/appserver/bin folder and execute the following command as Administrator:
This allows you to name the service uniquely so as to not cause problems with your existing service.
I would encourage you to reach out briefly to discuss this with your Account Manager, as they are often willing to work with clients who are performing operations such as this.
Please let me know if you have further questions on the process.
Thanks,
Ryan
Replies have been locked on this page!