Security - eXist: A NoSQL Database and Application Development Platform - page 184

Subsequent to disabling the AutoDeploymentTrigger , you can also delete the
$EXIST_HOME/autodeploy folder.
Removing preinstalled EXPath packages
By default, eXist ships with a number of EXPath packages providing libraries and
applications that are installed by the autodeployment mechanism the first time eXist
is started. These packages are excellent in a development environment, but less desir‐
able in a production environment. Of particular concern are the dashboard and
eXide applications, which provide facilities for remotely administering eXist through
web pages.
If you have started eXist before disabling the autodeployment mechanism, as
described in the previous section, you may remove these applications from a running
eXist instance by executing the following XQuery (for example, from the Java Admin
Client):
xquery version "1.0" ;
import module namespace repo = "http://exist-db.org/xquery/repo" ;
(:~
: This XQuery removes the preinstalled EXPath packages
: that ship with eXist 2.1
:)
declare variable $ local:preinstalled-pkgs := (
"http://exist-db.org/apps/shared" ,
"http://exist-db.org/apps/dashboard" ,
"http://exist-db.org/apps/eXide"
);
for $ pkg in $ local:preinstalled-pkgs return (
repo:undeploy ( $ pkg ),
repo:remove ( $ pkg )
)
Securing eXist's network services
All of the network services and APIs discussed in “Disabling network services and
APIs” on page 181 rely on an underlying Java application server to actually connect
them to incoming network requests. eXist uses the Jetty application server by default,
but can be deployed into any Java application server of your choosing.
eXist ships with Jetty, servicing incoming HTTP and XML-RPC requests on TCP
port 8080 and HTTPS and XML-RPC over SSL requests on TCP port 8443. This con‐
figuration is held in the Jetty configuration file $EXIST_HOME/tools/jetty/etc/
jetty.xml .