Configure a Bloomreach Experience Manager Project for Deployment in Bloomreach Cloud
Overview
This page describes how to prepare a Bloomreach Experience Manager (XM) project for deployment in Bloomreach Cloud. It outlines the required steps and configuration tasks to ensure your implementation is compatible with the cloud environment.
Prerequisites
- A Bloomreach Experience Manager project based on version 13, 14, 15, or 16.
Prepare Your Project for Bloomreach Cloud
Use the following checklist to verify that your project meets the requirements for deployment in Bloomreach Cloud. Documentation links are provided for each step.
¹ If you are not using Essentials, manually add the Enterprise Repository and the Lucene Export Service to your project.
Post-Deployment Configuration in Bloomreach Cloud
After the first deployment in Bloomreach Cloud, complete the following configuration steps to ensure your instance operates as expected.
| Step | XM 13 Documentation | XM 14 / 15 / 16 Documentation |
|---|---|---|
| Configure virtual hosts | Configure virtual hosts for an environment (13) | Configure virtual hosts for an environment (14 / 15 / 16) |
| Configure the Relevance SQL data store | Configure the Relevance SQL data store for Bloomreach Cloud (13 / 14 / 15 / 16) | |
| Configure CMS security | Login page captcha and auto-completion (13) Password safety validation and password expiration (13) Create users and groups (13) | Login page captcha and auto-completion (14 / 15 / 16) Password safety validation and password expiration (14 / 15 / 16) Create users and groups (14 / 15 / 16) |
| Remove or update default user accounts (admin, editor, author, webmaster) | ||
| Configure repository maintenance jobs | Event log cleanup (13) Form data cleanup (13) | Event log cleanup (14 / 15 / 16) Form data cleanup (14 / 15 / 16) |
Verification
- Confirm that all required features and services are present in your project.
- Validate that your project builds and packages successfully.
- Deploy to a test environment in Bloomreach Cloud and verify application startup.
- Test key functionality, including content delivery, repository access, and CMS login.