Related Research Articles
Active Directory (AD) is a directory service developed by Microsoft for Windows domain networks. Windows Server operating systems include it as a set of processes and services. Originally, only centralized domain management used Active Directory. However, it ultimately became an umbrella title for various directory-based identity-related services.
The Lightweight Directory Access Protocol is an open, vendor-neutral, industry standard application protocol for accessing and maintaining distributed directory information services over an Internet Protocol (IP) network. Directory services play an important role in developing intranet and Internet applications by allowing the sharing of information about users, systems, networks, services, and applications throughout the network. As examples, directory services may provide any organized set of records, often with a hierarchical structure, such as a corporate email directory. Similarly, a telephone directory is a list of subscribers with an address and a phone number.
In distributed computing, a remote procedure call (RPC) is when a computer program causes a procedure (subroutine) to execute in a different address space, which is written as if it were a normal (local) procedure call, without the programmer explicitly writing the details for the remote interaction. That is, the programmer writes essentially the same code whether the subroutine is local to the executing program, or remote. This is a form of client–server interaction, typically implemented via a request–response message-passing system. In the object-oriented programming paradigm, RPCs are represented by remote method invocation (RMI). The RPC model implies a level of location transparency, namely that calling procedures are largely the same whether they are local or remote, but usually, they are not identical, so local calls can be distinguished from remote calls. Remote calls are usually orders of magnitude slower and less reliable than local calls, so distinguishing them is important.
Network File System (NFS) is a distributed file system protocol originally developed by Sun Microsystems (Sun) in 1984, allowing a user on a client computer to access files over a computer network much like local storage is accessed. NFS, like many other protocols, builds on the Open Network Computing Remote Procedure Call system. NFS is an open IETF standard defined in a Request for Comments (RFC), allowing anyone to implement the protocol.
X.500 is a series of computer networking standards covering electronic directory services. The X.500 series was developed by the Telecommunication Standardization Sector of the International Telecommunication Union (ITU-T). ITU-T was formerly known as the Consultative Committee for International Telephony and Telegraphy (CCITT). X.500 was first approved in 1988. The directory services were developed to support requirements of X.400 electronic mail exchange and name lookup. The International Organization for Standardization (ISO) and International Electrotechnical Commission (IEC) were partners in developing the standards, incorporating them into the Open Systems Interconnection suite of protocols. ISO/IEC 9594 is the corresponding ISO/IEC identification.
In computer science, inter-process communication (IPC), also spelled interprocess communication, are the mechanisms provided by an operating system for processes to manage shared data. Typically, applications can use IPC, categorized as clients and servers, where the client requests data and the server responds to client requests. Many applications are both clients and servers, as commonly seen in distributed computing.
In computing, a directory service or name service maps the names of network resources to their respective network addresses. It is a shared information infrastructure for locating, managing, administering and organizing everyday items and network resources, which can include volumes, folders, files, printers, users, groups, devices, telephone numbers and other objects. A directory service is a critical component of a network operating system. A directory server or name server is a server which provides such a service. Each resource on the network is considered an object by the directory server. Information about a particular resource is stored as a collection of attributes associated with that resource or object.
X.400 is a suite of ITU-T recommendations that define the ITU-T Message Handling System (MHS).
Messaging Application Programming Interface (MAPI) is an API for Microsoft Windows which allows programs to become email-aware. While MAPI is designed to be independent of the protocol, it is usually used to communicate with Microsoft Exchange Server.
Microsoft Exchange Server is a mail server and calendaring server developed by Microsoft. It runs exclusively on Windows Server operating systems.
Microsoft Mail was the name given to several early Microsoft e-mail products for local area networks, primarily two architectures: one for Macintosh networks, and one for PC architecture-based LANs. All were eventually replaced by the Exchange and Outlook product lines.
NIS+ is a directory service developed by Sun Microsystems to replace its older 'NIS'. It is designed to eliminate the need for duplication across many computers of configuration data such as user accounts, host names and addresses, printer information and NFS disk mounts on individual systems, instead using a central repository on a master server, simplifying system administration. NIS+ client software has been ported to other Unix and Unix-like platforms.
Kolab is a free and open source groupware suite. It consists of the Kolab server and a wide variety of Kolab clients, including KDE PIM-Suite Kontact, Roundcube web frontend, Mozilla Thunderbird and Mozilla Lightning with SyncKolab extension and Microsoft Outlook with proprietary Kolab-Connector PlugIns.
Distributed File System (DFS) is a set of client and server services that allow an organization using Microsoft Windows servers to organize many distributed SMB file shares into a distributed file system. DFS has two components to its service: Location transparency and Redundancy. Together, these components enable data availability in the case of failure or heavy load by allowing shares in multiple different locations to be logically grouped under one folder, the "DFS root".
Microsoft RPC is a modified version of DCE/RPC. Additions include partial support for UCS-2 strings, implicit handles, and complex calculations in the variable-length string and structure paradigms already present in DCE/RPC.
XML Enabled Directory (XED) is a framework for managing objects represented using the Extensible Markup Language (XML). XED builds on X.500 and LDAP directory services technologies.
The Directory Assistance Service (DAS) is an obsolete protocol and service for accessing X.500 directory services. DAS was intended to provide a lightweight means for clients to access X.500 directory services via a split-Directory User Agent model. Here, the Directory User Agent (DUA) is split into a Directory Assistance (DA) client and a Directory Assistant. The directory user would interact with the DA-client, the DA-Client would communicate with the Directory Assistant using the DA protocol, and the Directory Assistant would communicate with the Directory Service using the X.500 Directory Access Protocol (DAP). That is, the Directory Assistant is a Directory Assistance protocol to DAP gateway. This design allows the DA-client to access the directory without requiring it to support the cumbersome Open Systems Interconnection protocol stack.
The first release of Microsoft Exchange Server was version 4.0 in April 1996, when it was sold as an upgrade to Microsoft Mail 3.5. Before that, Microsoft Mail v2.0 was replaced in 1991 by "Microsoft Mail for PC Networks v2.1", based on Network Courier from its acquisition of Consumers Software. Exchange Server was an entirely new X.400-based client–server mail system with a single database store that also supported X.500 directory services. During its development, Microsoft migrated their own internal email from a XENIX-based system to Exchange Server from April 1993, with all 32,000 Microsoft mailboxes on Exchange by late 1996. The directory used by Exchange Server eventually became Microsoft's Active Directory service, an LDAP-compliant directory service. Active Directory was integrated into Windows 2000 as the foundation of Windows Server domains.
Kopano is an open-source groupware application suite originally based on Zarafa. The initial version of Kopano Core (KC) was forked from the then-current release of Zarafa Collaboration Platform, and superseded ZCP in terms of lineage as ZCP switched to maintenance mode with patches flowing from KC. Kopano WebApp similarly descended from Zarafa WebApp. Since October 2017, Kopano Core is also known more specifically as Kopano Groupware Core, since Kopano B.V. developed more products that were not directly requiring groupware components.
References
- ↑ Daniel Blum (1989-10-30). "Details of X.500 architecture". Network World. IDG Network World Inc. 6 (43): 58. ISSN 0887-7661.
- ↑ Zahir Tari and Omran Bukhres (2001). Fundamentals of distributed object systems: the CORBA perspective. Parallel and distributed computing. Vol. 8. John Wiley and Sons. p. 219. ISBN 978-0-471-35198-6.
- ↑ "X.500: Directory Access Protocol (DAP)". Javvin Technologies, Inc. Archived from the original on 2005-11-23. Retrieved 2005-09-22.
- 1 2 3 4 5 6 "Platform SDK: Active Directory: Directory System Agent". MSDN . Microsoft. Archived from the original on 2005-05-27. Retrieved 2005-09-22.
- 1 2 3 4 5 6 "Active Directory: Active Directory Diagnostics, Troubleshooting, and Recovery: Summary of Active Directory Architecture: Directory System Agent". Windows 2000 Server Resource Kit. Microsoft . Retrieved 2010-10-02.
