X-Git-Url: http://git.indexdata.com/?a=blobdiff_plain;f=doc%2Fproxy.xml;h=0fdbd1306d316b865e3c20588477ab058da32e08;hb=9e1bd9899f0a7d7e7c0a9097ffb1ff64db2627c9;hp=051e0fb6bec9188ab38f43351c51ec25611d5e71;hpb=d94ff2fae57f9d9ef58d6bed35fbd308474adad8;p=yazpp-moved-to-github.git diff --git a/doc/proxy.xml b/doc/proxy.xml index 051e0fb..0fdbd13 100644 --- a/doc/proxy.xml +++ b/doc/proxy.xml @@ -58,7 +58,7 @@ start it up. It will work exactly as usual, but all the packets will be sent via the proxy, which will generate a log like this: - + @@ -172,7 +173,7 @@ When a client reconnects, query and record caching works better, if the proxy assigns it to the same backend as before. And the result set - (if any) is re-used. To achive this, Index Data defined a session + (if any) is re-used. To achieve this, Index Data defined a session cookie which identifies the backend session. @@ -298,7 +299,7 @@ Configuration: target The element target which may be repeated zero - or more times with parent elemtn proxy contains + or more times with parent element proxy contains information about each backend target. The target element have two attributes: name which holds the logical name of the backend @@ -309,7 +310,6 @@ <?xml version="1.0"?> - <!-- $Id --> <proxy> <target name="server1" default="1"> <!-- description of server1 .. --> @@ -375,7 +375,7 @@ measures the number of bytes transferred within the last minute. The pdu is the number of requests in the last minute. The retrieve holds the maximum records to - be retrived in one Present Request. + be retrieved in one Present Request. If a bandwidth/pdu limit is reached the proxy will postpone the @@ -455,7 +455,7 @@ or a particular record syntax request from the client. - The syntax has one equired attribute: + The syntax has one required attribute: type which is the Preferred Record Syntax. @@ -473,14 +473,14 @@ type should be XML. The proxy will use preferred record syntax USMARC/MARC21 against the backend target. - To accept USMARC and offer MARCXML XML recors but reject - all other requests the following configuaration could be used: + To accept USMARC and offer MARCXML XML records but reject + all other requests the following configuration could be used: <proxy> <target name="mytarget"> - <syntax type="usmarc"/> - <syntax type="xml" marcxml="1"/> - <syntax type="*" error="238"/> + <syntax type="usmarc"/> + <syntax type="xml" marcxml="1"/> + <syntax type="*" error="238"/> </target> </proxy> @@ -495,7 +495,7 @@ a target session is shut down. - This can also be specified on the command line bt using option + This can also be specified on the command line by using option -T. Refer to . @@ -552,7 +552,81 @@ - + +
+ Configuration: log + + The element log is the child of element + proxy and specifies what to be logged by the + proxy. + + + Specify the log file with command-line option -l. + + + The text of the log element is a sequence of + options separated by white space. See the table below: + Logging options + + + + + + Option + Description + + + + + client-apdu + + Log APDUs as reported by YAZ for the + communication between the client and the proxy. + This facility is equivalent to the APDU logging that + happens when using option -a, however + this tells the proxy to log in the same file as given + by -l. + + + + server-apdu + + Log APDUs as reported by YAZ for the + communication between the proxy and the server (backend). + + + + clients-requests + + Log a brief description about requests transferred between + the client and the proxy. The name of the request and the size + of the APDU is logged. + + + + server-requests + + Log a brief description about requests transferred between + the proxy and the server (backend). The name of the request + and the size of the APDU is logged. + + + + +
+
+ + To log communication in details between the proxy and the backend, th + following configuration could be used: + + server-apdu server-requests + +]]> + + +
+
Proxy Usage @@ -605,4 +679,4 @@ sgml-namecase-general:t End: --> - \ No newline at end of file +