Skip to content
EXPath Console for MarkLogic
JavaScript XQuery CSS HTML PHP Go
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
doc Resize the screenshot. May 9, 2016
src Refactored. Jun 3, 2019
test Alright, okay, remove the screenshot. Mar 7, 2019
tools Install guide. May 9, 2016
work New project area. Feb 20, 2016
xproject Update the Star Wars test data set. Mar 2, 2019
.gitignore Upgrade to the newest mlproj-core. Apr 10, 2018 Remove `sudo` from install notes. Nov 7, 2018

Intro Install Package manager Browser Document manager Profiler

EXPath Console for MarkLogic

The EXPath Console for MarkLogic, or just "the Console" for short, provides the following main features:

  • package manager
  • browser (for documents and triples)
  • document manager
  • XQuery profiler

The console has been written to offer an intuitive user experience. The pages should be intuitive and self-explaining. If one page does not contain enough help for you to understand what to do, please report it to the EXPath mailing list.

Screenshot of the Console

Intro Install Package manager Browser Document manager Profiler


Use mlproj. To install it, just use the following (or read the full install notes):

npm install mlproj -g

Get the latest stable version from the EXPath download area (search for the ZIP file with the name "EXPath Console for MarkLogic", and unzip it). Or clone or download the GitHub repository (the branch master should correspond to the latest stable release, when develop is the main development branch).

Then setup the databases and the app server on MarkLogic. Execute the following commands from the download directory (the one containing the src/ directory.) On the command line, override the host, username and password as needed (use -z to get prompted for the password):

mlproj -e prod -h newhost -p port:9000 setup
mlproj -e prod -h newhost deploy

If you want to use the modules straight from the file system, use the following instead (MarkLogic must be installed on localhost then):

mlproj -e dev setup

Instead of overriding some values on the command line every time (e.g. if you have to change the host name), you can create a new environment file in xproject/ml/, which imports either dev.json or prod.json, and set different values as needed. See mlproj help or for details.

If you kept the default port number, you can access the Console on http://localhost:8010/.

Intro Install Package manager Browser Document manager Profiler

Package manager

Screenshot of the package manager

The Console provides support for XAR packages. A XAR package is a collection of XML-related files, like XQuery modules, XSLT stylesheets or XML schemas. The console helps installing packages, deleting them, well, managing packages on MarkLogic. The result is that one can manage packages on MarkLogic by using a user-friendly web UI.

Packages are installed on an app server-basis (that is, a HTTP, XDBC, or ODBC app server). A specific app server has to be initialised to support packages (a package repository is created on its module database or directory). All you need to do is to click on the button Initialise when displaying an app server which has not been initialised. Then you can install a package.

If you have a XAR file on your filesystem, you can use the "Install from file" feature. Just select the file and click Install. You can also install packages straight from CXAN. CXAN is an organized, online source of packages (it is organized as a list of persons or organisations, each providing several packages, e.g. fgeorges provides the package fgeorges/fxsl, among others). The form "Install from CXAN" let you select which package you want to install, and the Console downloads it and installs it automatically.

Once a package has been installed on an app server, other modules running in the same app server can import an XQuery modules from the package, just by importing it using the module namespace. Without specifying any "at clause", decoupling dependencies between the importing and the imported modules:

import module namespace "";

Intro Install Package manager Browser Document manager Profiler


Screenshot of the browser

The browser provides you with a web UI to browse the content of a database, in a convenient, directory-like, hierarchical way.

Regardless whether or not the directories are materialized as such on the database, the Console present you with the hierarchical view of the directories, and the documents they contain. You can delete existing documents, or even entire directories, and upload files from your file system or create new documents from scratch. You can display the documents themselves (displaying their content, the collections they are part of, some meta-data, manging their permissions...) You can even edit XML and XQuery files on place with syntax highlighting!

Another way to browse the content is to browse collections. On MarkLogic, there is no such concept as a "collection directory", but here also, the Console present you in a convenient directory-like view. The collection names are simply split using "/" as a delimiter, each part being shown as a "collection directory". For each part that is an actual collection, all the documents in that collection are listed.

Finally, you can also browse the triples in a database. In that case, you browse through the flat list of all RDF "resources" in the database. A resource is any URI which appears as the subject of at least one triple. Displaying the resouce itself shows you all its properties (that is, the properties and values of all triples with the same subject URI).

Intro Install Package manager Browser Document manager Profiler

Document manager

Screenshot of the document manager

The document manager let you upload files from your file system to create new documents, as well as deleting existing documents on a database. All forms on this page, both for insertion and deletion, require to select a target database.

The simplest form is to select a simple file and give its entire URI. This is complementary to the browser, which let you create a new document under a specific "directory", if you prefer to copy and past the entire URI instead of browsing directories.

You can also upload an entire directory structure (with optional regular expressions to filter which file to upload). Or by using a ZIP file (which is then opened on MarkLogic, each of its content file becoming a new document in the database).

The last way to upload content is by providing a file containing triples (in any format supported by MarkLogic: Turtle, N3...) The file is parsed on the server, and the triples it contains are stored in the triple store as "managed triples". This is an easy way to ingest triples stored in a file if you don't want to manage which documents they are stored in.

The last forms let you delete documents and directories. You can achieve the same by using the browser, but here, you provide a complete URI instead, as a text field.

Intro Install Package manager Browser Document manager Profiler


Screenshot of the profiler

The Console also contains a profiler. It is very similar to the profiler included in the MarkLogic QConsole, except on a couple of points:

  • The execution context is a bit more clear: you select either a database, or an app server (by type), and app servers are listed with some information.
  • You can save and load the result of profiling, either in XML or in JSON.

The ability to save and load profiling reports let you save a few executions, sometimes by changing a little bit the code, and then load the reports themselves in MarkLogic and do some analysis on them. It is then possible to make some computations in XQuery or JavaScript, to see the impact of each change, or to help investigating where the time is spent.

Or with the downloaded profiling results, you can of course use tools like Excel, gnuplot, Power BI, D3, or any tool capable of drawing visualization for the changes in profiling results you get over your different modifications.

You can’t perform that action at this time.