anchor.diff:  reserved and treated specifically. See <<anchor-configuration-service>>
   for details.
   
  +WARNING: It is recommended to configure the proxy 'proxy.xml' globally and not
  +inside the workspace directory. If multiple deegree instances are operated within
  +a container, it is impossible to configure different proxies.
  +See <<anchor-global-configuration>>
  +
   TIP: The configuration format has to match the workspace subdirectory, e.g.
   metadata store configuration files are only considered when they are
   located in _datasources/metadata_.
  
positive.code: TIP: The required dependencies are specific to every type of resource and are
  documented for each resource configuration format.
  
  === Using the service console for managing resources
  
  As an alternative to dealing with the workspace resource configuration
  
negative.code: Note that the user running the web application container must have
  read/write access to this directory.
  
  
  [[anchor-global-configuration]]
  ==== Global configuration files and the active workspace
  
  If you downloaded all four example workspaces (as described in <<anchor-lightly>>), set a console password and the proxy parameters,
  