Page History
...
Property: | server | ||||
Example Value: | server = http://127.0.0.1/solr/statistics | ||||
Informational Note: | Is used by the SolrLogger Client class to connect to the Solr server over http and perform updates and queries. In most cases, this can (and should) be set to localhost (or 127.0.0.1).
Assuming you get an HTTP 200 OK response, then you should set | ||||
Property: | spiderips.urls | ||||
Example Value: | spiderips.urls =
| <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="c9bfc2dc-2534-4660-a1cd-01651f3a2fcf"><ac:plain-text-body><![CDATA[ | |||
Informational Note: | List of URLs to download spiders files into [dspace]/config/spiders. These files contain lists of known spider IPs and are utilized by the SolrLogger to flag usage events with an "isBot" field, or ignore them entirely.
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="36b13fac-59f0-4e23-ae53-bc2618079cd3"><ac:plain-text-body><![CDATA[from your [dspace]/bin directory | ]]></ac:plain-text-body></ac:structured-macro> | |||
Property: | dbfile | ||||
Example Value: | dbfile = ${dspace.dir}/config/GeoLiteCity.dat | ||||
from your [dspace]/bin directory | |||||
Property: | dbfile | ||||
Example Value: | dbfile = ${dspace.dir}/config/GeoLiteCity.dat <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="fb2b5373-da04-4577-b2bb-90794c4adc4e"><ac:plain-text-body><![CDATA[ | ||||
Informational Note: | The following referes to the GeoLiteCity database file utilized by the LocationUtils to calculate the location of client requests based on IP address. During the Ant build process (both fresh_install and update) this file will be downloaded from [http://www.maxmind.com/app/geolitecity] if a new version has been published or it is absent from your [dspace]/config directory. | ||||
Property: | resolver.timeout | ||||
Example Value: | resolver.timeout = 200 | ||||
Informational Note: | Timeout in milliseconds for DNS resolution of origin hosts/IPs. Setting this value too high may result in solr exhausting your connection pool. | ||||
Property: | useProxies | ||||
Example Value: | useProxies = true | ||||
Informational Note: | Will cause Statistics logging to look for X-Forward URI to detect clients IP that have accessed it through a Proxy service (e.g. the Apache mod_proxy). Allows detection of client IP when accessing DSpace. [Note: This setting is found in the DSpace Logging section of dspace.cfg] | ]]></ac:plain-text-body></ac:structured-macro> | |||
Property: | statistics.item.authorization.admin | ||||
Example Value: | statistics.item.authorization.admin = true | ||||
Informational Note: | When set to true, only general administrators, collection and community administrators are able to access the statistics from the web user interface. As a result, the links to access statistics are hidden for non logged-in admin users. Setting this property to "false" will display the links to access statistics to anyone, making them publicly available. | ||||
Property: | solr.statistics.logBots | ||||
Example Value: | solr.statistics.logBots = true | ||||
Informational Note: | When this property is set to false, and IP is detected as a spider, the event is not logged. | ||||
Property: | solr.statistics.query.filter.spiderIp | ||||
Example Value: | solr.statistics.query.filter.spiderIp = false | ||||
Informational Note: | If true, statistics queries will filter out spider IPs -- use with caution, as this often results in extremely long query strings. | ||||
Property: | solr.statistics.query.filter.isBot | ||||
Example Value: | solr.statistics.query.filter.isBot = true | ||||
Informational Note: | If true, statistics queries will filter out events flagged with the "isBot" field. This is the recommended method of filtering spiders from statistics. | ||||
Property: | query.filter.bundles | ||||
Example | query.filter.bundles=ORIGINAL | ||||
Informational | A comma seperated list that contains the bundles for which the file statistics will be displayed. |
...
Code Block |
---|
cd [dspace-source]/dspace mvn package cd [dspace-source]/dspace/target/dspace-<version>-build.dir ant -Dconfig=[dspace]/config/dspace.cfg update cp -R [dspace]/webapps/* [TOMCAT]/webapps |
...
The last step is only used if you do not follow the recommended practice of configuring _\[dspace\]/webapps_ as location for webapps in your servlet container (Tomcat, Resin or Jetty). If you only need to build the statistics, and don't make any changes to other web applications, you can replace the copy step above with:
Code Block |
---|
cp -R dspace/webapps/solr TOMCAT/webapps |
_Again, only if you are not mounting \ [dspace\]/webapps directly into your Tomcat, Resin or Jetty host (the recommended practice)_ Wiki Markup
Restart your webapps (Tomcat/Jetty/Resin)
...
Manually Installing/Updating GeoLite Database File
...
The GeoLite Database file (at \ [dspace\]/config/GeoLiteCity.dat) is used by the Statistics engine to generate location/country based reports. (_Note: If you are not using DSpace Statistics, this file is not needed._)
In most cases, this file is installed automatically when you run ant fresh_install
. However, if the file cannot be downloaded & installed automatically, you may need to manually install it.
...
You have two options to install/update this file:
...
- Attempt to re-run the automatic installer from your DSpace Source Directory (\[dspace-source\]). This will attempt to automatically download the database file, unzip it and install it into the proper location:
unmigrated-wiki-markupCode Block ant update_geolite
- NOTE: If the location of the GeoLite Database file is known to have changed, you can also run this auto-installer by passing it the new URL of the GeoLite Database File: {{
ant
\-Dgeolite=
\[full-URL-of-geolite
\]
update_geolite
}}
- NOTE: If the location of the GeoLite Database file is known to have changed, you can also run this auto-installer by passing it the new URL of the GeoLite Database File: {{
- OR, you can manually install the file by performing these steps yourself:
- First, download the latest GeoLite Database file from http://geolite.maxmind.com/download/geoip/database/GeoLiteCity.dat.gz
- Next, unzip that file to create a file named GeoLiteCity.datunmigrated-wiki-markup
- Finally, move or copy that file to your DSpace installation, so that it is located at {{\
[dspace
\]/config/GeoLiteCity.dat
}}.