DOCSLIB.ORG

Building a Service Oriented Architecture with the Apache Servicemix ESB Bruce Snyder IONA Technologies

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Building a Service Oriented Architecture with the Apache Servicemix ESB Bruce Snyder IONA Technologies Colorado Software Summit: October 21 – 26, 2007 © Copyright 2007, IONA Technologies Building a Service Oriented Architecture with the Apache ServiceMix ESB Bruce Snyder IONA Technologies Bruce Snyder — Building a Service Oriented Architecture with the Apache ServiceMix ESB Slide 1 Colorado Software Summit: October 21 – 26, 2007 © Copyright 2007, IONA Technologies How is SOA Like Cycling Up a Mountain? - Break down large tasks into smaller ones! -- Bite size pieces are more realistic -- Many small goals instead of one big one Bruce Snyder — Building a Service Oriented Architecture with the Apache ServiceMix ESB Slide 2 Colorado Software Summit: October 21 – 26, 2007 © Copyright 2007, IONA Technologies Build on Many Small Successes to Reach Your Goal! - Build on many small successes to reach your goal Bruce Snyder — Building a Service Oriented Architecture with the Apache ServiceMix ESB Slide 3 Colorado Software Summit: October 21 – 26, 2007 © Copyright 2007, IONA Technologies Breaking Down the Problem is Half the Battle... - SOA is: -- An architectural paradigm - SOA is not: -- A product -- One size fits all - Smaller, more distinct, distributed and reusable units of logic called services - Composite services - aggregate of - Designed to better withstand unpredictable change Bruce Snyder — Building a Service Oriented Architecture with the Apache ServiceMix ESB Slide 4 Colorado Software Summit: October 21 – 26, 2007 © Copyright 2007, IONA Technologies Service compositions are about a coordinated aggregate of services - Loose coupling - Service contracts - Autonomy - Abstraction - Reusability - Composability - Statelessness - Discoverability Bruce Snyder — Building a Service Oriented Architecture with the Apache ServiceMix ESB Slide 5 Colorado Software Summit: October 21 – 26, 2007 © Copyright 2007, IONA Technologies Services Form Composite Applications - SOA is all about composite applications -- Many reusable services aggregated into a service composition Bruce Snyder — Building a Service Oriented Architecture with the Apache ServiceMix ESB Slide 6 Colorado Software Summit: October 21 – 26, 2007 © Copyright 2007, IONA Technologies A Service Oriented Analogy - Gated community in a home owners assoc. -- Provides services (grounds maintenance, cable TV, security, clubhouse w/ pool, etc.) -- Used by many people (consumers) -- HOA community is comprised of many owners -- Adherence to basic conventions --- HOA requirements --- Address on house --- Mailbox at end of driveway --- Pay dues! Bruce Snyder — Building a Service Oriented Architecture with the Apache ServiceMix ESB Slide 7 Colorado Software Summit: October 21 – 26, 2007 © Copyright 2007, IONA Technologies A story about skydiving... - Michael Holmes - Top ten skydiver in the world - Member of the British skydiving team - Reigning New Zealand champion - 7,000+ jumps to his name - Aware of the risks of his career - Knows that panic-induced human error is to blame for almost all accidents Bruce Snyder — Building a Service Oriented Architecture with the Apache ServiceMix ESB Slide 8 Colorado Software Summit: October 21 – 26, 2007 © Copyright 2007, IONA Technologies “I didn’t have time to think about anything... really I was just angry that I’d done everything exactly as I should and it hadn’t worked.” - Michael plummeted 12,000 ft. to a failed parachute Bruce Snyder — Building a Service Oriented Architecture with the Apache ServiceMix ESB Slide 9 Colorado Software Summit: October 21 – 26, 2007 © Copyright 2007, IONA Technologies There’s no substitute for experience and knowledge of human organizational behavior in terms of SOA - People use their experience even if it doesn't apply to the current situation -- See Harwells Laws -- http://www.makingitclear.com/pages/harwellslaws.html - Industry full of hope that is pinned on cookbook SOA methodologies -- There is no one-size-fits-all SOA recipe! --- Follow this recipe and you’ll be safe --- Go through the following 10 steps and your SOA will be a success. - You might end up being, “angry that you’d done everything exactly as you should and it still didn’t work!” Bruce Snyder — Building a Service Oriented Architecture with the Apache ServiceMix ESB Slide 10 Colorado Software Summit: October 21 – 26, 2007 © Copyright 2007, IONA Technologies Java Business Integration - Standards based architecture for pluggable components in a reliable manner - Elimination of vendor lock-in - Provides a base for a service oriented architecture - JBI allows two types of plug-ins: -- Service Engines --- Provides functionality local to the NMR -- Binding Components --- Provides transports and protocols to communicate with services remote to the NMR --- Normalizes payload Bruce Snyder — Building a Service Oriented Architecture with the Apache ServiceMix ESB Slide 11 Colorado Software Summit: October 21 – 26, 2007 © Copyright 2007, IONA Technologies JBI Packaging - Packaging for configurations of components -- Service Unit (SU) --- META-INF/jbi.xml -- Service Assembly (SA) --- META-INF/jbi.xml --Similar to WARs and EARs with Java EE - Each SU is like a little Spring application -- Including dependencies - Each SA is an outer package -- SUs listed as dependencies Bruce Snyder — Building a Service Oriented Architecture with the Apache ServiceMix ESB Slide 12 Colorado Software Summit: October 21 – 26, 2007 © Copyright 2007, IONA Technologies Apache ServiceMix -- Apache License 2.0 -- Combines SOA and Event Driven Architecture --- http://enterpriseintegrationpatterns.com/docs/EDA.pdf -- Built on Apache ActiveMQ -- Implements JBI and so much more! -- Connectivity centric -- Smart Routing capabilities -- It’s very flexible! Bruce Snyder — Building a Service Oriented Architecture with the Apache ServiceMix ESB Slide 13 Colorado Software Summit: October 21 – 26, 2007 © Copyright 2007, IONA Technologies Apache ServiceMix Architecture Bruce Snyder — Building a Service Oriented Architecture with the Apache ServiceMix ESB Slide 14 Colorado Software Summit: October 21 – 26, 2007 © Copyright 2007, IONA Technologies Configuration . (conf/servicemix.xml) Bruce Snyder — Building a Service Oriented Architecture with the Apache ServiceMix ESB Slide 15 Colorado Software Summit: October 21 – 26, 2007 © Copyright 2007, IONA Technologies Developing Integrations With ServiceMix Demo Development demo using ServiceMix Bruce Snyder — Building a Service Oriented Architecture with the Apache ServiceMix ESB Slide 16 Colorado Software Summit: October 21 – 26, 2007 © Copyright 2007, IONA Technologies Visualization Bruce Snyder — Building a Service Oriented Architecture with the Apache ServiceMix ESB Slide 17 Colorado Software Summit: October 21 – 26, 2007 © Copyright 2007, IONA Technologies So What’s Coming in ServiceMix 4.0? Framework: OSGi (Apache Felix) SOAP Support: Apache CXF Message Broker: Apache ActiveMQ Routing Engine: Apache Camel Bruce Snyder — Building a Service Oriented Architecture with the Apache ServiceMix ESB Slide 18 Colorado Software Summit: October 21 – 26, 2007 © Copyright 2007, IONA Technologies What is Apache Camel? Bruce Snyder — Building a Service Oriented Architecture with the Apache ServiceMix ESB Slide 19 Colorado Software Summit: October 21 – 26, 2007 © Copyright 2007, IONA Technologies What is EIP? - The bible of integration patterns Bruce Snyder — Building a Service Oriented Architecture with the Apache ServiceMix ESB Slide 20 Colorado Software Summit: October 21 – 26, 2007 © Copyright 2007, IONA Technologies Example Pattern: Content Based Router RouteBuilder builder = new RouteBuilder() { public void configure() { from("seda:a").choice().when(header ("foo").isEqualTo("bar")).to("seda:b") .when(header("foo").isEqualTo ("cheese")).to("seda:c").otherwise().to ("seda:d"); } }; - The Java version of the Camel CBR Bruce Snyder — Building a Service Oriented Architecture with the Apache ServiceMix ESB Slide 21 Colorado Software Summit: October 21 – 26, 2007 © Copyright 2007, IONA Technologies Example Pattern: Content Based Router <camelContext id="buildSimpleRouteWithChoice" xmlns="http://activemq.apache.org/camel/schema/spring"> <route> <from uri="seda:a"/> <choice> <when> <predicate> <header name="foo"/> <isEqualTo value="bar"/> </predicate> <to uri="seda:b"/> </when> <when> <predicate> <header name="foo"/> <isEqualTo value="cheese"/> </predicate> <to uri="seda:c"/> </when> <otherwise><to uri="seda:d"/></otherwise> </choice> </route> </camelContext> - The XML version of the CBR Bruce Snyder — Building a Service Oriented Architecture with the Apache ServiceMix ESB Slide 22 Colorado Software Summit: October 21 – 26, 2007 © Copyright 2007, IONA Technologies Camel Makes Routing Much Easier! from(“http://localhost:8080/requests/”). tryBlock(). to(“activemq:queue:requests”). setOutBody(constant(“<ack/>”)). handle(Throwable.class). setFaultBody(constant(“<nack/>”)); from((“activemq:queue:requests?transacted=true”). process(requestTransformer). to(“http://host:8080/Request”). filter(xpath(“//nack”)). process(nackTransformer). to(“jdbc:store”); from(“http://localhost:8080/responses/”). tryBlock(). to(“activemq:queue:responses”). setOutBody(constant(“<ack/>”)). handle(Throwable.class). setFaultBody(constant(“<nack/>”)); from(“activemq:queue:responses?transacted=true”). process(responseTransformer). to(“jdbc:store”); from(“http://localhost:8080/pull/”). to(“jdbc:load”); - Message routing is much easier with Camel! Bruce Snyder — Building a Service Oriented Architecture with the Apache ServiceMix ESB Slide 23 Colorado Software Summit: October 21 – 26, 2007 © Copyright 2007, IONA Technologies Thank You for Attending Please fill out your surveys Bruce Snyder — Building a Service Oriented Architecture with the Apache ServiceMix ESB Slide 24.
Load more

Recommended publications
  • Talend Open Studio for Big Data Release Notes
    Talend Open Studio for Big Data Release Notes 6.0.0 Talend Open Studio for Big Data Adapted for v6.0.0. Supersedes previous releases. Publication date July 2, 2015 Copyleft This documentation is provided under the terms of the Creative Commons Public License (CCPL). For more information about what you can and cannot do with this documentation in accordance with the CCPL, please read: http://creativecommons.org/licenses/by-nc-sa/2.0/ Notices Talend is a trademark of Talend, Inc. All brands, product names, company names, trademarks and service marks are the properties of their respective owners. License Agreement The software described in this documentation is licensed under the Apache License, Version 2.0 (the "License"); you may not use this software except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0.html. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. This product includes software developed at AOP Alliance (Java/J2EE AOP standards), ASM, Amazon, AntlR, Apache ActiveMQ, Apache Ant, Apache Avro, Apache Axiom, Apache Axis, Apache Axis 2, Apache Batik, Apache CXF, Apache Cassandra, Apache Chemistry, Apache Common Http Client, Apache Common Http Core, Apache Commons, Apache Commons Bcel, Apache Commons JxPath, Apache
    [Show full text]
  • Return of Organization Exempt from Income
    OMB No. 1545-0047 Return of Organization Exempt From Income Tax Form 990 Under section 501(c), 527, or 4947(a)(1) of the Internal Revenue Code (except black lung benefit trust or private foundation) Open to Public Department of the Treasury Internal Revenue Service The organization may have to use a copy of this return to satisfy state reporting requirements. Inspection A For the 2011 calendar year, or tax year beginning 5/1/2011 , and ending 4/30/2012 B Check if applicable: C Name of organization The Apache Software Foundation D Employer identification number Address change Doing Business As 47-0825376 Name change Number and street (or P.O. box if mail is not delivered to street address) Room/suite E Telephone number Initial return 1901 Munsey Drive (909) 374-9776 Terminated City or town, state or country, and ZIP + 4 Amended return Forest Hill MD 21050-2747 G Gross receipts $ 554,439 Application pending F Name and address of principal officer: H(a) Is this a group return for affiliates? Yes X No Jim Jagielski 1901 Munsey Drive, Forest Hill, MD 21050-2747 H(b) Are all affiliates included? Yes No I Tax-exempt status: X 501(c)(3) 501(c) ( ) (insert no.) 4947(a)(1) or 527 If "No," attach a list. (see instructions) J Website: http://www.apache.org/ H(c) Group exemption number K Form of organization: X Corporation Trust Association Other L Year of formation: 1999 M State of legal domicile: MD Part I Summary 1 Briefly describe the organization's mission or most significant activities: to provide open source software to the public that we sponsor free of charge 2 Check this box if the organization discontinued its operations or disposed of more than 25% of its net assets.
    [Show full text]
  • Apache Karaf Users' Guide
    Apache Karaf Users' Guide Copyright 2010 The Apache Software Foundation 1 Table of contents • 1. Overview • 2. Quick start • 2.1. Quick Start (Source) • 3. Installation • 4. Understanding Karaf • 4.1. Console and Commands • 4.2. Remote Console • 4.3. Logging system • 4.4. Deployer • 4.5. Security framework • 4.6. Provisioning • 4.7. Administration • 4.8. Configuration • 5. Using Karaf • 5.1. Troubleshooting, Debugging and Profiling • 5.2. Developping applications • 5.3. Creating bundles for third party dependencies • 6. Advanced uses • 6.1. Extending the console • 6.2. Building custom distributions • 6.3. Programmatically connect to the console • 6.4. Embedding Karaf • 6.5. Deploying security providers • 6.6. Installing additional features • 6.7. Configuring Failover Deployments • 7. Optional Features • 7.1. Enabling Colorized Console Output On Windows 2 1. Overview Apache Karaf is a small OSGi based runtime which provides a lightweight container onto which various components and applications can be deployed. Here is a short list of features supported by the Karaf: • Hot deployment: Karaf supports hot deployment of OSGi bundles by monitoring jar files inside the [home]/deploy directory. Each time a jar is copied in this folder, it will be installed inside the runtime. You can then update or delete it and changes will be handled automatically. In addition, the Karaf also supports exploded bundles and custom deployers (blueprint and spring ones are included by default). • Dynamic configuration: Services are usually configured through the ConfigurationAdmin OSGi service. Such configuration can be defined in Karaf using property files inside the [home]/etc directory. These configurations are monitored and changes on the properties files will be propagated to the services.
    [Show full text]
  • Apache Karaf 2.2.3, the Transitive Dependencies for This POM and the Bundles Listed in Src/Main/Resources/ Bundles.Properties
    Apache Karaf Version 2.2.3 Apache Karaf Users' Guide 1 Copyright 2011 The Apache Software Foundation 2 Table of contents Overview Quick Start Users Guide Developers Guide 3 Overview 4 OVERVIEW Karaf Overview Apache Karaf is a small OSGi based runtime which provides a lightweight container onto which various components and applications can be deployed. Here is a short list of features supported by the Karaf: • Hot deployment: Karaf supports hot deployment of OSGi bundles by monitoring jar files inside the [home]/deploy directory. Each time a jar is copied in this folder, it will be installed inside the runtime. You can then update or delete it and changes will be handled automatically. In addition, Karaf also supports exploded bundles and custom deployers (Blueprint and Spring ones are included by default). • Dynamic configuration: Services are usually configured through the ConfigurationAdmin OSGi service. Such configuration can be defined in Karaf using property files inside the [home]/etc directory. These configurations are monitored and changes on the properties files will be propagated to the services. • Logging System: using a centralized logging back end supported by Log4J, Karaf supports a number of different APIs (JDK 1.4, JCL, SLF4J, Avalon, Tomcat, OSGi) • Provisioning: Provisioning of libraries or applications can be done through a number of different ways, by which they will be downloaded locally, installed and started. • Native OS integration: Karaf can be integrated into your own Operating System as a service so that the lifecycle will be bound to your Operating System. • Extensible Shell console: Karaf features a nice text console where you can manage the services, install new applications or libraries and manage their state.
    [Show full text]
  • Hänninen, Arttu Enterprise Integration Patterns in Service Oriented Systems Master of Science Thesis
    CORE Metadata, citation and similar papers at core.ac.uk Provided by Trepo - Institutional Repository of Tampere University Hänninen, Arttu Enterprise Integration Patterns in Service Oriented Systems Master of Science Thesis Examiner: Prof. Tommi Mikkonen Examiners and topic approved in the council meeting of Faculty of Information Technology on April 3rd, 2013. II TIIVISTELMÄ TAMPEREEN TEKNILLINEN YLIOPISTO Tietotekniikan koulutusohjelma Hänninen, Arttu: Enterprise Integration Patterns in Service Oriented Systems Diplomityö, 58 sivua Kesäkuu 2014 Pääaine: Ohjelmistotuotanto Tarkastajat: Prof. Tommi Mikkonen Avainsanat: Enterprise Integration Patterns, Palvelukeskeinen arkkitehtuuri (SOA), Viestipohjainen integraatio Palvelupohjaisen integraation toteuttaminen mihin tahansa tietojärjestelmään on haas- tavaa, sillä integraatioon liittyvät järjestelmät voivat muuttua jatkuvasti. Integraatiototeu- tusten tulee olla tarpeeksi joustavia, jotta ne pystyvät mukautumaan mahdollisiin muu- toksiin. Toteutukseen voidaan käyttää apuna eri sovelluskehyksiä, mutta ne eivät vält- tämättä takaa mitään standardoitua tapaa tehdä integraatio. Tätä varten on luotu joukko ohjeita (Enterprise Integration Patterns, EIP), jotka kuvaavat hyväksi havaittuja tapoja tehdä integraatioita. Tässä työssä keskitytään näiden mallien tutkimiseen ja siihen, miten niitä voidaan hyödyntää yritysjärjestelmissä. Jotta tutkimukseen saadaan konkreettinen vertailutulos, erään järjestelmän integraatioratkaisu tullaan päivittämään uuteen. Uusi ratkaisu hyödyntää sovelluskehystä,
    [Show full text]
  • Full-Graph-Limited-Mvn-Deps.Pdf
    org.jboss.cl.jboss-cl-2.0.9.GA org.jboss.cl.jboss-cl-parent-2.2.1.GA org.jboss.cl.jboss-classloader-N/A org.jboss.cl.jboss-classloading-vfs-N/A org.jboss.cl.jboss-classloading-N/A org.primefaces.extensions.master-pom-1.0.0 org.sonatype.mercury.mercury-mp3-1.0-alpha-1 org.primefaces.themes.overcast-${primefaces.theme.version} org.primefaces.themes.dark-hive-${primefaces.theme.version}org.primefaces.themes.humanity-${primefaces.theme.version}org.primefaces.themes.le-frog-${primefaces.theme.version} org.primefaces.themes.south-street-${primefaces.theme.version}org.primefaces.themes.sunny-${primefaces.theme.version}org.primefaces.themes.hot-sneaks-${primefaces.theme.version}org.primefaces.themes.cupertino-${primefaces.theme.version} org.primefaces.themes.trontastic-${primefaces.theme.version}org.primefaces.themes.excite-bike-${primefaces.theme.version} org.apache.maven.mercury.mercury-external-N/A org.primefaces.themes.redmond-${primefaces.theme.version}org.primefaces.themes.afterwork-${primefaces.theme.version}org.primefaces.themes.glass-x-${primefaces.theme.version}org.primefaces.themes.home-${primefaces.theme.version} org.primefaces.themes.black-tie-${primefaces.theme.version}org.primefaces.themes.eggplant-${primefaces.theme.version} org.apache.maven.mercury.mercury-repo-remote-m2-N/Aorg.apache.maven.mercury.mercury-md-sat-N/A org.primefaces.themes.ui-lightness-${primefaces.theme.version}org.primefaces.themes.midnight-${primefaces.theme.version}org.primefaces.themes.mint-choc-${primefaces.theme.version}org.primefaces.themes.afternoon-${primefaces.theme.version}org.primefaces.themes.dot-luv-${primefaces.theme.version}org.primefaces.themes.smoothness-${primefaces.theme.version}org.primefaces.themes.swanky-purse-${primefaces.theme.version}
    [Show full text]
  • Talend Open Studio for Big Data Release Notes
    Talend Open Studio for Big Data Release Notes 6.5.1 Contents Copyleft.......................................................................................................................3 System requirements...................................................................................................4 Talend Open Studio for Big Data: new features........................................................4 Talend Open Studio for Big Data: bug fixes............................................................. 7 Talend Open Studio for Big Data: deprecated items................................................. 7 Talend Open Studio for Big Data: known issues and limitations...............................7 Talend Open Studio for Big Data: hints and notes.................................................... 8 Documentation............................................................................................................ 9 Reporting defects and issues.................................................................................... 10 Talend Open Studio for Big Data 6.5.1 © Talend 2018 Copyleft Adapted for 6.5.1. Supersedes previous releases. Publication date: January 18, 2018 This documentation is provided under the terms of the Creative Commons Public License (CCPL). For more information about what you can and cannot do with this documentation in accordance with the CCPL, please read: http://creativecommons.org/licenses/by-nc-sa/2.0/. Notices Talend is a trademark of Talend, Inc. All brands, product names, company names, trademarks
    [Show full text]
  • Service Oriented Integration with Servicemix and Camel
    Service Oriented Integration with ServiceMix and Camel Chris Custine Principal Engineer IONA Technologies Agenda What is an ESB? What is JBI? Introduction to ServiceMix Introduction to Camel ServiceMix and Camel Working Together Roadmap for Servicemix 4.0 2 © 2007 IONA Technologies What is... an ESB? 3 © 2007 IONA Technologies What is an ESB? "An Enterprise Service Bus (ESB) is a new architecture that exploits Web services, messaging middleware, intelligent routing, and transformation. ESBs act as a lightweight, ubiquitous integration backbone through which software services and application components flow.” (Gartner) 4 © 2007 IONA Technologies What is an ESB? An ESB acts as a shared messaging layer for connecting applications and other services throughout an enterprise computing infrastructure. It supplements its core asynchronous messaging backbone with intelligent transformation and routing to ensure messages are passed reliably. Services participate in the ESB using either web services messaging standards or JMS (LooselyCoupled.com) 5 © 2007 IONA Technologies What is an ESB? An ESB is an open standards, message-based, distributed, integration solution that provides routing, invocation, and mediation services to facilitate the interactions of disparate distributed information technology resources (applications, services, information, platforms) in a reliable manner. (Brenda Michelson, Elemental Links) 6 © 2007 IONA Technologies What is... JBI? 7 © 2007 IONA Technologies What is JBI? JBI defines an architecture that allows the construction
    [Show full text]
  • Apache Karaf 2.4.1 Guides
    Apache Karaf Version 2.4.1 Apache Karaf Users' Guide 1 Copyright 2011 The Apache Software Foundation The PDF format of the Karaf Manual has been generated by Prince XML (http://www.princexml.com). 2 Table of contents Overview Quick Start Users Guide Developers Guide 3 Overview 4 OVERVIEW Karaf Overview Apache Karaf is a small OSGi based runtime which provides a lightweight container onto which various components and applications can be deployed. Here is a short list of features supported by the Karaf: • Hot deployment: Karaf supports hot deployment of OSGi bundles by monitoring jar files inside the deploy directory. Each time a jar is copied in this folder, it will be installed inside the runtime. You can then update or delete it and changes will be handled automatically. In addition, Karaf also supports exploded bundles and custom deployers (Blueprint and Spring ones are included by default). • Dynamic configuration: Services are usually configured through the ConfigurationAdmin OSGi service. Such configuration can be defined in Karaf using property files inside the etc directory. These configurations are monitored and changes on the properties files will be propagated to the services. • Logging System: using a centralized logging back end supported by Log4J, Karaf supports a number of different APIs (JDK 1.4, JCL, SLF4J, Avalon, Tomcat, OSGi) • Provisioning: Provisioning of libraries or applications can be done through a number of different ways, by which they will be downloaded locally, installed and started. • Native OS integration: Karaf can be integrated into your own Operating System as a service so that the lifecycle will be bound to your Operating System.
    [Show full text]
  • Red Hat Fuse 7.3 Release Notes
    Red Hat Fuse 7.3 Release Notes What's new in Red Hat Fuse Last Updated: 2020-06-26 Red Hat Fuse 7.3 Release Notes What's new in Red Hat Fuse Legal Notice Copyright © 2020 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
    [Show full text]
  • Interop.Jar Activation
    Resource name License name License reference Usage Type a-j-interop.jar Eclipse 1.0 http://www.j-interop.org/license.html Dynamic library http://mirrors.ibiblio.org/pub/mirrors/maven2/javax/activation/act activation-1.1.jar CDDL 1.0 ivation/1.1/activation-1.1.pom Dynamic library activation.jar LGPL 2.1 https://github.com/wildfly/wildfly/blob/master/README.md Dynamic library http://mirrors.ibiblio.org/pub/mirrors/maven2/org/apache/activem activemq-all-5.7.0.jar Apache 2.0 q/activemq-all/5.7.0/activemq-all-5.7.0.pom Dynamic library http://mirrors.ibiblio.org/pub/mirrors/maven2/org/apache/activem activemq-core-5.7.0.jar Apache 2.0 q/activemq-core/5.7.0/activemq-core-5.7.0.pom Dynamic library http://mirrors.ibiblio.org/pub/mirrors/maven2/org/apache/activem activemq-pool-5.7.0.jar Apache 2.0 q/activemq-pool/5.7.0/activemq-pool-5.7.0.pom Dynamic library http://mirrors.ibiblio.org/pub/mirrors/maven2/org/apache/activem activemq-protobuf-1.1.jar Apache 2.0 q/protobuf/activemq-protobuf/1.1/activemq-protobuf-1.1.pom Dynamic library http://mirrors.ibiblio.org/pub/mirrors/maven2/org/apache/axis2/a addressing-1.6.2.jar Apache 2.0 ddressing/1.6.2/addressing-1.6.2.pom Dynamic library advancedPersistentLookupLib-1.0.jar Commercial http://www.talend.com Dynamic library aether-api-1.11.jar Eclipse 1.0 https://www.eclipse.org/aether/download/ Dynamic library aether-connector-asynchttpclient-1.11.jar Eclipse 1.0 https://www.eclipse.org/aether/download/ Dynamic library aether-connector-wagon-1.11.jar Eclipse 1.0 https://www.eclipse.org/aether/download/ Dynamic
    [Show full text]
  • Morningstar Document Research FORM 10-K
    ® ℠ Morningstar Document Research FORM 10-K PROGRESS SOFTWARE CORP /MA - PRGS Filed: January 29, 2009 (period: November 30, 2008) Annual report which provides a comprehensive overview of the company for the past year Table of Contents UNITED STATES SECURITIES AND EXCHANGE COMMISSION Washington, D.C. 20549 FORM 10-K � ANNUAL REPORT PURSUANT TO SECTION 13 OR 15(d) OF THE SECURITIES EXCHANGE ACT OF 1934 For the Fiscal Year Ended November 30, 2008 or � TRANSITION REPORT PURSUANT TO SECTION 13 OR 15(d) OF THE SECURITIES EXCHANGE ACT OF 1934 Commission File Number: 0-19417 PROGRESS SOFTWARE CORPORATION (Exact name of registrant as specified in its charter) MASSACHUSETTS 04-2746201 (State or other jurisdiction of incorporation or organization) (I.R.S. Employer Identification No.) 14 Oak Park Bedford, Massachusetts 01730 (Address of principal executive offices) Telephone Number: (781) 280-4000 Securities registered pursuant to Section 12(b) of the Act: Title of Each Class Name of Each Exchange on Which Registered Common Stock $.01 par value The NASDAQ Stock Market LLC Securities registered pursuant to Section 12(g) of the Act: None Indicate by check mark if the registrant is a well-known seasoned issuer, as defined in Rule 405 of the Securities Act. Yes � No � Indicate by check mark if the registrant is not required to file reports pursuant to Section 13 or Section 15(d) of the Exchange Act. Yes � No � Indicate by check mark whether the registrant (1) has filed all reports required to be filed by Section 13 or 15(d) of the Securities Exchange Act of 1934 during the preceding 12 months (or for such shorter period that the registrant was required to file such reports), and (2) has been subject to such filing requirements for the past 90 days.
    [Show full text]