Difference between revisions of "ESciDoc MPDL LDAP/Single LDAP Server"
Jump to navigation
Jump to search
| Line 34: | Line 34: | ||
**'''Latency'''- refers to the elapsed time between when an application makes an LDAP request and when it receives a response. | **'''Latency'''- refers to the elapsed time between when an application makes an LDAP request and when it receives a response. | ||
**'''Throughput'''- refers to the total sustainable operation load that the directory can handle | **'''Throughput'''- refers to the total sustainable operation load that the directory can handle | ||
[[Image:ExampleCalculationsBusy_EMail_Service.gif]] | |||
*Level of service - expected availability 99,98% (according PubMan expected availability) | *Level of service - expected availability 99,98% (according PubMan expected availability) | ||
Revision as of 08:51, 30 March 2010
Single LDAP Server[edit]
- A Single eSciDoc LDAP Server will be installed to support the MPDL productive instances of eSciDoc core services and solutions
- Configuration used as described at LocalDirectoryService, see image below
http://www.openldap.org/doc/admin24/config_local.png
The Client in this case is actually the eSciDoc login form.
Configuration with eSciDoc[edit]
- see Login configuration for eSciDoc- Part: Login via LDAP server
Design checklist[edit]
Directory needs and applications that will use the directory[edit]
- Applications that will use MPDL LDAP
- escidoc-core services
- escidoc-based-solutions
- Oranizational structure to be considered for MPDL-based LDAP
- Geographical location: Institutes (sometimes their departments?) are located throughout Germany and several institutes are outside of Germany
- NIMS (Japan): if it stays with current PubMan repository, additional effort of exchange with NIMS LDAP might be needed
- Performance
- Latency- refers to the elapsed time between when an application makes an LDAP request and when it receives a response.
- Throughput- refers to the total sustainable operation load that the directory can handle
- Level of service - expected availability 99,98% (according PubMan expected availability)
Data needs[edit]
- Determine your data needs
- Design your schema
- Design your namespace
- Design the topology of your directory
- Design your directory replication scheme
- Design your directory for security and privacy