HARDWARE ARCHITECTURE

DOCUMENT

Project / Subproject:

PLAN-JO No. 10030

Reference Number / Version:

D.HAD / 0.07

PLAN JO RELEASE 1
Hardware Architecture Document
Version 0.07
22/12/2006

Issue Date:

Document File Name:

Page:

22/12/2006

239161723.doc

1 of 14

HARDWARE ARCHITECTURE
DOCUMENT

Project / Subproject:

PLAN-JO No. 10030

Reference Number / Version:

D.HAD / 0.07

Table of Contents
1

INTRODUCTION.................................................................................................................................................................8

LOGICAL PERSPECTIVE OF THE SYSTEM................................................................................................................9

SERVER CONFIGURATION..............................................................................................................................................9
3.1
Hardware Infrastructure................................................................................................................................................10
3.1.1
Application Layer..................................................................................................................................................10
3.1.2
Content Layer........................................................................................................................................................11
3.1.3
Database Server Layer..........................................................................................................................................11
3.1.4
Shared Storage.......................................................................................................................................................11

CORRELATION OF HARDWARE RESOURCES AND THROUGHPUT.................................................................11

SOFTWARE & DIRECTORY STRUCTURE..................................................................................................................16

Issue Date:

Document File Name:

Page:

22/12/2006

239161723.doc

2 of 14

HARDWARE ARCHITECTURE
DOCUMENT

Project / Subproject:

PLAN-JO No. 10030

Reference Number / Version:

D.HAD / 0.07

TABLE OF FIGURES
Figure 1: Logical separation of the PLAN-JO system.................................................................................................9
Figure 2: The Documentum Repository.....................................................................................................................10
Figure 3: Directory structure.....................................................................................................................................17

Issue Date:

Document File Name:

Page:

22/12/2006

239161723.doc

3 of 14

HARDWARE ARCHITECTURE
DOCUMENT

Project / Subproject:

PLAN-JO No. 10030

Reference Number / Version:

D.HAD / 0.07

LIST OF TABLES
Table 1: User/Workload profile.................................................................................................................................11
Table 2: Workload-Specific Criteria..........................................................................................................................12
Table 3: Document profile.........................................................................................................................................13
Table 4: Platform profile...........................................................................................................................................14
Table 5: System output sizing....................................................................................................................................15
Table 6: Software components.................................................................................................................................16

Issue Date:

Document File Name:

Page:

22/12/2006

239161723.doc

4 of 14

HARDWARE ARCHITECTURE
DOCUMENT

Project / Subproject:

PLAN-JO No. 10030

Reference Number / Version:

D.HAD / 0.07

Introduction

This document provides the proposed hardware architecture of the PLAN-JO system. The document presents a
configuration based on existing hardware of the Publications Office. It is based on the SUN Fire SFx800
architecture, using one physical server. Additionally, the logical perspective is provided as well. Finally estimates of
the systems throughput in terms of hardware resources/load are provided.

Issue Date:

Document File Name:

Page:

22/12/2006

239161723.doc

5 of 14

HARDWARE ARCHITECTURE
DOCUMENT

Project / Subproject:

PLAN-JO No. 10030

Reference Number / Version:

D.HAD / 0.07

Logical Perspective of the System

The figure below illustrates an abstract view of the logical system distribution:

Internal Users: These users of the PLAN-JO system are located in the Publications Office premises
(Receptionist, PPA, PPC, etc.); they use the intranet. Their interface to the application is going to be based
on the Documentum Webtop/Desktop.
Internal Systems: Internal Systems interfacing/intergrading with PLAN-JO (Financial system, OJ-Format,
Ceres).
External Users: Remote Publications Office users (authors, printers). They will access the system through
the Webtop.
External Systems: External Systems interfacing with PLAN-JO (Authors production application).

Figure 1: Logical separation of the PLAN-JO system

Server Configuration

Utilising the hardware already available at OPOCE , the proposed configuration/solution is to use a SUN Fire
SFx800 server and assign resources to each layer using the Solaris Resource Manager. The advantages of this
configuration can be summarised as follows:
Issue Date:

Document File Name:

Page:

22/12/2006

239161723.doc

6 of 14

HARDWARE ARCHITECTURE
DOCUMENT

Better Return of Investment;

Less cost than the clustered solution;

Better redundancy than the separate machine configuration;

Easier maintenance than the cluster solution;

Less effort to set up;

3.1

Project / Subproject:

PLAN-JO No. 10030

Reference Number / Version:

D.HAD / 0.07

Hardware Infrastructure

The layers that constitute the system should be initially identified before distributing the available hardware
resources between them. The first layer is the Application server, which will provide the Webtop interface to the
clients. Furthermore, it can support any other enterprise components that will be developed with respect to the PlanJO (e.g EJBs, JMS for the DEMED integration etc.). The next layer is the Content server. The Content server
provides resources for the DocBroker and mediates all the requests of the Webtop to the Repository. The Repository
conceptually consists of three distinct parts. The first one is the file repository itself, which will be hosted on the
Content server and the metadata repository which will be stored in the Database server. Finally, the third part is the
Indexes store. It holds all the indexes that will be build on the documents and they are used for the search capabilities
of the system. A detailed illustration of the Repository is provided below:

Figure 2: The Documentum Repository

To provide the necessary resources for the above components, it is proposed to use two boards in a Sunfire SF4800
or SF6800 enclosures. Each one of the boards will have the following characteristics:

4 CPUs Ultra Sparc IV+ running at 1.5 GHz

4x8MB Ecache

4 banks of 2GB memory options (16 x 512MB DIMMs, 8GB total for the board)

It is proposed to separate the resources as presented below:

3.1.1

Application Layer

The application Layer will run the web tier, Webtop. The following resources should be allocated to it:

2 CPUs Ultra Sparc IV+ running at 1.5 GHz

2x8MB Ecache

8GB of RAM
Issue Date:

Document File Name:

Page:

22/12/2006

239161723.doc

7 of 14

HARDWARE ARCHITECTURE
DOCUMENT
3.1.2

Project / Subproject:

PLAN-JO No. 10030

Reference Number / Version:

D.HAD / 0.07

Content Layer

The following resources should be allocated to the Content Layer :

4 CPUs Ultra Sparc IV+ running at 1.5 GHz

4x8MB Ecache

16GB of RAM

3.1.3

Database Server Layer

The following resources should be allocated to the Database Server Layer :

2 CPUs Ultra Sparc IV+ running at 1.5 GHz

2x8MB Ecache

8GB of RAM

3.1.4

Shared Storage

The existing optical EMC2 already available at the Publications Offices premises will be used for storage.
Details regarding the throughput of the configuration in conjunction with the system workload and the documents
profile is provided in the next section.

Correlation of Hardware resources and Throughput

This section provides a preliminary estimate of the systems throughput with respect to the available system
resources. All the data are calculated using Documentums Sizing Tool. The following table presents the expected
user/workload profile:

User/Workload Profile
User Profile
Heavy Users
Light Users
%Heavy Users Active
%Light Users Active
Heavy Users/Busy hour
Light users/Busy hour
Total Users/Busy hour
Estimated % Growth of
Users Per Year
Level of Customization
Workflow Intensive

Web
Publisher 5.3
0
0
0%
0%
0
0
0

Portal
5.3
0
0
0%
0%
0
0
0

Webtop 5.3 &

Forms 5.3
100
50
40%
10%
40
5
45

DCM
5.3
0
0
0%
0%
0
0
0

Desktop 5.3
0
0
0%
0%
0
0
0

0%
None
Yes

0%
None
Yes

10%
None
Yes

0%
None
Yes

0%
None
Yes

Table 1: User/Workload profile

The next table presents the expected workload specific criteria per component

Workload-Specific

WDK/Webtop based Applications

BPM

Issue Date:

Document File Name:

Page:

22/12/2006

239161723.doc

8 of 14

DAM
5.3
0
0
0%
0%
0
0
0
0%
None
Yes

HARDWARE ARCHITECTURE
DOCUMENT

Project / Subproject:

PLAN-JO No. 10030

Reference Number / Version:

D.HAD / 0.07

Criteria
Web Publisher 5.2.5
Max Rendition
Queueing time (secs)
CIS Enabled?
Change Set processing
during peak hours
Index page regeneration
during peak hours
Content Server
Number of custom
types
Number of CS
Instances per machine

Session Pooling Enabled

15
Yes

Classic or Streamline

Yes

Clustered App Server

Yes

Peak Fulltext Queries /min

Extended HTTP Timeout

Yes
Classic
No

Peak Manual Activities per min

300

Automatic Activities per hour

600
100

BPS messages per hour

No
0

Portal 5.2.5

20
1

Operations per user per hour

60

Components per page

Table 2: Workload-Specific Criteria

Issue Date:

Document File Name:

Page:

22/12/2006

239161723.doc

9 of 14

HARDWARE ARCHITECTURE
DOCUMENT
Content Loading
CPU Input
Loading days per year

Document Profile
Content Profile
Num of Original
Source
Documents: Yr 1
Estimated
Average Size
(kbytes)

Project / Subproject:

PLAN-JO No. 10030

Reference Number / Version:

D.HAD / 0.07

Num. of Docs/Day
170.016

20

** Do not include these

documents

24

in the profile
below.

Content Input
Window (hrs)
118

Num. AutoWF
Tasks per Doc

Avg. Versions per

Document
Average
Additional
Renditions

Average Size (Kb)

Document or Media
Transformation
Services?

DTS

Renditioning Priority

ASAP

15

Full Text Indexing

None

Custom Attribute
size per Doc
(kbytes)
Number of
Custom Attributes
Document
Sizes(kb):

170

Numbe
r of
New
Docs
Per
Year

Avg. # of
Add'l
Rend.

Avg. Rend.
Size
(% of Orig)

Average
# of
Version
s

154.56
0
7.728
7.728

1
1
1

30%
50%
0%

6
6
6

Yes
Yes
Yes

Average
Size (KB)

Number
of Source
Docs in
First Year

% of All

Request
Media
Transformation?

100
100
500

154.560
7.728
7.728

91%
5%
5%

No
No
No

HTML/Web Pages

0%

No

40%

Yes

XML

0%

No

0%

No

Images

0%

No

20%

No

Contentless

0%

No

0%

No

MPEG

0%

No

15%

No

27%

6,0

Format/Input Type

Word
TIFF
PDF

Total
Weighted
Average

700

170016

100%

118

1
70.016

Table 3: Document profile

Issue Date:

Document File Name:

Page:

22/12/2006

239161723.doc

10 of 14

Content
to be FT
Indexed

HARDWARE ARCHITECTURE
DOCUMENT

Project / Subproject:

PLAN-JO No. 10030

Reference Number / Version:

D.HAD / 0.07

Platform Profile Information

Years of Coverage for
Hardware
High Availability Needs
Database Server Type

3
none
Oracle

JVM version

1,4

Web-tier machines
Content Server
machines
Index Agent/Server
machines
RDBMS machines
CIS Server machines
Site Caching Services
Target machines
Document
Transformation
machines
PDF Aqua Server
machines
Media Transformation
Servers

CPUs per
server
2

MHz
1500

CPU type
SPARC

1500

SPARC

2
N/A
1

1500
1500
1500

SPARC
SPARC
SPARC

1500

SPARC

1500

SPARC

1500

SPARC

1500

SPARC

Table 4: Platform profile

Base on the above data the following estimates are deducted in terms of system sizing parameters:

System Sizing Output

User Profile Summary
User population after 3 years
Users/busy hour after 3 years
Number of Documents from all sources after 3
years

182
54
510.048
6.120.600

source
source + versions + rend.

Estimated Hardware Resource Summary

Output

CPUs

Content Server

Index Agent/Server
WDK/App Server (Web)

0
1

RDBMS Server

***

Memory (MB)
2.304

***

512

Disk
Space (MB)
441.4
92
-

Est. Disk
IOs/sec
3
0
6

1.5
7.424

68

12

6
Total for Servers

10.240

443.0

21

Issue Date:

Document File Name:

Page:

22/12/2006

239161723.doc

11 of 14

Project / Subproject:

HARDWARE ARCHITECTURE
DOCUMENT

PLAN-JO No. 10030

Reference Number / Version:

D.HAD / 0.07
60

Document Transformation Svr

CIS Server
Site Caching Serv. Target
PDF Aqua Server
Media Transformation Svr

2
0
0
0
0

Hardware Deployment Options

Option #1
Host-based (Web + Content Serv. +
FT + DB)
Option #2
Web Tier Server separate
Content Server/FT Index subsystem
combined
RDBMS separate
Option #3
Web Tier separate
Content Server separate
Index Agent / Index Server (Fulltext)
NAS device recommended for file
sharing
RDBMS separate

Other Servers
Document Transformation Service
PCs
PDF Aqua Servers
CIS Servers
Site Caching Services Targets
Media Transformation Servers
Notes

Note: These estimates are NOT adjusted for High Availability

Note: No single server machine should have less than 2 CPUs

(note: Not Adjusted for HA needs)

# of machines

CPUs/machine

1
1

2
3

1
1
1

2
2
0

1
1

2
0
0
0
0

1
1
1
1
1

WARNING: Fulltext Index Server CPU demands are greater than single node
configuration.
Table 5: System output sizing

It is a good sizing practice for the Index server to have four times the processing power of the Content server.
However, full text indexing is not required by Plan-JO specs. Thus a good estimate for the Index server is to have
twice the CPU power of the content server . Additionally, the users will work on the documents that they have
Issue Date:

Document File Name:

Page:

22/12/2006

239161723.doc

12 of 14

HARDWARE ARCHITECTURE
DOCUMENT

Project / Subproject:

PLAN-JO No. 10030

Reference Number / Version:

D.HAD / 0.07

checked out for quite a long time, consequently a huge database activity is not expected. So it is estimated that 2
CPUs should be allocated to DB, 4 CPUs to the layer of the Context and the Index Server and 2 CPUs to the
Application server layer.

Software & Directory Structure

The following table provides a preliminary deployment matrix of the software identified above. The final software
packages will be described in the Technical Specification document.

Node

Application
server

Java
Applicatio
n Server
JMS BEA
WebLogic
8.1 SP5
(Weblogic 9.2
is not certified
by
Documentum)

Operating
System

Solaris 10

Documentum Components

RDBMS

Documentum Webtop,
WDK,
Business Process Services,
Documentum Administrator
(Solaris, Version 5.3 SP3. This is the
exact version for these products )

Content
server

Solaris 10

DB server

Solaris 10

Documentum Content Server

(Solaris-Oracle, Version 5.3 SP3)

Oracle 10g Release 2

(10.2.0.1)

Table 6: Software components

Although this is beyond the scope of this guide, as details will be included in the D.RE1.001-IIN-Installation
Instructions, the following schematics provides the directory layout that will be used during the installation of the
required software packages.

Issue Date:

Document File Name:

Page:

22/12/2006

239161723.doc

13 of 14

HARDWARE ARCHITECTURE
DOCUMENT

Project / Subproject:

PLAN-JO No. 10030

Reference Number / Version:

D.HAD / 0.07

The following figure represents the organisation of the filesystem:

/applications
|
-- /planjo
|
-- /users
|
|
|
-- /system (to install by Publications Office)
|
|
|
|
|
-- /init.d
|
|
|
|
|
-- /...
|
|
|
|
|
|
-- /bea (link to /home/bea)
|
|
|
-- /oracle
|
|
-- /...
(if required - link to /home/...)
|
|
|
-- /planjo (if required - link to /home/planjo)
|
|
-- /xchange
|
-- /DEMED
|
|
|
-- /in

Start/stop scripts

oracle binaries

|
-- ... other interfaces ...
(The names of the different filesystems are in bold)

Figure 3: Directory structure

Issue Date:

Document File Name:

Page:

22/12/2006

239161723.doc

14 of 14