Changeset 2822
- Timestamp:
- 04/22/13 07:54:38 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
vlo/trunk/DEPLOY-README
r2817 r2822 10 10 11 11 The VLO importer and web application are contained in an 12 archive named like12 archive. In the case of version 2.13, the archive is named 13 13 14 14 vlo_parent-2.13-Distribution.tar.gz … … 27 27 cd x 28 28 With tar -xvf vlo_parent-2.13-Distribution.tar.gz 29 vlo_parent-2.13 will be created. 30 Take y to be vlo_parent-2.13 29 vlo_parent-2.13 will be created in the x directory. 31 30 32 Make the server's Tomcat user own the files unpacked.31 To begin with, make the server's Tomcat user own the files unpacked. 33 32 34 33 3. Solr server installation … … 37 36 server. 38 37 39 Unpack x/y/war/solr/solr.war in a directory in which you want the Solr 40 server to reside, say z, 41 /var/lib/tomcat6/webapps/vlodist/vlo_parent-2.13/war/solr 42 cd z 43 unzip x/y/war/solr/vlo_solr.war 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: 40 41 /var/lib/tomcat6/webapps/vlodist/vlo_parent-2.13/war/solr 42 43 cd y 44 unzip x/vlo_parent-2.13/war/vlo_solr.war 44 45 45 46 Make the Tomcat user owner of the files in the tree that starts in 46 the zdirectory.47 the y directory. 47 48 48 In the z directory, modify META-INF/context.xml 49 Assign the desired context path value, for example: vlo_solr/ 50 This means that if url is the url of the web server, the Solr 51 server will be reachable at url/vlo_solr/ 49 In y/META-INF/context.xml file you will probably need to modify some 50 definitions. 51 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/ 57 58 url. 52 59 53 Assign x/y/config/solr to the solr/home parameter.60 - Assign x/vlo_parent-2.13/config/solr to the solr/home parameter. 54 61 55 Copy the META-INF/context.xml file to 62 Next, copy the y/META-INF/context.xml file to 63 56 64 /var/lib/tomcat6/conf/Catalina/localhost/vlo_solr.xml 57 or to a directory equivalent to it.58 If necessary, make the Tomcat user owner of the vlo_solr.xml file.59 65 60 Create a link for the Tomcat server so that it knows where to look 61 for the solr server installation: 62 ln -sf x/y/war/solr/ /var/lib/tomcat6/webapps/vlo_solr 63 or equivalent. 64 The link created should identify the path defined the context file, 65 vlo_solr in this case. 66 or to a directory equivalent to it. If necessary, make the Tomcat user owner 67 of the vlo_solr.xml file. 66 68 67 If necessary, change the ownership of the link to the Tomcat user. 69 Create a link for the Tomcat server so that it knows where to look for the 70 solr server installation: 68 71 69 Please modify WEB-INF/classes/log4j.properties72 ln -sf y/solr/ /var/lib/tomcat6/webapps/vlo_solr 70 73 71 if you would like logging configured different from the type of 72 logging packaged. 74 or equivalent. The link created should identify the path defined the context 75 file, vlo_solr in this case. 76 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 81 y/WEB-INF/classes/log4j.properties 73 82 74 83 Restart tomcat: 75 84 /etc/init.d/tomcat6 restart 76 85 77 Inspect the Tomcat log file directory, inspect the solr.log file.86 Inspect the Tomcat log file directory, and inspect the solr.log file. 78 87 79 88 4. Web application installation 80 89 81 Similar to the solr archive, unpack x/y/war/vlo.war in a directory 82 in which you want the vlo web application to reside, say z, x/y/vlo 83 itself. 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. 84 92 85 93 cd z 86 unzip x/ y/war/solr/vlo.war94 unzip x/vlo_parent-2.13/war/vlo.war 87 95 88 96 Make the Tomcat own the files in and below the z directory. 89 97 90 Modify META-INF/context.xml91 Assign the desired context path value, for example: vlo/92 If url is the url of the web server, the vlo web application will be93 reachable at url/vlo/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. 94 102 95 Because the packaged configuration is suitable to very specific 96 (development) circumstances only, in most cases it does fit the 97 production environment. You can specify an alternative, external 98 configuration file, preferably the same file as the one used by 99 the importer. 103 Because the packaged configuration is suitable to very specific (development) 104 circumstances only, in most cases it does fit the production environment. You 105 can specify an alternative, external configuration file, preferably the same 106 file as the one used by the importer (see 5). 100 107 101 Most likely, you will need to assign another value to the solrUrl 102 parameter. This parameter is used to let the VLO web application 103 know where it can reach the Solr server. You can set the value of 104 this parameter in an external configuration file, or directly in 105 the context file. 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 112 107 Copy the META-INF/context.xml context file to 113 Like in the case of the solr server, copy the z/META-INF/context.xml context 114 file to: 115 108 116 /var/lib/tomcat6/conf/Catalina/localhost/vlo.xml 109 117 110 Create a link for the Tomcat server so that it knows where to look 118 or to another, comparable path. 119 120 Also, create a link for the Tomcat server so that it knows where to look 111 121 for the vlo web application installation: 112 ln -sf x/y/war/vlo/ /var/lib/tomcat6/webapps/vlo113 Like in the case of the Solr server, the link created should114 identify the path defined the context file.115 122 116 Again, if necessary, change the ownership of the context file and 117 the link to the Tomcat user. 123 ln -sf z/solr /var/lib/tomcat6/webapps/vlo 118 124 119 Like in the case of the Solr server, you can change the web 120 application's way of logging. This time, modifications should be 121 applied to WEB-INF/classes/log4j.properties 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. 128 129 If you like, you can change the web application's way of logging. This time, 130 modifications should be applied to: 131 132 z/WEB-INF/classes/log4j.properties 122 133 123 134 Restart the Tomcat server: … … 125 136 /etc/init.d/tomcat6 restart 126 137 127 or equivalent. This will cause the new Solr server and vlo web 128 application tobecome active.138 or equivalent. This will cause the new Solr server and vlo web application to 139 become active. 129 140 130 Finally, inspect the Tomcat log file directory, and inspect the 131 vlo.log file.141 Finally, inspect the Tomcat log file directory, and inspect the vlo.log file 142 also. 132 143 133 144 5. Importer configuration … … 141 152 -c path/VloConfig.xml 142 153 143 to the command in the importer script .154 to the command in the importer script in the x/vlo_parent-2.13/bin directory. 144 155 145 156 Most likely, the dataRoot values need to be changed. This is what a … … 163 174 /var/lib/tomcat6/conf/Catalina/localhost/vlo_solr.xml 164 175 165 or in a file equivalent to this one, should be reflected in the value 166 ofthis parameter.176 or in a file equivalent to this one, should be reflected in the value of 177 this parameter. 167 178 168 Whenever the definition of the database changes, it is recommended 169 to clear the database before starting an importer run. To do this, 170 make sure that the 'deletaAllFirst' parameter equals true before 171 the run. After that, the original value of the parameter could be 172 restored. 179 Whenever the definition of the database changes, it is recommended to clear 180 the database before starting an importer run. To do this, make sure that the 181 'deletaAllFirst' parameter equals true before the run. After that, the 182 original value of the parameter could be restored. 173 183 174 184 6. Importing data … … 178 188 ./vlo_solr_importer.sh 179 189 180 script in the x/y/bin directory. Messages are logged to the 181 console. Because meta data is not static, it is recommended to run 182 the importer a couple of times a week. Please note that, given the 183 current (04.2013) set of data, a run could take more than four 184 hours. 185 186 187 188 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.
Note: See TracChangeset
for help on using the changeset viewer.