Deploy

Bloomreach Experience Manager requires several configuration tasks immediately after the first deployment to ensure secure and reliable operation.

Delivery tier virtual hosts are stored in the content repository and managed through the Console application.

Jackrabbit 2 uses a database-backed journal to coordinate cluster messaging, and the journal can grow over time as write operations increase.

Bloomreach Experience Manager stores all content and configuration in the repository database, so a daily backup of the entire repository database prevents data loss.

Authoring (cms) and delivery (site) web applications can run in separate containers when the deployment is not headless.

Large asset uploads in MySQL require increasing the maxallowedpacket variable to support larger files, but higher values can reduce performance.

PingFilter checks whether a cluster node is ready to handle traffic behind a load balancer.

Restricting access to /content/documents/administration requires changing the default authorization setup so the folder no longer matches the /hippo:configuration/hippo:domains/content domain and instead matches a new /hippo:configuration/hippo:domains/content-administration domain.

Bloomreach Experience Manager delivery tier includes four default users: configuser, liveuser, previewuser, and sitewriter.

Bloomreach Experience Manager (brXM) project distributions for production deployment may include H2 Database libraries that are not used in production.