Difference between revisions of "PubMan 6 1"
Jump to navigation
Jump to search
| Line 65: | Line 65: | ||
== Core Infrastructure == | == Core Infrastructure == | ||
Details available at [[Escidoc-core_Migration_v1.1_to_v1.2|Core Migration 1.1 to 1.2]] | Details available at [[Escidoc-core_Migration_v1.1_to_v1.2|Core Migration 1.1 to 1.2]] | ||
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. | all below mentioned changes have to be applied to all affected servers. | ||
*Fedora | *Fedora | ||
Revision as of 13:07, 2 August 2010
This page shall contain every change that is made during a qa release of the version mentioned above. If it's not here, it never happened!
PubMan 6.1 Release[edit]
Affected Servers[edit]
PubMan EAR[edit]
Copy pid-cache-ds.xml to the JBoss deploy directory
PubMan Properties[edit]
- new property: escidoc.cone.subjectVocab (for the indication which controlled vocabs are displayed as browse by). Current value = ddc
- new property: escidoc.framework_access.login.url (to be used to login to escidoc-core)
Pid cache:
escidoc.pidcache.cache.size.max=1000 escidoc.pidcache.refresh.interval=120 escidoc.pidcache.dummy.url=http://pubman.mpdl.mpg.de/pubman/faces/PidNotResolved.jsp?id= escidoc.pid.gwdg.service.url=http://handle.gwdg.de:8080/pidservice escidoc.pid.gwdg.timeout=3000 escidoc.pid.pidcache.service.url=http://dev-pubman.mpdl.mpg.de/pidcache/handle escidoc.pid.service.create.path=/write/create escidoc.pid.service.view.path=/read/view escidoc.pid.service.delete.path=/write/delete escidoc.pid.service.update.path=/write/modify escidoc.pid.service.search.path=/read/search escidoc.pid.gwdg.user.login=1234 escidoc.pid.gwdg.user.password=mypwd escidoc.pidcache.user.name=<pid_manager_login> escidoc.pidcache.user.password=<pid_manager_password>
- new property: escidoc.pubman.genres.configuration=WEB-INF/classes/Genres.xml
- new properties block for Search&Export service
escidoc.search.and.export.default.sql.query=escidoc.metadata=test and escidoc.content-model.objid=escidoc:persistent4 escidoc.search.and.export.indexes.explain.query=/srw/search/escidoc_all?operation=explain escidoc.search.and.export.default.sort.keys= escidoc.search.and.export.default.sort.order=ascending escidoc.search.and.export.start.record=1 escidoc.search.and.export.maximum.records=50
Core Infrastructure[edit]
Details available at Core Migration 1.1 to 1.2
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"
Core Properties[edit]
Change Property for Lucene Indexing stylesheet:
gsearch.escidoc.indexingStylesheet = http://escidoc1.escidoc.mpg.de/resources/searchIndexDefinition/mpdlEscidocXmlToLucene_1.2.xslt
Core Database[edit]
- Migration 1.1 to 1.2
- a database migration is required!
- migration procedure delivered by FIZ has to be tested thoroughly!
- The database migration uses certain fingerprints in order to determine the current version of the db. The layout of our database differs from the one assumed by the db-migration tool. Therefore it is necessary to run the following script prior to the db-migration:
- Modify admin-tool.properties.
- Check the following entries:
- datasource.script.prefix=check-which-one
- datasource.url=check-which-one
- datasource.driverClassName=org.postgresql.Driver
- datasource.username=check-which-one
- datasource.password=check-which-one
- creator_id=the user-id of a sysadmin user
- escidoc.database.tablespace.list=tbl_index
- call ant db-migration
- DO NOT USE THE JAR FILE with the db-migration argument!
Common Services[edit]
- the following modules have been updated and reflect all schema and interface changes:
- framework_access
- common_logic
- common_logic_ear
- all three modules completed all our current unit- and integration tests successfully.
Validation Database[edit]
CoNE Database[edit]
- add "image/bmp" to mimetypes and escidocmimetypes
- add "video/x-ms-wmv" to mimetypes and escidocmimetypes
- run
update triples set predicate = 'http://purl.org/escidoc/metadata/terms/0.1/suffix' where predicate = 'urn:cone:suffix'; update triples set predicate = 'http://www.w3.org/1999/02/22-rdf-syntax-ns#value' where predicate = 'http://www.w3.org/1999/02/22-rdf-syntax-ns#/value'; update triples set predicate = 'http://www.w3.org/2001/XMLSchema-instance type' where predicate = 'http://www.w3.org/2001/XMLSchema-instance/type';
- import these RDFs into CoNE:
- run [1]
- reset ddc model:
http://localhost:8080/cone/reset.jsp?model=ddc
- run
delete from matches m1 where m1.id in ( select id from matches left join triples on id = subject where subject is null); delete from results r1 where r1.id in ( select id from results left join triples on id = subject where subject is null);
Data Migration[edit]
- Check if PubMan Import Task Content-Model is present (escidoc:importtask1), otherwise create one and add to properties (escidoc.import.task.content-model).
eSciDoc Admin[edit]
svn up rctgescidocadmin stop rctgescidocadmin start