Ask Questions and Find Answers
Important:
Ask is now read-only. You can review any existing questions and answers, but not add anything new.
But - don't panic! While ask is no more, we've replaced it with discuss - the new Liferay Discussion Forum! Read more here here or just visit the site here:
discuss.liferay.com
RE: RE: Maintenance without portal downtime
Hi everyone,
 I have a request in this regard given the
  institutional importance of a portal developed in Liferay 7.1 and
  since it is necessary to maintain the functioning and availability of
  the institutional site 24 hours a day for 365 days without
  interruptions even in the event of an update / patch / fixpack
 Can
  you kindly indicate alternative methods and procedures suggested to
  avoid carrying out maintenance interventions without machine downtime
  ?
 Many thanks
Can you keep your old environment in read-only mode while you upgrade/install a fix pack in the new environment?
Thanks Alberto for your help,
 regarding your suggestion to keep
  my old environment in read-only mode
 could you give me a
  suggestion on how to configure liferay for this specific operation
  Thank you very much
There's a portal.properties entry
auth.login.disabled=true
(default: false, of course) See documentation here.
Really interesting
 so confirm that with this type of
  configuration the users are disabled from logging in but also maintain
  read-only access
 and at the end of the update the login enablement
  and complete functionality of the portal returns
Yes, that's the property.
  
 You should have a cluster with at least two nodes. In summary,
  this would be the process for two nodes:
- Shutdown node 1
 - Startup the node 1 with that property
 - Stop node 2
 - Run the upgrade or install the patch and starup the node 2
 - Once is up, shutdown the node 1 with the old Liferay version
 - Startup the node 1 with the new Liferay version
 
Very good
 Thanks for the valuable suggestions