Talk:Escidoc-core Migration v1.1 to v1.2
Jump to navigation
Jump to search
Some numbers[edit]
coreservice[edit]
Migration of FOXMLs[edit]
- > 2h (caused by copying > 40G of data)
Migration of escidoc-core database[edit]
- Total size: 37G
- Biggest issue: statistical data
- Total time: 149 minutes 46 seconds
Recache[edit]
- 3 hours
Reindex[edit]
- 2000 items / hour
- almost all have FT to index
- no of items ca: 16000
r-coreservice[edit]
Migration of FOXMLs[edit]
- > 2h (caused by copying > 40G of data)
Migration of escidoc-core database[edit]
- Total size: ca 7G (raw statistics were cleaned-up before migration took place)
- Biggest issue: statistical data
- Total time: less then 2 hours
Recache[edit]
- 5 hours
Reindex[edit]
- 5000 items / hour
- no FT to index
- no of items approx: 26000
peercoreservice[edit]
Recache[edit]
- ca 2 hours
- no of items ca: 5000
Reindex[edit]
- 1000 items /hour
- all have FT to index
- no of items ca: 5000
Older input that was on PubMan_6_1 page, moved here, just in case.[edit]
The current version of escidoc-core used for this release is 1.2. all below mentioned changes have to be applied to all affected servers.
- Fedora
- the version of Fedora has to be 3.3.1
- the fedora-3.3-fix01-installer.jar delivered by FIZ creates an entry in the fedora.fcfg file, which prevents Fedora to be started before the JBoss instance containing the escidoc-core.ear.
Inside the <datastore id="localPostgreSQLPool"> section, the parameter
<param name="ddlConverter" value="de.escidoc.core.common.business.fedora.mptstore.PostgresDDLGenerator"/>
has to be set to
<param name="ddlConverter" value="fedora.server.utilities.PostgresDDLConverter"/>
if you need to start a standalone Fedora instance.
- The Patch "MPTStore patch" is not added during the installation of the customized fedora, so it has to be added manually. See Add the MPTStore patch bottom.
- JBoss
- the applicxation server has to be updated with a new patch (delivered by FIZ)
- FOXML
- switching from escidoc-core 1.1 to 1.2 requires a migration of the Fedora FOXML files
- the migration procedure delivered by FIZ has to be tested thoroughly!!!
- see also Core database ...
- if there are any escidoc resources containing capital letters in their internal PID, those resources have to be renamed, and all references to those renamed resources have to be updated in any other resource. (use foxml_migration-jar-with-dependencies.jar with the cmodel argument in order to update references to the content-model escidoc:TOC).
- Renaming of escidoc:TOC content model:
- export the escidoc:TOC object from Fedora.
- purge the escidoc:TOC object from Fedora.
- modify the exported xml file: the creation date of the RELS-EXT datastreams MUST be different! (RELS-EXT.0 < RELS_EXT.1 etc.).
- ingest the changed FOXML object.
- XACML
- AA policies delivered with the core-infrastructure can not be used as default policies (they are communicated)
- AA Policies for MPDL are in SVN Common services - XACML
- affected AA schema tables in escidoc-core database: escidoc_policies, scope_df, escidoc_roles
- ToDO: run the following script on escidoc-core database AFTER MIGRATION OF THE CORE DATABASE IS FINISHED "changes 1.2-MPDL.sql"