Web Services in the Real World

Afkham Azeez – WSO2 Inc.

Eran Chinthaka – Indiana University

Agenda

• Academic Use-cases• Eran Chinthaka

• Industry Use-cases• Afkham Azeez

Academic Usage

LEAD – Linked Environment for Atmospheric Discovery

SevereThunderstorms

FogRain and

Snow

Rain andSnow

IntenseTurbulence

Snow andFreezing

Rain

“Optimal” Weather Prediction Using Dynamic Adaptivity

On-DemandGrid Computing

StreamingObservations

Storms Forming

Forecast ModelData Mining

Refine forecast grid

Instrument Steering

Flexibility with SOA Architecture

Data Storage

Application services

Compute Engine

User Portal

Portalserver

DataCatalogservice

MyLEAD UserMetadatacatalog

MyLEAD Agentservice

DataManagement

Service

WorkflowEngine

Workflow graph

ProvidenceCollection

service

Event Notification Bus

FaultTolerance

& scheduler

Sigiri : Efficient Job Submission to Large-scale systems

Goals

Customized and robust submission of jobs

Reliable Monitoring

Eran Chinthaka, Suresh Marru, Beth Plale School of Informatics and Computing, Indiana University, Bloomington, Indiana.

Walakulu – Framework for Interacting with Multiple Cloud Environments

Eran Chinthaka, Suresh Marru, Beth Plale School of Informatics and Computing, Indiana University, Bloomington, Indiana.

Reusable eScience Software Stack

• Open Grid Computing Environments project led by Indiana University adopts software components from domain specific Science Gateways and generalizes/hardens/tests and releases them to the gateway community at large.

• E-Science Community has adopted Axis2 as the default Web Service Framework.

• With the inspiration and experience with axis2, OGCE project is pursuing to submit a ASF incubator proposal to collaborate, develop and maintain Scientific workflow tool suite.

Industry Usage

1. Dynamic Routing + Auditing

• Traffic directed to different endpoints during the day

– Routing to different endpoints based on the config

• Optimizing resource allocation

• All service requests/responses should be logged for auditing purposes

• Switching configurations should be seamless

1. Dynamic Routing + Auditing

2. Push and Pull

Reconcile data between two systems periodically

2. Push and Pull

3. MDM & EDA

• Multiple customized IT management systems

• Different formats for data representation in these systems

3. MDM & EDA

3. MDM & EDA

• Adaptor Layer

– Axis2 used for hosting adaptor services which talk to backend (BE) systems

– Publishes events when changes occur in the BE systems

– Publishes & subscribes to specific G-message events

– Converts GBOs into ASBOs

• Integration Server

– Acts as the event broker.

– Transforms events into a generic format

– Manages subscriptions

• Logic Server

– Manages the master data repository

– Takes care of the feedback problem

• Registry

– Used for storing topics, subscriptions, policies

4. Validation + Protocol Bridging

• All service requests coming in should be validated & scanned for viruses

• Actual services should be exposed only via certain transports

4. Protocol Bridging

5. External Authentication

6. External Authorization

7. Auto-scaling

• Service deployment should be auto-scaled– Scaled up when load increases– Scaled down when the load decreases

7. Auto-scaling

8. Cloud Gateway

• Some of the services within the corporate network need to be made available on the cloud

8. Cloud Gateway

Questions

Thank You