FabricServer Technology Overview

1

Package, Deploy and Manage Enterprise Applications on Package, Deploy and Manage Enterprise Applications on Physical, Virtual or Cloud-Based EnvironmentsPhysical, Virtual or Cloud-Based Environments

FabricServerFabricServer

2

FabricServer

• FabricServer is management software used to package, deploy and manage enterprise applications on physical, virtual or cloud based datacenter environments

• FabricServer extends the principles of DataSynapse’s market leading Grid computing platform:

- Shared and dynamic infrastructure- Automated application packaging and deployment- Built in application resiliency and failover

• And adds support for virtualization, utility and cloud computing for enterprise applications based on standard development platforms (e.g. JEE, Microsoft apps, etc..)

• Benefits of using FabricServer:- Lowering application time to deploy for complex enterprise applications- Lowering infrastructure costs, through improved utilization of data center resources- Improving application performance against SLAs- Driving adoption of virtualization (e.g VMware) and external cloud models (e.g. EC2)

3

FabricServer - Basics

FabricServer

Package OncePackage Once

FabricServer provides tools and templates required to build

self-contained, runnable packages of applications and platforms

Platforms Packaged Legacy

Tools

Self-ContainedPackages

ConfigurationInformation

FabricServer

Run AnywhereRun Anywhere

FabricServer manages those packages and can activate on any runtime environment (physical,

virtual, cloud)

CloudsVirtualPhysical

Automated Deployment

ServiceRepository

Run-TimeBroker

PolicyEngine

Manage RuntimeManage Runtime

FabricServer allows production support teams to create policies

for how applications will be managed at run time

CloudsVirtualPhysical CloudsVirtualPhysical

FabricServerService

Repository

Run-TimeBroker

PolicyEngine

FabricServerService

Repository

Run-TimeBroker

PolicyEngine

Closed Loop Policy-Based

Allocationof Infrastructure

4

Run-Time Architecture

FabricServerBroker

FailoverFabric Broker

Shared Pool of FabricServer HostsShared Pool of FabricServer Hosts

Daemon

• Monitors host & spawns one or more engines

• 1 per physical host)

Engine• Manages application instances• Isolates applications on hosts• 1 or many per physical host

Component

• A application component instance• Multiple components = application• 1 per engine

< HTTPS >

VM

VM

VM

Engines are only started as needed

Engines can be deployed to physical or virtual servers

The entire stack of an enterprise app will typically be distributed across different engines

Bare Metal Server

ApplicationPlatform

Operating System

DataSynapseEngine

DataSynapseEngine

Virtual Machine –VMware

Virtual Machine –VMware

App SpecificConfiguration

Application Code

App SpecificConfiguration

Application Code

5

Brokers and Engines

• 100% server based Java Application• Runs on Windows, Solaris, HPUX, AIX and most Linux

distros• Requires a standard J2SE

FabricServerBroker

Operations Dashboard

Application Component and

Library (with SDK)

PolicyManager

Auditing and Logging Allocation Engine

Statistics ManagerReal

-tim

e Sy

stem

s Mon

itor

Security Manager

DataSynapseEngine

• Runs on Windows, Solaris, and most Linux distros

• Started and managed by an agent that runs on the host called the Engine Daemon.

- Daemon starts and stops engine instances based on Policy

- Engine Daemon starts Engine instances, monitors them and restarts them if there are failures or reconfigurations

• DataSynapse Engine:- Starts/stops/monitors

applications in other processes- More than one engine instance

can run per host

FabricServerBroker

Host

Engine Daemon

Engine Instance

< HTTPS >

6

FabricServer ToolsDataSynapse Studio:

• An eclipse based UI for infrastructure architects to design and build application infrastructure templates

Key Features:

• Graphical and command line tools simplify creating and updating FabricServer artifacts

•Wizards and structured XML file editing ease the creation of components and configuration templates

• Libraries can be easily compared and modified

• Applications can be smoke tested within Studio before deploying to a full FabricServer environment

FabricServer UI:• A web application UI for

production support personnel to manage and monitor a FabricServer environment

Key Features:

• Create and activate policies and schedules

•Monitor and manage all applications running on FabricServer

•Manage utility environment and configuration

• Diagnose, log, and configure complex systems

7

Pre-Built Artifacts

Containers: - The controlling logic for the application server environment that configures, starts,

monitors, and shuts down the processes. - SDK that enables you to create your own containers

Distributions:- The application component run-time “Golden Image” packaged

as a single image- These images contain no DataSynapse code or modifications to

the vendor package

FabricServer Repository

Distributions

Containers

Components

…

… SDK

…

Components:- The app deployment artifacts, platform configuration, and runtime

context required to run anywhere in a FabricServer environment

Applications:- Collection of components that make up an application, e.g. WAS

Deployment manager, Cluster of managed servers, MQSeries

8

Supported Containers

Supported Containers- Full production support for existing releases- New releases are shipped with core DataSynapse

product release- Updates to ISV application are supported

within 9 months- Licensed and charge as per standard price list

Vendor Product Version

Oracle / BEA WebLogic 8.1, 9.x, 10.x

IBM WebSphere 6.1

Microsoft IIS 5 & 6

JBoss J2EE Server 4.0.2 , 4.2.1

Apache Tomcat 5.x

Command Line Container N/A N/A

Shared Source Containers- “Starting point” for developing a custom container - Source code shared in an online code repository- Updates and maintenance provided on SOW basis- No software license, no software license charge

Vendor Product Version

Actuate iServer V8

JReport Enterprise Server 7

Cognos ReportNet 8.1. and 8.2

Cognos BI 8.2

Hyperion BI 9.2.01

Oracle BI EE 10.3.2.1

Business Objects XI R2

Composite InformationServer 3.7.1

Informatica PowerCenter 8.1.1

Documentum Content Server 5.3

GigaSpaces Cache 5.2

GemStone GemFire Server 1.0

Coherence Data Grid 3.3

9

..

Using FabricServerUsing FabricServer

10

Packaging Templates in FabricServerFabricServer provides tools and templates required to build self-contained packages of enterprise applications:

FabricServer

Distributions

Containers

Configuration Data

…

… SDK

…

•Architect uses the pre-built containers and distros that correspond to the components and services of his architecture

•He adds in the specific configuration information for his architecture

•Uses build capabilities in DataSynapse Studio to create a new template

•Templates are stored in FabricServer

Application Architecture

JEE Web Cluster

Templates

JMS Server

…

Infrastructure Architect

Studio

11

Bare Metal Server

ApplicationPlatform

Operating System

DataSynapseEngine

Virtual Machine – VMware

App SpecificConfiguration

Application Code

Adding Application Code to Template

• Developers use their standard deployment tools to deploy and configure application

• Utility captures all configuration changes and generates self contained package

• FabricServer manages the package and can provision it to any runtime environment (physical, virtual, cloud)

StandardTemplates

JMS Service

Admin Server

JEE Web Cluster

FabricServer

Run-TimeBroker

PolicyEngine

ServiceRepository

ApplicationDeveloper

Self-Contained Package

12

Deploying Applications with FabricServer

CloudsVirtualPhysical

FabricServerService

RepositoryRun-Time

BrokerPolicyEngine

• FabricServer stores and manages self-contained packages

• FabricServer can provision it to any runtime environment (physical, virtual, cloud)

• Self contained packages contain all of the information pertaining to servers, versions, customizations, and applications

• Users create deployment policies in FabricServer which tells the system:

- What templates to use - What application code to use- What environment to deploy

on (physical / virtual/ cloud)- How much infrastructure is

required- Performance metrics

Automated Deployment

13

FabricServer Deployment Policies

• Fabric administrators configure policies that dictates how Fabric Broker should provision applications

• Policy Manager contains a list of policies and a schedule, which specifies which policy should be active at any given time

Deploying Applications – users can create policies that have all of configuration data required to deploy enterprise applications:

- Allocation Rules– Min / max infrastructure (how many cpus/processes?)

- Deployment Preferences – class of machine (eg. X86 blade, dual core), OS (Windows, Linux), etc..

- Prioritization – which applications are more business critical than others

- Service Levels – rules for monitoring performance and how new clustered instances should be added / deleted based on throughput or other metrics

14

Upgrading / Versioning Applications

FabricServerService

RepositoryRun-Time

BrokerPolicyEngine

CloudsVirtualPhysical

• FabricServer manages all of the components and applications that it stores

• If a new version is uploaded to the broker, FabricServer will update all the deployments automatically and / or allow you to run versioned services in parallel for testing / comparison

Bare Metal Server

ApplicationPlatform

Operating System

DataSynapseEngine

Virtual Machine – VMware

App SpecificConfiguration

Application Code

ApplicationDeveloper

New Release

AutoUpgrade

Version

15

Deploying Applications Into VMware

Physical Machine

Virtual Machine

Operating System

Engine

1. Decompose the entire software stack – OS, Infrastructure Platform, Application2. FabricServer detects the need for a new VM when application policy is activated 3. FabricServer makes call to VI3 to start a new, OS specific, VM with a DS engine 4. FabricServer provisions and configures the application in the newly started VM5. Application processes are activated and monitored

VMware VI3

VI SDK

VMware Virtual Center

FabricServer

ServiceRepository

Run-TimeBroker

PolicyEngine

Template Code

16

Managing Applications at Run-Time

•FabricServer ships with all the tools required for supporting production applications and infrastructure. Typically application support teams will use the FabricServer UI for:

•Operations quick view•Drill down capabilities•Align priorities•Charting and trends•Measuring SLA metrics:

- Application usage- Throughput- Response time- CPU utilization- Memory

17

Logging and Reporting

• FabricServer logs Broker and Engine activity, also containers and applications write log files that can be accessed through FabricServer.

• FabricServer creates three kinds of log files: - Broker Logs –

• Log information from many Broker component including Engine login to the Broker and allocation of Engines to Applications, startup information including any exceptions raised in case of problems during startup and exceptions raised during normal system operation

- Engine Logs – • Log information about the operation of particular Engines including startup, their

attempts to run Containers and Applications, as well as the statistics they report.- Application Logs –

•May be provided by some Domains or applications, data and format vary and are determined by the particular application.

18

Advanced Policies – SLA Management

• As part of the packaging model in FabricServer applications are instrumented to publish performance metrics

• Application support teams can create policies that allocate / de-allocate infrastructure to a specific application based on the metrics that the app publishes to FabricServer

• This closed loop model – enables support teams to build out shared pools of servers that expand and contract application footprint dynamically based on real time metrics

CloudsVirtualPhysical CloudsVirtualPhysical

FabricServerService

Repository

Run-TimeBroker

PolicyEngine

FabricServerService

Repository

Run-TimeBroker

PolicyEngine

Closed Loop Policy-Based Allocation of Infrastructure

SystemMetrics

ProvisionApplications

19

..

Questions ?Questions ?