...
| Anchor |
|---|
| _Toc154574493 |
|---|
| _Toc154574493 |
|---|
|
synchConfig
Looks something like this for an OC:
| Code Block |
|---|
|
<?xml version="1.0" encoding="UTF-8"?>
<fews-master-config xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/synchronisationConfiguration.xsd">
<queueconnection>
<factory jndi="ConnectionFactory"/>
</queueconnection>
<defaultMcId>MC00</defaultMcId>
<mc id="MC00">
<jndicontext factory="org.jnp.interfaces.NamingContextFactory" provider="jnp://localhost:1099" prefixes="org.jboss.naming:org.jboss.interfaces"/>
<queue>
<root jndi="TEST/MC00/"/>
<synch jndi="External/JMSQueue/OCIncoming" timeout="10"/>
</queue>
</mc>
<synchronisation>
<messaging maxrecords="1000" maxlobdata="30000000"/>
<processor maxlistsize="500000"/>
<schema location="nl/wldelft/fews/master/data/synchdata/synchronisation_schema.xsd"/>
</synchronisation>
<login timeout="10" />
</fews-master-config>
|
The synchConfig does not normally require editting.
The only setting that may demand editting is the <login timeout="10" />, which controls the timeout for a login attempt (in seconds). (This element may be absent, in which case the timeout is 10secs)
It may be needed to extend this timeout if the JMS server is very busy (very many clients starting up and synchronising at the same time, e.g. when all the PCs for a workshop are all starting up at the same time).
Note: the xml config can only extend the time out from the default 10 secs. Settings less than 10 secs are ignored)To be completed
| Anchor |
|---|
| _Toc154574494 |
|---|
| _Toc154574494 |
|---|
|
synchProfiles
...