![]() Make sure the shell script ( zipdownload) is executable, and edit it to configure the database access credentials.ĭo note that the executable does not need access to the entire Dataverse installation database. To the cgi-bin directory of the chosen Apache server ( /var/www/cgi-bin standard). Aside from the name change, there have been noĬhanges in the functionality of the tool).Ĭopy it, together with the shell script cgi-bin/zipdownload (A pre-built jar file wasĭistributed under that name as part of the 5.0 release on GitHub. In the releases 5.0-5.9 it existed under the name ZipDownloadService-v1.0.0. The version were changed as of the release 5.10, as part of an overall cleanup and reorganization of the project In the Dataverse Software 5.0+ source tree for more information.įollow the instructions in the file above to build zipdownloader-0.0.1.jar. Please consult the README at scripts/zipdownload The service needs to have access to the database as well as to the storage filesystem, and/or S3 bucket). This service running on a different host system, freeing the cycles on the main Application Server. Since zipping is also a CPU-intensive task, it is possible to have This moves these potentially long-running jobs completely outside the Application Server (Payara), and prevents worker threads from becoming locked serving them. Requested (that they are authorized to download), but the request is redirected to a standalone zipper service runningĪs a cgi-bin executable under Apache. If this option ( :CustomZipDownloadServiceUrl) is enabled, instead of enforcing the size limit on multi-file zippedĭownloads (as normally specified by the option :ZipDownloadLimit), we attempt to serve all the files that the user Once a standardized version of you Custom Terms are registered as a license, an SQL update like the following can be used to have datasets use it:Īs of Dataverse Software 5.0 we offer an experimental optimization for the multi-file, download-as-zip functionality. Security: with the license terms maintained external to Dataverse, users cannot edit specific terms and curators do not need to check for edits Usability: the license can be selected for new datasets without allowing custom terms and without users having to cut/paste terms or collection administrators having to configure templates with those termsĮfficiency: custom terms are stored per dataset whereas licenses are registered once and all uses of it refer to the same object and external URL Once the license is registered with Dataverse, making an SQL update to change datasets/versions using that license to reference it instead of having their own copy of those custom terms. Using the API to make sure the license is active and deciding whether the license should also be the default. Using the Dataverse API to register the new license as one of the options available in your installation. an HTML document with sections corresponding to the terms fields that are used.ĭefining a name, short description, URL (where it is posted), and optionally an icon URL for this license. Doing this would include:Ĭreating and posting an external document that includes the custom terms, i.e. In addition, if many datasets use the same set of Custom Terms, it may make sense to create and register a standard license including those terms. Password aliases ( dataverse.db.password, etc.) are stored per app server. See Edit Draft Versions Logging section in Monitoring of the Admin Guide for details. See also :MDCLogPath section in the Configuration section of this guide and the Make Data Count section of the Admin Guide.ĭataset draft version logging occurs separately on each app server. If Make Data Count is used, its raw logs must be copied from each app server to single instance of Counter Processor. By default the sitemap is written to the directory /usr/local/payara6/glassfish/domains/domain1/docroot/sitemap. When a sitemap is created by an app server it is written to the filesystem of just that app server. By default these logos and footers are written to the directory /usr/local/payara6/glassfish/domains/domain1/docroot/logos. When users upload a logo or footer for their Dataverse collection using the “theme” feature described in the Dataverse Collection Management section of the User Guide, these logos are stored only on the app server the user happened to be on when uploading the logo. Only one app server can be the dedicated timer server, as explained in the Dataverse Installation Application Timers section of the Admin Guide. You should be conscious of the following when running multiple app servers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |