FabricServer Technology Overview


Published on

DataSynapse FabricServer™ dynamically configures, activates and scales enterprise applications based on business policies and business demand. With FabricServer, IT organizations can focus on simplifying application management and deployment as drivers to increase operational efficiency and agility while reducing costs and complexity.

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • FabricServer Technology Overview

    1. 1. Package, Deploy and Manage Enterprise Applications on Physical, Virtual or Cloud-Based Environments FabricServer
    2. 2. FabricServer <ul><li>FabricServer is management software used to package, deploy and manage enterprise applications on physical, virtual or cloud based datacenter environments </li></ul><ul><li>FabricServer extends the principles of DataSynapse’s market leading Grid computing platform: </li></ul><ul><ul><li>Shared and dynamic infrastructure </li></ul></ul><ul><ul><li>Automated application packaging and deployment </li></ul></ul><ul><ul><li>Built in application resiliency and failover </li></ul></ul><ul><li>And adds support for virtualization, utility and cloud computing for enterprise applications based on standard development platforms (e.g. JEE, Microsoft apps, etc..) </li></ul><ul><li>Benefits of using FabricServer: </li></ul><ul><ul><li>Lowering application time to deploy for complex enterprise applications </li></ul></ul><ul><ul><li>Lowering infrastructure costs, through improved utilization of data center resources </li></ul></ul><ul><ul><li>Improving application performance against SLAs </li></ul></ul><ul><ul><li>Driving adoption of virtualization (e.g VMware) and external cloud models (e.g. EC2) </li></ul></ul>
    3. 3. FabricServer - Basics FabricServer Package Once FabricServer provides tools and templates required to build self-contained, runnable packages of applications and platforms Tools Self-Contained Packages Configuration Information Platforms Packaged Legacy FabricServer Run Anywhere FabricServer manages those packages and can activate on any runtime environment (physical, virtual, cloud) Clouds Virtual Physical Automated Deployment Service Repository Run-Time Broker Policy Engine Manage Runtime FabricServer allows production support teams to create policies for how applications will be managed at run time Closed Loop Policy-Based Allocation of Infrastructure
    4. 4. Run-Time Architecture FabricServer Broker Failover Fabric Broker Shared Pool of FabricServer Hosts Daemon <ul><li>Monitors host & spawns one or more engines </li></ul><ul><li>1 per physical host) </li></ul>Engine <ul><li>Manages application instances </li></ul><ul><li>Isolates applications on hosts </li></ul><ul><li>1 or many per physical host </li></ul>Component <ul><li>A application component instance </li></ul><ul><li>Multiple components = application </li></ul><ul><li>1 per engine </li></ul>< HTTPS > Engines are only started as needed VM VM VM Engines can be deployed to physical or virtual servers The entire stack of an enterprise app will typically be distributed across different engines
    5. 5. Brokers and Engines <ul><li>100% server based Java Application </li></ul><ul><li>Runs on Windows, Solaris, HPUX, AIX and most Linux distros </li></ul><ul><li>Requires a standard J2SE </li></ul>DataSynapse Engine <ul><li>Runs on Windows, Solaris, and most Linux distros </li></ul><ul><li>Started and managed by an agent that runs on the host called the Engine Daemon. </li></ul><ul><ul><li>Daemon starts and stops engine instances based on Policy </li></ul></ul><ul><ul><li>Engine Daemon starts Engine instances, monitors them and restarts them if there are failures or reconfigurations </li></ul></ul><ul><li>DataSynapse Engine: </li></ul><ul><ul><li>Starts/stops/monitors applications in other processes </li></ul></ul><ul><ul><li>More than one engine instance can run per host </li></ul></ul>Operations Dashboard Application Component and Library (with SDK) Policy Manager Auditing and Logging Allocation Engine Statistics Manager Real-time Systems Monitor Security Manager FabricServer Broker Host Engine Daemon Engine Instance < HTTPS >
    6. 6. FabricServer Tools <ul><li>DataSynapse Studio: </li></ul><ul><li>An eclipse based UI for infrastructure architects to design and build application infrastructure templates </li></ul><ul><li>Key Features: </li></ul><ul><li>Graphical and command line tools simplify creating and updating FabricServer artifacts </li></ul><ul><li>Wizards and structured XML file editing ease the creation of components and configuration templates </li></ul><ul><li>Libraries can be easily compared and modified </li></ul><ul><li>Applications can be smoke tested within Studio before deploying to a full FabricServer environment </li></ul><ul><li>FabricServer UI: </li></ul><ul><li>A web application UI for production support personnel to manage and monitor a FabricServer environment </li></ul><ul><li>Key Features: </li></ul><ul><li>Create and activate policies and schedules </li></ul><ul><li>Monitor and manage all applications running on FabricServer </li></ul><ul><li>Manage utility environment and configuration </li></ul><ul><li>Diagnose, log, and configure complex systems </li></ul>
    7. 7. Pre-Built Artifacts <ul><li>Containers: </li></ul><ul><ul><li>The controlling logic for the application server environment that configures, starts, monitors, and shuts down the processes. </li></ul></ul><ul><ul><li>SDK that enables you to create your own containers </li></ul></ul><ul><li>Distributions: </li></ul><ul><ul><li>The application component run-time “Golden Image” packaged as a single image </li></ul></ul><ul><ul><li>These images contain no DataSynapse code or modifications to the vendor package </li></ul></ul>FabricServer Repository Distributions Containers Components … … SDK … <ul><li>Components: </li></ul><ul><ul><li>The app deployment artifacts, platform configuration, and runtime context required to run anywhere in a FabricServer environment </li></ul></ul><ul><li>Applications: </li></ul><ul><ul><li>Collection of components that make up an application, e.g. WAS Deployment manager, Cluster of managed servers, MQSeries </li></ul></ul>
    8. 8. Supported Containers <ul><li>Supported Containers </li></ul><ul><ul><li>Full production support for existing releases </li></ul></ul><ul><ul><li>New releases are shipped with core DataSynapse product release </li></ul></ul><ul><ul><li>Updates to ISV application are supported within 9 months </li></ul></ul><ul><ul><li>Licensed and charge as per standard price list </li></ul></ul><ul><li>Shared Source Containers </li></ul><ul><ul><li>“ Starting point” for developing a custom container </li></ul></ul><ul><ul><li>Source code shared in an online code repository </li></ul></ul><ul><ul><li>Updates and maintenance provided on SOW basis </li></ul></ul><ul><ul><li>No software license, no software license charge </li></ul></ul>N/A N/A Command Line Container 5.x Tomcat Apache 4.0.2 , 4.2.1 J2EE Server JBoss 5 & 6 IIS Microsoft 6.1 WebSphere IBM 8.1, 9.x, 10.x WebLogic Oracle / BEA Version Product Vendor 3.3 Data Grid Coherence 1.0 GemFire Server GemStone 5.2 Cache GigaSpaces 5.3 Content Server Documentum 8.1.1 PowerCenter Informatica 3.7.1 Information Server Composite R2 XI Business Objects BI EE Oracle 9.2.01 BI Hyperion 8.2 BI Cognos 8.1. and 8.2 ReportNet Cognos 7 Enterprise Server JReport V8 iServer Actuate Version Product Vendor
    9. 9. . Using FabricServer
    10. 10. Packaging Templates in FabricServer <ul><li>FabricServer provides tools and templates required to build self-contained packages of enterprise applications: </li></ul>FabricServer Distributions Containers Configuration Data … … SDK … <ul><li>Architect uses the pre-built containers and distros that correspond to the components and services of his architecture </li></ul><ul><li>He adds in the specific configuration information for his architecture </li></ul><ul><li>Uses build capabilities in DataSynapse Studio to create a new template </li></ul><ul><li>Templates are stored in FabricServer </li></ul>Application Architecture JEE Web Cluster Templates JMS Server … Studio Infrastructure Architect
    11. 11. Adding Application Code to Template <ul><li>Developers use their standard deployment tools to deploy and configure application </li></ul><ul><li>Utility captures all configuration changes and generates self contained package </li></ul><ul><li>FabricServer manages the package and can provision it to any runtime environment (physical, virtual, cloud) </li></ul>Bare Metal Server Application Platform Operating System Standard Templates Application Developer Self-Contained Package DataSynapse Engine Virtual Machine – VMware App Specific Configuration Application Code JMS Service Admin Server JEE Web Cluster FabricServer Run-Time Broker Policy Engine Service Repository
    12. 12. Deploying Applications with FabricServer <ul><li>FabricServer stores and manages self-contained packages </li></ul><ul><li>FabricServer can provision it to any runtime environment (physical, virtual, cloud) </li></ul><ul><li>Self contained packages contain all of the information pertaining to servers, versions, customizations, and applications </li></ul><ul><li>Users create deployment policies in FabricServer which tells the system: </li></ul><ul><ul><li>What templates to use </li></ul></ul><ul><ul><li>What application code to use </li></ul></ul><ul><ul><li>What environment to deploy on (physical / virtual/ cloud) </li></ul></ul><ul><ul><li>How much infrastructure is required </li></ul></ul><ul><ul><li>Performance metrics </li></ul></ul>Automated Deployment Clouds Virtual Physical FabricServer Service Repository Run-Time Broker Policy Engine
    13. 13. FabricServer Deployment Policies <ul><li>Fabric administrators configure policies that dictates how Fabric Broker should provision applications </li></ul><ul><li>Policy Manager contains a list of policies and a schedule, which specifies which policy should be active at any given time </li></ul><ul><li>Deploying Applications – users can create policies that have all of configuration data required to deploy enterprise applications: </li></ul><ul><ul><li>Allocation Rules– Min / max infrastructure (how many cpus/processes?) </li></ul></ul><ul><ul><li>Deployment Preferences – class of machine (eg. X86 blade, dual core), OS (Windows, Linux), etc.. </li></ul></ul><ul><ul><li>Prioritization – which applications are more business critical than others </li></ul></ul><ul><ul><li>Service Levels – rules for monitoring performance and how new clustered instances should be added / deleted based on throughput or other metrics </li></ul></ul>
    14. 14. Upgrading / Versioning Applications <ul><li>FabricServer manages all of the components and applications that it stores </li></ul><ul><li>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 </li></ul>Application Developer New Release Auto Upgrade Version FabricServer Service Repository Run-Time Broker Policy Engine Clouds Virtual Physical Bare Metal Server Application Platform Operating System DataSynapse Engine Virtual Machine – VMware App Specific Configuration Application Code
    15. 15. Deploying Applications Into VMware Physical Machine Virtual Machine Operating System Engine <ul><li>Decompose the entire software stack – OS, Infrastructure Platform, Application </li></ul><ul><li>FabricServer detects the need for a new VM when application policy is activated </li></ul><ul><li>FabricServer makes call to VI3 to start a new, OS specific, VM with a DS engine </li></ul><ul><li>FabricServer provisions and configures the application in the newly started VM </li></ul><ul><li>Application processes are activated and monitored </li></ul>Template Code VMware VI3 VI SDK VMware Virtual Center FabricServer Service Repository Run-Time Broker Policy Engine
    16. 16. Managing Applications at Run-Time <ul><li>FabricServer ships with all the tools required for supporting production applications and infrastructure. Typically application support teams will use the FabricServer UI for: </li></ul><ul><li>Operations quick view </li></ul><ul><li>Drill down capabilities </li></ul><ul><li>Align priorities </li></ul><ul><li>Charting and trends </li></ul><ul><li>Measuring SLA metrics: </li></ul><ul><ul><li>Application usage </li></ul></ul><ul><ul><li>Throughput </li></ul></ul><ul><ul><li>Response time </li></ul></ul><ul><ul><li>CPU utilization </li></ul></ul><ul><ul><li>Memory </li></ul></ul>
    17. 17. Logging and Reporting <ul><li>FabricServer logs Broker and Engine activity, also containers and applications write log files that can be accessed through FabricServer. </li></ul><ul><li>FabricServer creates three kinds of log files: </li></ul><ul><ul><li>Broker Logs – </li></ul></ul><ul><ul><ul><li>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 </li></ul></ul></ul><ul><ul><li>Engine Logs – </li></ul></ul><ul><ul><ul><li>Log information about the operation of particular Engines including startup, their attempts to run Containers and Applications, as well as the statistics they report. </li></ul></ul></ul><ul><ul><li>Application Logs – </li></ul></ul><ul><ul><ul><li>May be provided by some Domains or applications, data and format vary and are determined by the particular application. </li></ul></ul></ul>
    18. 18. Advanced Policies – SLA Management <ul><li>As part of the packaging model in FabricServer applications are instrumented to publish performance metrics </li></ul><ul><li>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 </li></ul><ul><li>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 </li></ul>Closed Loop Policy-Based Allocation of Infrastructure System Metrics Provision Applications
    19. 19. . Questions ?