Service Oriented Architecture

2y ago
16 Views
2 Downloads
1.61 MB
60 Pages
Last View : 2d ago
Last Download : 2m ago
Upload by : Mya Leung
Transcription

Federal AviationAdministrationService OrientedArchitectureTraining SessionPresented to: STDDS ProgramBy:Leonid Felikson, Amresh DasVeracity Engineering

Agenda Service Oriented Architecture (SOA) OverviewSOA Services: Web Services and JMS ServicesSystem Wide Information Management (SWIM)BreakNAS Enterprise Management Services (NEMS)STDDS Program Using SWIMQ&AService Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration2

Agenda Service Oriented Architecture (SOA) OverviewSOA services: Web services and JMS servicesSystem Wide Information Management (SWIM)NAS Enterprise Management Services (NEMS)STDDS Program Using SWIMQ&AService Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration3

What is Service Oriented Architecture Service-Oriented Architecture (SOA) is a software and architecturedesign pattern based on a structured collection of discrete softwaremodules known as services. SOA is a set of principles and methodologies for designing anddeveloping software in the form of interoperable services. A service is the most fundamental unit of service-oriented logic, amechanism to enable access to one or more capabilities, where theaccess is provided using a prescribed interface and is exercisedconsistent with constraints and policies as specified by the servicedescription.SOA is something we DO, not something we buy!SOA is about ARCHITECTURE, not about technology!Service Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration4

SOA is Architectural ParadigmParadigmsCharacteristicsPrinciples andConstraintsPatterns ServiceStructure and OrganizationFactoring andGranularityTopologyInterdependenciesInterfaces andContractsFrameworksImplementationAdapted from GartnerService Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration5

The key differentiators of SOA SOA exhibits technology-neutral best practices. SOA is built on the standards leading to cost-effectiveimplementations on a global basis with broad support by vendors. Services are “course-grained” and “loosely-coupled” allowing formuch more flexibility than older technologies with respect to reusing and re-combining (composing) the services to create newbusiness functions both within and across enterprises. SOA best practices create designs which embody businessprocesses — and enhance the ability to outsource and extendprocesses to business partners. SOA encompasses legacy systems and processes so that theusefulness of existing investments can be preserved and evenincreased.Service Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration6

The key differentiators of SOA, cont’d SOA enables designing interoperable services for exchangingdata. The strategic nature of service-oriented computing is one of itsdistinguishing characteristics. It contrasts the more tacticalnature of traditional silo-based application development. Strategic goals of SOA:–––––––Increased Intrinsic InteroperabilityIncreased FederationIncreased Business and Technology AlignmentIncreased Vendor Diversification OptionsIncreased ROIIncreased Organizational AgilityReduced IT BurdenService Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration7

SOA Business Benefits and OutcomesAdapted from GartnerService Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration8

SOA Governance OverviewGovernance means establishing and enforcing how people andsolutions work together to achieve organizational objectives. SOA Governance is the application of policies, rules, andstandards needed to ensure that all of the independent SOAbased efforts (whether in the design, development, deployment,or operations of a service) come together to meet enterpriserequirements. (from SWIM Governance Policies Version 2.0) SOA governance is viewed as the application of Businessgovernance, IT governance, and EA governance to SOA. SOA Governance ensures successful business and IT alignment.Service Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration9

SOA Governance Overview, cont’d SWIM Governance is the realization of SOA Governance by theSWIM program, with the major goal of enabling a set ofenforceable policies, procedures, processes, tools, andorganizational activities that together ensure a consistentalignment between FAA/NAS business objectives and SOA bestpractices, methodologies, and technological solutions. SWIM SOA Governance processes are supported by use of theNAS Service Registry/Repository (NSRR). NSRR is a SWIM-supported capability for making servicesvisible, accessible, and understandable across the NAS. NSRR supports a flexible mechanism for service discovery, anautomated policies-based way to manage services throughoutthe services lifecycle, and a catalog for relevant artifacts.Service Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration10

Service Life Cycle StagesLifecycle StageDescriptionProposedThe stage during which the business needs for the proposed service areidentified and assessed as to whether needs can be met through the useof SOA.DefinitionThe stage during which the service's business requirements aregathered and the service design is produced based on theserequirements.DevelopmentThe stage during which the service specifications are developed and theservice is built.VerificationThe stage during which the service is being inspected and/or tested toconfirm that the service is of sufficient quality, complies with theprescribed set of standards and regulations, and is approved for use.ProductionThe stage during which the service is available for use by its intendedconsumers.DeprecatedThe stage during which the service can no longer be used by newconsumers.RetiredThe stage during which the service is disposed of and is no longer used.Service Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration11

Service Oriented Architecture Overview, cont’d SOA infrastructure is a set of software products that enablerealization of services, provide necessary life-cycle support forhosting and managing services, enable communication betweenservices and ensure required security capabilities. An example of FAA SOA infrastructure components:– NAS Enterprise Messaging Services (NEMS)– NAS Service Registry/Repository (NSRR) Service design time policies are defined and enforced Industry and FAA standards are in-use and enforced. i.e.:––––XML, SOAP, WSDLFAA-STD-065A, Preparation of Web Service Description DocumentsFAA-STD-066, Web Service TaxonomiesFAA-STD-073, Preparation of JMS Description DocumentsService Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration12

Agenda Service Oriented Architecture (SOA) OverviewSOA Services: Web Services and JMS ServicesSystem Wide Information Management (SWIM)NAS Enterprise Management Services (NEMS)STDDS Program Using SWIMQ&AService Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration13

SOA Services Overview, cont’d SOA is architecture oriented toward services A SOA service is the most fundamental unit of service-orientedlogic, a mechanism to enable access to one or more capabilities,where the access is provided using a prescribed interface and isexercised consistent with constraints and policies as specified bythe service description.SOA is not Web services (or JMS services)Web services don’t require and are not necessary for SOASOA or JABOWS?Service Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration14

SOA Services Overview, cont’d The eight service-orientation design principles– Standardized Service Contract– Service Loose Coupling– Service Abstraction– Service Reusability– Service Autonomy– Service Statelessness– Service Discoverability– Service ComposabilityService Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration15

SOA Services OverviewSOA ServicesWeb ServicesA platform-independent, loosely-coupledsoftware component designed to supportinteroperable machine-to-machineinteraction over a network. It has aninterface described in a machineprocessable format. Other systems interactwith the Web service in a mannerprescribed by its description by means ofXML-based messages conveyed usingInternet transport protocols in conjunctionwith other Web-related standards.Service Oriented Architecture Training Session for STDDSNovember 2014JMS ServicesA Java application or process that produces(Message Producer) and/or receives(Message Consumer) messages usingJava Message Service (JMS) API.Federal AviationAdministration16

SOA Services Overview, cont’d Web service is a software designed and developed in order toimplement service oriented principles and architecturalapproach Web service is a software component implemented based onindustry accepted standards. Web service interface is a self-contained description of serviceand means of interacting and interoperating with it.Service Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration17

SOA Services Overview, cont’d A JMS service is a software designed and developed in order toimplement business capability using Java Messaging Service(JMS).- acts as a JMS client in message exchange model. uses messaging transport protocol as oppose to HTTP protocol. can exchange messages synchronously and asynchronously. has a message structure that is defined by JMS APIstandard.Service Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration18

SOA Services Overview, cont’dWeb serviceJMS service- uses SOAP standard messagestructure and HTTP transportprotocol;- uses JMS based messagestructure, most often uses XMLas message payload;- its interface is defined bystandard based (WSDL)service description document;- always uses intermediaryinfrastructure, MessageProvider, and acts as a JMSclient in message exchangemodel;- its capabilities and qualities ofservice are described by FAAstandard based Web ServicesDescription Document(WSDD);- allows primarily synchronousmessage exchange.Service Oriented Architecture Training Session for STDDSNovember 2014- its capabilities and qualities ofservice are described by FAAstandard based JMS DescriptionDocument (JMSDD);- allows asynchronous messageexchange.Federal AviationAdministration19

Web Services and JMS Service Description Web Services Description Language (WSDL) is a W3Crecommendation– WSDL is an XML based protocol for information exchange in decentralizedand distributed environments– WSDL definition describes how to access a web service and whatoperations it will perform Web Service Description Document (WSDD) is a Web servicedescription that is rendered as a human-readable document in a wayconsistent with FAA acquisition process standards and practices.– The core of the WSDD consists of three parts: Service Profile, ServiceInterface, and Service Implementation. Each part represents importantaspects of describing a Web service, and each can be characterized asanswering a particular questionService Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration20

JMS Services Description JMS Service is described using JMS Service Description Document(JMSDD).– JMSDD is JMS service description that is rendered as a human-readabledocument in a way consistent with FAA acquisition process standards andpractices.– JMSDD consists of three parts: Service Profile, Service Interface, andService Implementation. Each part represents important aspects ofdescribing a JMS service, and each can be characterized as answering aparticular question.Service Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration21

Agenda Service Oriented Architecture (SOA) OverviewSOA Services: Web Services and JMS ServicesSystem Wide Information Management (SWIM)NAS Enterprise Management Services (NEMS)STDDS Program Using SWIMQ&AService Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration22

System Wide Information Management (SWIM)SWIM consists of standards, infrastructure, and governancethat enable the management of Air Traffic Management relatedinformation and its exchange between qualified parties viainteroperable services The SWIM Program implements SOA in the NAS. SWIM allows the FAA to create reusable system interfaces morequickly and cost effectively. SWIM facilitate interoperability and data-sharing needed for NextGen. SWIM replaces unique interfaces with modern standards based dataexchange. SWIM provides SWIM users access to information without directlyconnecting to another system. Provides enterprise security for incoming and outgoing data.Service Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration23

System Wide Information Management, cont’dService Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration24

System Wide Information Management, cont’d ?without SWIMLegacy operating environment:point-to-point connectionswith SWIMSWIM operating environment:Data Exchange(Published once, consumed by many)Service Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration25

System Wide Information Management, cont’dMission Services/Application Layer:FDPS, STDDS, ITWS, AIM, etc.Common Support:Data Standards & HarmonizationEnterprise Messaging:SWIM Core ServicesPhysical Network:FTI Operational IP networkprovides secure transportService Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration26

System Wide Information Management, cont’d SWIM data exchange capability is implemented via NAS Enterprise MessagingService (NEMS) NAS Enterprise Security Gateway (NESG) supports SWIM data exchangesbetween NAS and non-NAS customers Service registration, discovery and lifecycle management is supported by theNAS Service Registry/Repository (NSRR)Service Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration27

SWIM CapabilitiesEnterprise Messaging Services– Provides a standards driven method ofexchanging messages across a variety ofNAS and non-NAS programs.– Supports both JMS services & Webservices.Information Assurance– NAS Enterprise Messaging Service(NEMS) deployment of the NESG meetsNAS Boundary Protection Requirements.SOA Suitability– Provides assessment of FAA programsfor SOA applicability and reports to NASTechnical Review Board (TRB).Service Oriented Architecture Training Session for STDDSNovember 2014sSOA Governance– Provides standards, policies, andprocedural guidelines to support thefunctional requirements for implementingall aspects of service-orienteddevelopment.– Making all services discoverable,searchable, and retrievable, through aformal cataloging process of servicemetadata, by establishing and operatingthe NSRR.– Promoting interoperability among FAAsystems by developing a common set ofsemantic and structural artifacts andpromulgating them through communitiesof stakeholders.Federal AviationAdministration28

System Wide Information Management, cont’dInteroperability, discoverability and reuse are the key goals ofSWIM Governance. To achieve these goals, SWIMGovernance provides:– Standards: FAA-STD-065A, FAA-STD-066, FAA-STD-073,etc.– Governance Policy specifies applicable standards andprocedures.– Service Lifecycle Management Process (SLMP) describesthe enforcement of SWIM Governance policies andstandards from identification to retirement of a SOA Service.SLMP is synchronized with AMS milestones.Service Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration29

System Wide Information Management, cont’d Service registration, discovery and SLMP automation issupported by the NSRR NSRR is the authoritative source of all SWIM service metadata Service metadata includes a set artifacts such asWSDL, XML schema, ConOps, SLAServiceRegistry Providers and Consumers must register in theNSRRDiscover and ConsumePublish and RegisterServicesServices Registration of SWIM Services early in thelifecycle provides Consumers visibility intoexisting and future SWIM services As the Service moves through the servicelifecycle, the description in the NSRR becomesmore refined, and supporting artifacts are addedfor consumer discoveryService Oriented Architecture Training Session for STDDSNovember Federal AviationAdministration30

Agenda Service Oriented Architecture (SOA) OverviewSOA Services: Web Services and JMS ServicesSystem Wide Information Management (SWIM)NAS Enterprise Management Services (NEMS)STDDS Program Using SWIMQ&AService Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration31

NAS Enterprise Management Services (NEMS)Messaging is a technology that enables high-speed, asynchronous,program-to-program communication with reliable delivery.An application orprocess thatcreates andsendsmessages.A basic unit ofcommunication from onesoftware agent to anothersent in a single MessageMessageMessage Oriented Middleware (MoM)or Message ProviderService Oriented Architecture Training Session for STDDSNovember 2014An application orprocess thatreceives messages.A software orhardwareinfrastructuresupporting sendingand receivingmessages betweendistributed systems.Federal AviationAdministration32

NEMS, cont’d The NAS Enterprise Messaging Service (NEMS) is an FTI Service,which provides for an Enterprise SOA messaging infrastructure for theNAS The NEMS supports two types of standards-based messagingexchange patterns: Publish/Subscribe and Request/ Response Publish/Subscribe model is used when a Service Provider (Publisher)wants to continually publish data to multiple Service Consumers– The Publisher publishes a data stream to the NEMS, from which theConsumers consume data– The Publish/ Subscribe model is typically used for services that require aconstant, persistent feed of data– The Publish/Subscribe model is typically implemented using JavaMessage Service (JMS)Service Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration33

NEMS, cont’d The Request/Response model is better suited for services with dataexchanges on an ad-hoc basis– Typically used when a Consumer sends a message to a Producer andexpects to receive a message back from the Producer, such as anacknowledgement receipt or a reply message with a data payload The Request/Response model is typically implemented as SOAPbased Web services NEMS provides a Web service proxy capability and transports the datavia HTTP protocolService Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration34

NEMS, cont’dJava Message Service (JMS) is a Java-based application programminginterface (API) that provides a common way for Java programs tocreate, send, receive, and read an enterprise messaging system'smessages.JMS Provider is a messaging system that implements the JMSapplication programming interface (API) in addition to the otheradministrative and control functionality required of a full-featuredmessaging product.JMS Client is an application or process that produces and/or receivesmessages.(from FAA SWIM Controlled Vocabulary)Note. JMS Queue messages are processed only once but are notnecessarily delivered in the order sent. Messages in the queue pool maybe processed concurrently, resulting in a later message being receivedby a recipient before an earlier one.Service Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration35

NEMS, cont’dJMS message structure includes message header (with messageproperties) and message body. Message Header contains values used by both clients andproviders for identifying and routing messagesMessage Properties contain vendor-specific values andcould also contain application-specific messagesMessage Body (Payload) contains the actual (business)data transferring the messageService Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration36

NEMS, cont’dThe JMS specification supports two messaging models:– Point-to-Point (PTP) modelEach message is addressed to only one consumer. It allows users to sendmessages both asynchronously and synchronously using different channels(queues). Typically, in the PTP model, a user requests a message that aproducer sends to the queue, rather than subscribing to a channel andreceiving all messages sent on a particular topic.– Publish/Subscribe (Pub/Sub) modelThe pub/sub messaging model is similar to the notion of one-to-manyrelationships. It allows the producer to send messages to many users at onetime. Consumers can subscribe to a particular topic, or channel, and receiveall messages within the chosen topic. This model is always asynchronous.Note: Unlike a queue, a topic is a distribution mechanism for publishingmessages that are delivered to multiple subscribers.Service Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration37

NEMS, cont’dMessageProducer(Sender)A JMS client thatsends messages to aqueue.A JMS client thatreceives messagesfrom a queue.MessageConsumer(Receiver)Queue 2A staging area thatcontains messages thathave been sent and arewaiting to be read.Queue 1Service Oriented Architecture Training Session for STDDSNovember 2014P2P Messaging ModelFederal AviationAdministration38

NEMS, cont’dPub/Sub Messaging ModelMessageNote: A JMS client (Publisher)sends messages to a topic ortopics.Service Oriented Architecture Training Session for STDDSNovember 2014ProviderNote: A JMS client (Subscriber)retrieves messages from atopic or topics.Federal AviationAdministration39

NEMS, cont’dThe following diagram depicts relationship between different roles inMessaging:Service Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration40

NEMS, cont’dWS Proxy/Messaging ApproachRequests are loadbalanced to eachmanaged serverDMNBlade A1Proxy AWeb serviceClientLoadBalancer(future)Proxy facilitates:- Authentication and Access Control- Monitoring- Mediation (future)Domain ServerBlade B1Web service AProxy ABlade C1Proxy AService Oriented Architecture Training Session for STDDS11/13/2014November 2014Federal AviationAdministration41

NEMS Services & Service LifecycleSystem LevelCapabilitiesBasicBasic B1: Run-time Subscription B2: Message Reliability QoS*U1: WS-C: Web Service Consumer B3: Mediation* U2: WS-P: Web Service Producer B4: Availability &Performance* U3: JMS-C: JMSSubscription - Consumer B5: Security Services* B6: Web Services*U4: JMS-P: JMS PublishingProducerEnhanced New proposalStage 1:ServiceProposalStage 2:ServiceDefinitionStage 3:ServiceDevelopmentStage 4:ServiceVerification E1: Mediation B7: Run-time Registry E2: Performance B8: Interoperability E3: Service Orchestration B9: Service Orchestration E4: SLAs B10: Producer/ConsumerSLAs* E5: Security E6: Interoperability B11: Enterprise Repository E7: Reports B13: Global Load Balancer* E8: Dynamic Subscriptions B14: Local Load Balancers* O1: Publications to R&D On Order via contracts letterInfrastructure ServicesStage 5:ServiceProductionStage 6:ServiceDeprecationStage 7:ServiceRetirementAligns withKey SiteB12: DynamicEnhancedSubscriptions* FAA SWIM Service Lifecycle ManagementOn-RampingServicesIISWIMService LifecycleStage 2, 3, & 4QualificationSWIMService LifecycleStage 5INEMSServiceLifecycleIIIIVBase CapabilitiesOn-Ramping ServicesNEMS Inf rastructureOperationsRolloutSWIMService LifecycleStage 5,6DisconnectSWIMService LifecycleStage 7DMN, DAN, DSN, vDEX, NESGs, GLB, LLBService Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration42

Global Load Balancer Capabilities Load balance traffic among multiple geographically distributedsites Select alternate NEMS sites in the event of site failures Direct specific clients to data centers based on configured policies Key Components– DNS—This front-end process focuses on the interaction with the DNSservers.– Probes—This back-end process gathers state and load informationfrom devices within the data center such as local server loadbalancers.– Rules and associations—This process establishes a relationshipbetween the front-end and back-end process.– Global load-balancing management policy and algorithms—Theseprocesses direct client traffic to the distributed data centers based ona defined policy.Service Oriented Architecture Training Session for STDDS11/13/2014November 2014Federal AviationAdministration43

Local Load Balancer Capabilities Load balance traffic among local server poolsSelect alternate server in the event of server failuresDirect specific clients to servers based on configured policiesKey Components– VIPS— Provide entry points to the load balancer– Probes/Monitors—This back-end process gathers state and loadinformation from servers within the server pools.– Rules and associations—This process establishes a relationshipbetween the VIPS and Health Checks.– Local load-balancing management policy and algorithms—Theseprocesses send client traffic to the servers within a server poolbased on a defined policy. Status Update– Global and Local Load balancers are deployed and manageablein the NAS Ops today for NEMSService Oriented Architecture Training Session for STDDS11/13/2014November 2014Federal AviationAdministration44

Global/Local Load Balancer DeploymentOEXACYATLSLC DNSServerDNSServer DNSServerDNSServer DNSServerDNSServer DNSServerDNSServer GlobalLoadBalancerGlobalLoadBalancer GlobalLoadBalancerGlobalLoadBalancer GlobalLoadBalancerGlobalLoadBalancer C .Service Oriented Architecture Training Session for STDDS11/13/2014November 2014ARTCCARTCCFederal AviationAdministrationARTCC45

NESG Logical Architecture for 2-way SOA ServicesJMSProducer NAS Enterprise Security GatewayorInternal DMZConsumerInternalNEMSXMLMessagingNodeGWTrusted DEXMessagingNodeExternal cerorConsumer OSB will host proxies for access to internal NASservices and proxies for access to un-trusted DMNservices OSB will host proxies for access to trustedDMN Services and proxies for access toexternal services Adds security protection and monitoring point Adds security protection and monitoring pointService Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration46

NEMS Infrastructure LAZABZMEOEXExisting NEMS NodesNEMS GatewayZTLR&D and FNTB NodesZFWPlanned NEMS Nodes 2014ZJXZHUZANPNOCCZMAMission Support Nodes(Admin)ARTCC SitesFTI Operations CenterService Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration47

Agenda Service Oriented Architecture (SOA) OverviewSOA Services: Web Services and JMS ServicesSystem Wide Information Management (SWIM)Break, 10:00 - 10:15NAS Enterprise Management Services (NEMS)STDDS Program Using SWIMQ&AService Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration48

STDDS Program Using SWIMSWIM Terminal Data Distribution Service (STDDS) DeploymentTower Data LinkServices(TDLS) RunwayVisual RangeAirport SurfaceDetectionEquipment,ModelXAirport SurfaceSurveillanceCapabilityElectronicFlight StripTransfer SystemService Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration49

STDDS Current ArchitectureService Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration50

STDDS Current SystemSTDDS interfaces with the following tower systems: Airport Surface Detection Equipment Model X (ASDE-X) - STDDSreceives surface surveillance data, and sends the event data to NEMS viathe Surface Movement Event Service (SMES). In addition, STDDS sendsposition report and generic flight plan data to NEMS via SMES.Runway Visual Range (RVR) - STDDS receives RVR observations andsends them directly to NEMS via the Airport Data Service (APDS).Electronic Flight Strip Transfer System (EFSTS) - STDDS receivescontroller entered departure events (e.g. taxi start, takeoff) and sendsthem directly to NEMS via the Tower Departure Event Service (TDES).Tower Data Link Services (TDLS) - STDDS receives clearance deliveryinformation from TDLS and sends it as departure events directly to NEMSvia the TDES.Airport Surface Surveillance Capability (ASSC) data delivered to NEMSfrom the ASSC system at SFO.STARS program to obtain TAIS data through the AIG processors.Service Oriented Architecture Training Session for STDDSNovember 2014Federal AviationAdministration51

Release 3 – Interfacing with ary NEMSTDESActiveMQSTDDSWeblogicSecondary NEMSSTDDS (2 to N)ExternalClient(s) InternalClient(s)STDDS (N 1 to M)Primary NEMSSTDDS (M 1 to 39)Publish to JMS QueueFailover LinksPublish to TopicsService Oriented Architecture Training Session for STDDSNovember 2014Secondary NEMSPrimary NEMSSecondary NEMSFederal AviationAdministration52

JMS vs Web servicesSTDDS uses JMS and not Web services for the followingreasons: Most of the STDDS message are small in size but the frequency ishigh so

Service Oriented Architecture Training Session for STDDS November 2014 What is Service Oriented Architecture Service-Oriented Architecture (SOA) is a software and architecture design pattern based on a structured collection of discrete software modules known as services. SOA i

Related Documents:

"A service oriented architecture is an approach to design and integrate software in a modular method where each module is precisely a 'loosely coupled service' ,,,” “Service Oriented Architecture is nothing but business oriented architecture ” “SOA is a framework enabling

foundation for conducting business in the context of Service Oriented Architecture; the Realizing Services view which addresses the requirements for constructing a Service Oriented Architecture; and the Owning Service Oriented Architecture view which focuses on the governance and management of SOA-based systems. Status:

Web Services and Service Oriented Architecture Thomas Soddemann Delaman Workshop 2004 21 Service Oriented Architectures (SOA) Service Oriented Architecture Web Services CORBA Jini EJB An architecture of software which is composed of services. No Objects Objects Objects Objects Simple WS: No session, no state [ e.g. Shopping Cart realization?

What is Service-Oriented Architecture (SOA)? SOA is a software architecture style that focuses on service components (services) that are reusable across multiple applications and enterprises. While Service-Oriented Architecture (SOA) is an old concept, current standards and technologies have paved the way to add efficiency to IT and gain

Services view which addresses the requirements for constructing a Service Oriented Architecture; and the Owning Service Oriented Architecture view which focuses on the governance and management of SOA-based systems. Status: This document was last revised or

What is Computer Architecture? “Computer Architecture is the science and art of selecting and interconnecting hardware components to create computers that meet functional, performance and cost goals.” - WWW Computer Architecture Page An analogy to architecture of File Size: 1MBPage Count: 12Explore further(PDF) Lecture Notes on Computer Architecturewww.researchgate.netComputer Architecture - an overview ScienceDirect Topicswww.sciencedirect.comWhat is Computer Architecture? - Definition from Techopediawww.techopedia.com1. An Introduction to Computer Architecture - Designing .www.oreilly.comWhat is Computer Architecture? - University of Washingtoncourses.cs.washington.eduRecommended to you b

Service-Oriented Architecture (SOA) is a paradigm of modernized Information Technology. The design of SOA corresponds suggests shifting towards IT and its applications. As such, SOA is a referenced architecture adopted as a standard architecture [2]. In any organization the architecture can be scheme into

“Am I My Brother’s Keeper?” Cain & Abel by Tintoretto. Everything can be taken from a man but the last of the human freedoms - to choose one’s attitude in an given set of circumstances, to choose one’s own way.--Auschwitz Survivor, Victor E. Frankl Human Gene Map. OnegShabbat Archives –Emanuel Ringleblum Remembrance: To record and to teach future Generations. The time has come to .