Presenceconfig.xml

From PresenceWiki
Revision as of 08:01, 12 August 2015 by Rob (Talk | contribs)

Jump to: navigation, search

This is the main Presence configuration XML file. It is located in the "res/config/" directory within the Presence installation directory.

The following is a sample of a typical presenceconfig.xml file:

<?xml version="1.0" encoding="UTF-8"?>
<presence-config>
    <database>
<!-- Pointbase Pre version 4 -->
  <!--      <host url="jdbc:pointbase:server://mattxp/presence"/>
        <credentials password="932fc95d5255fd3b8aeb772886349141" username="admin"/>
        <jdbc-driver>com.pointbase.jdbc.jdbcUniversalDriver</jdbc-driver>
-->

<!-- Hyper SQL Version 4+ -->
        <database use_sql_to_validate_db_connection="true" validation_sql="select count(1) from INFORMATION_SCHEMA.DOMAINS">
        <host url="jdbc:hsqldb:hsql://robw7/presence"/>
        <credentials password="PBSYSADMIN" username="PBSYSADMIN"/>

    </database>
    <lookandfeel>system</lookandfeel>
    <!-- Defines how Presence writes files. Values can be overridden at task element level. -->
    <file-settings>
        <!-- may be "system", "unix" or "windows" -->
        <line-separators>system</line-separators>
        <!-- select attribute may be "auto", "system", "unicode" or "specify" 
			auto - if characters outside the system character set are found, UTF-16LE will be used. Otherwise
					the system default character set will be used.
			system - always uses the system character set. Characters outside this will be written as '?'.
			unicode - always uses UTF-16LE to write characters. Two bytes are used for each character.
			specify - always use the specified character set. charset attribute must have a value which
						is the character set to use.
		-->
        <encoding charset="" select="auto"/>
    </file-settings>
    <primary-server>
        <encryption-server port="8217"/>
        <debug-engine port="8218"/>
        <admin-listener port="8215"/>
        <on-demand-server port="8221"/>
        <ws-server port="8241"/>
        <heartbeat port="8230"/>
        <channel-subscription-server port="8081"/>
    </primary-server>
    <rpc-server port="8220"/>
    <slave-server>
        <on-demand-server port="8222"/>
        <slave-task-runner port="8219"/>
        <heartbeat port="8231"/>
    </slave-server>
    <administrator email="pryor@european-presence.com"/>
    <ws-settings>
        <service soapAddress="http://david/presencews"/>
    </ws-settings>
    <proxy-settings>
        <http>
            <proxyHost>none</proxyHost>
            <proxyPort>80</proxyPort>
            <nonProxyHosts>
                <!--
					This is a list of hosts that Presence should connect to directly
					instead of via the proxy server. Host names can contain the full name
					of the host (eg "localhost"), or wildcard patterns, eg "*.mynetwork.com"
				-->
                <host>localhost</host>
            </nonProxyHosts>
        </http>
        <ftp>
            <proxyHost>none</proxyHost>
            <proxyPort>none</proxyPort>
            <nonProxyHosts>
                <!-- as with http nonProxyHosts list, see above. -->
                <host>localhost</host>
            </nonProxyHosts>
        </ftp>
    </proxy-settings>
    <java-compilation>
        <!-- Specifies the compiler to use and the command syntax for dynamically compiling
    	script segments in task elements -->
        <classpath>
            <!-- 
Register java archives with the compiler 
by inserting "entry" elements
with jar name or directory in between
opening and closing tag, eg:

<classpath>
	<entry>tools.jar</entry>
	<entry>common.jar</entry>
	<entry>interfaces.jar</entry>
</classpath>

Note that regardless of the values specified
here, the compiler will always be told to include
the jars that are in Presence's classpath to
search for classes. These jars will be appended
to whatever jars are specified here, meaning they
will be searched last.

In addition to registering jars with the compiler,
you also need to make them available to the Presence
runtime environment. To achieve this, enter the administration
console and select Tools > Jar Manager, and choose "import jar".
This will import the contents of the jar into the Presence database,
making it accessible to all servers running on the Presence site.

-->
        </classpath>
        <compile-command>
            <!--

Specify the command that should be executed 
to compile the dynamic code. The default will
work assuming that JDK bin directory is on the
system PATH variable. Effectively this will
run a command similar to:

   javac -classpath tools.jar;common.jar;... -d ./res/ext/ MyTempCode.java

Note that classpath items are separated by semi-colons
on windowsy platforms and commas on unixy systems.

If you are not using the Sun jdk, if the compiler is not
on the system search path, or if you have an otherwise
unusual setup, you may need to tweak with these
values.	

Regardless, the special markers ${classpath}, ${target-dir} and ${source-file}
should always appear somewhere in the command call. These will be replaced with
the correct values at runtime.

			-->
            <part>javac</part>
            <part>-classpath</part>
            <part>${classpath}</part>
            <part>-d</part>
            <part>${target-dir}</part>
            <part>${source-file}</part>
        </compile-command>
    </java-compilation>
    <!-- enables the channel subscription http server to listen on the primary server over SSL. -->
    <server-sockets>
        <socket key="com.internationalpresence.server.debug.DebugEngine" port="2789"/>
        <socket key="com.internationalpresence.server.remotecall.RemoteTaskCallListener$DelegatedListener" port="2790"/>
        <socket key="com.internationalpresence.v33.server.queue.QueuedProcessChangeListener" port="2791"/>
        <socket key="com.internationalpresence.admin.TaskInvalidator" port="2902"/>
    </server-sockets>
</presence-config>