To consistently upgrade serverConfig, it is recommended to use the latest default.serverConfig and default.runtimeConfig in iWay DQS version 9.0.1 and higher runtime as a starting point and/or template. Alternatively, you can follow the steps in this section in case you just need to upgrade the old version 7 or version 8 server configuration to version 9, and you do not plan to use any new server components available in version 9.0.1 and higher.

To configure the server:

1. Move the fileSystemRoots attribute from the configuration element of the global server to the ServerFileSystemServiceComponent configuration element.
2. Change the content for ServerFileSystemServiceComponent by defining the roots sub-element, which defines root folders for the remote filesystem, as shown in the following default.serverConfig syntax:

   <server>
   	<port>7777</port>
   	...
   	<serverComponents>
   		...
   		<component class="com.ataccama.dqc.server.services.
   ServerFilesystemServiceComponent">
   			<roots>
   				<root>d:/opt</root>
   				<root>pathvar://data/ext</root>
   			</roots>
   		</component>
   		...
   	</serverComponents>
   </server>

3. Add the runtimeConfiguration attribute.

   In iWay DQS version 9.0.1 and higher, this is the link to an external runtimeConfiguration file with DB connections and path variable connections (to be shared with batch processing). The path to the runtimeConfiguration file can be either absolute or relative (in that case, it is calculated against the folder containing the serverConfig.xml file).

   The following syntax shows a sample default.serverConfig:

   <server>
   	<port>7777</port>
   	...
   	<runtimeConfiguration>default.runtimeConfig</runtimeConfiguration>
   	...
   </server>

   The following syntax shows a sample default.runtimeConfig:

   <runtimeconfig>
   	<pathVariables>
   		<pathVariable name="data" value="/usr/share/data"/>
   	</pathVariables>
   	<dataSources>
   		<dataSource driverclass="org.apache.derby.jdbc.ClientDriver"
    name="derby"
   			url="jdbc:derby://localhost:1527/test"
   			user="test"
   password="crypted:DES:uj3hAwlJSWwwD1Jp62KwJRz8lUK36qMUto5HhuV6Izg="/>
   	</dataSources>
   	<loggingConfig>logging.xml</loggingConfig>
   </runtimeconfig>

4. Move the the databaseConnections and pathVariables attributes to the external runtimeConfiguration file mentioned in the previous step.

   The LoggingComponent has a new logic: it can be specified in the external runtimeConfiguration file, mentioned previously, or locally in the server configuration. For more information, see the template.

5. When upgrading from version 7, the structure of the filter component must be redefined as follows:

   <server>
   	<port>7777</port>
   	...
   	<serverComponents>
   		...
   		<component class="com.ataccama.dqc.web.HttpDispatcher">
   			<filters>
   				<filterDef>
   					<filter name="MyRequestLog"
   class="com.ataccama.dqc.web.filters.RequestResponseTimeLogger">
   						<headers><header>soapAction</header>
   						</headers>
   						<level>INFO</level>
   						<appendClientInfo>false</appendClientInfo>
   					</filter>
   					<mappings>
   						<mapping listeners="default" urlPattern="/"/>
   					</mappings>
   				</filterDef>
   			</filters>
   		</component>
   		...
   	</serverComponents>
   </server>

   Note: There is a new filterDef sub-element, and the mappings element has been moved to the same level as filter.