DOCSLIB.ORG

Basex Server

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Basex Server BaseX Documentation Version 7.8 BaseX Documentation: Version 7.8 Content is available under Attribution-ShareAlike 3.0 Unported (CC BY-SA 3.0). Table of Contents 1. Main Page .............................................................................................................................. 1 Getting Started .................................................................................................................. 1 XQuery Portal .................................................................................................................... 1 Advanced User's Guide ..................................................................................................... 2 I. Getting Started ........................................................................................................................ 3 2. Command-Line Options ................................................................................................... 4 BaseX Standalone ..................................................................................................... 4 BaseX Server ............................................................................................................ 6 BaseX Client ............................................................................................................. 7 BaseX HTTP Server .................................................................................................. 9 BaseX GUI .............................................................................................................. 10 Changelog ............................................................................................................... 11 3. Getting Started ............................................................................................................. 12 Getting Started ........................................................................................................ 12 User Interfaces ................................................................................................ 12 Tutorials and Slides ......................................................................................... 12 4. Start Scripts .................................................................................................................. 13 Main Package .......................................................................................................... 13 Windows: basex.bat ......................................................................................... 13 Linux/Mac: basex ............................................................................................. 13 HTTP Server ........................................................................................................... 14 Windows: basexhttp.bat ................................................................................... 14 Linux/Mac: basexhttp ....................................................................................... 14 Changelog ............................................................................................................... 14 5. Startup ......................................................................................................................... 16 Getting Started ........................................................................................................ 16 Requirements .................................................................................................. 16 Concurrent Operations ..................................................................................... 16 BaseX GUI ...................................................................................................... 16 BaseX Standalone ........................................................................................... 17 BaseX Server .................................................................................................. 17 BaseX Client ................................................................................................... 17 BaseX HTTP Server ........................................................................................ 17 Changelog ............................................................................................................... 18 II. User Interfaces ..................................................................................................................... 19 6. Database Server ........................................................................................................... 20 Startup .................................................................................................................... 20 Create a database ........................................................................................... 20 Execute a query .............................................................................................. 20 Create a new database .................................................................................... 20 Switch the database ........................................................................................ 21 Close or delete a database .............................................................................. 21 Create a collection ........................................................................................... 21 Delete a document .......................................................................................... 21 Delete a collection ........................................................................................... 22 Get server information ..................................................................................... 22 Backup and restore ......................................................................................... 22 See also .......................................................................................................... 22 7. Graphical User Interface ................................................................................................ 23 Startup .................................................................................................................... 23 Create Database .............................................................................................. 23 Realtime Options ............................................................................................. 23 Querying .......................................................................................................... 23 Visualizations ................................................................................................... 24 What’s Next? ................................................................................................... 26 iii BaseX Documentation 8. Shortcuts ...................................................................................................................... 27 Editor ...................................................................................................................... 27 Editor Shortcuts ............................................................................................... 27 Changelog ....................................................................................................... 31 9. Standalone Mode .......................................................................................................... 32 Startup .................................................................................................................... 32 Working with the BaseX Console ...................................................................... 32 See also .......................................................................................................... 32 10. Web Application .......................................................................................................... 33 Servlet Container ..................................................................................................... 33 Configuration ................................................................................................... 33 Available Services ........................................................................................... 34 Maven ..................................................................................................................... 35 Configuration ................................................................................................... 35 User Management ................................................................................................... 35 Changelog ............................................................................................................... 35 III. General Info ......................................................................................................................... 36 11. Binary Data ................................................................................................................. 37 Storage ................................................................................................................... 37 Usage ............................................................................................................. 37 12. Commands ................................................................................................................. 38 Basics ..................................................................................................................... 38 Command Scripts ...........................................................................................
Load more

Recommended publications
  • JSON Application Programming Interface for Discrete Event Simulation Data Exchange
    JSON Application Programming Interface for Discrete Event Simulation data exchange Ioannis Papagiannopoulos Enterprise Research Centre Faculty of Science and Engineering Design and Manufacturing Technology University of Limerick Submitted to the University of Limerick for the degree of Master of Engineering 2015 1. Supervisor: Prof. Cathal Heavey Enterprise Research Centre University of Limerick Ireland ii Abstract This research is conducted as part of a project that has the overall aim to develop an open source discrete event simulation (DES) platform that is expandable, and modular aiming to support the use of DES at multi-levels of manufacturing com- panies. The current work focuses on DES data exchange within this platform. The goal of this thesis is to develop a DES exchange interface between three different modules: (i) ManPy an open source discrete event simulation engine developed in Python on the SimPy library; (ii) A Knowledge Extraction (KE) tool used to populate the ManPy simulation engine from shop-floor data stored within an Enterprise Requirements Planning (ERP) or a Manufacturing Execution System (MES) to allow the potential for real-time simulation. The development of the tool is based on R scripting language, and different Python libraries; (iii) A Graphical User Interface (GUI) developed in JavaScript used to provide an interface in a similar manner to Commercial off-the-shelf (COTS) DES tools. In the literature review the main standards that could be used are reviewed. Based on this review and the requirements above, the data exchange format standard JavaScript Object Notation (JSON) was selected. The proposed solution accom- plishes interoperability between different modules using an open source, expand- able, and easy to adopt and maintain, in an all inclusive JSON file.
    [Show full text]
  • JSON JSON (Javascript Object Notation) Ecmascript Javascript
    ECMAScript JSON ECMAScript is standardized JavaScript. The current version is the 12th edition: Péter Jeszenszky Ecma International, ECMAScript 2021 Language Specification, Standard ECMA-262, 12th ed., June 2021. https://www.ecma- international.org/publications-and-standards/standards/ecma-262/ October 8, 2021 The next version currently under development is ECMAScript 2022: ECMAScript 2022 Language Specification https://tc39.es/ecma262/ Péter Jeszenszky JSON October 8, 2021 1 / 94 Péter Jeszenszky JSON October 8, 2021 3 / 94 JSON (JavaScript Object Notation) JavaScript Lightweight, textual, and platform independent data exchange format. Used for representing structured data. The term JavaScript is used for the implementations of ECMAScript by different vendors. Can be read and written easily by humans. See also: JavaScript technologies overview Can be generated and processed easily by computer programs. https://developer.mozilla.org/en- US/docs/Web/JavaScript/JavaScript_technologies_overview Originates from the ECMAScript programming language. Website: https://www.json.org/ Péter Jeszenszky JSON October 8, 2021 2 / 94 Péter Jeszenszky JSON October 8, 2021 4 / 94 JavaScript Engines (1) Node.js (1) SpiderMonkey (written in: C/C++; license: Mozilla Public License 2.0) https://spidermonkey.dev/ A JavaScript runtime environment built on the V8 JavaScript engine The JavaScript engine of the Mozilla Project. that is designed to build scalable network applications. V8 (written in: C++; license: New BSD License) https://v8.dev/ Website: https://nodejs.org/ https://github.com/nodejs/node https://github.com/v8/v8/ License: MIT License The JavaScript engine of Chromium. Written in: C++, JavaScript JavaScriptCore (written in: C++; license: LGPLv2) https://developer.apple.com/documentation/javascriptcore https: Platform: Linux, macOS, Windows //github.com/WebKit/webkit/tree/master/Source/JavaScriptCore The JavaScript engine developed for the WebKit rendering engine.
    [Show full text]
  • Declarative Access to Filesystem Data New Application Domains for XML Database Management Systems
    Declarative Access to Filesystem Data New application domains for XML database management systems Alexander Holupirek Dissertation zur Erlangung des akademischen Grades Doktor der Naturwissenschaften (Dr. rer. nat.) Fachbereich Informatik und Informationswissenschaft Mathematisch-Naturwissenschaftliche Sektion Universität Konstanz Referenten: Prof. Dr. Marc H. Scholl Prof. Dr. Marcel Waldvogel Tag der mündlichen Prüfung: 17. Juli 2012 Abstract XML and state-of-the-art XML database management systems (XML-DBMSs) can play a leading role in far more application domains as it is currently the case. Even in their basic configuration, they entail all components necessary to act as central systems for complex search and retrieval tasks. They provide language-specific index- ing of full-text documents and can store structured, semi-structured and binary data. Besides, they offer a great variety of standardized languages (XQuery, XSLT, XQuery Full Text, etc.) to develop applications inside a pure XML technology stack. Benefits are obvious: Data, logic, and presentation tiers can operate on a single data model, and no conversions have to be applied when switching in between. This thesis deals with the design and development of XML/XQuery driven informa- tion architectures that process formerly heterogeneous data sources in a standardized and uniform manner. Filesystems and their vast amounts of different file types are a prime example for such a heterogeneous dataspace. A new XML dialect, the Filesystem Markup Language (FSML), is introduced to construct a database view of the filesystem and its contents. FSML provides a uniform view on the filesystem’s contents and allows developers to leverage the complete XML technology stack on filesystem data.
    [Show full text]
  • Using Map and Reduce for Querying Distributed XML Data
    Using Map and Reduce for Querying Distributed XML Data Lukas Lewandowski Master Thesis in fulfillment of the requirements for the degree of Master of Science (M.Sc.) Submitted to the Department of Computer and Information Science at the University of Konstanz Reviewer: Prof. Dr. Marc H. Scholl Prof. Dr. Marcel Waldvogel Abstract Semi-structured information is often represented in the XML format. Although, a vast amount of appropriate databases exist that are responsible for efficiently storing semi- structured data, the vastly growing data demands larger sized databases. Even when the secondary storage is able to store the large amount of data, the execution time of complex queries increases significantly, if no suitable indexes are applicable. This situation is dramatic when short response times are an essential requirement, like in the most real-life database systems. Moreover, when storage limits are reached, the data has to be distributed to ensure availability of the complete data set. To meet this challenge this thesis presents two approaches to improve query evaluation on semi- structured and large data through parallelization. First, we analyze Hadoop and its MapReduce framework as candidate for our distributed computations and second, then we present an alternative implementation to cope with this requirements. We introduce three distribution algorithms usable for XML collections, which serve as base for our distribution to a cluster. Furthermore, we present a prototype implementation using a current open source database, named BaseX, which serves as base for our comprehensive query results. iii Acknowledgments I would like to thank my advisors Professor Marc H. Scholl and Professor Marcel Wald- vogel, who have supported me with advice and guidance throughout my master thesis.
    [Show full text]
  • Evolutionary Tree-Structured Storage: Concepts, Interfaces, and Applications
    Evolutionary Tree-Structured Storage: Concepts, Interfaces, and Applications Dissertation submitted for the degree of Doctor of Natural Sciences Presented by Marc Yves Maria Kramis at the Faculty of Sciences Department of Computer and Information Science Date of the oral examination: 22.04.2014 First supervisor: Prof. Dr. Marcel Waldvogel Second supervisor: Prof. Dr. Marc Scholl i Abstract Life is subdued to constant evolution. So is our data, be it in research, business or personal information management. From a natural, evolutionary perspective, our data evolves through a sequence of fine-granular modifications resulting in myriads of states, each describing our data at a given point in time. From a technical, anti- evolutionary perspective, mainly driven by technological and financial limitations, we treat the modifications as transient commands and only store the latest state of our data. It is surprising that the current approach is to ignore the natural evolution and to willfully forget about the sequence of modifications and therefore the past state. Sticking to this approach causes all kinds of confusion, complexity, and performance issues. Confusion, because we still somehow want to retrieve past state but are not sure how. Complexity, because we must repeatedly work around our own obsolete approaches. Performance issues, because confusion times complexity hurts. It is not surprising, however, that intelligence agencies notoriously try to collect, store, and analyze what the broad public willfully forgets. Significantly faster and cheaper random-access storage is the key driver for a paradigm shift towards remembering the sequence of modifications. We claim that (1) faster storage allows to efficiently and cleverly handle finer-granular modifi- cations and (2) that mandatory versioning elegantly exposes past state, radically simplifies the applications, and effectively lays a solid foundation for backing up, distributing and scaling of our data.
    [Show full text]
  • Applying Representational State Transfer (REST) Architecture to Archetype-Based Electronic Health Record Systems
    Applying representational state transfer (REST) architecture to archetype-based electronic health record systems Erik Sundvall, Mikael Nyström, Daniel Karlsson, Martin Eneling, Rong Chen and Håkan Örman Linköping University Post Print N.B.: When citing this work, cite the original article. Original Publication: Erik Sundvall, Mikael Nyström, Daniel Karlsson, Martin Eneling, Rong Chen and Håkan Örman, Applying representational state transfer (REST) architecture to archetype-based electronic health record systems, 2013, BMC Medical Informatics and Decision Making, (13), 57. http://dx.doi.org/10.1186/1472-6947-13-57 Licensee: BioMed Central http://www.biomedcentral.com/ Postprint available at: Linköping University Electronic Press http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-87696 Sundvall et al. BMC Medical Informatics and Decision Making 2013, 13:57 http://www.biomedcentral.com/1472-6947/13/57 SOFTWARE Open Access Applying representational state transfer (REST) architecture to archetype-based electronic health record systems Erik Sundvall1*, Mikael Nyström1, Daniel Karlsson1, Martin Eneling1, Rong Chen1,2 and Håkan Örman1 Abstract Background: The openEHR project and the closely related ISO 13606 standard have defined structures supporting the content of Electronic Health Records (EHRs). However, there is not yet any finalized openEHR specification of a service interface to aid application developers in creating, accessing, and storing the EHR content. The aim of this paper is to explore how the Representational State Transfer (REST) architectural style can be used as a basis for a platform-independent, HTTP-based openEHR service interface. Associated benefits and tradeoffs of such a design are also explored. Results: The main contribution is the formalization of the openEHR storage, retrieval, and version-handling semantics and related services into an implementable HTTP-based service interface.
    [Show full text]
  • Polishing Structural Bulk Updates in a Native XML Database
    Polishing Structural Bulk Updates in a Native XML Database Master thesis presented by Lukas Kircher Submitted to the Department of Computer and Information Science at the University of Konstanz Reviewers Prof. Dr. Marc H. Scholl Prof. Dr. Marcel Waldvogel October 2013 Abstract BaseX is a native XML database on the foundation of a fixed-length, sequen- tial document encoding. Built with a strong focus on reading performance, this thesis shows that the Pre/Dist/Size encoding is yet perfectly capable of handling massive bulk update transactions. Despite its theoretical limi- tations regarding structural changes of the tree, we show that performance is indeed restricted by the document order and disk access patterns. Dur- ing tests with the XQuery Update Facility (XQUF), we delete 1.8 million nodes in 22.4 seconds, evenly distributed over a 1.1GB XMark document in- stance. Compared to the prior approach, this equals a reduction of processing time by 99.99%. To achieve this, we extend the obligatory implementation of the XQUF pending update list with an additional low-level layer, that pre-calculates tree structure adjustments in-memory. This layer adds little overhead and further enables us to merge update operations and curb frag- mentation that finds its origin at the user level. To not violate the document order, the XQUF is only arduously brought together with the concept of effi- cient bulk updates. A method is introduced that imposes an order on update primitives to finally get a ready-to-apply sequence of atomic updates. The reviewed implementation is fully consistent with the XQUF specification and has already proven rock-solid efficiency in production use.
    [Show full text]
  • Efficient and Failure-Aware Replication of an XML Database
    Efficient and failure-aware replication of an XML database Master thesis presented by Dirk Kirsten (01/775833) Submitted to the Department of Computer and Information Science at the University of Konstanz 1st Referee Prof. Dr. Marc Scholl 2nd Referee Prof. Dr. Marcel Waldvogel Mentor Dr. Christian Grün September 2014 ABSTRACT english BaseX is a native XML database with a single point of failure. If the database server fails, the data is unreachable. Therefore, we introduce the concept of replication to BaseX to achieve high availability. We explore sev- eral update management strategies and introduce an update management suitable for the specific requirements of BaseX. As a primary is needed as updating location within our replication architecture, we present several leader election algorithms and show and implement a modified version thereof to fit our requirements. To detect failures, a probabilistic accrual failure detector is used, which is able to detect failures fast and reliably. The thesis shows a favorable performance of the systems in terms of repli- cation and transaction latency of the replication system. Hence, the used replication system high availability with a minimal performance impact in terms of transaction runtimes. deutsch BaseX ist eine native XML Datenbank, welche momentan über einen Single Point of Failure verfügt. Wenn ein einzelner Datenbankserver ausfällt, sind alle Daten nicht verfügbar. Daher wird BaseX in dieser Arbeit derart erweit- ert, indem wir das Konzept der Replikation einführen und somit Hochver- fügbarkeit erreichen. Wir präsentieren eine Übersicht über diverse Update- Management-Strategien und führen eine geeignete Strategie für BaseX ein, um die angestrebten Designziele zu erreichen.
    [Show full text]
  • Classical Hypermedia Virtues on the Web with Webstrates
    Classical Hypermedia Virtues on the Web with Webstrates Niels Olof Bouvin Clemens Nylandsted Klokmose Department of Computer Science Center for Advanced Visualization & Interaction Aarhus University, Denmark Aarhus University, Denmark [email protected] [email protected] ABSTRACT We show and analyze herein how Webstrates can augment the Web from a classical hypermedia perspective. Webstrates turns the DOM of Web pages into persistent and collaborative objects. We demonstrate how this can be applied to realize bidirectional links, shared collaborative annotations, and in-browser authorship and development. Categories and Subject Descriptors H.4.5 [Hypertext/Hypermedia]: Architectures Figure 1: Webstrates persist and synchronize through opera- Keywords tional transformations any changes to the Document Object Web, hypermedia, collaboration, dynamic documents Model of pages, called Webstrates, served from the Web- strates server to all clients of the same webstrate (from [32]). Introduction The vision of hypermedia was to create a richly intertwingled world of words, ideas, and concepts; an all-encompassing found in the form of, e.g., wikis and Web-based productivity collection of documents and works readily available for the suites such as Google Docs, these are usually either limited information worker to peruse, structure, correlate, add to, in functionality, or closed proprietary platforms. and amend using powerful tools and abstractions [15, 23, 36]. Earlier attempts have been made to rectify some of the What we have ended up with is both less and far more. shortcomings of the Web, such as augmenting the hypermedia The modern Web is all-encompassing in scope, and available functionality available [13]. Invariantly, these attempts have to a high and growing percentage of the world’s population.
    [Show full text]
  • Basex Documentation
    BaseX Documentation Version 9.1 BaseX Documentation: Version 9.1 Publication date 2018-10-31 Content is available under Attribution-ShareAlike 3.0 Unported (CC BY-SA 3.0). Table of Contents 1. Main Page ................................................................................................................................ 1 Getting Started .................................................................................................................... 1 XQuery Portal ..................................................................................................................... 1 Advanced User's Guide ......................................................................................................... 2 I. Getting Started .......................................................................................................................... 3 2. Getting Started .................................................................................................................. 4 Overview .................................................................................................................... 4 3. Startup ............................................................................................................................. 6 Getting Started ............................................................................................................ 6 Distributions ........................................................................................................ 6 Requirements ......................................................................................................
    [Show full text]
  • Xquery 3.0 69 Higher-Order Functions 75 Full-Text 82 Full-Text/Japanese 85 Xquery Update 87 Java Bindings 91 Packaging 92 Xquery Errors 95 Serialization 105
    BaseX Documentation Version 7.2 PDF generated using the open source mwlib toolkit. See http://code.pediapress.com/ for more information. PDF generated at: Sat, 24 Mar 2012 17:30:37 UTC Contents Articles Main Page 1 Getting Started 3 Getting Started 3 Startup 4 Startup Options 6 Start Scripts 13 User Interfaces 16 Graphical User Interface 16 Shortcuts 20 Database Server 23 Standalone Mode 26 Web Application 27 General Info 30 Databases 30 Binary Data 32 Parsers 33 Commands 37 Options 50 Integration 64 Integrating oXygen 64 Integrating Eclipse 66 Query Features 68 Querying 68 XQuery 3.0 69 Higher-Order Functions 75 Full-Text 82 Full-Text/Japanese 85 XQuery Update 87 Java Bindings 91 Packaging 92 XQuery Errors 95 Serialization 105 XQuery Modules 108 Cryptographic Module 108 Database Module 113 File Module 120 Full-Text Module 125 HTTP Module 128 Higher-Order Functions Module 131 Index Module 133 JSON Module 135 Map Module 140 Math Module 144 Repository Module 148 SQL Module 149 Utility Module 153 XSLT Module 157 ZIP Module 160 ZIP Module: Word Documents 162 Developing 164 Developing 164 Integrate 165 Git 166 Maven 172 Releases 174 Translations 175 HTTP Services 176 REST 176 REST: POST Schema 184 RESTXQ 185 WebDAV 189 WebDAV: Windows 7 190 WebDAV: Windows XP 192 WebDAV: Mac OSX 195 WebDAV: GNOME 197 WebDAV: KDE 199 Client APIs 201 Clients 201 Standard Mode 202 Query Mode 203 PHP Example 205 Server Protocol 206 Server Protocol: Types 210 Java Examples 212 Advanced User's Guide 214 Advanced User's Guide 214 Configuration 215 Catalog Resolver 216 Statistics 218 Backups 222 User Management 222 Transaction Management 224 Logging 225 Events 226 Indexes 228 Execution Plan 230 References Article Sources and Contributors 231 Image Sources, Licenses and Contributors 233 Article Licenses License 234 Main Page 1 Main Page Welcome to the documentation of BaseX! BaseX [1] is both a light-weight, high-performance and scalable XML Database and an XPath/XQuery Processor with full support for the W3C Update and Full Text extensions.
    [Show full text]
  • INEX Efficiency Track Meets Xquery Full Text in Basex
    INEX Efficiency Track meets XQuery Full Text in BaseX Sebastian Gath, Christian Gr¨un,Alexander Holupirek, and Marc H. Scholl <firstname>.<lastname>@uni-konstanz.de Department of Computer & Information Science Box D 188, 78457 Konstanz, Germany University of Konstanz Abstract. BaseX is an early adopter of the upcoming XQuery Full Text Recommendation. This extended abstract describes the challenges of joining the INEX Efficiency Track using BaseX, an XML database system. We will describe some of the problems we encountered during the application of XQuery Full Text to the INEX topic set and discuss the remaining comparability problem. 1 Introduction: BaseX and XQuery Full Text The existence of more than fifty XQuery processors clearly underlines the large interest in querying XML documents and collections. While many of the database- driven implementations offer their own extensions to support full-text requests, the upcoming XPath and XQuery Full Text 1.0 Recommendation [1] (XQFT) aims to satisfy the need for a unified language extension and might attract more developers and users from the Information Retrieval community. The recommen- dation offers a wide range of content-based query operations, classical retrieval tools such as Stemming and Thesaurus support, and an implementation-defined scoring model that allows developers to adapt their database to a large vari- ety of use cases and scenarios. BaseX is, to the best of our knowledge, the first implementation to fully support all features of the specification. More implemen- tations are expected to follow in the near future as soon as the recommendation has reached its final state. In this extended abstract, we present some aspects encountered during our par- ticipation in the INEX Efficiency Track 2009 using our XQFT-based database system BaseX [3, 4, 6].
    [Show full text]