alga
Sep 11, 2009
  6985
(0 votes)

A bit more information about the different EPiServerMail 4.4 / 4.4 SP1 installation options

1) Install EPiServer Community Integration

Target platform - CMS (5.1.422.256 or later) + Mail Module + Community Module (3.2 or later)

This installs components which allow EPiServerMail to interact with EPiServer's Community Module.  It provides support for:

  1. sending mail to users in EPiServer Community with a specific set of attributes;  and
  2. sending mail to users in EPiServer Community selected by a User Search.

It installs no databases and makes no database changes.

2) Install Mail on Existing Site

Target platform EPiServer - CMS (5.1.422.256 or later) with or without Community Module. Important: EPiMail 4.3 or earlier must be uninstalled before choosing this installation (see Uninstalling EPiServerMail 4.3).

This installs all components required for EPiServerMail to work. As certain components are shared between EPiServerMail and the Community Module, a new separate database with required tables and stored procedures will automatically be installed for EPiServerMail if the Community Module is not already installed.

3) Install EPiServer Mail without database (When you are mirroring)

Target platform EPiServer - Load balanced environments, with a single database with tables and stored procedures which support the needs of EPiServerMail.

This installs all components required for an EPiServerMail instance to work. By itself it installs no databases and makes no database changes.

4) Install SQL Server Database

Target platform EPiServer - Multiple instances of EPiServerMail in a load balanced environment, without a suitably configured database.

This installs the database, along with database tables and stored procedures which support the needs of one or more EPiServerMail instances.

Sep 11, 2009

Comments

Please login to comment.
Latest blogs
Opti ID overview

Opti ID allows you to log in once and switch between Optimizely products using Okta, Entra ID, or a local account. You can also manage all your use...

K Khan | Jul 26, 2024

Getting Started with Optimizely SaaS using Next.js Starter App - Extend a component - Part 3

This is the final part of our Optimizely SaaS CMS proof-of-concept (POC) blog series. In this post, we'll dive into extending a component within th...

Raghavendra Murthy | Jul 23, 2024 | Syndicated blog

Optimizely Graph – Faceting with Geta Categories

Overview As Optimizely Graph (and Content Cloud SaaS) makes its global debut, it is known that there are going to be some bugs and quirks. One of t...

Eric Markson | Jul 22, 2024 | Syndicated blog

Integration Bynder (DAM) with Optimizely

Bynder is a comprehensive digital asset management (DAM) platform that enables businesses to efficiently manage, store, organize, and share their...

Sanjay Kumar | Jul 22, 2024

Frontend Hosting for SaaS CMS Solutions

Introduction Now that CMS SaaS Core has gone into general availability, it is a good time to start discussing where to host the head. SaaS Core is...

Minesh Shah (Netcel) | Jul 20, 2024

Optimizely London Dev Meetup 11th July 2024

On 11th July 2024 in London Niteco and Netcel along with Optimizely ran the London Developer meetup. There was an great agenda of talks that we put...

Scott Reed | Jul 19, 2024