SOA 18 Beusenberg Thiruvengadam

  • Upload
    polalco

  • View
    219

  • Download
    0

Embed Size (px)

DESCRIPTION

SOA Sonic Flow.

Citation preview

  • SOA-18: Sonic ESB Application Deployment using SDMFrank BeusenbergApplied Technology Consultant

    Kannan ThiruvengadamApplied Architect

    2008 Progress Software Corporation*

    AgendaIntroductionDeployment Procedureusing ESB Deployment toolsusing Sonic Deployment ManagerDemousing Sonic Deployment ManagerComparison

    Sonic ESB Application Deployment using SDMSOA-18: Sonic ESB Application Deployment using SDM

    2008 Progress Software Corporation*

    I created a Sonic based app in Workbench

    How to deploy and run this on my QA env?

    Deployment the needSOA-18: Sonic ESB Application Deployment using SDM

    2008 Progress Software Corporation*

    Deployment the partsDomain ManagerMessage BrokerESB Container 2ESB Container 1SOA-18: Sonic ESB Application Deployment using SDMSonic MQ and ESB

    2008 Progress Software Corporation*

    Sonic Application consists ofESB ProcessesDetour Pattern Implementation ProcessProcess Document ProcessESB ServicesContent Based Routing ServiceXML Transformation ServiceSimulation Service [Custom]ESB EndpointsDetourPattern.EntrySimulationServiceInstance.EntryESB ResourcesConfiguration/Definition Files (xcbr, xslt, xml)JAR FilesDeployment The ESB partWhat do I deploy?SOA-18: Sonic ESB Application Deployment using SDM

    2008 Progress Software Corporation*

    ESB Artifacts need to be placed on an MQ platform

    Introduction What do I deploy?q1q2q3q4ESB ServicesMQ Brokerep1ep2ep3ep4SOA-18: Sonic ESB Application Deployment using SDM

    2008 Progress Software Corporation*

    AgendaIntroductionDeployment Procedureusing ESB Deployment toolsusing Sonic Deployment ManagerDemousing Sonic Deployment ManagerComparison

    Sonic ESB Application Deployment using SDMSOA-18: Sonic ESB Application Deployment using SDM

    2008 Progress Software Corporation*

    ESB DeploymentSteps Involved in ESB DeploymentSOA-18: Sonic ESB Application Deployment using SDM

    2008 Progress Software Corporation*

    ESB DeploymentSonic ESB Deployment ToolGraphical ToolExport SonicESB Artifacts for DeploymentCreate Deployment Archive (.XAR)Sonic ESB Admin ToolCommand Line ToolCreate Map FileApply Map File to ArchiveTools Involved with ESB DeploymentSOA-18: Sonic ESB Application Deployment using SDM

    2008 Progress Software Corporation*

    ESB DeploymentMessaging InfrastructureJMS DestinationsMF ContainersBrokersClustersDRA Configuration...

    XAR only deals with ESB artifactsWhat is NOT in XARSOA-18: Sonic ESB Application Deployment using SDM

    2008 Progress Software Corporation*

    ESB Deployment

    Exclude required artefacts (e.g. dev.CBR) from ignore listby modifying default ExportProperties.xml

    Export using ESBAdmin

    ESBAdmin> export archive c:\Projects\Sales\salesdev.xar C:\Projects\Sales\ExportProperties.xml

    Including development environment artefactsSOA-18: Sonic ESB Application Deployment using SDM

    2008 Progress Software Corporation*

    AgendaIntroductionDeployment Procedureusing ESB Deployment toolsusing Sonic Deployment ManagerDemousing Sonic Deployment ManagerComparison

    Sonic ESB Application Deployment using SDMSOA-18: Sonic ESB Application Deployment using SDM

    2008 Progress Software Corporation*

    What is SDM?SDM

    2008 Progress Software Corporation*

    Sonic Deployment ManagerSoftware tool to perform

    Installation

    Configuration

    DeploymentWhat is it?SOA-18: Sonic ESB Application Deployment using SDM

    2008 Progress Software Corporation*

    Sonic Deployment ManagerWhat is a model?SOA-18: Sonic ESB Application Deployment using SDM

    2008 Progress Software Corporation*

    Sonic Deployment ManagerBenefitsCompletely Automated Server Installation Software Lifecycle SupportVersioned Sonic ConfigurationsRepeatable Installation of Sonic DeploymentUpdates of an existing Sonic DeploymentSOA-18: Sonic ESB Application Deployment using SDM

    2008 Progress Software Corporation*

    Sonic Deployment ManagerCreate the Model to describe your deployment configurationDomain ManagerMessage BrokersContainersAcceptorsOther SonicMQ artifacts

    Run SDM to create the deployment described in the Model.How do I use it?SOA-18: Sonic ESB Application Deployment using SDM

    2008 Progress Software Corporation*

    Sonic Deployment ManagerDomain ConfigurationDomain ManagerBase ConfigurationMessage BrokersClustersAcceptorsESB ConfigurationESB ContainersESB XAR File(s)Event Monitor

    Levels of ConfigurationSOA-18: Sonic ESB Application Deployment using SDM

    2008 Progress Software Corporation*

    Sonic Deployment ManagerNot everything is exported by domaintoModelExamplesJNDI objectsSecurity configuraiton elementsUsersGroupsACLsQoPsFor security-related config elementsUse admin utility (configadmin)Whats leftSOA-18: Sonic ESB Application Deployment using SDM

    2008 Progress Software Corporation*

    Other deployment tasks

    Incremental Deployment! Also via SDM!

    CleanInstallationUpdateInstallation

    Version the involved model file(s)!

    Version Control

    ApproachSOA-18: Sonic ESB Application Deployment using SDM

    2008 Progress Software Corporation*

    The Deployment Model

    Model.xml

    Domain ConfigurationDescribes the ModelConnection to the Domain ManagerCreate the Domain ManagerInstall Sonic MQInstall Sonic ESBSOA-18: Sonic ESB Application Deployment using SDM

    2008 Progress Software Corporation*

    The Deployment ModelDomain ConfigurationSOA-18: Sonic ESB Application Deployment using SDM

    2008 Progress Software Corporation*

    The Deployment Model

    Model.xml

    Base ConfigurationDescribes the Broker and MF Container to create for messagingDescribes the Cluster containing the Broker(s)SOA-18: Sonic ESB Application Deployment using SDM

    2008 Progress Software Corporation*

    The Deployment ModelBase Configuration SampleSOA-18: Sonic ESB Application Deployment using SDM

    2008 Progress Software Corporation*

    The Deployment Model

    Model.xml

    ESB ConfigurationDescribes the XAR to importDescribes the ESB Container to createSOA-18: Sonic ESB Application Deployment using SDM

    2008 Progress Software Corporation*

    The Deployment ModelESB ConfigurationSOA-18: Sonic ESB Application Deployment using SDM

    2008 Progress Software Corporation*

    AgendaIntroductionDeployment Procedureusing ESB Deployment toolsusing Sonic Deployment ManagerDemousing Sonic Deployment ManagerComparison

    Sonic ESB Application Deployment using SDMSOA-18: Sonic ESB Application Deployment using SDM

    2008 Progress Software Corporation*

    DemoSOA-18: Sonic ESB Application Deployment using SDM

    2008 Progress Software Corporation*

    Summary Roles of ToolsDomain ManagerMessage BrokerESB Container 2ESB Container 1SOA-18: Sonic ESB Application Deployment using SDMSonic MQ and ESBESBExport/ImportS

    D

    M

    2008 Progress Software Corporation*

    Summary - SDMThe deployment process is nowAutomatedSimplifiedRepeatableLess error-proneVery useful for large and frequent deployments

    SOA-18: Sonic ESB Application Deployment using SDM

    2008 Progress Software Corporation*

    For More Information, go toRelated Exchange SessionsContinuous Integration in SOA Projects by Andreas GiesRelease Management for SOA by Mitchell HorowitzDocumentationSDM User GuideSonic ESB Deployment GuidePSDNSonic Deployment papersSOA-18: Sonic ESB Application Deployment using SDM

    2008 Progress Software Corporation*

    Questions?SOA-18: Sonic ESB Application Deployment using SDM

    2008 Progress Software Corporation*

    Thank YouSOA-18: Sonic ESB Application Deployment using SDM

    2008 Progress Software Corporation*

    SOA-18: Sonic ESB Application Deployment using SDM

    ********Make this animated slide to show the process.*ANT files for creating XAR file in Workbench**Note: You can obtain an initial copy of ExportProperties.xml by using the Deployment tool. ExportProperties.xml is part of the XAR produced

    ExportProperties.xml should remove the desired artifacts from the ignore list

    Domain1 tcp://localhost:2506 Administrator

    *********Change uppercase XML to lowercase for model.xml***Add reference to previous XML tags in here.*********