1

GridServer Overview

2

• High performance SOA platform

• Modern, open and extensible

• Multi-platform, multi-language

• Self-managing:- HA/Failover- Deployment and

provisioning- Monitoring

• Large platform ecosystem of premier ISVs

GridServer – Service Execution Environment

Physical Server

Cross-language service containers host application components

Application Components

Service Interface

ApplicationServers

SpreadsheetsThin

ClientsMainframe

Batch Clients

Rich Clients

3

How it Works

Physical server has one Daemon and 1 (or more) engines

Daemon - monitors host and spawns one or more engines

Engine creates service instances, controls, monitors, and isolates from other service instances

Physical Machine

4

SpeedLink: Low-Latency, High-Throughput Extension to GridServer

Real-time computing, 300 micro-second execution latency

Extreme volume services

Variable size dynamic pool that can be assigned directly to a client

Example client types:• ESB endpoint

• Application server

• Web service

Application Components

5

Key Feature Summary

• Dynamic Scaling of Services:- GridServer configures and manages services based on schedule, policy, and priority

• Unparalleled Performance:- GridServer dynamically scales services to meet SLA targets-

• Availability:- Guaranteed Service Execution – even if the hardware fails - Automatic failover and failback of services

• Centralized Command and Control:- GridServer simplifies the configuration and management of running multiple services across

widely distributed resources

6

Performance and Scaling

• Services can be scaled to meet performance or SLA demands

• Execution of online parallel transactions delivers the greatest flexibility and scalability

• Service availability delivers unparalleled horizontal scalability

Director

Broker

Node 1 Node 2 Node 3 Node 4

GridServer Manager

• 30 + brokers on a single grid

• 3,000 + engines on a single broker

• 30,000 + engines on a single gridBroker

Node 5 Node 6

Broker

7

Dynamic Resource Sharing

• The resource pool is a heterogeneous collection of engines, consisting of different platforms and operating systems

• Engine behavior is controlled at the individual component level, including mode and availability

• Because of resource sharing, engines can be configured to automatically move to where they’re needed – thereby ensuring high resource availability

Director

Broker B Broker CBroker A

Director

Broker B Broker CBroker A

8

Centralized Command and Control

• GridServer’s Admin Console is accessed via a web browser

• Alternatively, Admin API’s are accessible via SOAP, C++, .NET, and Java

• Provides complete plant management, including:- Configuration and control of all GridServer resources- Graphical monitoring- Engine and Driver installation- Event-based email notification- Batch scheduling- Secure Login- Reporting

9

Application Resource Management

• Configuration options can be specified to affect how services are executed on Engines, controlling everything from stateful execution to retry logic and notifications

- Service options also provide the ability to specify resource limits (“don’t scale this execution past a specified number of engines”)

• All components can be configured, reconfigured dynamically and monitored

• Services can be reprioritized at execution

10

Data Caching

• GridCache™ provides durable state maintenance with a distributed data cache to distribute data all Engines on request via a full-featured distributed, replicated caching server and standards-based API (JCache – JSR107)

• Pluggable loaders for abstracting and controlling the interface to enterprise data resources

• Supports life-cycle management, bulk loading, XML, and RDBMS connection pooling

• Data locality is supported at the task and service levels

• Support for third-party caching products including Gemfire, Coherence, GigaSpaces is also available

11

Monitoring and Reporting

• Reporting database tables provide visibility into the demand and consumption of applications and resources

• Reporting is extended through VersaVision for near real-time portal-based reporting

• All GridServer components– Directors, Brokers, Engines, and Clients– maintain logs with configurable expirations and detail levels

• GridServer’s dashboard provides an Ajax-based console of current activity with drill-down capability

• The Service Status Report provides a historical view of executed services

12

Ease of Implementation

• GridServer is installed via a single implementation package that’s always the same, regardless of the platform or operating system

• Once unpackaged, GridServer Directors and Brokers are configured through the Admin GUI

• Engines are installed a single time and automatically keep themselves up-to-date with service deployments and software updates

• Transparent network tools are supported

13

Thanks

For more information go to www.datasynapse.com