DOCSLIB.ORG

Red Hat Jboss Fuse 6.3 Release Notes

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Red Hat JBoss Fuse 6.3 Release Notes What's new in Red Hat JBoss Fuse Last Updated: 2020-10-27 Red Hat JBoss Fuse 6.3 Release Notes What's new in Red Hat JBoss Fuse JBoss A-MQ Docs Team Content Services [email protected] Legal Notice Copyright © 2016 Red Hat. 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. The OpenStack ® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community. All other trademarks are the property of their respective owners. Abstract These notes provide an overview of the changes between each release of Red Hat JBoss Fuse. Table of Contents Table of Contents .C . H. .A . P. .T .E . R. 1.. .W . .H . .A .T . '.S . .N . E. .W . 3. 1.1. NEW FEATURES 3 1.2. IMPORTANT NOTES 3 .C . H. .A . P. .T .E . R. 2. D. .E . P. .R . E. .C . A. .T .E . D. A. .N . .D . .R . E. M. O. V. .E .D . .F . E. .A . T. U. R. E. .S . 6. 2.1. CUMULATIVE LIST OF DEPRECATED 6.X FEATURES 6 2.2. APRIL 2017 6.3 ADDENDUM 6 2.3. OCTOBER 2016 GA 7 .C . H. .A . P. .T .E . R. 3. U. N. .S . U. .P . P. O. R. .T .E . D. F. .E . A. .T .U . .R .E . S. 9. APACHE ARIES BLUEPRINT WEB MODULE IS UNSUPPORTED 9 THE PHP SCRIPTING LANGUAGE IS NOT SUPPORTED IN APACHE CAMEL ON APACHE KARAF 9 THE PYTHON SCRIPTING LANGUAGE IS NOT SUPPORTED IN APACHE CAMEL ON APACHE KARAF 9 THE INTEGRATION PACK IS NOT SUPPORTED IN FABRIC DEPLOYMENTS 9 .C . H. .A . P. .T .E . R. 4. .K .N . .O . W. N. I. S. S. .U . E. .S . 1.0 . 4.1. CVE SECURITY VULNERABILITIES 10 4.2. LIST OF KNOWN ISSUES 10 .C . H. .A . P. .T .E . R. 5. R. .E . S. .O . L. .V . E. .D . .I S. .S .U . E. .S . 1.8 . 5.1. GENERAL - 6.3.0 18 5.2. MESSAGING - 6.3.0 20 5.3. SWITCHYARD 26 5.4. ROUTING 28 5.5. CAMEL ON JBOSS EAP 48 5.6. WEB SERVICES 50 5.7. FUSE ON JBOSS EAP 69 5.8. CONTAINER - 6.3.0 69 5.9. FUSE FABRIC - 6.3.0 73 5.10. MANAGEMENT CONSOLE - 6.3.0 82 5.11. JON PLUG-INS 86 .C . H. .A . P. .T .E . R. 6. .E .N . .H . A. .N . C. .E . M. E. N. T. S. .8 . 7. 6.1. GENERAL - 6.3.0 87 6.2. MESSAGING - 6.3.0 87 6.3. SWITCHYARD 90 6.4. ROUTING 91 6.5. WEB SERVICES 124 6.6. FUSE ON JBOSS EAP 135 6.7. CONTAINER - 6.3.0 135 6.8. FUSE FABRIC - 6.3.0 137 6.9. MANAGEMENT CONSOLE - 6.3.0 138 6.10. JON PLUG-INS 139 .C . H. .A . P. .T .E . R. 7. S. .U . P. .P . O. .R . T. .E . D. C. .O . N. F. I. G. .U . R. .A . T. .I O. .N . .S . .1 4. .0 . 7.1. INFORMATION ON THE CUSTOMER PORTAL 140 1 Red Hat JBoss Fuse 6.3 Release Notes 2 CHAPTER 1. WHAT'S NEW CHAPTER 1. WHAT'S NEW Abstract This section describes the main features and changes in version 6.3. 1.1. NEW FEATURES The main new features in version 6.3 are: JBoss Fuse tooling is available in Red Hat JBoss Developer Studio starting with Developer Studio 11.0. Previously, Fuse tooling was available in Red Hat JBoss Developer Studio Integration Stack. The look and feel of the Fuse tooling Camel route editor has been revised. The Camel CDI component has been rewritten to provide better integration with the JSR 299: Contexts and Dependency Injection (CDI) programming model. See chapter "Camel CDI" in "Deploying into Apache Karaf" for more details. New Camel Braintree component (camel-braintree) provides integration with various payment systems, including PayPal. See chapter "Braintree" in "Apache Camel Component Reference" for more details. New Camel ServiceNow component (camel-servicenow) provides integration with the ServiceNow REST API. See chapter "ServiceNow" in "Apache Camel Component Reference" for more details. RH-SSO adapter for JBoss Fuse is now supported in combination with the 6.3.0 Roll Up 2 patch version of JBoss Fuse. See the section JBoss Fuse Adapter from the RH-SSO 7.1 Securing Applications and Services Guide for more details. NOTE JBoss Fuse 6.3.0 Roll Up 1 is the minimum required version, but 6.3.0 Roll Up 2 is recommended. 1.2. IMPORTANT NOTES Oracle JDK 1.7 is incompatible with Maven central repository Due to recent changes in the security requirements for connecting to the Maven central repository, Oracle JDK 1.7 is no longer compatible with Maven central and is unable to download Maven artifacts. We recommend that you upgrade to Oracle JDK 1.8 to avoid this issue. See Section 4.2, “List of Known Issues” for more details. New Maven repository Since JBoss Fuse 6.3, the JBoss Fuse Maven artifacts are available only from the following Maven repositories: https://maven.repository.redhat.com/ga 3 Red Hat JBoss Fuse 6.3 Release Notes https://maven.repository.redhat.com/earlyaccess/all Hence for JBoss Fuse 6.3, you need to edit your Maven settings.xml file, replacing the old repo.fusesource.com repository URLs (at https://repo.fusesource.com/nexus/content/repositories/releases and https://repo.fusesource.com/nexus/content/groups/ea) with the new Maven repository URLs. NOTE Older versions of JBoss Fuse (prior to 6.3) continue to use the old Maven repositories. ActiveMQ runtime can now be wired to JMS 2.0 API bundle in OSGi In JBoss Fuse 6.3, the ActiveMQ runtime has been modified so that it is compatible with and can be wired to the JMS 2.0 API bundle. This does not imply that ActiveMQ supports JMS 2.0. In fact, ActiveMQ still supports JMS 1.1 only. This change does mean, however, that it is now possible to deploy an ActiveMQ broker (which is a JMS 1.1 application) alongside a JMS 2.0 compliant application in the same OSGi container. This can be useful, for example, if you want to deploy two different messaging products in the same Apache Karaf container. Upgraded Jetty from 8.1.x to 9 In the Apache Karaf container, Jetty (which provides the default HTTP servlet container for Karaf) has been upgraded from Jetty 8.1.x to Jetty 9. This has a significant impact on the Jetty container configuration, affecting settings in the etc/org.ops4j.pax.web.cfg file, in the etc/jetty.xml file, and in the Camel Jetty endpoint. For more details, see chapter "Securing the Jetty HTTP Server" in "Security Guide" and chapter "Securing the Camel Jetty Component" in "Security Guide" . Apache Karaf package name changed from jboss-fuse-full to jboss-fuse-karaf The package name for the Apache Karaf distribution of JBoss Fuse has changed from jboss-fuse- full-ProductVersion.zip to jboss-fuse-karaf-ProductVersion.zip in this release. CXF security changes Note the following important changes to CXF security in this release: The STS (Security Token Service) now issues tokens using the RSA-SHA256 signature algorithm by default (previously RSA-SHA1), and the SHA-256 digest algorithm (previously SHA-1). The SAML/XACML functionality previously available in the cxf-rt-security module is now in the cxf-rt-security-saml module. New interceptor required for transactional RFC SAP endpoints A new interceptor object is provided in JBoss Fuse 6.3, which is needed to configure transactional RFC destinations properly for the Camel SAP component. For details, see section "Interceptor for tRFC and qRFC destinations" in "Apache Camel Component Reference". Make Quickstart Examples Available In previous releases, profiles for quickstart example were available by default. The new default behavior is that profiles for quickstart examples are not available in a new fabric. To create a fabric in which you 4 CHAPTER 1.
Recommended publications
  • Open Source Used in DNAC-Wide Area Bonjour Magneto

    Open Source Used in DNAC-Wide Area Bonjour Magneto

    Open Source Used In DNAC-Wide Area Bonjour Magneto Cisco Systems, Inc. www.cisco.com Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices. Text Part Number: 78EE117C99-1090203837 Open Source Used In DNAC-Wide Area Bonjour Magneto 1 This document contains licenses and notices for open source software used in this product. With respect to the free/open source software listed in this document, if you have any questions or wish to receive a copy of any source code to which you may be entitled under the applicable free/open source license(s) (such as the GNU Lesser/General Public License), please contact us at [email protected]. In your requests please include the following reference number 78EE117C99-1090203837 Contents 1.1 javax-activation 1.2.0 1.1.1 Available under license 1.2 metrics-servlets 3.1.0 1.3 mongodb-driver 3.0.4 1.4 jaxb-core 2.3.0 1.4.1 Available under license 1.5 antlr 2.7.6 1.5.1 Available under license 1.6 spring-boot-autoconfigure 1.5.12.RELEASE 1.7 spring-instrument 4.3.19.RELEASE 1.7.1 Available under license 1.8 nimbus-jose-jwt 4.3.1 1.9 javax-inject 1 1.9.1 Available under license 1.10 json-smart 1.3.1 1.11 opentracing-util 0.31.0 1.12 xpp3-min 1.1.3.4.O 1.12.1 Notifications 1.12.2 Available under license 1.13 ojdbc 6 1.14 jax-ws-api 2.3.0 1.15 aspect-j 1.9.2 1.15.1 Available under license 1.16 jetty-util 9.3.27.v20190418 1.17 unirest-java 1.4.5 1.18 jetty-continuation 9.3.27.v20190418 Open Source Used In
  • Weld 3.0.2.Final - CDI Reference Implementation

    Weld 3.0.2.Final - CDI Reference Implementation

    Weld 3.0.2.Final - CDI Reference Implementation CDI: Contexts and Dependency In- jection for the Java EE platform by Gavin King, Pete Muir, Jozef Hartinger, Martin Kouba, Dan Allen, and David Allen and thanks to Nicola Benaglia, Gladys Guerrero, Eun- Ju Ki,, Terry Chuang, Francesco Milesi, and Sean Wu A note about naming and nomenclature ............................................................................. ix I. Beans ............................................................................................................................ 1 1. Introduction ......................................................................................................... 5 1.1. What is a bean? ......................................................................................... 5 1.2. Getting our feet wet .................................................................................... 5 2. More about beans ................................................................................................ 9 2.1. The anatomy of a bean ............................................................................. 10 2.1.1. Bean types, qualifiers and dependency injection ............................... 10 2.1.2. Scope ............................................................................................ 13 2.1.3. EL name ........................................................................................ 13 2.1.4. Alternatives .................................................................................... 14 2.1.5. Interceptor
  • Chapter 12 Calc Macros Automating Repetitive Tasks Copyright

    Chapter 12 Calc Macros Automating Repetitive Tasks Copyright

    Calc Guide Chapter 12 Calc Macros Automating repetitive tasks Copyright This document is Copyright © 2019 by the LibreOffice Documentation Team. Contributors are listed below. You may distribute it and/or modify it under the terms of either the GNU General Public License (http://www.gnu.org/licenses/gpl.html), version 3 or later, or the Creative Commons Attribution License (http://creativecommons.org/licenses/by/4.0/), version 4.0 or later. All trademarks within this guide belong to their legitimate owners. Contributors This book is adapted and updated from the LibreOffice 4.1 Calc Guide. To this edition Steve Fanning Jean Hollis Weber To previous editions Andrew Pitonyak Barbara Duprey Jean Hollis Weber Simon Brydon Feedback Please direct any comments or suggestions about this document to the Documentation Team’s mailing list: [email protected]. Note Everything you send to a mailing list, including your email address and any other personal information that is written in the message, is publicly archived and cannot be deleted. Publication date and software version Published December 2019. Based on LibreOffice 6.2. Using LibreOffice on macOS Some keystrokes and menu items are different on macOS from those used in Windows and Linux. The table below gives some common substitutions for the instructions in this chapter. For a more detailed list, see the application Help. Windows or Linux macOS equivalent Effect Tools > Options menu LibreOffice > Preferences Access setup options Right-click Control + click or right-click
  • Administration and Configuration Guide

    Administration and Configuration Guide

    Red Hat JBoss Data Virtualization 6.4 Administration and Configuration Guide This guide is for administrators. Last Updated: 2018-09-26 Red Hat JBoss Data Virtualization 6.4 Administration and Configuration Guide This guide is for administrators. Red Hat Customer Content Services Legal Notice Copyright © 2018 Red Hat, Inc. This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed. 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, 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 Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
  • 10 Steps to Improving Your Deployment Process to Wildfly and Jboss EAP Whitepaper

    10 Steps to Improving Your Deployment Process to Wildfly and Jboss EAP Whitepaper

    10 steps to improving your deployment process to WildFly and JBoss EAP Whitepaper Table of contents Best practices for application deployments 3 Versioned artifacts together with application configuration 3 Versioned and templatized JBoss profile configuration 4 Best practices for deployments to IIS 4 Standard runtime control setup 4 Runtime control, insight, and deployment service 5 Automation 5 Automated application and configuration deployment 5 Automated JBoss middleware provisioning 5 Secure self-service 5 Integration 6 Consider components outside the Red Hat stack 6 Integrate with your development toolchain 6 Digital.ai | 10 steps to improving your deployment process to WildFly and JBoss EAP 2 Whitepaper At Digital.ai, we have decades of accumulated experience deploying to JBoss EAP and broader Red Hat middleware environments. Based on this Versioning knowledge, we have collected a list of practices and recommendations that can help you improve your 1. Versioned artifacts together with application deployment process to your JBoss- application configuration based middleware stack. 2. Versioned and templatized JBoss Many of the following practices, which we have profile configuration grouped into Versioning, Management, Automation, and Integration “tracks”, are applicable and valuable in other middleware environments too. Management The lightweight and flexible nature of JBoss1, the 3. Standard runtime control setup consequent wide variety of possible setups, and the relatively rapid pace of change of automation 4. Runtime control, insight, and interfaces, result in a number of JBoss-specific deployment service challenges too. Automation Versioning 5. Automated application and 1. Versioned artifacts together with application configuration deployment configuration 6. Automated JBoss middleware Real apps running on JBoss are more than just an EAR file.
  • Dialogic® Powermedia™ XMS JSR 309 Connector Software Installation

    Dialogic® Powermedia™ XMS JSR 309 Connector Software Installation

    Dialogic® PowerMedia™ XMS JSR 309 Connector Software Release 3.2 Installation and Configuration Guide with TeleStax JBoss Application Server February 2017 Rev 3.1 www.dialogic.com Copyright and Legal Notice Copyright © 2016-2017 Dialogic Corporation. All Rights Reserved. You may not reproduce this document in whole or in part without permission in writing from Dialogic Corporation at the address provided below. All contents of this document are furnished for informational use only and are subject to change without notice and do not represent a commitment on the part of Dialogic Corporation and its affiliates or subsidiaries ("Dialogic"). Reasonable effort is made to ensure the accuracy of the information contained in the document. However, Dialogic does not warrant the accuracy of this information and cannot accept responsibility for errors, inaccuracies or omissions that may be contained in this document. INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH DIALOGIC® PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN A SIGNED AGREEMENT BETWEEN YOU AND DIALOGIC, DIALOGIC ASSUMES NO LIABILITY WHATSOEVER, AND DIALOGIC DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF DIALOGIC PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY INTELLECTUAL PROPERTY RIGHT OF A THIRD PARTY. Dialogic products are not intended for use in certain safety-affecting situations. Please see http://www.dialogic.com/company/terms-of-use.aspx for more details. Due to differing national regulations and approval requirements, certain Dialogic products may be suitable for use only in specific countries, and thus may not function properly in other countries.
  • Release Notes for Fedora 20

    Release Notes for Fedora 20

    Fedora 20 Release Notes Release Notes for Fedora 20 Edited by The Fedora Docs Team Copyright © 2013 Fedora Project Contributors. 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/. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. 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, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. For guidelines on the permitted uses of the Fedora trademarks, refer to https:// fedoraproject.org/wiki/Legal:Trademark_guidelines. 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. All other trademarks are the property of their respective owners.
  • Third Party Library Attributions

    Third Party Library Attributions

    Third Party Library Attributions Table of Contents 1. Summary 2. PureWeb® Software Third Party Library Attributions 3. PureWeb iOS Client Libraries 3.1. Cocoa Lumberjack Framework 3.2. Sodium Crypto Library 4. ResolutionMD Server Libraries 4.1. Apache Commons 4.2. Apache PDFBox 4.3. Apache HttpComponents 4.4. Arial Unicode Font 4.5. Auto 4.6. Boost 4.7. Bootstrap 4.8. Cairo 4.9. CanJS 4.10. Curl 4.11. dcm4che2 4.12. dcm4che3 4.13. dcm4che5 4.14. DCMTK 4.15. Drools Expert 4.16. Eclipse Implementation of JAXB 4.17. Eclipse Metro 4.18. Eclipse ORB 4.19. Eclipse Project for JAX-WS 4.20. FFmpeg 4.21. FreeMarker 4.22. Freetype 4.23. FTGL 4.24. Glew 4.25. google-api-java-client 4.26. google-api-java-client-services 4.27. google-code-prettify 4.28. google-http-java-client 4.29. google-oauth-java-client 4.30. grcp-java 4.31. guava 4.32. html5shiv 4.33. HAPI 4.34. ICU 4.35. ITK 4.36. Java implementation of JSON Web Token (JWT) 4.37. Jersey 4.38. Joda-Time 4.39. jQuery 4.40. jQuery File Upload Plugin 4.41. jQuery Hashchange 4.42. jQuery UI 4.43. JSON Web Token support for the JVM 4.44. jsoup Java HTML Parser 4.45. Lo-Dash 4.46. libpng 4.47. llvm 4.48. logback 4.49. Mesa 3D Graphics Library 4.50. minizip 4.51. PixelMed 4.52. opencensus-java 4.53. requirejs 4.54. SLF4J 4.55. wysihtml5 4.56. zlib 5.
  • Migration Guide

    Migration Guide

    MIGRATION GUIDE DIGITAL EXPERIENCE MANAGER 7.2 1 MIGRATION GUIDE DIGITAL EXPERIENCE MANAGER 7.2 SUMMARY 1 INTRODUCTION ...................................................................................................................................................... 4 2 HOW TO UPGRADE FROM DIGITAL EXPERIENCE MANAGER 7.1 TO 7.2 ..................................... 5 2.1 Code base review and potential impacts .................................................................. 5 2.2 Deployment scripts/procedure review ....................................................................... 5 2.3 Test environment migration ............................................................................................ 5 3 RENDER FILTER CHANGE .................................................................................................................................... 6 3.1 Render Filters priority is now a Float instead of an Integer ............................. 6 3.1.1 Impact on the migration to Digital Experience 7.2............................................... 6 4 CUSTOM IMPLEMENTATIONS OF USERS AND GROUPS PROVIDERS ........................................... 7 5 CODE THAT NEEDS TO BE UPGRADED ........................................................................................................ 8 5.1 Overridden jmix:list’s hidden.header views need to be upgraded ................ 8 5.2 Apache PDFBox was upgraded to version 2.0.3 with API changes ............... 8 5.3 osgi:list interface needs to be changed ....................................................................
  • Open Source Licenses for Inspire R11

    Open Source Licenses for Inspire R11

    Open Source Licenses for Inspire R11 An Overview Version 11.0 GMC Software AG © 2016 GMC Software AG. All rights reserved. http://www.gmc.net/documentation CLASSIFICATION: PUBLIC Open Source Licenses for Inspire An Overview Product version 11.0 Document version 11.0.0.1 Release date: November 2016 GMC Software AG www.gmc.net See also all GMC documentation online Should you have any queries, suggestions or comments concerning these materials, please do not hesitate to contact us at [email protected]. This document contains information classified as Public. Multiple sites of the GMC Software group of companies hold certificates to ISO 9001, ISO 27001 and ISO 14001. Copyright Information contained within this document may contain technical inaccuracies or typographical errors. Changes will be added periodically and modifications will be made thereto without prior notification. GMC Software AG does not enter into any obligations or responsibilities regarding the content of this document and does not assume any legal liability – neither expressed or implied – for its accuracy, completeness and/or usefulness. Copying of the software or manual on to any data storage medium or in any other way, except for explicit company internal use, is strictly forbidden without the prior written authorization of GMC Software AG. Failure to comply with these restrictions is liable to prosecution. Trademarks GMC Software Technology and its logo are trademarks and service marks of GMC Software AG registered in Switzerland, the US and numerous other countries. Adobe and Adobe ® PDF Library™ are trademarks or registered trademarks of Adobe Systems Inc. in the US and other countries.
  • Return of Organization Exempt from Income

    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.
  • Oracle to Openjdk Migrations

    Oracle to Openjdk Migrations

    DATASHEET Make the Move from Oracle Java to Supported OpenJDK Oracle License Changes Cost of Cost of Number Number Oracle Java OpenJDK OpenLogic of Core of The new licensing requirements for Oracle Java SE Annual Annual Support Users Servers SE subscriptions have prompted many appli- Subscription Subscription cation development teams to reevaluate their 512 32 $92,160 $0 $30,880 options. 992 62 $179,280 $0 $56,080 Many teams are following analysts’ advice and adopting OpenJDK with supported and certified COST COMPARISON OF ORACLE JAVA VERSUS OPENJDK WITH OPENLOGIC SUPPORT builds from other vendors. the free OpenJDK license with OpenLogic support. Whether you have a OpenLogic can help organizations make the small or large core user base, the savings are substantial. move from Oracle Java to a supported OpenJDK The above comparison assumes the following: model with the following: • Most servers have dual, octa-core CPUs for a total • Free, certified and supported builds of of 16 cores. OpenJDK available at openlogic.com/ • The average user is in the 500 – 999 core tier priced openjdk-downloads. at $20/core/month (based on most recent Oracle Java • Enterprise support for any Java, including SE Subscription Global Price List). builds from other vendors. • The average customer has negotiated a 25% discount • Migration services to help you move seam- from Oracle. lessly from Oracle to OpenJDK. Java Support from OpenLogic Achieve Cost-Savings with Supported OpenJDK OpenLogic offers commercial support for all Java distributions, includ- ing Adopt OpenJDK, IBM, and Oracle’s Java. Based on the price of an Oracle Java SE subscription, which includes licensing and support, we’ve put Java support from OpenLogic includes security patches and bug fixes, together a conservative estimate of the annual in addition to guidance for the usage and administration of Java and the cost savings you can expect when migrating to JVM.