DOCSLIB.ORG

Coremedia 8 Migration Guide Coremedia 8 Migration Guide |

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Coremedia 8 Migration Guide Coremedia 8 Migration Guide | CoreMedia 8 //Version 7.1.8-16 CoreMedia 8 Migration Guide CoreMedia 8 Migration Guide | CoreMedia 8 Migration Guide Copyright CoreMedia AG © 2015 CoreMedia AG Ludwig-Erhard-Straße 18 20459 Hamburg International All rights reserved. No part of this manual or the corresponding program may be reproduced or copied in any form (print, photocopy or other process) without the written permission of CoreMedia AG. Germany Alle Rechte vorbehalten. CoreMedia und weitere im Text erwähnte CoreMedia Produkte sowie die entsprechenden Logos sind Marken oder eingetragene Marken der CoreMedia AG in Deutschland. Alle anderen Namen von Produkten sind Marken der jeweiligen Firmen. Das Handbuch bzw. Teile hiervon sowie die dazugehörigen Programme dürfen in keiner Weise (Druck, Fotokopie oder sonstige Verfahren) ohne schriftliche Genehmigung der CoreMedia AG reproduziert oder vervielfältigt werden. Unberührt hiervon bleiben die gesetzlich erlaubten Nutzungsarten nach dem UrhG. Licenses and Trademarks All trademarks acknowledged. 19.May 2015 CoreMedia 8 ii CoreMedia 8 Migration Guide | 1. Preface ............................................................................. 1 1.1. Audience ................................................................ 2 1.2. Typographic Conventions ........................................... 3 1.3. CoreMedia Services .................................................. 5 1.3.1. Registration .................................................. 5 1.3.2. CoreMedia Releases ....................................... 5 1.3.3. Documentation ............................................. 6 1.3.4. CoreMedia Training ........................................ 8 1.3.5. CoreMedia Support ........................................ 9 1.4. Change Chapter ..................................................... 12 2. Overview ........................................................................ 13 2.1. Supported Environments ......................................... 14 2.2. Updated and New Components and Features ............... 16 2.3. Blueprint Changes .................................................. 17 2.4. Removed Components ............................................ 18 2.5. API Changes .......................................................... 19 2.5.1. Java API ..................................................... 19 2.5.2. Studio API .................................................. 26 2.6. CLI Changes .......................................................... 28 2.7. Updated Third-Party Libraries ................................... 30 3. Migration Tasks ................................................................ 32 3.1. Prerequisites ......................................................... 33 3.2. Migrating the Project Workspace ............................... 34 3.2.1. Chef Deployment ......................................... 34 3.2.2. Content Security Policy ................................. 34 3.3. Migrating the Servers .............................................. 36 3.4. Migrating Workflows ............................................... 37 3.4.1. Publication Workflows .................................. 37 3.5. Migrating Content Types .......................................... 38 3.6. Migrating CAE Applications ...................................... 41 3.6.1. CAE Modularization ...................................... 41 3.6.2. Changes in the CAE Tag Library ....................... 42 3.7. Migrating CAE Web Resources .................................. 44 3.8. Migrating Search .................................................... 51 3.9. Migrating the CAE Feeder ........................................ 54 3.10. Migrating the Content Feeder ................................. 56 3.11. Migrating Studio Customizations ............................. 58 3.11.1. Studio Plugins ........................................... 58 3.11.2. Content Security Policy ............................... 60 3.11.3. Page Grid ................................................. 60 3.11.4. Teaser Text ............................................... 61 CoreMedia 8 iii CoreMedia 8 Migration Guide | 3.12. Migrating Multi-Site Features .................................. 63 3.12.1. Site Model/Sites Service .............................. 63 3.12.2. MultiSiteUtil ......................................... 65 3.12.3. Document Forms ....................................... 72 3.12.4. Sites Structure ........................................... 73 3.12.5. Groups and Rights ...................................... 75 3.12.6. Multi-Site Workflows .................................. 75 3.12.7. Version Cleanup ........................................ 76 3.13. Migrating Elastic Social .......................................... 77 3.13.1. Data Changes ............................................ 77 3.13.2. Migration Tool ........................................... 78 3.13.3. Performing the Migration ............................ 78 Index ................................................................................. 81 CoreMedia 8 iv CoreMedia 8 Migration Guide | List of Tables 1.1. Typographic conventions ................................................... 3 1.2. Pictographs .................................................................... 3 1.3. CoreMedia manuals .......................................................... 6 1.4. Log files check list .......................................................... 10 1.5. Changes ....................................................................... 12 2.1. Supported Operation Systems ........................................... 14 2.2. Supported Databases ...................................................... 14 2.3. Other Environments ........................................................ 14 2.4. Client environments ....................................................... 15 2.5. Changes command line tools ........................................... 28 2.6. Overview of third-party library versions .............................. 30 3.1. Changed/New CoreMedia 8 Content Types .......................... 38 3.2. CAE Module contents ...................................................... 41 3.3. CoreMedia 8 Common Template Changes ........................... 44 3.4. CoreMedia 8 Sites Template Changes ................................. 46 3.5. CoreMedia 8 Extensions Template Changes ......................... 47 3.6. CoreMedia 8 Web resources structure for each theme ........... 50 3.7. CoreMedia 8 JS Changes .................................................. 50 3.8. Substitution of MultiSiteUtil.as methods ............................ 65 3.9. Substitution of MultiSiteUtil.as constants ........................... 70 3.10. Substitution of MultiSiteUtil.java methods ........................ 70 CoreMedia 8 v CoreMedia 8 Migration Guide | List of Examples 3.1. Retrieving SitesService ................................................. 65 3.2. Retrieving SitesService ................................................. 70 3.3. Retrieving ContentSiteAspect ......................................... 70 3.4. Using multiLanguageDocumentForm ................................. 73 CoreMedia 8 vi Preface | 1. Preface This manual describes the migration from a CoreMedia 7 Blueprint system to a CoreMedia 8 Blueprint system. ➞ Chapter 2, Overview [13] gives a high-level overview of all changes. This in- cludes new, deprecated and removed components and third-party software; new operation and configuration schemes, and much more. ➞ Chapter 3, Migration Tasks [32] describes the details for the actual migration tasks according to the migration scenarios. CoreMedia 8 1 Preface | Audience 1.1 Audience This manual is intended for developers, architects, and project managers who plan to migrate from CoreMedia 7 to CoreMedia 8. Project managers and architects should review Chapter 3, Migration Tasks [32] to gain a quick understanding of the neces- sary steps. CoreMedia 8 2 Preface | Typographic Conventions 1.2 Typographic Conventions CoreMedia uses different fonts and types in order to label different elements. The following table lists typographic conventions for this documentation: Element Typographic format Example Table 1.1. Typographic conventions Source code Courier new cm systeminfo start Command line entries Parameter and values Class and method names Packages and modules Menu names and entries Bold, linked with | Open the menu entry Format|Normal Field names Italic Enter in the field Heading CoreMedia Components The CoreMedia Component Applications Use Chef Entries In quotation marks Enter "On" (Simultaneously) pressed Bracketed in "<>", linked with Press the keys <Ctrl>+<A> keys "+" Emphasis Italic It is not saved Buttons Bold, with square brackets Click on the [OK] button Code lines in code examples \ cm systeminfo \ which continue in the next line -u user Mention of other manuals Square Brackets See the [Studio Developer Manual] for more information. In addition, these symbols can mark single paragraphs: Pictograph Description Table 1.2. Pictographs Tip: This denotes a best practice or a recommendation. Warning: Please pay special attention to the text. CoreMedia 8 3 Preface | Typographic Conventions Pictograph Description Danger: The violation of these rules causes severe damage. CoreMedia 8 4 Preface | CoreMedia Services 1.3 CoreMedia Services This section describes the CoreMedia services that support you in running a Core- Media system successfully. You will find all the URLs that guide you to the right places. For most of the services you need
Load more

Recommended publications
  • The Definitive Guide to Automating Content Migration Migrating Digital Content Without Scripting Or Consultants
    White Paper The Definitive Guide to Automating Content Migration Migrating digital content without scripting or consultants. September 2012 Executive Summary Contents Today’s organizations are adopting Content Management 1 Executive Summary Systems to reduce cost, increase efficiency, and improve 2 Content Migration: The Hidden customer service, but migrating digital assets into a new CMS Challenges can be a significant effort. 3 Traditional Content Migration Too often organizations begin a migration without fully 4 Content Migration with Kapow Katalyst understanding the challenges they face—resulting in slipped deadlines, reduced scope, and even project failure. 7 Kapow Katalyst Content Migration in Action This white paper will alert you to the key issues that can arise 8 Automate Your Content Migration with Kapow Katalyst when planning and executing a CM project, and show how Kapow Katalyst™ has addressed those issues—in project after project—and enabled cost and schedule reductions up to 90%. White Paper The Definitive Guide to Automating Content Migration 2 Content Migration: The Hidden Challenges Kapow Katalyst enabled Lenovo Today’s organizations depend on sharing a wide variety of digital content, to access content held in a including websites, digital media, and documents. But selecting the right Content diverse group of data stores, Management System to house and manage your digital assets is only the first including Quest DB, Domino DB, step—the real challenges arise while migrating content to your new CMS. What static HTML, and custom .NET makes content migration (CM) so complex, unpredictable, and high-risk? Let’s applications. explore a few reasons. Digital Assets May be Missing It’s not uncommon for assets to be lost or misplaced.
    [Show full text]
  • Content Matrix 9.3 Release Notes February 2021
    Metalogix® Content Matrix 9.3 Release Notes February 2021 These release notes provide information about the latest Metalogix® Content Matrix release. · New Features · Resolved Issues · Known Issues · System Requirements · Product Licensing · Third Party Contributions · About Us New Features Version 9.3 of Metalogix Content Matrix introduces the following features: · Content Matrix supports Windows Server 2019 and SQL Server 2019. · The Content Matrix Console client application requires Microsoft .NET Framework 4.7.2 to run. · Support for the migration of Publishing sites to Communication sites has been added. · You can convert classic pages to modern pages from within Content Matrix using a solution provided by the PnP Community. · Support for the migration of classic web parts via the Import Pipeline has been added. (Refer to the SharePoint Edition user documentation for a complete list of supported web parts.) · An option has been added to the Connect to SharePoint dialog which allows you to connect to an Office 365 tenant that uses a custom domain with OAuth authentication. · Azure private container naming conventions have been implemented to make it easier to identify and delete containers and queues created by Content Matrix during migrations that use the Import Pipeline. · The following enhanced security practices have been implemented (which include practices that comply with Federal Information Processing Standards (FIPS)): § Users have the option to encrypt a connection to a SQL Server database. Content Matrix 1 § An option has been added to installer which will allow users to run Content Matrix without being a local Administrator on the machine where it is installed. § Content Matrix now validates certificates used when making on-premises SSL/TLS connections to SharePoint.
    [Show full text]
  • 1. Is the Web CMS Decision Influenced by UNT's Peer
    Proudly serving: UNT UNT | Health Science Center UNT | Dallas UNT | System Administrative Office RFP #: RFP752-20-243052-JD SUBMITTAL DUE DATE: July 17, 2020, 2:00 pm, local time TITLE: Web Content Management System DATE: July 10, 2020 Addendum #1 Please note the following clarifications are hereby made to the aforementioned RFP. Questions and Answers 1. Is the Web CMS decision influenced by UNT’s Peer Institutions? https://policy.unt.edu/peer-institutions UNT, UNT Dallas and UNT System will be included in this project. The peers list referenced in the question is used by the policy office and does not necessarily have an influence on this RFP. 2. Is the current web platform development team expected to support the new platform, or will support rely on the platform host? Either option will be considered. 3. Do any of the sites utilize a CDN? Our theme fonts and some of our modules utilize a 3rd party CDN. 4. How are new features determined to be added to a site? Current state? The necessity of features is currently decided by local site administrators to suffice the specific needs of the area/department. Features are either added by installing a ready-made module, or a custom solution can be built by campus developers/site admins. Future state? To fulfill the diverse needs of departments across campus, the vendor will need to be able to handle a considerable number of ‘Feature Requests’ or provide a system that enables campus developers to extend functionality themselves. 5. How are remediations put into place when sites do not meet WCAG compliance? UNT currently uses scanning software to identify WCAG compliance issues and site owners are responsible for remediating issues.
    [Show full text]
  • Deployment Guide for Plumtree Enterprise Web Suite 5, V6
    DEPLOYMENT GUIDE FOR THE PLUMTREE ENTERPRISE WEB SUITE 5 Version 6 May 2005 Copyright Information in this document is subject to change without notice. Companies, names, and data used in examples herein are fictitious unless otherwise noted. © 2001-2005 Plumtree Software. All rights reserved. Plumtree Software may have patents or pending patent applications, trademarks, copyrights, or other intellectual property rights covering sub- ject matter in this document. The furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property rights except as expressly provided in any written license agreement from Plumtree Software. Full licensing information is available in the files: PortalAttributions.txt; OEWCAttributions.txt; ContentServerAttributions.txt; CollaborationServerAttributions.txt; and Stu- dioServerAttributions.txt, on the Plumtree Corporate Portal 5.0 and higher; Plumtree Optional Enterprise Web Components 5.0.2 and higher; Plumtree Content Server 5.0 and higher; Plumtree Collaboration Server 3.0 and higher; and Plumtree Studio Server 2.0 and higher installation CD images. The Plumtree software (“Software”) described and covered in this document is commercial computer software developed exclusively at pri- vate expense, and in all respects is proprietary data belonging solely to Plumtree or its suppliers. (a) Department of Defense End Users. (i) If the Software is acquired by or on behalf of agencies or units of the Department of Defense (DoD), then, pursuant to DoD FAR Supplement Section 227.7202 and its successors (48 C.F.R. 227.7202) the Government’s right to use, reproduce or disclose the Software acquired under this Agreement is subject to the restrictions of the Software License Agreement between the Licensee and Plumtree.
    [Show full text]
  • Content Migration Approaches-V2
    Content Migration Approaches for Documentum M. Scott Roth Content Management Solutions Architect for Government Solutions September 20, 2008 Content Migration Approaches for Documentum Table of Contents Introduction ..................................................................................... 3 Preparation ...................................................................................... 4 Scenario 1 ....................................................................................... 5 Scenario 2 ....................................................................................... 7 Scenario 3 ..................................................................................... 10 Scenario 4 ..................................................................................... 13 Summary ....................................................................................... 19 References and Resources ................................................................ 21 About Flatirons Solutions ................................................................. 23 About the Author ............................................................................ 23 2 COPYRIGHT © 2008 FLATIRONS SOLUTIONS CORPORATION Content Migration Approaches for Documentum Introduction Recently, there has been a lot of discussion about content migration1; in the blogosphere, on the message boards, and in my company. Some of it may be fueled by the push to upgrade everyone to D6/6.5. Or, perhaps, everyone is virtualizing their infrastructure and
    [Show full text]
  • Best Practice Guidelines and Recommendations for Large-Scale Long-Term Repository Migration; for Preservation of Research Data; for Bit Preservation
    Final best practice guidelines and recommendations For Large-scale long-term repository migration; For Preservation of research data; For Bit preservation Authors Large-scale long-term repository migration: Miguel Ferreira, José Carlos Ramalho, Rui Castro, Luís Faria, Vitor Fernandes, Luís Miguel Ferros, Hélder Silva, (KEEP Solutions), Ivan Vujic (Microsoft Research), Opher Kutner (Ex Libris), Lynne Chivers (British Library), Kåre Fiedler Christiansen (State & University Library of Denmark), Stanislav Barton (Internet Memory) Preservation of research data: Catherine Jones, Simon Lambert (Science and Technology Facilities Council), Barbara Sierman (National Library of the Netherlands), Kirnn Kaur (British Library) Bit preservation: Lieke Ploeger, Barbara Sierman (National Library of the Netherlands), Catherine Jones (Science and Technology Facilities Council), Bram van der Werf (Open Planets Foundation), Ivan Vujic (Microsoft Research), Opher Kutner (Ex Libris), Kirnn Kaur (British Library) February 2014 This work was partially supported by the SCAPE Project. The SCAPE project is co-funded by the European Union under FP7 ICT-2009.4.1 (Grant Agreement number 270137). This work is licensed under a CC-BY-SA International License Introduction to the best practice guidelines and recommendations The SCAPE project1 aims to enhance the state of the art in digital preservation with a particular emphasis on the scalability of its solutions: that is, their capacity to handle digital objects that may be very numerous, individually very large, heterogeneous or complex. The motivating force of the SCAPE project is scalability, interpreted in several dimensions: number of objects, size of objects, complexity of objects, and heterogeneity of collections. The best practice guidelines and recommendations cover three areas of digital preservation.
    [Show full text]
  • Open Source Content Management Systems Redux
    Vol. 11, No. 3 April, 2003 www.gilbane.com Published by: Bluebill Advisors, Inc. 763 Massachusetts Ave. Cambridge, MA 02139 USA (617) 497.9443 ™ Fax (617) 497.5256 www.bluebilladvisors.com Editor: Frank Gilbane [email protected] (617) 497.9443 Content, Computing, and Commerce – Technology & Trends Editors Emeriti: Tim Bray [email protected] (604) 708.9592 David Weinberger OPEN SOURCE CONTENT MANAGEMENT [email protected] (617) 738.8323 Senior Editors: SYSTEMS REDUX Sebastian Holst [email protected] Bill Trippe We looked at Open Source software and what it meant to the content [email protected] (617) 497.9443 management market a couple of years ago. Since then there has been a huge amount of both development and implementation. Contributor Bob Recent Contributors: Girish Altekar Doyle helped put together the Third Annual OSCOM (Open Source Con- [email protected] tent Management System) conference at Harvard Law School a few weeks Bob Boiko ago, and also attended the recent Massachusetts Software and Internet [email protected] JoAnn Hackos Council series of Technology Roundtables on Open Source. Bob provides [email protected] an update on developments and issues in the Open Source CMS market – Rita Warren [email protected] some of which may surprise you! Production Assistant: Sarah G. Dionne Welcome Sebastian! [email protected] Industry veteran Sebastian Holst (who also wrote our earlier article on (617) 497.9443 Open Source as a contributor) has now joined us a Senior Editor. In addi- Subscriptions: tion, Sebastian will be heading-up our consulting activity. You can reach [email protected] (617) 497.9443 him at [email protected].
    [Show full text]
  • Content Matrix 9.1 Release Notes February 2020
    Metalogix® Content Matrix 9.1 Release Notes February 2020 These release notes provide information about the latest Metalogix® Content Matrix release. · New Features · Resolved Issues · Known Issues · System Requirements · Product Licensing · Third Party Contributions · About Us New Features Version 9.1 of Metalogix Content Matrix introduces the following features: · For SharePoint Edition migrations to SharePoint Online that Use Azure/SPO Container Office 365 Upload, you can monitor the progress of the job from the time it is submitted through its completion, including Microsoft-side processing. · Office O365 OAuth Authentication can now be used for PowerShell migration (as long as the job is configured in the UI) and Distributed/Self-Service migration. · Nintex Forms can now be migrated to a SharePoint on-premises target. (Refer to SharePoint Edition help for limitations.) · The Email Viewer WSP, formerly used but no longer needed to view .MSG and .EML files migrated from Public Folder Edition, has been removed from the installer. Resolved Issues The following is a list of issues addressed in this release. Description Work Item Case No. The issue "When using Public Folder Edition for a large 437698 4570303-1 migration from Exchange (MAPI) to SPO using Azure Metalogix Content Matrix 1 Release Notes Description Work Item Case No. pipeline, the message One or more errors occurred is logged" has been resolved. The issue "When using Public Folder Edition, an error in 440327 4561346-1 IMAPISession occurs while retrieving properties for few emails for a PST source" has been resolved. The issue “When using Public Folder Edition, the error 432203 4567398-1 message The remote server returned an error: (404) Not Found occurs while migrating data to SPO Azure from a PST file having 1GB data" has been resolved.
    [Show full text]
  • Administering My Webmethods Server
    Administering My webMethods Server Version 10.3 October 2018 This document applies to My webMethods Server 10.3 and to all subsequent releases. Specifications contained herein are subject to change and these changes will be reported in subsequent release notes or new editions. Copyright © 2004-2020 Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors. The name Software AG and all Software AG product names are either trademarks or registered trademarks of Software AG and/or Software AG USA Inc. and/or its subsidiaries and/or its affiliates and/or their licensors. Other company and product names mentioned herein may be trademarks of their respective owners. Detailed information on trademarks and patents owned by Software AG and/or its subsidiaries is located at http://softwareag.com/licenses/. Use of this software is subject to adherence to Software AG's licensing conditions and terms. These terms are part of the product documentation, located at http://softwareag.com/licenses/ and/or in the root installation directory of the licensed product(s). This software may include portions of third-party products. For third-party copyright notices, license terms, additional rights or restrictions, please refer to "License Texts, Copyright Notices and Disclaimers of Third Party Products". For certain specific third-party license restrictions, please refer to section E of the Legal Notices available under "License Terms and Conditions for Use of Software AG Products / Copyright and Trademark Notices of Software AG Products". These documents are part of the product documentation, located at http://softwareag.com/licenses/ and/or in the root installation directory of the licensed product(s).
    [Show full text]
  • Migrating a Web Site to Drupal Smoothly Transfer Content, Users, Interface, and Metadata
    Migrating a Web Site to Drupal Smoothly Transfer Content, Users, Interface, and Metadata Abstract: Drupal’s advantages for running enterprise web sites are well established by such companies as FedEx, The Economist, and The White House. But many who would like to use it hesitate because they fear loss of assets now managed by their current site’s platform, or expect the procedure to transfer those assets to be prohibitively difficult. This paper examines scenarios for migrating from other content-management systems (CMSes) such as Vignette, Jive, FatWire, ColdFusion, and Joomla. It evaluates reasons for migration, describes migration methods and tools, and suggests best practices. MSKU#: 0046 2 Migrating a Web Site to Drupal Executive Summary Web sites become harder to maintain as they age. First, evolving web trends demand capabilities that older technologies don’t have. Second, enterprise data and site structure become messy, calling for a reorganization. Third, business factors (such as the availability of qualified consultants) may make the legacy system uneconomic to maintain. Many organizations seek to address all three problems by migrating their sites to a modern CMS. But standing in their way are uncertainties about the migration process, among them: s How can we best plan the migration? s Will we be able to transfer all our data, including users, tags, and metadata? s Do the reasons for migrating justify the costs? This paper answers such questions, particularly as they relate to migrations from such common enterprise CMSes as Jive, Vignette, FatWire, ColdFusion, and Joomla1, as well as from sites built in static HTML.
    [Show full text]
  • Panopticon 2021.1 Visualization Server Installation & Reference Guide
    Altair® Panopticon™ v2021.1 VISUALIZATION SERVER INSTALLATION AND REFERENCE GUIDE TABLE OF CONTENTS [1] INTRODUCTION ....................................................................................................................................... 1 Overview ......................................................................................................................................................... 1 System Requirements ..................................................................................................................................... 1 System Hardware Requirements ...................................................................................................... 3 [2] SETUP ....................................................................................................................................................... 5 Installation Packages ...................................................................................................................................... 5 Panopticon Visualization Server Deployment Model ........................................................................ 6 Server Platforms ............................................................................................................................... 7 Environment Promotion Options ..................................................................................................................... 8 Installation ......................................................................................................................................................
    [Show full text]
  • Oracle Webcenter Content System Administrator's Guide for Oracle
    Oracle® WebCenter Content System Administrator's Guide for Content Server 11g Release 1 (11.1.1) E10792-04 November 2011 Oracle WebCenter Content System Administrator's Guide for Content Server, 11g Release 1 (11.1.1) E10792-04 Copyright © 2010, 2011, Oracle and/or its affiliates. All rights reserved. Primary Author: Karen Johnson Contributors: Asif Bashar, Aaron Briel, Bing Hua, Bob Lies, Arun Mannava, Ron Mellum, John Neely, Mark Plotnick, Yaswanth Ravella, David Tom, Ron van de Crommert, Bonnie Vaughan, Martin Wykes, Jean Wilson, Hui Ye, Michael Zanchelli This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.
    [Show full text]