In this chapter, we’ll give a short introduction to a popular application called Data Toolbox, the developers best friend for playing around with the low level NoSQL storage in Enonic XP.
Data Toolbox provides you with a web interface to visualize and manipulate your XP data, as well as other system related inforamtion. We’ll now see how to inspect content using Data Toolbox.
Data Toolbox is available on Enonic Market.
Just like Content Studio, Data toolbox should already have been installed, and can be launched from XP Admin:
XP menu →
Follow these steps to find and examine what your content looks like from the low level storage perspective:
Navigate to the
Data Treein the menu. Here, the toolbox lists repositories within your XP instance, you should at least have the following:
This is the current repository that holds your content.
This is the default repository.
This is where the audit log is stored. The audit log allows you to see a log of everything that’s been done in your XP instance, such as content creation, user administration, etc., and also tells you when it was done and by whom.
This is where XP stores core data about your system, such as installed applications and users.
This is a separate repository where scheduled jobs are stored.
com.enonic.cms.my-first-project. Here you will see two branches (as discussed above). As long as you’ve published your content, you can choose either one of these.
Keep navigating further down the tree:
content. Now you should see all the content of your site listed. Navigate to
artiststo find actual pieces of content.
Choose one of your artists and check out both the info view and the JSON view, available via the buttons in the table row.Figure 2. The Data Toolbox node info view
To inspect the data associated with the artist, you can select "Display properties", which will bring up data about the node, such as its display name, its owner, when it was created, etc.Figure 3. The display properties view
Finally, you can navigate to the
dataproperty, where you’ll find the data stored on the artist.Figure 4. The properties.data view