DOCSLIB.ORG

Using the FUSE Services Framework Service Engine

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Using the FUSE Services Framework Service Engine FUSE ESB Using the FUSE Services Framework Service Engine Version 3.3 December 2007 Making Software Work Together™ Draft Draft Using the FUSE Services Framework Service Engine IONA Technologies Version 3.3 Published 12 May 2008 Copyright © 2001-2008 IONA Technologies PLC Trademark and Disclaimer Notice IONA Technologies PLC and/or its subsidiaries may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this publication. Except as expressly provided in any written license agreement from IONA Technologies PLC, the furnishing of this publication does not give you any license to these patents, trademarks, copyrights, or other intellectual property. Any rights not expressly granted herein are reserved. IONA, IONA Technologies, the IONA logo, Orbix, High Performance Integration, Artix, FUSE, and Making Software Work Together are trademarks or registered trademarks of IONA Technologies PLC and/or its subsidiaries. Java and J2EE are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. CORBA is a trademark or registered trademark of the Object Management Group, Inc. in the United States and other countries. All other trademarks that appear herein are the property of their respective owners. While the information in this publication is believed to be accurate, IONA Technologies PLC makes no warranty of any kind to this material including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. IONA shall not be liable for errors contained herein, or for incidental or consequential damages in connection with the furnishing, performance, or use of this material. Copyright Notice No part of this publication may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, photocopying, recording or otherwise, without prior written consent of IONA Technologies PLC. No third-party intellectual property right liability is assumed with respect to the use of the information contained herein. IONA Technologies PLC assumes no responsibility for errors or omissions contained in this publication. This publication and features described herein are subject to change without notice. Portions of this document may include Apache Foundation documentation, all rights reserved. Draft Draft Table of Contents Introduction to the FUSE Services Framework Service Engine ........................................................... 9 Developing a Service Using Java as a Starting Point ...................................................................... 11 Creating the SEI ............................................................................................................ 12 Annotating the Code ....................................................................................................... 15 Required Annotations ............................................................................................. 16 Optional Annotations .............................................................................................. 19 Developing a Service Using WSDL as a Starting Point ................................................................... 29 Creating a Service Unit to Deploy a Service ................................................................................. 33 Using MTOM to Process Binary Content ..................................................................................... 37 Using Message Interceptors ..................................................................................................... 39 A. Endpoint Properties ........................................................................................................... 41 B. Using the Maven Tooling ..................................................................................................... 43 Setting Up a FUSE ESB Project ......................................................................................... 44 A Service Unit Project ..................................................................................................... 46 A Service Assembly Project .............................................................................................. 47 Index .................................................................................................................................. 49 3 4 Draft Draft List of Tables 1. @WebService Properties ....................................................... 16 2. @SOAPBinding Properties ...................................................... 20 3. @WebMethod Properties ......................................................... 21 4. @RequestWrapper Properties ................................................. 22 5. @ResponseWrapper Properties ............................................... 23 6. @WebFault Properties ........................................................... 23 7. @WebParam Properties ........................................................... 25 8. @WebResult Properties ......................................................... 26 9. Optional Endpoint Attributes ................................................... 35 10. Elements Used to Configure an Endpoint's Interceptor Chain ......... 39 A.1. Endpoint Property Attributes ................................................ 41 A.2. Endpoint Property Beans ..................................................... 41 5 6 Draft Draft List of Examples 1. Simple SEI ......................................................................... 13 2. Simple Implementation Class .................................................. 14 3. Interface with the @WebService Annotation ............................... 17 4. Annotated Service Implementation Class ................................... 18 5. Specifying an RPC/LITERAL SOAP Binding with the @SOAPBinding Annotation ............................................................................. 20 6. SEI with Annotated Methods ................................................... 24 7. Fully Annotated SEI .............................................................. 26 8. FUSE Services Framework Code Generation Command .................. 29 9. Maven Configuration for Generating Starting Point Code From WSDL .................................................................................. 30 10. JBI Descriptor for a FUSE Services Framework Service Engine Service Unit ........................................................................... 33 11. Namespace Declaration for Using FUSE Services Framework Service Engine Endpoints .................................................................... 34 12. Simple Endpoint Configuration .............................................. 34 13. Adding a Jar to a Service Unit's Classpath ................................ 36 14. Configuring an Endpoint to Use MTOM .................................... 37 15. Method Using Binary Data ................................................... 38 16. Configuring an Interceptor Chain ............................................ 40 B.1. POM Elements for Using FUSE ESB Tooling ............................. 44 7 8 Draft Draft Introduction to the FUSE Services Framework Service Engine Summary The FUSE Services Framework service engine allows you to deploy JAX-WS based POJOs into the FUSE ESB and expose them as endpoints inside the ESB. Overview The FUSE Services Framework service engine allows you to develop services as annotated POJOs and deploy them as endpoints inside the ESB. Once the services are exposed inside the ESB other ESB endpoints can access the services they provide. When working with this service engine involves three steps: 1. Implementing your service logic as an annotated POJO. 2. Adding the needed configuration to your service unit. 3. Packaging the configuration and required jars into a service assembly for deployment. Key features The FUSE Services Framework service engine has the following features: • automatic WSDL generation • jsr181 support • JAX-WS Support • JAXB 2.0 support • MTOM support • Java proxy support Steps for working with the FUSE Using the FUSE Services Framework service engine to develop a service Services Framework service usually involves the following steps: engine 9 Draft Draft 1. Implementing the service's functionality using an annotated POJO. If you want to start with Java code see Developing a Service Using Java as a Starting Point. If you want to start with a WSDL contract see Developing a Service Using WSDL as a Starting Point. 2. Create a service unit to deploy the POJO into the FUSE Services Framework service engine. See Creating a Service Unit to Deploy a Service. 3. Bundle the service unit into a service assembly so it can be deployed into the FUSE ESB container. More information For more information about developing services using FUSE Services Framework see the FUSE Services Framework library. [http://open.iona.com/documentation/fuse-service-framework-documentation]. 10 Draft Draft Developing a Service Using Java as a Starting Point Summary Developing a service using a POJO is as simple as annotating your classes to add in the information needed to generate a WSDL contract. Table of Contents Creating the SEI .................................................................................................................... 12 Annotating the Code ............................................................................................................... 15 Required Annotations ....................................................................................................
Load more

Recommended publications
  • 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]
  • 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]
  • Artix ESB Release Notes
    TM Artix ESB Release Notes Version 5.1, December 2007 Making Software Work TogetherTM IONA Technologies PLC and/or its subsidiaries may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this publication. Except as expressly provided in any written license agreement from IONA Technologies PLC, the furnishing of this publication does not give you any license to these patents, trademarks, copyrights, or other intellectual property. Any rights not expressly granted herein are reserved. IONA, IONA Technologies, the IONA logo, Orbix, High Performance Integration, Artix, FUSE, and Making Software Work Together are trademarks or registered trademarks of IONA Technologies PLC and/or its subsidiaries. Java and J2EE are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. CORBA is a trademark or registered trademark of the Object Management Group, Inc. in the United States and other countries. All other trademarks that appear herein are the property of their respective owners. While the information in this publication is believed to be accurate, IONA Technologies PLC makes no warranty of any kind to this material including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. IONA shall not be liable for errors contained herein, or for incidental or consequential damages in connection with the furnishing, performance or use of this material. COPYRIGHT NOTICE No part of this publication may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, photocopying, recording or otherwise, without prior written consent of IONA Technologies PLC.
    [Show full text]
  • Service Oriented Integration with Apache Servicemix
    Service Oriented Integration With Apache ServiceMix Bruce Snyder Principal Engineer IONA Technologies Agenda • Enterprise Service Bus • Java Business Integration • Apache ServiceMix ESB www.javapolis.com What is an ESB? www.javapolis.com 4 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) www.javapolis.com 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) www.javapolis.com 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) www.javapolis.com Do I need an ESB? ESB Planning Process www.javapolis.com 8 What is JBI? www.javapolis.com 9 What is JBI? JBI defines an architecture that allows the construction of integration systems from plug-in components, that interoperate
    [Show full text]
  • Artix ESB Release Notes
    ® Artix ESB Release Notes Version 5.5, December 2008 Progress Software Corporation and/or its subsidiaries may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this publication. Except as expressly provided in any written license agreement from Progress Software Corporation, the furnishing of this publication does not give you any license to these patents, trademarks, copyrights, or other intellectual property. Any rights not expressly granted herein are reserved. Progress, IONA, Orbix, High Performance Integration, Artix, FUSE, and Making Software Work Together are trademarks or registered trademarks of Progress Software Corporation and/or its subsidiaries in the U.S. and other countries. Java and J2EE are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. CORBA is a trademark or registered trademark of the Object Management Group, Inc. in the U.S. and other countries. All other trademarks that appear herein are the property of their respective owners. While the information in this publication is believed to be accurate Progress Software Corporation makes no warranty of any kind to this material including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Progress Software Corporation shall not be liable for errors contained herein, or for incidental or consequential damages in connection with the furnishing, performance or use of this material. No part of this publication may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, photocopying, recording or otherwise, without prior written consent of IONA Technologies PLC.
    [Show full text]
  • When to Use Open Source
    When to Use Open Source Making the right decisions about open source and commercially licensed SOA software Large corporations have traditionally relied on commercially licensed (“closed source”) software for mission-critical infrastructure, but open source solutions are increasingly common in enterprise architecture. As open source technologies have earned a reputation for reliability and performance, enterprise IT organizations now deploy a mix of open and closed source software with great success. Open source software is developed collaboratively and is owned by a community rather than a single vendor. The source code is freely available, and users are permitted and encouraged to change, improve, and redistribute the software – subject to the terms of the open source license. The benefits of open source software include: Code Transparency – Enterprises enjoy full access to the source code of an open source solution, so their IT infrastructure isn’t running on a black box of proprietary code. Standards Support – Open source projects tend to be designed to support industry standards, and to interoperate with other open source and commercial technologies. Cost savings – Users do not pay a license fee to adopt open source software nor do they pay for updates, significantly reducing total cost of the project. Vendor-neutrality – True open source software is developed and owned by a developer community, so open source adopters are not locked in to a vendor’s platform by proprietary modules and technical prerequisites. Innovation – With a large community that includes end users contributing to the project, open source software provides a practical vehicle for the latest technology advancements. Despite these benefits, deploying open source software can introduce some risk: open source solutions do not always have the support and services typically provided by commercial software vendors.
    [Show full text]
  • SCA Service Component Architecture
    SSSCCCAAA SSSeeerrrvvviiiccceee CCCooommmpppooonnneeennnttt AAArrrccchhhiiittteeeccctttuuurrreee Assembly Model Specification SCA Version 1.00, March 15 2007 Technical Contacts: Michael Beisiegel IBM Corporation Henning Blohm SAP AG Dave Booz IBM Corporation Mike Edwards IBM Corporation Oisin Hurley IONA Technologies plc. Sabin Ielceanu TIBCO Software Inc. Alex Miller BEA Systems, Inc. Anish Karmarkar Oracle Ashok Malhotra Oracle Jim Marino BEA Systems, Inc. Martin Nally IBM Corporation Eric Newcomer IONA Technologies plc. Sanjay Patil SAP AG Greg Pavlik Oracle Martin Raepple SAP AG Michael Rowley BEA Systems, Inc. Ken Tam BEA Systems, Inc. Scott Vorthmann TIBCO Software Inc. Peter Walker Sun Microsystems Inc. Lance Waterman Sybase, Inc. SCA Service Component Architecture Copyright Notice © Copyright BEA Systems, Inc., Cape Clear Software, International Business Machines Corp, Interface21, IONA Technologies, Oracle, Primeton Technologies, Progress Software, Red Hat, Rogue Wave Software, SAP AG., Siemens AG., Software AG., Sun Microsystems, Inc., Sybase Inc., TIBCO Software Inc., 2005, 2007. All rights reserved. License The Service Component Architecture Specification is being provided by the copyright holders under the following license. By using and/or copying this work, you agree that you have read, understood and will comply with the following terms and conditions: Permission to copy, display and distribute the Service Component Architecture Specification and/or portions thereof, without modification, in any medium without fee or royalty is hereby granted, provided that you include the following on ALL copies of the Service Component Architecture Specification, or portions thereof, that you make: 1. A link or URL to the Service Component Architecture Specification at this location: • http://www.osoa.org/display/Main/Service+Component+Architecture+Specifications 2.
    [Show 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
    [Show full text]
  • Java Router, Deployment Guide
    Artix ESB Java Router, Deployment Guide Version 5.1 December 2007 Making Software Work Together™ Java Router, Deployment Guide IONA Technologies Version 5.1 Published 19 Dec 2007 Copyright © 1999-2007 IONA Technologies PLC Trademark and Disclaimer Notice IONA Technologies PLC and/or its subsidiaries may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this publication. Except as expressly provided in any written license agreement from IONA Technologies PLC, the furnishing of this publication does not give you any license to these patents, trademarks, copyrights, or other intellectual property. Any rights not expressly granted herein are reserved. IONA, IONA Technologies, the IONA logos, Orbix, Artix, Making Software Work Together, Adaptive Runtime Technology, Orbacus, IONA University, and IONA XMLBus are trademarks or registered trademarks of IONA Technologies PLC and/or its subsidiaries. Java and J2EE are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. CORBA is a trademark or registered trademark of the Object Management Group, Inc. in the United States and other countries. All other trademarks that appear herein are the property of their respective owners. While the information in this publication is believed to be accurate, IONA Technologies PLC makes no warranty of any kind to this material including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. IONA shall not be liable for errors contained herein, or for incidental or consequential damages in connection with the furnishing, performance, or use of this material. Copyright Notice No part of this publication may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, photocopying, recording or otherwise, without prior written consent of IONA Technologies PLC.
    [Show full text]
  • SCA/SDO Industry Collaboration Launch
    IT Firms Create New Industry Specifications to Help SOA Application Development November 30, 2005. BEA Systems, IBM Corporation, IONA Technologies, Oracle, SAP AG, Siebel Systems, Sybase, Xcalia and Zend Technologies today announced an effort to develop specifications and resulting collaborative technologies that simplify how organizations create and implement applications in a Service Oriented Architecture. Using the SOA Programming Model specifications, organizations can more easily create new and transform existing IT assets into reusable services that may be rapidly adapted to meet changing business requirements. Further, the specifications greatly reduce complexity associated with developing applications by providing a way to unify services regardless of programming language and deployment platform. The specifications take advantage of an emerging trend called Service Oriented Architecture (SOA), which structures IT assets as a series of reusable services that perform business functions. By structuring applications as a series of services, IT assets become more agile and organizations are better able to align their investments in dynamic business environments. For example, using the specifications a mortgage lender can significantly reduce the complexity of automating the loan approval process by developing a set of interconnected “services” based on existing applications tying data on new home owners including credit reports to processes for ordering home appraisals and rate locking. As a result, the lender services more customers while providing more value. In addition, by adopting these specifications organizations gain a higher degree of investment protection, because they can deploy services with a variety of middleware technologies. The SOA Programming Model specifications include the Service Component Architecture (SCA) to simplify the development of creating business services and Service Data Objects (SDO) for accessing data residing in multiple locations and formats.
    [Show full text]
  • IONA and PROGRESS SOFTWARE ANNOUNCE LICENSING and DEVELOPMENT AGREEMENT Submitted By: Saffron Communications (Hertfordshire) Tuesday, 4 April 2000
    IONA AND PROGRESS SOFTWARE ANNOUNCE LICENSING AND DEVELOPMENT AGREEMENT Submitted by: Saffron Communications (Hertfordshire) Tuesday, 4 April 2000 Progress® SonicMQ Internet Messaging Server to be integrated in IONA’s iPortal Application Server; Progress Software to license IONA’s iPortal Application Server Technology IONA Technologies (NASDAQ: IONA) and Progress Software Corporation (NASDAQ: PRGS), have announced the signing of a multi-million dollar agreement in which the companies will engage in joint development efforts and exchange best-of-breed Java 2 Enterprise Edition (J2EE) technologies. Under the license agreements, IONA will integrate Progress® SonicMQ Internet messaging server into the iPortal Application Server, and Progress Software will license IONA’s iPortal Application Server technology and incorporate it into Progress Software’s next-generation application server. Progress Software’s SonicMQ licensed by IONA Technologies SonicMQ is an award-winning, standards-based scalable messaging infrastructure for Internet application interoperation. Together with key standards beyond the JMS specification such as eXtensible Markup Language (XML), SonicMQ provides Internet resilient messaging, which is essential for effective B2B enterprise integration. SonicMQ is the first standalone Java Messaging Server (JMS) server from a major software vendor and has won several awards, including Best Java Middleware from attendees at the SIGS Conference for Java Development and a World Class Award from the magazine Java Developer's Journal. IONA’s iPortal Application Server is the only application server based on Enterprise JavaBeans technology and the Java 2 Platform that combines 'Xtreme Scalability' with an easy-to-use graphical development tool for the assembly, deployment and administration of EJB components. iPortal Application Server utilises IONA's patent-pending Adaptive Runtime Technology to deliver the most scalable EJB-based server on the market today.
    [Show full text]
  • Progress Software Corp /Ma
    PROGRESS SOFTWARE CORP /MA FORM 10-K (Annual Report) Filed 01/29/10 for the Period Ending 11/30/09 Address 14 OAK PARK BEDFORD, MA 01730 Telephone 781-280-4473 CIK 0000876167 Symbol PRGS SIC Code 7372 - Prepackaged Software Industry Software & Programming Sector Technology Fiscal Year 11/30 http://www.edgar-online.com © Copyright 2010, EDGAR Online, Inc. All Rights Reserved. Distribution and use of this document restricted under EDGAR Online, Inc. Terms of Use. Table of Contents 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, 2009 or TRANSITION REPORT PURSUANT TO SECTION 13 OR 15(d) OF THE SECURITIES EXCHANGE ACT OF 1934 Commission File Number: 033-41752 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.
    [Show full text]