Liferay PaaS Go-Live Checklist
Liferay Cloud is committed to your project’s smooth launch. This go-live checklist should help you catch potential issues in advance and optimize your Cloud environments.
These items are critical to review before you go live:
Your plan quotas
Regularly scheduled backups
Project performance, including stress testing
Any registered custom domains
Correctly configured auto-scaling
Your team members invited and given the proper permissions
Prioritize these items as you go through this checklist so that your project launch is successful.
Reviewing Your Project Architecture
The goal of reviewing your project architecture is to be sure your environment, services, and features are optimized to achieve the end result of what you’re building.
Environment Specifications
Confirm that your production environment matches your subscription. On your production environment’s Settings page, the Environment Type should show as: Production.
For more information, see Environment Type.
Service Versions
Check your production environment’s services and confirm they are up-to-date. Compare the versions in your environment with the latest versions here.
Clustering
Confirm that clustering is properly configured, if you have a High Availability production environment. See Setting Up Clustering in Liferay Cloud.
Development Life Cycle and Workflow
Deploy test builds to confirm that the Software Development Life Cycle (SDLC) is working properly. When you generate a build with Liferay Cloud’s CI, it should appear on the Builds page in the Liferay Cloud console. Builds should be deployed from the Deployments page.
Here is more information about the SDLC and how to use it:
Reviewing Your Metrics
Your metrics include items such as the alerts you may receive, your quotas, and your ability to profile your environment. Adjust these properly before going into production.
Subscription Plan Quotas
Deploy to all of your environments to confirm each of their quotas. If you have changed the resource allocation for some services, revert these changes for your production environment before you go live.
See Quotas for more information.
Dynatrace
If you purchased High Availability or Dynatrace add-ons, check your subscription to confirm which environments should have Dynatrace set up to detect issues. Your project’s main contributors should have access to a Dynatrace dashboard to diagnose issues.
See Integrating Dynatrace with Production Environments for more information.
Alerts
Check the bell icon on the top-right of the Liferay Cloud console to check for any alerts that must be addressed.
Confirm that your project’s main contributors also have updated their preferences to receive alerts via email. See Real-Time Alerts for more information.
Reviewing Your Continuity Plan
Your continuity plan includes items to ensure your site keeps running in the event of various events.
Backups
Your production environment should take automatic backups on a fixed frequency. Check the frequency to ensure it matches your project’s needs.
Additionally, run a manual backup and restore it to your environment to make sure this process is working correctly. See the Backup Service and Restoring an Environment from the Backups Page for more information.
Auto-Scaling
If you have clustering configured, you should activate and test auto-scaling in your environment before going live. See Auto-Scaling for more information.
Disaster Recovery
If you purchased a Disaster Recovery environment, simulate a disaster scenario and verify how fast you can recover the environment in case of a regional outage.
See the Disaster Recovery Overview for more information.
Zero-Downtime Deployments
Deploy to your environments to verify that they do not cause downtime. If they do, consider adjusting your liveness and readiness probes.
See Self-Healing for more information.
Reviewing Your Project’s Benchmarks
Your performance benchmarks ensure your site runs as you plan it to run.
Performance
Analyze your environment’s performance metrics. If you migrated a self-hosted instance to Liferay Cloud, confirm that it runs as well in your new environment as it did before the migration.
See Application Metrics for more information.
Stress Testing
Run a stress test on your UAT environment and analyze the results. Let Liferay Support know the results by opening a Support ticket once you’ve tested your environment.
Reviewing Final Details
Custom Domains
Confirm that all of your DNS entries point to Liferay Cloud and check how the domains are referenced.
Changes or additions to custom domains can take up to 24-48 hours to fully propagate. Plan go-live times with this in mind.
See Custom Domains for more information.
Team Membership
Confirm that all of your team members are added to your project, and that they each have the correct roles and permissions per environment.
See Environment Teams and Roles for more information.
VPN Configuration
If you’ve configured a VPN, confirm that the connection is working as expected. See the VPN Integration Overview for more information.
Additional Consideration
This checklist was designed with a typical Liferay PaaS project in mind. Take special consideration for any unique customizations or integration your project uses.