Client and WebDav
If you are using the recommended xml database eXist (which also is bundled up with the registry).
Then you may like to know you can get right into the database.
eXist provides you with a WebStartable client allowing you to login in via a GUI and perform
numerous amounts of tasks such as changing usernames, backups, reindex, xquery, add/remove everything
possible to manipulate the database.
Also it supports WebDav which allows you to connect various Applications like XMLSpy or Oxygen as well as
your typical File Manager normally support WebDav meaning you can view the whole database just like any other
network drive on your system.
Below is the information to get you connected as well as some hints.
If you are running in the default mode of eXist database embedded internally with your webapp.
Because you would not wish to make your database public, you must make a change to a JNDI environment entry (property).
Edit JNDI property called "reg.custom.restrict.ipaddresses" allowing you
to restrict who has access to the WebDav and client Gui.
Just make a comma seperated list of ip addresses you allow. You may even do expressions if desired such as 128.9.*.
Much like changing properties during Configure go to the 'Edit Properties' in the menu to change this property.
eXist database is not fully initialized until a query happens this can be done by simply going to almost any jsp page such as the home (index.jsp) page of your registry or
when any component calls the registry via a web service call. Hence if you connect via WebDav or client GUI and says the 'eXist' db is not initialized then please go to the
home page of your registry which will initialize it. This usually happens when there is a restart of your servlet container or eXist then you immediately tried to access it via WebDav.
Many people like the use of XML editors such as Oxygen or XMLSpy to validate and edit the XML. But it is easy
just to edit the XML directly in the Database with the Client GUI or general Text editor via WebDav.
Please be sure to take caution and validate the XML. So be sure to
set schemaLocations in your XML Editor so you can validate or to take the XML and by using the simple "Enter Resource" jsp
pages here at the registry put in the XML so it is validated and certain to go into the registry correctly.
You can launch a web start client go to eXist
and click on the 'Launch' button on the left hand side to start a client and follow the options below.:
By default the username is "admin" password is empty.
Sample url for embedded:
or most likely this:
Sample url for external:
external eXist if downloaded is by default on port 8080, but if you download the external zip file astrogrid gives you
which has a few of the settings already set then default is 6080 port.
This is all you need to know to get into the database and try reindexing, xqueries, backups, setting up users and other. Do read
the next 2 important notes:
Some important things:
Be certain if you change usernames and passwords around then you will need to change
the registry JNDI properties to reflect your changes in the database.
Do not rename xml files in the astrogrid collections, the names are based on the identifier and
used for getting 1 single Resource directly (on the GetResource interface) instead of querying for a Resource.
WebDav can be used with your database to map your database like a regular network drive, where by you
can edit, delete, add various content. Several popular apps that may interest you to connect via
WebDav are XMLSpy and Oxygen allowing you to get a more easy interface to the xml documents.
All of this can be setup and is explained on the following link:
eXist WebDav Doc
*Just one small note. Many XML Registry Resources will not have the schemaLocation stored in the database XML.
Which means for validation and to make an easy to use Interface with Oxygen or XMLSpy you will
need to set the schemalocation yourself. Down below are a list of various places to obtain
Sample Schema Location Places:
The schemaLocations below can be found at:
your local registry at:
At the time of this writing these schemas were not published.