Changes between Version 5 and Version 6 of installation_QCG_BES_AR
- Timestamp:
- 05/16/11 13:09:13 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
installation_QCG_BES_AR
v5 v6 128 128 in order to enable password authentication for the user `smoa_comp`. 129 129 130 '''Note:''' You must reload the PostgreSQL server in order to make the changes visible e.g:130 '''Note:''' You must reload the PostgreSQL server in order to make the changes visible e.g: 131 131 132 132 {{{ … … 181 181 }}} 182 182 183 * You need to create ODBC Data Source Name. You can do this by editing system-wide, i.e. /etc/odbc.ini, configuration file and adding new section. In this example we assume that the DSN (Database Source Name) will be smoa_comp, real database name is also smoa_comp and appropriate drivers for PostgreSQL database (i.e. the <code>libodbcpsql.so</code> and <code>libodbcpsqlS.so</code> files) are located in /usr/local/lib: 184 183 * You need to create ODBC Data Source Name. You can do this by editing system-wide, i.e. `/etc/odbc.ini`, configuration file and adding new section. In this example we assume that the DSN (Database Source Name) will be `smoa_comp`, real database name is also `smoa_comp` and appropriate drivers for PostgreSQL database (i.e. the `libodbcpsql.so` and `libodbcpsqlS.so` files) are located in `/usr/local/lib`: 184 185 {{{ 186 #!div style="font-size: 90%" 187 {{{#!default 185 188 [smoa_comp] 186 189 Description = SMOA Computing database … … 191 194 Port = 5432 192 195 ReadOnly = No 193 194 {{Note|}} Verify if paths given in the ''Driver'' and ''Setup'' sections are valid. 195 196 {{Note|}} The PostgreSQL odbc driver on many systems is distributed as a separate package (the <code>postgresql-odbc</code> or similar). Don't use the PostgreSQL driver shipped with the UnixODBC source tarball, as this one is known to be [https://bugzilla.redhat.com/show_bug.cgi?id=458708#c7 obsolete]. 197 198 * It is recommended to use a command line client to access the database through ODBC to check if everything was configured correctly. For example, unixODBC provides an <code>isql</code> client: 199 196 }}} 197 }}} 198 '''Note:''' Verify if paths given in the ''Driver'' and ''Setup'' sections are valid. 199 200 '''Note''' The PostgreSQL odbc driver on many systems is distributed as a separate package (the `postgresql-odbc` or similar). Don't use the PostgreSQL driver shipped with the UnixODBC source tarball, as this one is known to be [[https://bugzilla.redhat.com/show_bug.cgi?id=458708#c7|obsolete]]. 201 202 * It is recommended to use a command line client to access the database through ODBC to check if everything was configured correctly. For example, unixODBC provides an `isql` client: 203 204 {{{ 205 #!div style="font-size: 90%" 206 {{{#!sh 200 207 $ isql -v smoa_comp smoa_comp <password> 201 208 +---------------------------------------+ … … 209 216 SQL>quit 210 217 $ 211 212 {{Note|}}It is recommended to run this command as user different than root (e.g. the smoa_comp user).218 }}} 219 '''Note:''' It is recommended to run this command as user different than root (e.g. the smoa_comp user). 213 220 214 221 == Service configuration == 215 You can find the complete reference guide in the SMOA Computing manual (that can be found under the <code>doc/</code> directory). For convenience we provided below sample service configuration files (located in <code>PREFIX/etc/smoa-compd.xml</code> - do not mislead this file with the client configuration file which is named <code>smoa-comp.xml</code>) that you can use as templates:222 You can find the complete reference guide in the SMOA Computing manual (that can be found under the `doc/` directory). For convenience we provided below sample service configuration files (located in `PREFIX/etc/smoa-compd.xml` - do not mislead this file with the client configuration file which is named `smoa-comp.xml`) that you can use as templates: 216 223 217 224 === Template configuration for the SMOA Computing service deployed on the top of LSF system === 225 226 {{{ 227 #!div style="font-size: 90%" 228 {{{#!xml 218 229 219 230 <?xml version="1.0" encoding="UTF-8"?> … … 301 312 </sm:Service> 302 313 </Configuration> 303 </sm:SMOACore> 314 </sm:SMOACore> 315 }}} 316 }}} 304 317 305 318 === Template configuration for the SMOA Computing service deployed on the top of Sun Grid Engine === 319 {{{ 320 #!div style="font-size: 90%" 321 {{{#!xml 306 322 307 323 <?xml version="1.0" encoding="UTF-8"?> … … 392 408 </sm:Service> 393 409 </Configuration> 394 </sm:SMOACore> 410 </sm:SMOACore> 411 }}} 412 }}} 395 413 396 414 === Template configuration for the SMOA Computing service deployed on the top of Torque (using Maui scheduler) === 397 <?xml version="1.0" encoding="UTF-8"?> 398 <sm:SMOACore 415 {{{ 416 #!div style="font-size: 90%" 417 {{{#!xml 418 419 <?xml version="1.0" encoding="UTF-8"?> 420 <sm:SMOACore 399 421 xmlns:sm="http://schemas.smoa-project.com/core/2009/01/config" 400 422 xmlns="http://schemas.smoa-project.com/comp/2009/01/config" … … 470 492 </sm:Service> 471 493 </Configuration> 472 </sm:SMOACore> 494 </sm:SMOACore> 495 }}} 496 }}} 497 473 498 In most cases it should be enough to change only following elements: 474 499 ; ''Database'' : the contact data for the Database created in the previously steps