İndir

What’s New in Sonic v7.5

Sonic ESB® 7.5

Jan BolSenior Solution Consultant

© 2007 Progress Software Corporation2 What’s New in Sonic V7.5

Sonic ESB 7.5 – First Look

Overview Sonic BPEL Server™

Actional: SOA Management DataXtend: Common Data Model Management ESB performance, availability and manageability SDM Q&A

Agenda


AcquiredActionalJanuary 2006

Sonic ESB 7.5

April 2007• WS-BPEL 2.0• SOA Management• Semantic Integration

IntroducedDataXtend SIDecember 2006

Sonic ESB 7.0

April 2006• Eclipse development• Advanced Web

services

Released CAATechnologyJune 2004• Unique, patented HA

Sonic ESB 6.0

March 2005• Continuous

Availability Architecture

Sonic XQ

March 2002• World’s First

Enterprise Service Bus

Sonic/GartnerCoin term ‘ESB’March 2003• Gartner Predicts ESB as

backbone for ENS

AcquiredeXcelonDecember 2002• XML

development tools

• XML database

20072007

20062006

20052005

20042004

20032003

Sonic ESB Timeline

20022002


SOA Integration

Incompatible systems• Web services• Everything else…

Distributed processing• Multiple sites• Multiple departments

Rapid Change• Competition• M&A• Regulation

Lots of turf control and organizational issues

CRM ERP

PARTNER SYSTEMS FINANCE

The problem that Sonic ESB solves

ORDERENTRY


The Sonic ESB Vision

Flexible integration of new and existing business applications

Any numberof processes

Any numberof locations

Any number of services

Across organizational boundaries and to remote sites

With low latency, high reliability and continuous availability

Evolve, scale and extend throughout the enterprise



Overview Sonic BPEL Server Actional: SOA Management DataXtend: Common Data Model Management ESB performance, availability and manageability SDM Q&A

Agenda


Service Orchestration in a Distributed World

Compose processes out of existing services and processes

Correlate events within and across running processes

Control flow: conditionals, loops, delays, scoped state

Manage concurrent (often long-running) service interactions

Compensate for completed activities in the event of failure

SERVICES

SERVICES

BPEL: Sophisticated, standards-based service orchestration


Full WS-BPEL 2.0Support

Standards-based service orchestration enhances developer productivity

Latest specification affords high level of portability

Sonic BPEL Server introduces no language extensions

Integrated into Sonic ESB Development Environment

Drag-and-drop Eclipse-based Workbench

Approaches “zero-programming” ideal

Integrated into Sonic ESB Distributed

Runtime Environment

Connects to heterogeneous endpoints, wherever deployed

Integrates ESB distributed mediation facilities

Integrates BPEL event correlation and ESB messaging semantics

Single-console debug across distributed BPEL, ESB intelligent routing, and integration services

Sonic BPEL Server

Product highlights


2

1

3

REPEAT

START

END

Use BPEL to iterate on 3-step process Each step invokes legacy resources But BPEL is completely binding-agnostic

• It knows only of WSDL

• How do I integrate with the target systems?

BPEL Integration example

ORDER

SHIP

BUILD

Sonic BPEL Server

WSDL LEGACY


1

2 3

BPEL orchestrates WSDL services into a process ESB binds WSDL to heterogeneous resources

BPEL Integration example

Sonic BPEL Server

ORDER

SHIP

BUILD

BPEL SERVER

2

1

3

REPEAT

START

END


2

1

3

REPEAT

START

END

That means two shipping systems: one local, one remote

The second shipping system needs special handling• We can’t ship without looking up customer information

that is in the remote fulfillment center

BPEL Integration example with two fulfillment centers

ORDER

LOCAL SHIP

BUILD

Sonic BPEL Server

WSDL LEGACY

REMOTE SHIP

?


A B C

Extend “SHIP” service using ESB intelligent routing• CBR selects branch• Itinerary directs message flow for additional mediation steps

Intelligent routing obviates WAN hop – no “central brain” Separation of BPEL and ESB concerns maximizes flexibility

BPEL Integration example with two fulfillment centers

BPEL SERVER

Sonic BPEL Server

1

2 3

BA

C

3 ITINERARY

REMOTE SHIP


BBPEL SERVER C

Clustered communication brokers scale to meet changing throughput requirements

Brokers dynamically route messages across clusters, firewalls and security domains

Continuous Availability Architecture (CAA) provides communications availability

Add service instances for transparent load-balancing, availability, disaster recovery

A

A

Sonic BPEL Server

Leverages ESB scalability, availability and reach


A B C

Debug BPEL and intelligent routing from Eclipse environment

On one server, or across clusters and the firewall – works the same

Set breakpoints and visually step through processes

Examine remote process and service state

Breakpoint

Distributed process debugger

Sonic BPEL Server

Breakpoint

Breakpoint

Breakpoint


Drag-and-drop, Eclipse-based development environment

Heterogeneous end-point connectivity

End-to-end visibility and control of integration across firewalls and WAN

• Distributed testing and debugging across BPEL, ESB and integration services

• Superior network performance in distributed environments

Robust, scalable communications

Sophisticated, standards-based orchestration

Developer productivity• Control flow: conditionals,

loops, delays, scoped state• Service invocation and

event correlation• Manage concurrent (often

long-running) service interactions

• Compensate for completed activities in the event of failure

Sonic BPEL Server

BPEL brings to ESB ESB brings to BPEL

BPEL and ESB synergy summary


Sonic BPEL Server

Integrated with Actional Looking Glass




Agenda


WEBLOGIC

ORACLE

SAP

WEBSPHERE

.NET

Integrates Actional for SOA Management

Visibility across and beyond edge of ESB• Incurs no measurable overhead• Scales with the distributed architecture of Sonic ESB

Traces the root cause of service level violations

Managing operations in a complex environment

RESPONSE TIME



Web 2.0Browser Based UI

Show process flow map at high level

Show process flow in depth




Agenda


Solving the “point-to-point” transformation problem

Integrates DataXtend SI

Sonic ESB eliminates the rigidity and fragility of point-to-point connections

How do I solve the similar problem in my data model transformations?

<XML>

<XML> <XML> <XML>

<XML>

Tran

sfor

mat

ion


<XML> <XML>

Common model management

Integrates DataXtend SI

Rapidly create common data model from any number of schema• Design mappings in Eclipse-based Workbench

Common model mediates transformations Deployed and managed as an ESB service

• Java-based validation and transformation• Regenerated if schema or common model change

<XML> <XML> <XML><XML> <XML> <XML><XML>

<XML> <XML>

Tran

sfor

mat

ion

<XML><XML>

<XML>

<XML>




Agenda


Sonic 7.5 Improvements

HTTP Tunneling• New embedded HTTP server

• 2x – 10x performance improvements

ESB Itinerary throughput Web service invocation XPath-based routing XSLT service

Performance



Advanced Web Services interoperability with WCF (Windows Communication Foundation )• WS-RM• WS-Security• WS-Policy and specific dialects• WS-Addressing

Other vendors in attendance were: Sun, Oracle, BEA, Sonic, JBoss, Canon, Nokia, Layer7Technologies, WSO2, The Aerospace Corp, Reactivity, JIBX, IONA and Ping Identity

Interoperability



Manageability• Role based seScurity for configuration and

management • Auditing of all configuration and management

activities New Continuous Availability Features

• DR-site architecture for HA management• Inter-cluster connections• New online backup operation

Availability - New Continuous Availability Features

This allows Sonic Directory Service to fully exploit CAA in the same manner as all Sonic communication brokers.


Version 7.0 & 6.1

AM DS

BR

AM DS

BR

Active Standby

SAN

DS Storage

AM DSBR

Active

DS Storage

AM DSBR

Standby

DS Storage

Shared DS - Scenario Remote Site - Scenario

Broker cluster

Broker cluster




Version 7.5

AM DSBR

Active

DS Storage

AM DSBR

Standby

DS Storage

replication connection

Broker cluster





Manageability

Role based security for configuration and management

Auditing of all configuration and management activities

In prior versions, a single administrator group performed all activities


Sonic v7.5 – Platform support

X64• Microsoft Windows Server 2003 x64 SP1[64-bit]

• Sun Solaris 10 [64-bit]

• Red Hat Enterprise Linux 4 Update 3[64-bit]

• IBM AIX 5L V5.3 (5300-04) [64-bit]

• HP-UX V11i V2 (11.23) [64-bit]

Following new hardware specs and new OS specs, higher memory allocation




Agenda


Sonic Deployment Manager

A tool that allows the creation and deployment of Sonic configurations in a reusable and repeatable fashion

A tool used for several years by Sonic PSO in support of large scale customer deployments• Now a full released and supported product

Release 7.5.1: Now shipping as a service pack


What is SDM?

Provides and enforces best practices• e.g. naming, Acceptor settings, deployment-

specific values, etc. Components are installed and configured

automatically Makes use of existing tools:

• Sonic Installer • ESB Deployment Tool• Sonic Configuration API


What is SDM’s Purpose?

Support large scale deployments Reduce time required for deployments

• And redeployment Reduce errors

• via validation and single model Simplify upgrades

• via reverse engineering Provide flexibility

• via virtual-to-physical mapping


Install and configure a remote host machine

Sonic

Installation CD

SDM Model

SDM

Environment

Tailoring

Parameters

Domain Manager

Install

Configure

Host #1

XML Model File• Validation

• Versioning

Ant XSLT




Agenda


Thank you foryour time


[email protected] 781 999 7000

İndir

Documents

Transcript of İndir