[Netarchivesuite-users] Add or change pseudo-top-level-domains

Mikis Seth Sørensen mss at statsbiblioteket.dk
Mon Jan 5 14:33:03 CET 2015


Hi Meelis

The pseudo top level domains are defined in the common settings of the
settings and are therefore distributed to all application as part of the
deploy process.


I think that the only managable way to maintain the NAS application
configuration for the system is to only make permanent changes to the
central settings used by the deploy process. As the number of NAS
applications rise it will become more and more difficult to maintain the
individual application configuration by hand, and it will be nearly
impossible to upgrade the system, as a upgrade normally includes some
changes to the settings which would need to be merged to the applications
settings individually.

Note that isn¹t neccessary to redeploy the entire system because of a
reconfiguration. As you can see from the RunNetarchiveSuite.sh quickstart
file, the configuration generation, deployment and startup/shutdown of the
applications are separate substeps. So you can still manually copy a new
configuration to an application and restart the application, even if you
use the central setting file to generate the application specific
settings. 

You can of course make temporary changes to the application
configurations, but these will overwritten the next time you do a system
deploy, typical in connection with a upgrade.

Cheers
Mikis

On 1/5/15, 8:21 AM, "Meelis Mihhailov" <meelis at nlib.ee> wrote:

>Hi Mikis and thanks for the reply.
>
>Do I understan correcty:
>Only good way to edit settings in a quick start setup is to redeploy the
>whole installation? Are those pseudo top level domains settings added to
>all those settings files that are created or are they present only in
>one file? :)
>
>
>-----------------------------------------------------
>Meelis Mihhailov
>Süsteemiadministraator / Systemadministrator
>Eesti Rahvusraamatukogu / National Library Of Estonia
>
>Telefon: 630 7178 / Phone: +372 630 7178
>E-post: meelis at nlib.ee / E-mail: meelis at nlib.ee
>
>Tõnismägi 2, 15189 Tallinn, ESTONIA
>
>www.eestirahvusraamatukogu.ee
>-----------------------------------------------------
>
>On 2.01.2015 11:42, Mikis Seth Sørensen wrote:
>> Hi Meelis
>>
>> If you are using the quickstart as the start point, you can just modify
>> the deploy_standalone_example.xml file used when installing the
>> quickstart system with the command:
>> ./RunNetarchiveSuite.sh NetarchiveSuite.zip
>> deploy_standalone_example.xml deploy/
>> This will generate the individual settings files in the deploy/localhost
>> dir. These files will as part of the RunNetarchiveSuite.sh script be
>> copied to the test at localhost:~/QUICKSTART/conf dir.
>>
>> So the normal way of maintaining the application configurations is to
>> modify the global settings.xml and use the deploy modules config and
>> script generation functionality (DeployApplication line in
>> RunNetarchiveSuite.sh) included in NAS to configure and deploy the
>> individual apps. This will not overwrite the existing databases in a NAS
>> system (but as always, remember to backup your system prior to a
>>redeploy).
>> So the global settings used in the quickstart is the
>> deploy_standalone_example.xml file given as argument for the
>> RunNetarchiveSuite.sh script. The configs found in the zip files
>> examples directory are just for inspiration, and are not used actively
>> in the quickstart.
>>
>> Hope that helps
>> Mikis
>>
>> From: Meelis Mihhailov <meelis at nlib.ee <mailto:meelis at nlib.ee>>
>> Reply-To: "netarchivesuite-users at ml.sbforge.org
>> <mailto:netarchivesuite-users at ml.sbforge.org>"
>> <netarchivesuite-users at ml.sbforge.org
>> <mailto:netarchivesuite-users at ml.sbforge.org>>
>> Date: Monday, December 29, 2014 at 10:06 AM
>> To: "netarchivesuite-users at ml.sbforge.org
>> <mailto:netarchivesuite-users at ml.sbforge.org>"
>> <netarchivesuite-users at ml.sbforge.org
>> <mailto:netarchivesuite-users at ml.sbforge.org>>
>> Subject: [Netarchivesuite-users] Add or change pseudo-top-level-domains
>>
>>     Hi all!
>>
>>     Is there a way to add/edit pseudo-top-level-domains if NAS has been
>>     installed with Quick Start?
>>     Currently using NAS version 4.4.0 and NAS version 4.2.0.
>>
>>     Manual shows that it should be set in the settings.xml file but as
>>     we use quick start for our installation the settings file exists
>>     only in the examples directory.
>>     Do I have to add the <topLevelDomains> code in to all the settings
>>     xml files under the "conf" directory ( settings_GUIApplication,
>>     settings_HarvestControllerApplication etc) or is there another place
>>     for these settings? :)
>>
>>     -----------------------------------------------------
>>     Meelis Mihhailov
>>     Eesti Rahvusraamatukogu / National Library Of Estonia
>>
>>     Telefon: 630 7178 / Phone: +372 630 7178
>>     E-post: meelis at nlib.ee / E-mail: meelis at nlib.ee
>>
>>     Tõnismägi 2, 15189 Tallinn, ESTONIA
>>
>>     www.eestirahvusraamatukogu.ee
>>     -----------------------------------------------------
>>
>>
>>
>> _______________________________________________
>> NetarchiveSuite-users mailing list
>> NetarchiveSuite-users at ml.sbforge.org
>> http://ml.sbforge.org/mailman/listinfo/netarchivesuite-users
>>
>_______________________________________________
>NetarchiveSuite-users mailing list
>NetarchiveSuite-users at ml.sbforge.org
>http://ml.sbforge.org/mailman/listinfo/netarchivesuite-users




More information about the NetarchiveSuite-users mailing list