The
AppConfig.xml file defines global application-level
configuration, including the host and port of the EAC Central Server, the
application name and whether or not SSL is to be used when communicating with
the EAC Central Server.
In addition, a default working and log
directory are specified and a default
lockManager is specified for use by other elements
defined in the document. All elements inherit these settings or override them.
<!--
########################################################################
# EAC Application Definition
#
-->
<app appName="MyApp" eacHost="myhost1.company.com" eacPort="8888"
dataPrefix="MyApp" sslEnabled="false" lockManager="LockManager">
<working-dir>${ENDECA_PROJECT_DIR}</working-dir>
<log-dir>./logs</log-dir>
</app>
The LockManager component obtains and releases locks and sets or removes flags using the EAC synchronization Web service.
A LockManager object is associated with the elements in the application, allowing multiple objects to test for the existence of locks and flags. If it is configured to release locks on failure, the Deployment Template attempts to release all acquired locks when a script or component invocation fails. Multiple LockManager components may be configured, if it is appropriate for some locks to be released on failure while others remain.
<!-- ######################################################################## # Lock Manager - Used to set/remove/test flags and obtain/release locks # --> <lock-manager id="LockManager" releaseLocksOnFailure="true" />
