Table of Contents

1        INTRODUCTION        

2        LOGICAL PERSPECTIVE OF THE SYSTEM        

3        SERVER CONFIGURATION        

3.1        Hardware Infrastructure        

3.1.1        Application Layer        

3.1.2        Content Layer        

3.1.3        Database Server Layer        

3.1.4        Shared Storage        

4        CORRELATION OF HARDWARE RESOURCES AND THROUGHPUT        

5        SOFTWARE & DIRECTORY STRUCTURE        

TABLE OF FIGURES

Figure 1: Logical separation of the PLAN-JO system        

Figure 2: The Documentum Repository        

Figure 3: Directory structure        

LIST OF TABLES

Table 1: User/Workload profile        

Table 2: Workload-Specific Criteria        

Table 3: Document profile        

Table 4: Platform profile        

Table 5: System output sizing        

Table 6:  Software components        

1. 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 system’s throughput in terms of hardware resources/load are provided.

2. 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

3. 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:

• 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;

1. 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 Plan-JO (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:

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

1. 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

2. 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. Shared Storage

The existing optical EMC2 already available at the Publications Office’s 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.

4. Correlation of Hardware resources and Throughput

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

Table 1: User/Workload profile

The next table presents the expected workload specific criteria per component

Table 2: Workload-Specific Criteria

Table 3: Document profile

Table 4: Platform profile

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

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 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.

5. 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.

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.

The following figure represents the organisation of the filesystem:

 Figure 3: Directory structure