<?xml version="1.0" encoding="UTF-8"?>
<!--
Copyright (C) 2000-2010  Ministere de la culture et de la communication (France), AJLSM
See LICENCE file
-->
<!DOCTYPE webpage PUBLIC "-//Norman Walsh//DTD Website V2.1b1//EN" "../../../dtd/website.dtd" [
  <!ENTITY applications SYSTEM "applications.xml" NDATA XML>
  <!ENTITY bases SYSTEM "bases.xml" NDATA XML>
  <!ENTITY entrepots SYSTEM "entrepots.xml" NDATA XML>
]>

<webpage id="serveur"> 

  <head>
	 <title>The SDX server</title>
	 <titleabbrev>Server</titleabbrev>
	 <author>
		<firstname>Martin</firstname>
		<surname>Sévigny</surname>
		<affiliation>
		  <orgname>AJLSM</orgname> 
		</affiliation>
	 </author>
	 <author>
		<firstname>Frédéric</firstname>
		<surname> Glorieux</surname>
		<affiliation>
		  <orgname>AJLSM</orgname> 
		</affiliation>
	 </author>
	 <revhistory>
		<revision>
		  <revnumber>1.0</revnumber> 
		  <date>2003-06-03</date> 
		</revision>
	 </revhistory>
  </head>

  <para>For SDX to make available indexing, search and display services for XML documents, a Web server, a servlet engine and SDX must be launched and configured correctly in order to answer requests. The execution of such an environment is called an SDX <emphasis>server</emphasis>, which is an instance of a working server. Several servers can be hosted in the same computer. However, this configurationshould not be necessary, SDX resources can be shared with no application conflict.</para>
  <para>The other SDX-2 objects, which are : applications, 
	 <olink targetdocent="bases">document bases</olink> and 
	 <olink targetdocent="entrepots">repositories</olink> are directly accessible when hosted on the same SDX server. o perform searches in remote databases, the SDX server will be the key to enter index aux indexes and documents.</para>
  <para>Among the key roles of the server, is to provide access to applications, bases and repositories it hosts, according to several security criteria. The server may also be responsible for additional tasks, such as for example being the interface for requests launched according to other protocoles, such as Z39.50 or OAI.</para>
  <section> 
	 <title>Server address</title>
	 <para>In order to make an application visible from the Internet, the SDX server must be installed in the computerwhich is linked to the Web, with a registrated domain name (or an IP address). This address allows remote applications (SDX or others) to use SDX services and to receive their results. Each SDX server opens URLs which answer according to the API-SDX. When asking the SDX server to perform searches in remote databases, hosted in other SDX servers, those servers provides entry points, it is therefore necessary to know their address.</para>
  </section> 
  <section> 
	 <title>Server identifier</title>
	 <para>To facilitate searches in multiple databases, particularly the interpretation of search results, all SDX servers must have a public identifier. This identifier must be unique among SDX servers, it is therefore strongly advised to build it with the technique of reverse domaine names, such as in the Java "paquetages". For example: <literal>fr.gouv.culture.sdx</literal>.</para>
	 <para>This identifier is mentionned in the <filename>WEB-INF/sdx/sdx.xconf</filename> file. It is the <sgmltag>id</sgmltag> attribute of the superior hierarchical element <sgmltag>sdx:framework</sgmltag>.</para>
	 <para>A good way to specify this unique identifier is to build SDX-2 from its sources ; during the process, it is asked to the user which identifier to use (this functionality is not yet implemented). </para>
  </section> 

</webpage> 
