• ActionPWRemoveContinued

Action PW Remove continued

Assigned

BAM+?

Prev assigned

Tasks adressed

["TaskX/1"]

Time estimated

2md

Time used

½md

Priority

3

Status

Description not reviewed

Iteration

16

Notes

also localhost:8080

Description

Currently (2008-11-27) username and password to Fedora and also localhost:8080 is hardcoded a number of places. The username and password should always be given as parameters to the webservices, and fedoraServerHost and fedoraServerPort can be given in a configuration or properties file?

• We will investigate the number of affected places, and make sure that we do not need to change any interfaces. Time estimate: ½md.
• We will remove the hardcoded username and password. Time estimate: ½md.

• We will introduce a properties file - or can we use fedora/server/config/fedora.fcfg? Time estimate: 1md.

Investigation Hardcoded Username + PW

• RIquery_webservice: only in test, ok
• disseminator_webservice: no longer used, ok

• domsutils introduces a DomsUserToken, which has a hardcoded username + pw default...

• import_from_horizon_webservice: only in test, ok
• ingest: no longer used, ok
• minidoms: no longer used, ok
• objectcreation_webservice: only in test, ok
• search_webservice: class SearchWS uses hardcoded username + pw to prepare connection, soon to be outdated?

• SummaFace: uses hardcoded username + pw to create DomsUserToken...

• testbed: install.sh + INSTALL uses hardcoded username + pw

To summarise, assuming search webservice is outdated, we only have hardcoded username + pw in connection with DomsUserToken (domsutils + SummaFace) and in testbed.

Investigation Hardcoded Host + Port

• RIquery_webservice: uses DomsUserToken with hardcoded serverurl...

• aarbog_objects: uses localhost:7900, outdated, ok
• avis_objects, basecollection, spolebaand_objects, radio_objects, yearbook_collection_V@: uses localhost:8080 for licences, schemas and webservices. What are they supposed to do?
• bitstorage_webservice: uses localhost:8080 to look up filecharacterizer_webservice, and in wsdl...
• disseminator_webservice: no longer used, ok
• domsmanagement: validator client?

• domsutils: DomsUserToken localhost:8080 default + DomsPIDGenerator webservice?

• filecharacterizer_webservice: only wsdl
• guiobjectmanipulation_webservice: hardcoded localhost:8100 should be changed!
• import_from_horizon_webservice: hardcoded localhost:8080 - but this is a mockup anyway?
• ingest: uses localhost:7900 in properties and test objects - no longer used?
• minidoms: no longer used

• objectcreation_webservices: uses localhost:8080 in DomsUserToken

• objectmanipulation_webservices: uses localhost:8080 in DomsUserToken

• pidgenerator_webservices: uses localhost:8080 in wsdl
• search_webservice: class SearchWS uses localhost:8080 to prepare connection, soon to be outdated?

• summaFace: SummaDomsInterface + SummaSideServiceLocator uses hardcoded localhost:8080 to fedora + search webservice...

• testbed: install.sh + INSTALL uses hardcoded localhost:8080

I recommend tidying up before attempting to fix. -- ["bam"] DateTime(2008-12-11T10:09:52Z)

Checklist For Working On An Action

The Life Cycle of an Action:

• Assign people for action definition: Done at start of iteration status meeting. Fill out Assigned

• Define the action: Describe information about what is to be done and how. Fill out Tasks Addressed and Time Estimated.

• Review the definition: Get another project group member to review the action definition, and update it.

• Assign people for action implementation: Done by project manager, usually the same persons who wrote the definition. Fill out Assigned and Prev assigned if new persons are assigned.

• Implement the action: See details below

• Review the action: Get another project group member to review what is implemented (code and documentation), and update it.

• Finish the action: Change the status to "Finished" and update the "time used" field on the action page.

Please make sure that you address the below issues, when working on an action:

• Update the state of the action to "In Progress" when you start working on it.
• Check if the tasks addressed by this action have their status set to "In Progress". If that is not the case, then change the state of them.

• Keep track of how much time that has been spent working on the action. If it addresses more than one task, then make a note on the action page about how much of the elapsed time that has been spent on the individual tasks. Hint: Continually updating the "Time used" field will make it easier for you.

• Update the "Progress History" and documentation pages of each task addressed by this action when appropriate. This depends on the situation, but in general, the task pages should hold all important related information about the work done, experiences gathered, identified requirements and so on.