Page History

...

• eaglei.datatools.repository.url
  The base-url of the eagle-i repository against which the SWEET runs.  This property needs to be provided even if the SWEET runs in the same server as the repository
  Default: None
  Requirements: MUST be an HTTPS end-point, since the SWEET back-end uses HTTP basic authentication. localhost cannot be used
  Example: https://somenode.eaglei.net
• eaglei.ui.centralSearch.url
  The full url for the central search application. This property is used to set the links in the menu of the SWEET application
  Default: http://search.eagle-i.net/central
  Requirements: None
  Example: http://search.eagle-i.net/central
• eaglei.catalyst.user
  A repository user that has anonymous access. This user is used for the SWEET webservices. If you would like to expose contact information to the webservices user, add this user to the Contact Properties ACL via the repository's administrative panel.
  Default: None
  Requirements: Valid repository username
  Example: specialRepoUser

...

• eaglei.model.url
  The full url for the model service that provides ontology term suggestion lists and access to the model class information. 
  Default: None
  Requirements: None
  Example: https://search.eagle-i.net/model

...

• Feedback Module
  Feedback mechanism that allows users of the SWEET, Search and Glossary applications to provide feedback about their use to you and your developers. We have parameterized these properties to allow to you to use either JIRA for tracking the issues or have an email sent.
  • eaglei.feedback.method
    Specify which method to use for submitting feedback. Be sure to set the corresponding required properties depending on which method you are using.
    Default: jira
    Requirements: Must be either 'jira' or 'email'
  • eaglei.feedback.jira.url TODO - rename to non Jira-specific
    If you are using JIRA, this will be the full url for connecting to JIRA.
    If you would like to have emails sent, this will be the full hostname for sending the email.
    Default: None
    Requirements: A valid url, including any port information needed to connect to the issue client. OR A valid hostname needed to send the email.
    Example:http://jira.eagle-i.net:8080/rpc/soap/jirasoapservice-v2
• Feedback Module (Jira)
  • eaglei.feedback.jira.user
    If the method for submitting feedback is JIRA, this is the corresponding JIRA user that will be used for the submission. If the method selected is EMAIL, this is the user for sending the email.
    Default: None
    Requirements: A valid JIRA User or EMAIL User.
  • eaglei.feedback.jira.password
    The password for the above mentioned user.
    Default: None
    Requirements: A valid password for the JIRA User or EMAIL UserFeedback Module (EMAIL)

...

• eaglei.sparqler.source.URL
  The base-url of the eagle-i repository against which the data tools runs.  This property needs to be provided even if the data tools back-end runs in the same server as the repository
  Default: None
  Requirements: Must be the base-url of the source repository. Must use protocol HTTPS, since privileged access is required to the source repository. localhost cannot be used
  Example: https://myRepository.net/
• eaglei.sparqler.target.URL
  Specifies the path to the target (sparqler) repository, which is to mirror the source repository.
  Default: None
  Requirements: Must be the base-url of the target (sparqler) repository. Must use protocol HTTPS, since privileged access is required to the target (sparqler) repository. localhost cannot be used
  Example: https://mySparqlerRepository.net/sparqler/
  
• eaglei.sparqler.lastSynchronizedDateFile
  The local path to the file in which the timestamp of the most recently synchronized data is stored.
  Example: /opt/eaglei/eagle-i-sparqler.last-sync-date.properties
  Requirements: the tomcat-user must have permission to write to this file (and to create it if it does not yet exist).

In file eagle-i-apps-credentials.properties:

• eaglei.sparqler.source.user
  The user-name under which the synchronizer obtains data from the source repository.
  Default: None
  Requirements: the named user must have sufficient access to use the "harvest" and "sparql" requests.
  Example: myUserName

• eaglei.sparqler.source.password
  The password to be used with the user-name under which the synchronizer obtains data from the source repository.
  Default: None
  Requirements: none
  Example: myPassword

• eaglei.sparqler.target.user
  The user-name under which the synchronizer adds data to or removes data from the target sparqler repository.
  Default: None
  Requirements: the named user must have sufficient access to use the "graph" request.
  Example: mySparqlerUserName

• eaglei.sparqler.target.password
  The password to be used with the user-name under which the synchronizer adds data to or removes data from the target sparqler repository.
  Default: None
  Requirements: None.
  Example: mySparqlerPassword

Optional Properties

In file eagle-i-apps.properties:

• eaglei.sparqler.syncData.captureFile
  Used for test- and debugging-purposes only. The base local path to files in which the data harvested from the source-repository, the data added to, and the data deleeted from the sparwqler repository.
  Default: None. If unset, no data is dumped to a file.
  Requirements: None.
  Example: /opt/eaglei/data/syncCapture

Optional Properties governing scheduling of synchronization

...