alfresco large scale enterprise deployments

Large Scale DeploymentsScalability and Reliability

Paul HamptonDirector of Product Marketing

Alfresco

Introduction

● Alfresco provide enterprise scale Content Management

● Many moving partso Application server

o Database

o Index stores

o Content stores

o Application

● Multiple points for potential failure

2

Single System Install

● Simple install

● Installs everything on one system

3

Share

EHCache

Tomcat

Co

nte

nt

Sto

re

Ind

ex

Da

taB

ase

Content storeDatabase

App Server

What Needs to be Clustered?

● Application Server

● Content Stores

● Databases

● The Application

● Note:

o Each server must have its own index

o EHCache must be synchronised between all servers

4

Share

EHCache

Tomcat

Co

nte

nt

Sto

re

Ind

ex

Da

taB

ase

Clustered Alfresco

● Clustered Alfresco serverso Share database and content

store

● Load balancer distributes load between servers

● Point of failureo Application Server o Database o Content store

5

Share

EHCache

Tomcat

Ind

ex

Share

EHCache

Tomcat

Ind

ex

Co

nte

nt

Sto

re

Da

taB

ase

Load Balancer

Can make use of high availability disk (i.e. SAN storage)

Replicated Content Stores

● Used to synchronise content between content stores

● Supports two modes

o Inbound

o Outbound

● Point of failureo Application Server o Database o Content store

6

Load Balancer

SecondaryContent

Store

Share

EHCache

Tomcat

Co

nte

nt

Sto

re

Ind

ex

Share

EHCache

Tomcat

Co

nte

nt

Sto

re

Ind

ex

Database

ReplicatingContent

Store

ReplicatingContent

Store

Example – Inbound

● Content is copied on read

● Pulls content from secondary content store when needed

7

Load Balancer

SecondaryContent

Store

Share

EHCache

Tomcat

Co

nte

nt

Sto

re

Ind

ex

Share

EHCache

Tomcat

Co

nte

nt

Sto

re

Ind

ex

Database

ReplicatingContent

Store

ReplicatingContent

Store

1

2

3

4

?5

6

7

Example – Outbound

● Content is copied on write

● Push content from primary store to secondary store

● Synchronous or Asynchronous

8

Load Balancer

SecondaryContent

Store

Share

EHCache

Tomcat

Co

nte

nt

Sto

re

Ind

ex

Share

EHCache

Tomcat

Co

nte

nt

Sto

re

Ind

ex

Database

ReplicatingContent

Store

ReplicatingContent

Store

1

2

3

45

?6

7

Database Clustering

● Use native DB clustering

● This is specific to the DB and OS

● Two options:

o Master / Slave

o Master / Master

9

Load Balancer

SecondaryContent

Store

Share

EHCache

Tomcat

Co

nte

nt

Sto

re

Ind

ex

Share

EHCache

Tomcat

Co

nte

nt

Sto

re

Ind

ex

Database

ReplicatingContent

Store

ReplicatingContent

Store

Database(Master)

Database(Slave)

Fallover

Database Clustering

Application Clustering

● Point of failureo Application Server o Database o Content store

● How to address scalability

10

Share

Tomcat

Share

Tomcat

Load Balancer

What About Scalability?

11

Share

Tomcat

Share

Tomcat

Load Balancer

JMX Administration

● Use standard JMX tools to access configuration settings

o Stop, Configure and Start Subsystems

● Monitor

o Database connections

o Memory usage

o Alfresco Subsystems

12

Configuration Synchronisation

● Use JMX to change configuration settings

● Settings are saved to Database

● Settings are synchronised to other Alfresco servers

13

Load Balancer

SecondaryContent

Store

Share

EHCache

Tomcat

Co

nte

nt

Sto

re

Ind

ex

Share

EHCache

Tomcat

Co

nte

nt

Sto

re

Ind

ex

Data base

ReplicatingContent

Store

ReplicatingContent

Store

Summary

● Alfresco has been designed to be...o Scalable

o Reliable

● Multiple options ● Enterprise Edition configuration tools simplify

configuration● More Information

o WIKI – Cluster Configuration

o Docs – Administering an Alfresco ECM Production Environment (page 158)

14

Questions?

16