Changeset 2874


Ignore:
Timestamp:
05/07/13 13:51:37 (11 years ago)
Author:
keeloo
Message:

Temporarily removed references to the tag facet from FacetConstants?, FacetConcepts? and FacetMappingFactoryTest?. This should enable the 2.13 beta release. Some minor changes regarding default parameter settings were applied to VloConfig? and VloConfigTest?.

Location:
vlo/trunk
Files:
2 edited

Legend:

Unmodified
Added
Removed

  • vlo/trunk/CHANGES

    r2817 r2874  
    11Bug Fixes and Features
    22
    3 Beta release 2.13 (April 2013)
     3Beta release 2.13 (May 2013)
    44
    55A new package, eu.clarin.cmdi.vlo.config was added taking care of the web
    … …  
    88
    99Both the importer and the web application use the same base file for
    10 configuration. The base file refers to cmdi2xhtml.xsl,
    11 facetConcepts.xml, and nationalProjectsMapping.xml file.
     10configuration. This file refers to external resources like for example
     11the nationalProjectsMapping.xml file.
    1212
    1313The base VloConfig.xml file that is included in the /src/main/resources

  • vlo/trunk/DEPLOY-README

    r2830 r2874  
    1919   - adapt the application's context files
    2020   and
    21    - adapt the main configuration file.
     21   - adapt the VloConfig.xml main configuration file.
    2222
    23232. Archive unpacking
    2424
    25    Unpack the archive in directory x,
    26    for example: /var/lib/tomcat6/webapps/vlodist/
    27    cd x
    28    With tar -xvf vlo_parent-2.13-Distribution.tar.gz
    29    vlo_parent-2.13 will be created in the x directory.
     25   Unpack the archive, for example
    3026
    31    To begin with, make the server's Tomcat user own the files unpacked.
     27   vlo_parent-2.13-Distribution.tar.gz
     28
     29   in a temporary directory temp. Copy the contents of the vlo_parent-2.13
     30   directory just created to a permanent directory, vlo, for example. In the
     31   tree starting in vlo, the VLO configuration is stored. Also, from the
     32
     33   vlo/bin
     34   
     35   directory, you can run the importer application.
    3236
    33373. Solr server installation
    3438
    3539   The VLO importer and web application use Solr as their database
    36    server.
     40   server. To install this server, first stop the Tomcat server:
    3741
    38    Unpack x/vlo_parent-2.13/war/solr.war in a directory named y in which you
    39    want the Solr server to reside. This could, for example be:
     42   /etc/init.d/tomcat6 stop
    4043
    41    /var/lib/tomcat6/webapps/vlodist/vlo_parent-2.13/war/solr
     44   Next, copy the Solr server web application archive to the Tomcat
     45   server web application directory. This could for example be
    4246
    43    cd y
    44    unzip x/vlo_parent-2.13/war/vlo_solr.war
     47   /var/lib/tomcat6/webapps
    4548
    46    Make the Tomcat user owner of the files in the tree that starts in
    47    the y directory.
     49   Step into this directory, apps,
    4850
    49    In y/META-INF/context.xml file you will probably need to modify some
    50    definitions.
     51   cd apps
     52 
     53   cp temp/vlo_parent-2.13/war/solr.war .
    5154
    52    - The context path value. If you define vlo_solr/ to be the value of the
    53      context path, and prefix is some string pointing to web server the
    54      application is installed on, the Solr server will be reachable at the
    55      
    56      prefix/vlo_solr/
     55   If it does not exist, create the vlo_solr directory, and unpack the web
     56   application archive in it:
    5757
    58      url.
    59  
    60    - Assign x/vlo_parent-2.13/config/solr to the solr/home parameter.
     58   cd vlo_solr
     59   unzip ../solr.war 
    6160
    62    Next, copy the y/META-INF/context.xml file to
     61   In apps/META-INF/context.xml file you modify the solr/home parameter to the
     62   path where the solr server finds its configuration and stores its data:
    6363
     64   vlo/config/solr
     65
     66   Copy the new context.xml file to the Tomcat configuration:
     67
     68   cp apps/META-INF/context.xml \
    6469   /var/lib/tomcat6/conf/Catalina/localhost/vlo_solr.xml
    6570
    66    or to a directory equivalent to it. If necessary, make the Tomcat user owner
    67    of the vlo_solr.xml file.
     71   If you would like logging to be configured different from the type of
     72   logging packaged, please modify
    6873
    69    Create a link for the Tomcat server so that it knows where to look for the
    70    solr server installation:
     74   apps/WEB-INF/classes/log4j.properties
    7175
    72    ln -sf y/solr/ /var/lib/tomcat6/webapps/vlo_solr
     76   If necessary, change the ownership of the files in the tree starting in
    7377
    74    or equivalent. The link created should identify the path defined the context
    75    file, vlo_solr in this case.
     78   vlo/config/solr
    7679
    77    If necessary, change the ownership of the link to the Tomcat user. And if
    78    you would like logging to be configured different from the type of logging
    79    packaged, please modify
     80   to the Tomcat user, so that the solr server can store data in it.
    8081
    81    y/WEB-INF/classes/log4j.properties
     82   Finally, start the Tomcat server:
    8283
    83    Restart tomcat:
    84    /etc/init.d/tomcat6 restart
     84   /etc/init.d/tomcat6 start
    8585
    86    Inspect the Tomcat log file directory, and inspect the solr.log file.
     86   To be sure the Solr server is working as it should, please inspect the Tomcat
     87   log file directory, and inspect the solr.log file.
    8788
    88894. Web application installation
    8990
    90    Similar to the solr archive, unpack x/vlo_parent-2.13/war/vlo.war in
    91    a directory z in which you want the vlo web application to reside.
     91   Similar to the Solr archive, stop the Tomcat server, and unpack
     92
     93   temp/vlo_parent-2.13/war/vlo.war in
    9294   
    93    cd z
    94    unzip x/vlo_parent-2.13/war/vlo.war
     95   the 
    9596
    96    Make the Tomcat own the files in and below the z directory.
     97   apps/vlo
    9798
    98    Modify the META-INF/context.xml file. Like in the case of the solr server,
    99    assign the desired context path value. Again, if prefix is a string pointing
    100    to the web server the application is installed on, the vlo web application
    101    will be reachable at the url/vlo/ url.
     99   directory.
    102100
    103101   Because the packaged configuration is suitable to very specific (development)
    104102   circumstances only, in most cases it does fit the production environment. You
    105103   can specify an alternative, external configuration file, preferably the same
    106    file as the one used by the importer (see 5).
     104   file as the one used by the importer (see 5). Please modify
    107105
    108    Most likely, you will need to assign another value to the solrUrl parameter.
    109    This parameter is used to let the VLO web application know where it can reach
    110    the Solr server. You can set the value of this parameter in an external
    111    configuration file, or directly in the context file.
     106   apps/META-INF/context.xml
    112107
    113    Like in the case of the solr server, copy the z/META-INF/context.xml context
    114    file to:
     108   by adding a reference to an external configuration file. By modifying this
     109   file, you can adapt the VLO configuration to your needs. You might, for
     110   example, need to assign another value to the solrUrl parameter also. This
     111   parameter is used to let the VLO web application know where it can reach the
     112   Solr server.
     113
     114   Instead of changing the value of the solrUrl parameter in the external
     115   configuration file, you could also supply an alternative value by adding
     116   the parameter to
     117
     118   apps/META-INF/context.xml
     119
     120   directly. The comments in this file will tell you how to add the parameter.
     121
     122   Like in the case of the Solr server, copy the apps/META-INF/context.xml
     123   context file to:
    115124
    116125   /var/lib/tomcat6/conf/Catalina/localhost/vlo.xml
    117126
    118    or to another, comparable path. Please make the Tomcat user own this file.
    119 
    120    Also, create a link for the Tomcat server so that it knows where to look
    121    for the vlo web application installation:
    122 
    123    ln -sf z/solr /var/lib/tomcat6/webapps/vlo
    124 
    125    Like in the case of the Solr server, the link created should identify the
    126    path defined the context file. Again, if necessary, change the ownership of
    127    the context file and the link to the Tomcat user.
     127   or to another, comparable path.
    128128
    129129   If you like, you can change the web application's way of logging. This time,
    130130   modifications should be applied to:
    131131
    132    z/WEB-INF/classes/log4j.properties
     132   apps/WEB-INF/classes/log4j.properties
    133133
    134    Restart the Tomcat server:
    135 
    136    /etc/init.d/tomcat6 restart
    137  
    138    or equivalent. This will cause the new Solr server and vlo web application to
    139    become active.
    140    
    141    Finally, inspect the Tomcat log file directory, and inspect the vlo.log file
    142    also.
     134   Finally, start the Tomcat server, and inspect the Tomcat log file directory,
     135   especially the vlo.log file.
    143136
    1441375. Importer configuration
    145138
    146    Both the web application and the importer should use one and the same
    147    configuration file. So if, for example, the web application's configuration
    148    is in
     139   As mentioned in the description of the web application installation, a
     140   typical setup needs an external configuration file. For consistency reasons
     141   both the web application and application that imports data into the Solr
     142   data base should use one and the same configuration file. So if, for example,
     143   the web application's configuration is in
    149144
    150145   path/VloConfig.xml, add
    … …  
    152147   -c path/VloConfig.xml
    153148
    154    to the command in the importer script in the x/vlo_parent-2.13/bin directory.
     149   to the command in the importer script in the vlo/bin directory.
    155150
    156    Most likely, the dataRoot values need to be changed. This is what a
    157    dataRoot definition could look like:
     151   Most likely, in the configuration file, the dataRoot values need to be
     152   changed. This is what a dataRoot definition could look like:
    158153
    159    <DataRoot>
    160         <originName>IPROSLA</originName>
    161         <rootFile>/lat/apache/htdocs/static-data-for-vlo-importer/</rootFile>
    162         <prefix>http://catalog.clarin.eu/</prefix>
    163         <tostrip>/lat/apache/htdocs/</tostrip>
    164         <deleteFirst>false</deleteFirst>
     154
     155   <originName>MPI self harvest</originName>
     156     <rootFile>/var/www/vlomd/self/</rootFile>           
     157     <prefix>http://m12404423/vlomd/</prefix>
     158     <tostrip>/var/www/vlomd/</tostrip>
     159     <deleteFirst>false</deleteFirst>
    165160   </DataRoot>
    166161
    167    A dataRoot describes the meta data files. The toStrip part of the
    168    description is left out of the rootFile part to create a link to the
     162   A dataRoot element describes the meta data files. The toStrip part of the
     163   description is left out of the rootFile part to create a http link to the
    169164   meta data; the links starts with the prefix.
    170165
    … …  
    188183   ./vlo_solr_importer.sh
    189184
    190    script in the x/x/vlo_parent-2.13/bin directory. Messages are logged to the
    191    console. Because meta data is not static, it is recommended to run the
    192    importer a couple of times a week. Please note that, given the current
    193    (04.2013) set of data, a run typically takes between four and file hours.
     185   script in the vlo/bin directory. Messages are logged to the console. Because
     186   meta data is not static, it is recommended to run the importer a couple of
     187   times a week. Please note that, given the current (04.2013) set of data, a
     188   run typically takes between four and file hours.
Note: See TracChangeset for help on using the changeset viewer.