Changes between Version 14 and Version 15 of VirtualCollectionRegistry


Ignore:
Timestamp:
08/26/14 08:05:42 (10 years ago)
Author:
Twan Goosen
Comment:

deployment

Legend:

Unmodified
Added
Removed
Modified
  • VirtualCollectionRegistry

    v14 v15  
    103103==== OAI provider ====
    104104
     105The VCR OAI provider is using the [source:/OAIProvider OAIProvider library], which consists of an out-of-the-box singleton ''OAIProvider'' instance and a servlet, in addition to an application specific ''Repository''. The repository is implemented by ''VirtualColletionRegistryOAIRepository'' in the ''eu.clarin.cmdi.virtualcollectionregistry.oai'' package, which also contains a Spring configuration class that links the repository with a ''!VirtualCollectionRegistry'' service instance on the one hand and the ''OAIProvider'' on the other. The servlet is mounted (via web.xml) at ''/oai'' and picks up the OAI provider instance automatically.
     106
    105107=== Deployment ===
    106108
    107 web.xml variations
     109The VCR builds into a single WAR file that can be deployed onto a servlet container (tested on and developed for Tomcat 7). There exists an alternative '''build profile''' called ''development'' (use ''mvn install -Pdevelopment'') which makes logging output go to the console and enables Tomcat user realm authentication. By default, however, the application is enabled for Shibboleth authentication and logging to a file on disk. To allow for the switch between authentication mechanism, the web.xml file is duplicated and one of the two is selected at package time - see [source:/VirtualCollectionRegistry/trunk/VirtualCollectionRegistry/src/main/webapp/WEB-INF].
    108110
    109 build profiles
     111Building the VCR at least up to the ''package'' phase (preferably ''mvn install'') will result in the creation of a .tar.gz file in the ''target'' directory that contains the deployable WAR file as well as the project documentation and licensing information in a directory that contains the artifact name and version number.
    110112
    111 deployment package
    112 
    113 server configuration (PID provider, other properties see readme)
     113Further deployment instructions (primarily adding a datasource and a number of parameters to ''context.xml'') can be found in the [source:/VirtualCollectionRegistry/trunk/VirtualCollectionRegistry/doc/README.txt README file].
    114114
    115115== Tickets ==
     
    120120Open tickets:
    121121
    122 
    123122[[TicketQuery(status=accepted|assigned|new|reopened), component=VCRegistry, order=priority, format=table, col=summary|priority|owner|reporter)]]