Changes between Version 36 and Version 37 of ESGFNodeInstallation


Ignore:
Timestamp:
Nov 13, 2013 11:37:09 AM (8 years ago)
Author:
carlos
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ESGFNodeInstallation

    v36 v37  
    376376
    377377
    378 Obtain a digital certificate from an ESGF trusted !MyProxy server, and rename it to whatever path you have defined in esg.ini :
     378
     379See the [[http://www2-pcmdi.llnl.gov/Members/bdrach/.personal/esg-publisher-configuration/|ESGF]] publication reference for details.
     380
     381After modifying `esgcet_models_table.txt` and `esg.ini` files, you have to update the data base by executing :
     382{{{
     383#!sh
     384$ cd /usr/local/uvcdat/1.4.0/bin/
     385$ ./esginitialize -c
     386}}}
     387
     388* `./esginitialize -d 0`: To remove all tables
     389
     390* `./esginitialize -c`  : Upgrade the database schema to the latest version, and initialize projects, models, experiments, and standard names from configuration files.
     391
     392
     393Obtain a digital certificate from an ESGF trusted !MyProxy server, and rename it to whatever path you have defined in esg.ini.
     394
     395[[NoteBox(warn, Remember\, you have to log in a Federation to do it.)]]
     396
    379397{{{
    380398#!sh
     
    382400}}}
    383401
    384 See the [[http://www2-pcmdi.llnl.gov/Members/bdrach/.personal/esg-publisher-configuration/|ESGF]] publication reference for details.
    385 
    386 * `./esginitialize -d 0`: To remove all tables
    387 
    388 * `./esginitialize -c`  : Upgrade the database schema to the latest version, and initialize projects, models, experiments, and standard names from configuration files.
    389 
    390 Example of how to use the commands above:
    391 {{{
    392 #!sh
    393 $ cd /usr/local/uvcdat/1.4.0/bin/
    394 $ ./esginitialize -d 0
    395 $ ./esginitialize -c
    396 
    397 }}}
    398402
    399403Finally, run the commands below to parse the cordex project on the local Data Node, ingest it in the local Postgres database, and send it for harvesting to the configured Index Node.