X-Git-Url: http://git.indexdata.com/?a=blobdiff_plain;f=doc%2Fadministration.xml;h=829ef7591505428863477952c443e459617edb76;hb=8fba721bcf0f18f9b03cf62c3aaf0a064fd7d9a7;hp=912f216b2f7f75faf396d384feb3e4f542dada19;hpb=878a848853ad9e4f63da983476161613e114672d;p=idzebra-moved-to-github.git diff --git a/doc/administration.xml b/doc/administration.xml index 912f216..829ef75 100644 --- a/doc/administration.xml +++ b/doc/administration.xml @@ -1,5 +1,5 @@ - + Administrating Zebra - @@ -1332,6 +1378,7 @@ where g = rset_count(terms[i]->rset) is the count of all documents in this speci mitaylor2microsoft.com --> + Dynamically ranking CQL queries @@ -1437,12 +1484,14 @@ where g = rset_count(terms[i]->rset) is the count of all documents in this speci Extended Services: Remote Insert, Update and Delete - Extended services are only supported when acessing the Zebra + + Extended services are only supported when accessing the Zebra server using the Z39.50 protocol. The SRU protocol does not support extended services. - - + + + The extended services are not enabled by default in zebra - due to the fact that they modify the system. Zebra can be configured @@ -1457,7 +1506,7 @@ where g = rset_count(terms[i]->rset) is the count of all documents in this speci And in the password file passwordfile, you have to specify users and - encrypted passwords as colon seperated strings. + encrypted passwords as colon separated strings. Use a tool like htpasswd to maintain the encrypted passwords. @@ -1472,7 +1521,7 @@ where g = rset_count(terms[i]->rset) is the count of all documents in this speci The general record type should be set to any record filter which is able to parse XML records, you may use any of the two - declarations (but not both simultaniously!) + declarations (but not both simultaneously!) recordType: grs.xml # recordType: alvis.filter_alvis_config.xml @@ -1482,21 +1531,26 @@ where g = rset_count(terms[i]->rset) is the count of all documents in this speci shadow: directoryname: size (e.g. 1000M) + See for additional information on + these configuration options. - It is not possible to carry information about record types or - similar to Zebra when using extended services, due to - limitations of the Z39.50 - protocol. Therefore, indexing filters can not be choosen on a - per-record basis. One and only one general XML indexing filter - must be defined. - - + + + It is not possible to carry information about record types or + similar to Zebra when using extended services, due to + limitations of the Z39.50 + protocol. Therefore, indexing filters can not be chosen on a + per-record basis. One and only one general XML indexing filter + must be defined. + + + @@ -1504,76 +1558,77 @@ where g = rset_count(terms[i]->rset) is the count of all documents in this speci Extended services in the Z39.50 protocol - The Z39.50 standard allowes + The Z39.50 standard allows servers to accept special binary extended services protocol packages, which may be used to insert, update and delete records into servers. These carry control and update information to the servers, which are encoded in seven package fields: - - - - +
Extended services Z39.50 Package Fields
+ Extended services Z39.50 Package Fields + - - - - - + + Parameter + Value + Notes + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + +
ParameterValueNotes
type'update'Must be set to trigger extended services
actionstring + + type + 'update' + Must be set to trigger extended services + + + action + string + Extended service action type with one of four possible values: recordInsert, recordReplace, recordDelete, and specialUpdate -
recordXML stringAn XML formatted string containing the record
syntax'xml'Only XML record syntax is supported
recordIdOpaquestring + + + + record + XML string + An XML formatted string containing the record + + + syntax + 'xml' + Only XML record syntax is supported + + + recordIdOpaque + string + Optional client-supplied, opaque record identifier used under insert operations. -
recordIdNumber positive numberZebra's internal system number, only for update - actions. -
databaseNamedatabase identifier + + + + recordIdNumber + positive number + Zebra's internal system number, + not allowed for recordInsert or + specialUpdate actions which result in fresh + record inserts. + + + + databaseName + database identifier + The name of the database to which the extended services should be applied. -
@@ -1584,25 +1639,26 @@ where g = rset_count(terms[i]->rset) is the count of all documents in this speci recordDelete (will fail if the record does not exist), and specialUpdate (will insert or update the record - as needed). + as needed, record deletion is not possible). - During a recordInsert action, the + During all actions, the usual rules for internal record ID generation apply, unless an optional recordIdNumber Zebra internal ID or a recordIdOpaque string identifier is assigned. The default ID generation is configured using the recordId: from - zebra.cfg. + zebra.cfg. + See . - The actions recordReplace or - recordDelete need specification of the additional - recordIdNumber parameter, which must be an - existing Zebra internal system ID number, or the optional - recordIdOpaque string parameter. + Setting of the recordIdNumber parameter, + which must be an existing Zebra internal system ID number, is not + allowed during any recordInsert or + specialUpdate action resulting in fresh record + inserts. @@ -1613,11 +1669,16 @@ where g = rset_count(terms[i]->rset) is the count of all documents in this speci xmlns:id="http://www.indexdata.dk/zebra/", where it can be picked up for later record updates or deletes. + - Records indexed with the alvis filter - have similar means to discover the internal Zebra ID. + A new element set for retrieval of internal record + data has been added, which can be used to access minimal records + containing only the recordIdNumber Zebra + internal ID, or the recordIdOpaque string + identifier. This works for any indexing filter used. + See . - + The recordIdOpaque string parameter is an client-supplied, opaque record @@ -1745,23 +1806,6 @@ where g = rset_count(terms[i]->rset) is the count of all documents in this speci - - - YAZ Frontend Virtual Hosts - - zebrasrv uses the YAZ server frontend and does - support multiple virtual servers behind multiple listening sockets. - - &zebrasrv-virtual; - - - Section "Virtual Hosts" in the YAZ manual. - http://www.indexdata.dk/yaz/doc/server.vhosts.tkl - - - - -