compromIsos fInAncIeros

To have greater flexibility in modeling the physical operational model, we separate the components as far as possible and place them on a number of different logical nodes, as show in Table 7-1. Sometimes we must separate the data aspect of a component from its execution aspect because the data can (and will be) stored on a different node. Because of the needed systems management functionality, we introduced additional logical nodes that do not host application functionality.

Table 7-1 Mapping components to logical nodes

Node Components

LN1 Gateway C11 Web-Frontend C12 Gateway LN2 Reporting C13 Dispatcher

C15 Reporting (execution aspect) C16 Data Access

LN3 Content Manager C13 Dispatcher

C14 Content Manager (execution aspect) LN4 Metadata C14 Content Manager (data aspect)

C15 Reporting (data aspect: reports) LN9 Modeling Client C10 Modeling Client

LN11 Deployment Manager This node is introduced because of WebSphere administration purposes

LN12 SM Presentation This node is introduced for presentation purposes for systems management functionality

LN13 SM Monitoring C23 Cloud Provisioning

plus additional systems management components LN21 Onboarding C21 Onboarding-Frontend

C22 Onboarding (execution aspect) C24 Authentication

C25 Notification: This component is not used because we do not integrate into an existing email-infrastructure

7.1.1 Overview of the logical operational model

The logical operational model follows the three-tier architecture of Cognos consisting of a data, application, and presentation tier, as documented in the online documentation at:

http://publib.boulder.ibm.com/infocenter/c8bi/v8r4m0/index.jsp For a quick overview, visit the following site:

http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP101437 We added an additional tier for the human actors and grouped the nodes into three submodels:

򐂰 The

Onboarding Application

contains the nodes and actors necessary to perform the onboarding process.

򐂰 The

Reporting

is the core piece of the Smart Analytics Cloud environment that delivers the reporting functionality and access to the data sources that are needed.

򐂰 The

System Management

collects all nodes that are needed to administer and monitor the solution. Because these nodes interact with every other node in the architecture, the connections are not drawn.

Depending on the different possibilities you have when you advance from the logical to the physical operational model, you deploy these submodels in separate ways (7.2.4, “Multiple deployment environments” on page 83). We reused the actors, as defined section 5.2, “System context of the Smart Analytics Cloud” on page 50.

Figure 7-1 Logical operational model

7.1.2 Node description

In this section, we describe the nodes of the logical operational model. For each node we give an overview of the installed software and functional components and their non-functional requirement characteristics.

As a reference, we list the needed software products but provide more about them in section 7.3, “Physical operational model” on page 84 and in Part 4, “Implementation” on page 135.

LN1 Gateway

The gateway is the entry point for every user of the Smart Analytics Cloud. It manages all web communication for the IBM Cognos 8 Platform. The workload on the IBM Cognos 8 Gateway server is comparatively lightweight; therefore, it requires minimal processing resources. Because we are running a high-available cloud, we deploy multiple redundant gateways with an external HTTP

The gateway consists of the following software:

򐂰 Web server: IBM WebSphere HTTP Server

򐂰 Application server: IBM WebSphere Application Server Network Deployment

򐂰 IBM Cognos Gateway

򐂰 IBM Tivoli Monitoring for O/S

򐂰 ITCAM for WebSphere

򐂰 ITCAM for HTTP Server

The non-functional requirements of this node are determined by the Cloud User actor.

LN2 Reporting

This node hosts the reporting engine of IBM Cognos 8 and the needed additional software and consists of the following software:

򐂰 Database management client: IBM DB2

򐂰 Application server: IBM WebSphere Application Server Network Deployment 򐂰 Reporting engine: IBM Cognos Report Server running on the application

server

򐂰 IBM Cognos Dispatcher

򐂰 IBM Tivoli Monitoring for O/S

򐂰 ITCAM for WebSphere

The non-functional requirements of this node are determined by the node

LN1

Gateway

.

LN3 Content Manager

The main service of this node is to manage the storage of customer application data, including security, configuration data, models, metrics, report

specifications, and report output. The Content Manager is needed to publish models, retrieve or store report specifications, handle scheduling information, and manage the Cognos name space. The Content Manager maintains its information in the databases on node

LN4 Metadata

. It consists of the following software:

򐂰 Database management client: IBM DB2

򐂰 Application server: IBM WebSphere Application Server Network Deployment

򐂰 Content management system: IBM Cognos Content Manager running on the

application server

򐂰 IBM Tivoli Monitoring for O/S

The non-functional requirements of this node are determined by the node

LN1

Gateway

.

LN4 Metadata

This node stores the queries and content of the reporting engine and the content management and consists of the following software:

򐂰 Database management system: IBM DB2

򐂰 Database for the queries 򐂰 Database for additional content 򐂰 IBM Tivoli Monitoring for DB2 򐂰 IBM Tivoli Monitoring for O/S

The non-functional requirements of this node are determined by the nodes

LN2

Reporting

and

LN3 Content Management

.

LN9 Modeling Client

This node is necessary to use the IBM Cognos 8 Framework software. It consists of the IBM Cognos Framework Manager software.

The non-functional requirements of this node are determined by the

Cloud

Power User

actor.

LN11 Deployment Manager

This is an administrative node that manages all application servers of the application tier. It consists of the following software:

򐂰 Application server: IBM WebSphere Application Server Network Deployment 򐂰 IBM Tivoli Monitoring for O/S

The non-functional requirements of this node are determined by the necessity to change the application server configuration.

LN12 SM Presentation

The Tivoli Systems Management functions use a centralized presentation node for user access. It consists of the Portal: Tivoli Enterprise Portal Server (TEPS) software.

LN13 SM Monitoring

This node hosts a number of systems management components for managing the Smart Analytics Cloud. This node collects monitoring data from the agents on the other nodes and stores it in the monitoring database.

This node consists of the following software:

򐂰 Database management system: IBM DB2 Universal Database™

򐂰 Monitoring Server: Tivoli Enterprise Monitoring Server (TEMS) 򐂰 Monitor Warehouse: Tivoli Monitoring Data Warehouse (TDW) 򐂰 Provisioning: Tivoli Provisioning Manager (TPM)

򐂰 Directory: Tivoli Directory Server (TDS)

LN21 Onboarding

This node holds the necessary execution parts of the onboarding application. The onboarding application is a self-service application that gains access to the cloud and registers a new application into the cloud. The data is stored in the node

LN22 Onboarding Data

. It consists of the following software:

򐂰 Application server: IBM WebSphere Application Server Network Deployment 򐂰 Web forms framework and the onboarding application

򐂰 ITCAM for WebSphere

The non-functional requirements of this node are determined by the

Cloud

Application Manager

actor.

LN22 Onboarding Data

This node holds the application data and metadata of the onboarding application. It consists of the following software:

򐂰 Database management system: IBM DB2

򐂰 The database for web forms framework 򐂰 The database of the onboarding application 򐂰 IBM Tivoli Monitoring for DB2

򐂰 IBM Tivoli Monitoring for O/S

The non-functional requirements of this node are determined by the node

LN21

Onboarding

.

In document memoria anual 2012 ener S G ae 2012 al anu memoria (página 168-173)