1 / 10

Advanced Weather Interactive Processing System II (AWIPS II)

Advanced Weather Interactive Processing System II (AWIPS II). AWIPS Development Environment (ADE) and the Common AWIPS Visualization Environment (CAVE) Module 5: Service Oriented Architecture (SOA). Module 5: Service Oriented Architecture - EDEX. Module 5 Objectives

layne
Download Presentation

Advanced Weather Interactive Processing System II (AWIPS II)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Advanced Weather Interactive Processing System II(AWIPS II) AWIPS Development Environment (ADE)and theCommon AWIPS Visualization Environment(CAVE) Module 5: Service Oriented Architecture (SOA)

  2. Module 5: Service Oriented Architecture - EDEX Module 5 Objectives • Understand the Architectural Pattern of What Is a Service Oriented Architecture (SOA) Service • Understand How Services Are Written • Understand How Services Are Integrated Into the System • Understand How to Monitor and Test an SOA Service

  3. AbstractMessageSrv +onCall() +register() SBNsatIngestSrv +process() SOA Service Design PatternWrap the Interface to the ESB/Container Required for JMX Management of User- Defined Attributes Hides Interface Details to Container Extracts Message Calls +process() on Return Reports exceptions AbstractSrvMBean Registers with JMX for Remote Monitoring AsciiIngestSrvMBean Does the Work of the Service Return Puts Message on Outbound Endpoint

  4. AbstractMessageSrv +onCall() +register() ESB Message Event Handling to Service Reference to Mule ESB events Extracts message out Of Mule ESB event Executes +process() Method of sub class

  5. SBNSatIngestSrv +process() SOA’s Service Process Method Retrieving the message as a byte[ ] Getting a Reference to the Plugin Decoding the file name to get meta data Putting the store() on the Outbound Endpoint Sending a message to the outbound Endpoint

  6. Wiring the SOA Service Into the Container Class Reference to SOA Service Implementation ingest.xml Inbound Endpoint is a ESB File sniffer with dir reference Outbound Endpoint Virtual memory Queue SEDA scaled

  7. Mule ESB/ Container Startup Reads Wiring Mule ESB uses library scanning to build CLASSPATH (concept borrowed from ANT) start.bat start SBNsatIngestSrv Is wired in index.xml

  8. JMX Console Connects to Mule ESB Runtime(JMX Is a T05 Capability, But T04 Has Some Basics) Connect JMX to Mule (activeMQ is automatic) SBNsatIngestSrv Remote Monitoring Through JMX

  9. Exercise: Monitoring an SOA ServiceSBNsatIngestSRV Monitoring • Startup: Server Process {activeMQ, Mule, Tomcat} • Monitor Mule’s Log File • Connect JMX console to MULE • Note statistics with regards to SBNsatIngestSRV • Ingest a raw IR satellite file • Look at what happened to the log file and JMX console

  10. Extra Credit: Debug SOA Service • Same exercise as before but with step-by-step debugging • Attach Eclipse IDE debugger to Mule • Set breakpoint toward the beginning of the +process() method in SBNsatIngestSrv • Ingest the raw IR satellite file • Watch as the breakpoint is hit • Step through the code from the breakpoint, watching the variables as they change

More Related