Difference between revisions of "PubMan Sword"

From MPDLMediaWiki
Jump to navigation Jump to search
Line 12: Line 12:
The PubMan SWORD interface is deployed within the PubMan ear, therefore one can access the above described servlets by the PubMan baseURL + the servlet path.  
The PubMan SWORD interface is deployed within the PubMan ear, therefore one can access the above described servlets by the PubMan baseURL + the servlet path.  


(Example with PubMan base url http://pubman.mpdl.mpg.de)
(Example with PubMan base url http://pubman.mpdl.mpg.de, note that sword functionality is not yet deployed on live server)


===Service Document===
===Service Document===

Revision as of 11:43, 1 April 2009

This page briefly describes the SWORD Server implementation in the PubMan solution. General Information about SWORD can be found here.

Implementation[edit]

For start the SWORD functionality is directly implemented in PubMan by exploiting and extending the sword api provided by JISC. In future we could have a seperate SWORD service for all eSciDoc solutions. PubMan implements 3 classes for the SWORD service:

  1. PubManSwordServer - Processing of requests
  2. PubManServiceDocumentServlet - Accepting requests for the Service Document (dependent on user credentials)
  3. PubManDepositServlet - Accepting requests for the deposits (dependent on user credentials)

Interface[edit]

The PubMan SWORD interface is deployed within the PubMan ear, therefore one can access the above described servlets by the PubMan baseURL + the servlet path.

(Example with PubMan base url http://pubman.mpdl.mpg.de, note that sword functionality is not yet deployed on live server)

Service Document[edit]

http://pubman.mpdl.mpg.de/pubman/faces/sword/servicedocument

Request:

Response:

Deposit Service[edit]

http://pubman.mpdl.mpg.de/pubman/faces/sword/deposit

Request:

Response: