[go: up one dir, main page]

WO2002021332A2 - Systeme et procede de gestion centralisee d'utilisateurs et authentification, autorisations et comptabilite bases sur des services de repertoires et des protocoles centraux - Google Patents

Systeme et procede de gestion centralisee d'utilisateurs et authentification, autorisations et comptabilite bases sur des services de repertoires et des protocoles centraux Download PDF

Info

Publication number
WO2002021332A2
WO2002021332A2 PCT/IL2001/000849 IL0100849W WO0221332A2 WO 2002021332 A2 WO2002021332 A2 WO 2002021332A2 IL 0100849 W IL0100849 W IL 0100849W WO 0221332 A2 WO0221332 A2 WO 0221332A2
Authority
WO
WIPO (PCT)
Prior art keywords
operating system
directory
nis
information
server
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/IL2001/000849
Other languages
English (en)
Other versions
WO2002021332A3 (fr
Inventor
Ilan Meller
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Individual
Original Assignee
Individual
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Individual filed Critical Individual
Priority to AU2001290217A priority Critical patent/AU2001290217A1/en
Publication of WO2002021332A2 publication Critical patent/WO2002021332A2/fr
Anticipated expiration legal-status Critical
Publication of WO2002021332A3 publication Critical patent/WO2002021332A3/fr
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25—Integrating or interfacing systems involving database management systems
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/17—Details of further file system functions
    • G06F16/178—Techniques for file synchronisation in file systems
    • G06F16/1794—Details of file format conversion

Definitions

  • the present invention relates to a system and a method for central management of directory services, and in particular, to such a system and method for management of information related to directory services, such as information concerning hosts, user groups and individual users, across a plurality of operating systems.
  • a more useful solution would enable such new and/or changed information to be automatically mirrored to all databases, particularly between databases being controlled by NIS and those controlled by Active DirectoryTM. Furthermore, such a solution should enable a heterogeneous network to be managed through Active DirectoryTM. Unfortunately, such a solution is not currently available.
  • the background art does not teach or suggest a system and a method for enabling information related to directory services to be automatically mirrored between databases controlled by different software services provided by different operating systems.
  • the background art also particularly does not teach such a system and method in order to provide central management of directory services in a heterogeneous network through Active DirectoryTM.
  • the present invention overcomes these deficiencies of the background art by providing a system and a method for automatically managing directory services across different operating systems, in order for such directory services to be managed centrally.
  • the present invention supports the management of directory services through Active DirectoryTM for computers operating according to a different operating system, which is more preferably the UNIX operating system.
  • the UNIX operating system provides such services through NIS.
  • the system and method of the present invention enable databases associated with Active DirectoryTM and NIS to be managed at a single central administration facility, such that a single management tool can be used to manage a heterogeneous network.
  • the present invention also enables the various utilities and tools available through NIS and Active DirectoryTM to be controlled through the GUI (graphic user interface) of Active DirectoryTM, thereby providing a more complete set of management features to the system administrator.
  • an implementation of the services of NIS is provided on a computational device being operated according to the
  • This computational device is a server on a heterogeneous network which includes both computational devices with UNIX and computational devices with the WindowsTM operating system.
  • the server of the present invention is able to both respond to requests for NIS services from UNIX-operated computational devices, and to read from, and write to, a database controlled by Active DirectoryTM.
  • directory services for the heterogeneous network are controlled through Active DirectoryTM.
  • the system administrator is able to manage these directory services for the entire network through the GUI (graphical user interface) for Active DirectoryTM, such as MMC for example.
  • the present invention enables all of the directory services information to be stored at a central database, most preferably- the Active DirectoryTM database, yet to be provided to computational devices on the heterogeneous network according to requests from both NIS and Active DirectoryTM processes.
  • a central database most preferably- the Active DirectoryTM database
  • such an implementation is provided by simulating NIS server services through a server which is operated according to the Windows 2000TM, or other similar operating system, rather than according to the Unix operating system.
  • these services are preferably provided through the WindowsTM directory service, rather than accessing data which is stored in flat files as for the existing NIS servers. Therefore, the services of the second operating system (in this example UNIX) are provided through the operation of a server according to the first operating system (in this example a WindowsTM operating system).
  • WindowsTM includes but is not limited to any operating systems by Microsoft Corp. (USA) or any similar operating systems.
  • UNIX refers to any UNIX-compliant operating system.
  • a software application could be written in substantially any suitable programming language, which could easily be selected by one of ordinary skill in the art.
  • the programming language chosen should be compatible with the computational device according to which the software application is executed. Examples of suitable programming languages include, but are not limited to, C, C++ and Java.
  • the present invention could be implemented as software, firmware or hardware, or as a combination thereof. For any of these implementations, the functional steps performed by the method could be described as a plurality of instructions performed by a data processor.
  • FIG 1. is a schematic block diagram of a background art NIS system
  • FIG. 2 is a schematic block diagram of a system according to the present invention, for communication between NIS and Active DirectoryTM processes.
  • the present invention is of a system and a method for automatically managing directory services across different operating systems, in order for such directory services to be managed centrally.
  • the present invention supports the management of directory services through Active DirectoryTM for computers operating according to a different operating system, which is more preferably the UNIX operating system.
  • the latter system provides such services through NIS.
  • the system and method of the present invention enable databases associated with Active DirectoryTM and NIS to be managed at a single central administration facility, such that a single management tool can be used to manage a heterogeneous network.
  • the present invention also enables the various utilities and tools available through NIS and Active DirectoryTM to be controlled through the GUI (graphic user interface) of Active DirectoryTM, thereby providing a more complete set of management features to the system administrator.
  • NIS Network Information Service
  • maps which are collections of entries. Each entry has a key and data.
  • the NIS protocol enables several basic, read only, operations on maps. These operations include retrieving the data of an entry identified by a key (match), retrieving the data of a map (all), etc.
  • Unix computers through the NIS client process (ypbind), perform such operations on the data by connecting to the NIS servers (machines running the ypserv process). For a plurality of servers, one of the NIS servers is defined as the NIS master, while the other servers are referred to as NIS slaves. NIS slaves retain a copy of the information, as it is kept on the NIS master, to be used as mirrored data for NIS client requests.
  • the information contained in the NIS maps can be updated only by the NIS master. After such an update the NIS master performs a process called a push, a process of populating the updated map information to all the other NIS servers (the NIS slaves).
  • the present invention is able to simulate an NIS master for the NIS clients and an LDAP client for the ActiveDirectoryTM clients. Therefore, NIS client machines may optionally be configured as clients of the server according to the present invention (shown as the "master environment" below).
  • NIS client machines may optionally be configured as clients of the server according to the present invention (shown as the "master environment" below).
  • Active DirectoryTM services rely upon the provision of objects, stored according to a hierarchical structure. These objects contain the necessary data to provide the directory services, and feature a unique name, composed of the relative name of the object and the path to that object from the top level. Each object has a set of attributes; each attribute may have several values.
  • the directory services themselves are structured as a network databasej which is not contained on a single server, but instead may "float" on the network by being stored in pieces on several different servers.
  • Lightweight Directory Access Protocol (LDAP) is one example of a standard protocol which is used to query the directory. Therefore, the present invention may also optionally be viewed as providing a mechanism for converting data stored according to one type of structure, such as the "flat" collection of entries, each of which has a key and data, for NIS protocol, to a second type of data structure, such as the hierarchical collection of objects of the ActiveDirectoryTM format.
  • the mechanism of the present invention also enables such data to be managed through the second type of services, while still supporting the actions of clients for the first type of services and architecture (in this case NIS clients).
  • an implementation of the services of NIS is provided on a computational device being operated according to the WindowsTM operating system.
  • This computational device is a server on a heterogeneous network which includes both computational devices with UNIX and computational devices with the WindowsTM operating system.
  • the server of the present invention is able to both respond to requests for NIS services from UNIX-operated computational devices, and to read from, and write to, a database controlled by Active DirectoryTM.
  • directory services for the heterogeneous network are controlled through Active DirectoryTM.
  • the system administrator is able to manage these directory services for the entire network through the GUI (graphical user interface) for Active DirectoryTM, such as MMC for example.
  • the present invention enables all of the directory services information to be stored at a central database, most preferably the Active DirectoryTM database, yet to be provided to computational devices on the heterogeneous network according to requests from both NIS and Active DirectoryTM clients.
  • the server which operates the NIS processes through the WindowsTM operating system is also able to operate a software module for automatically collecting information from computational devices on the heterogeneous network. More preferably, this software module is able to collect such information from NIS databases, thereby enabling the central Active DirectoryTM database to be constructed and/or updated with information from these databases. Optionally and most preferably, this software module is able to both collect this information from NIS databases for updating the central Active DirectoryTM database, and to update the NIS databases according to information entered into the central Active DirectoryTM database.
  • Figure 1 shows a background NIS system 10 for managing directory services for the UNIX operating system.
  • Directory services are generally implemented by organizations in order to centralize the management of user information, including user names and passwords, directory permissions, the operation of applications, and other elements of the system.
  • System 10 employs a source file 12 at a master server 14, which is the master server for controlling directory services.
  • Source file 12 contains user information, such as the previously described user name and password.
  • Source file 12 is turned into a binary file 16 for actual access, for example in order to check if the password which the user has entered is correct.
  • Binary file 16 actually contains a map of the directory information, such as the previously described user information. If the user or system administrator wants to change user information, such as the password of the user for example, the user or system administrator needs to operate a yppassword process 18 at a ypclient computational device 20, which in turn communicates the new password information to a rpc.yppassword daemon 22.
  • Rpc.yppassword daemon 22 in turn sends the information to a pwupdate process 24, to update binary file 16 at master server 14.
  • Binary file 16 may be mirrored as a binary file 26 at a slave server 28, which is a slave server controlled by master server 14. Slave server 28 is used in order to increase the scalability of the system. If source file 12 is updated at master server 14, one of two processes may be employed in order to change binary file 16 at master server 14, and also binary file 26 at slave server 28. The first such process involves the "make" command, and hence a make process 30, in order to completely recreate binary file 16; however, for incremental changes, such as changing a single password for example, pwupdate process 24 is used to update binary file 16 with the new information.
  • the changes to binary file 16 at master server 14 are then propagated to binary file 26 at slave server 28 through a ypxfrd process 32, which communicates with a ypxfr process 34 at slave server 28 to change binary file 26.
  • binary file 26 at slave server 28 is updated through ypxfrd 32 and ypxfr 34 processes.
  • Yppush 36 is activated and sends a command to ypserv process 40 at slave server 28 to refresh itself.
  • Ypserv process 40 then creates a new process, ypxfr process 34 in order to permit ypserv process 40 to continue serving other clients.
  • Ypxfr process 34 requests the entire binary file 26 from ypxfrd process 32, such that binary file 26 is then received.
  • Another method is to optionally retrieve the map record by record through the ypserv process on master server 14.
  • Yppush process 36 then receives a message from ypxfr process 34 indicating that the make process is complete.
  • a ypbind process 38 is used by the client. This process then communicates with ypserv process 40, in order to retrieve the information from binary file 26 at slave server 28 or from binary files 16 at master server 14.
  • ypserv process 40 communicates with ypserv process 40, in order to retrieve the information from binary file 26 at slave server 28 or from binary files 16 at master server 14.
  • the background art system of Figure 1 does not permit communication between the NIS processes and the processes of Active DirectoryTM.
  • the background art system of Figure 1 does not enable directory services information to be managed centrally through Active DirectoryTM, nor does this system enable NIS processes to retrieve information from a database controlled through Active DirectoryTM. Such communication between these different processes and central management of directory services is enabled by the system of the present invention, as shown in Figure 2.
  • the master environment provides an implementation of NIS processes through a WindowsTM operating system. It should be noted that optionally system 50 may only be implemented with the master environment; alternatively, as described in greater detail below, a slave environment may also optionally be provided.
  • a directory process 58 represents the Active DirectoryTM process, which is known in the art and which contains an equivalent to the maps of the NIS system of Figure 1, for holding the directory information such as the previously described user information.
  • Information may optionally be placed into directory process 58 through the regular activity of the Active DirectoryTM process.
  • information may also be inserted through a build process 56.
  • Build process 56 preferably reads directory information, such as user information for example, from a source file 54 which as previously described, holds such information for NIS (UNIX) based directory services.
  • Build process 56 therefore enables information from sources external to the Active DirectoryTM format to be incorporated and used for the Active DirectoryTM process of directory services.
  • information may optionally be read from a database 52, for example in order to convert information to the Active DirectoryTM format from a different type of operating system format.
  • Build process 56 is preferably assisted by information stored in one or more configuration and transformation files 57, which enable the information formatted according to the different (non- Active DirectoryTM type) operating system format to be translated into the Active DirectoryTM format.
  • the operation of build process 56 may optionally be divided into four stages, in which the first stage describes the source of the information itself (IP address, type of protocol to be used, username, password and so forth; the username and password in this case are for accessing the source of information).
  • the second stage describes the query to be performed on the source of information, optionally with such object parameters as search paths, description of objects to be retrieved and so forth.
  • the third stage is the transformation stage, for describing how to manipulate objects retrieved through the query of one type, such as NIS clients, in order to convert them into a format for clients being operated according to the second type of operating system (such as Active DirectoryTM queries); and the last stage describes the actual data structures being created, such as data in the Active DirectoryTM format for example.
  • Information may also optionally be entered through a standard WindowsTM management client 59, operating according to some version of the WindowsTM operating system. Such a WindowsTM management client 59 would typically enable directory-type information to be entered through a standard directory GUI (graphical user interface) 61, as is known in the art.
  • Simplement service 60 When new information, such as a new or changed user password, is sent to directory process 58, preferably several processes are triggered. The receipt of new or changed information by directory process 58 also triggers the activation of a Mother service 60 according to the present invention.
  • Simplement service 60 optionally and preferably communicates with directory process 58 according to a protocol such as the LDAP (lightweight directory access protocol) specification.
  • Simplement service 60 preferably receives information for building the maps which contain the user information from configuration and transformation files 57.
  • Configuration and transformation files 57 also preferably contain the necessary information which enables Sea service 60 to transform information in the Active DirectoryTM format to the NIS map format, in a similar but opposite manner to that described previously for build process 56.
  • the trigger of possibly service 60 is preferably performed through a trigger process 62.
  • Trigger process 62 may optionally poll directory process 58 regularly in order to receive the new information.
  • Trigger process 62 may optionally also be triggered by a new version of a yppush process 64 according to the present invention.
  • yppush process 64 could be manually activated, similar to the "make" process of Figure 1.
  • Yppush process 64 preferably causes trigger process 62 to refresh system 50, in order to accept new and/or changed information, for example.
  • Simplement service 60 also preferably contains new versions of ypxfrd process 66, yppasswd process 68 and ypserv process 70, which retain certain functionality from the equivalent versions of these processes from the background art NIS system, but which are preferably operated according to the WindowsTM operating system as shown for the purposes of this example.
  • Yppasswd process 18 preferably communicates with new yppasswd process 68 in order to perform the equivalent updating processes for Active DirectoryTM directory services. The information is then passed to directory process 58, for storage according to the Active DirectoryTM format.
  • the user can enter the new password through the background art yppasswd process 18 of the UNIX client environment, which in this example is shown as being operated by a UNIX client 71.
  • Yppasswd process 18 then communicates with yppasswd process 68 of Possible service 60.
  • the new information is then provided to directory process 58, for storage in the Active DirectoryTM format. More preferably, however, management of the heterogeneous network is provided through Active DirectoryTM, and in particular through standard directory GUI 61.
  • a slave server 74 is optionally present, but is not necessary. If present, a ypbind process 38 at UNIX client 71 may optionally communicate with either the master environment (simplement service 60) or alternatively may communicate with a ypserv process 40 of slave server 74. As shown for the purposes of this example, slave server 74 is optionally a UNIX-type server. If ypserv process 40 receives the command from new yppush process 64, then ypserv process 40 preferably generates a new ypxfr process 34 of slave server 74.
  • Ypxfr process 34 may optionally and preferably communicate with ypxfrd process 66 of possibly service 60 (through the arrow shown as "new"), which is equivalent to the process for NIS in which the NIS maps are transferred directly as binary files through ypxfrd.
  • ypxfr process 34 may communicate with ypserv process 70 of possibly service 60 (through the arrow shown as "old"), which is equivalent to the original process for map transfer through the NIS protocol, in which the map data is transferred record by record.
  • ypxfr process 34 preferably sends a response to yppush 64 (through the arrow marked as "response").
  • Directory services information can be requested either from the WindowsTM environment, for example from a standard directory services GUI 61, or from the UNIX environment, through ypbind process 38.
  • Standard directory services GUI 61 would communicate with directory process 58 of the master server, as both are operated according to the WindowsTM operating system.
  • ypbind 38 can receive the necessary information from the new ypserv process 70 of Published service 60, and/or from the actual ypserv process 40 of slave server 74, without requiring any modification of ypbind process 38.
  • each map contains objects which have an attribute, such as "name”, and a value, such as "John". If a query for the value of a particular object is sent from the NIS system client of UNIX to the Mother service at the master server, then optionally and preferably the query is answered by using the NIS map information, which is more preferably contained in memory.
  • the query itself is translated by the Of DirectoryTM format query, for example by a process of symbolic substitution. For example, if a request is made in which the user name is the key for retrieving information, then the retrieved account name forms the initial part of the translated query, followed by the necessary data fields such as the user password and group name in the correct formatting.
  • management of the directory services for this heterogeneous network is provided through Active DirectoryTM. More preferably, management is provided through standard directory GUI 61 for managing Active DirectoryTM.
  • An example of such a GUI is the MMC GUI (Microsoft Corp.). Therefore, the system administrator is able to manage both Active DirectoryTM and NIS processes and information through MMC. For example, the system administrator is preferably able to update user passwords and other user information for both NIS and Active DirectoryTM through MMC.
  • this preferred embodiment of the present invention supports the employment of a single Active DirectoryTM database for storing all directory services information in the heterogeneous network. This database is then managed through MMC.
  • system 50 has been described with regard to communication between the UNIX and WindowsTM operating systems for directory services, this is intended as an example only and is without any intention of being limiting.
  • protocols which can optionally be supported by the present invention across different operating systems include, but are not limited to, FTP (file transfer protocol) and RADIUS (an authentication protocol for users who use a telephony modem to connect to a server from remote sites).
  • the present invention is optionally and preferably used to support a central authentication system which would enable all of these protocols to be managed from a central interface.
  • each of these authentication systems has a separate database and separate authentication mechanism, which increases the difficulty of managing such systems, particularly in a heterogeneous networking environment.
  • the present invention is not limited to regular computational environments, but could also optionally be used with cellular telephones, for example for authentication through WAP (wireless application protocol).
  • WAP wireless application protocol
  • the present invention could also optionally be extended to central management of such services as accounting and billing administration, for example, or license administration, as another example.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Stored Programmes (AREA)

Abstract

L'invention porte sur un système et un procédé de gestion et synchronisation automatiques des services de répertoires par l'intermédiaire de différents systèmes d'exploitation permettant de centraliser la gestion desdits services. L'invention assure de préférence la gestion des services de répertoires par l'intermédiaire d'Active DirectoryTM et de NIS, et à l'aide d'un ordinateur tournant sous UNIX et fournissant de tels services par l'intermédiaire de NIS. Le système et le procédé de l'invention permettent de gérer les bases de données associées à Active DirectoryTM et à NIS depuis une seule installation centrale, et de n'utiliser qu'un seul outil de gestion pour gérer un réseau hétérogène. L'invention permet également de commander les différentes facilités et outils disponibles sur NIS et d'Active DirectoryTM à l'aide de l'interface graphique d'Active DirectoryTM (MMC ou console de gestion de MicrosoftTM), ce qui donne à l'administrateur du système un ensemble plus complet de possibilités de gestion.
PCT/IL2001/000849 2000-09-07 2001-09-07 Systeme et procede de gestion centralisee d'utilisateurs et authentification, autorisations et comptabilite bases sur des services de repertoires et des protocoles centraux Ceased WO2002021332A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2001290217A AU2001290217A1 (en) 2000-09-07 2001-09-07 System and method for central user management and authentication, authorization and accounting based on directory services and standard protocols

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US23070600P 2000-09-07 2000-09-07
US60/230,706 2000-09-07

Publications (2)

Publication Number Publication Date
WO2002021332A2 true WO2002021332A2 (fr) 2002-03-14
WO2002021332A3 WO2002021332A3 (fr) 2003-11-06

Family

ID=22866249

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IL2001/000849 Ceased WO2002021332A2 (fr) 2000-09-07 2001-09-07 Systeme et procede de gestion centralisee d'utilisateurs et authentification, autorisations et comptabilite bases sur des services de repertoires et des protocoles centraux

Country Status (2)

Country Link
AU (1) AU2001290217A1 (fr)
WO (1) WO2002021332A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109241214A (zh) * 2018-07-27 2019-01-18 珠海国津软件科技有限公司 一种根据服务目录形成服务地图成图方法

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6108649A (en) * 1998-03-03 2000-08-22 Novell, Inc. Method and system for supplanting a first name base with a second name base

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109241214A (zh) * 2018-07-27 2019-01-18 珠海国津软件科技有限公司 一种根据服务目录形成服务地图成图方法
CN109241214B (zh) * 2018-07-27 2021-09-10 珠海国津软件科技有限公司 一种根据服务目录形成服务地图成图方法

Also Published As

Publication number Publication date
WO2002021332A3 (fr) 2003-11-06
AU2001290217A1 (en) 2002-03-22

Similar Documents

Publication Publication Date Title
US6920455B1 (en) Mechanism and method for managing service-specified data in a profile service
EP0720091B1 (fr) Gestion de jetons à plusieurs niveaux pour des systèmes de fichiers distribués
US7035931B1 (en) Volume location service for a distributed file system
JP4771321B2 (ja) データをジャバ・システム・データベース・エントリ及びｌｄａｐディレクトリ・サービスの間で交換するための方法及びデータ・フォーマット
CN101563686B (zh) 在目录服务中的动态拓扑改变的自动发现和重新配置
US7693962B2 (en) Method and system for seamlessly accessing remotely stored files
US6553368B2 (en) Network directory access mechanism
US7441007B1 (en) System and method for allowing applications to retrieve properties and configuration information from a persistent store
CN100547589C (zh) 用于处理搜索查询的方法和系统
US20090248737A1 (en) Computing environment representation
US7409397B2 (en) Supporting replication among a plurality of file operation servers
US20030130984A1 (en) System and methods for asynchronous synchronization
US20020032775A1 (en) System and method for transmitting and retrieving data via a distributed persistence framework
EP1701280B1 (fr) Serveur de fichiers et procédé pour la traduction des identifiants d'utilisateur
CN102239476A (zh) 用于存储集群的共享名称空间
EP2780839A1 (fr) Systèmes et procédés pour l'intégration de services dynamique
US8380806B2 (en) System and method for absolute path discovery by a storage virtualization system
US7167867B1 (en) Self-describing file system
CA2559819C (fr) Systeme mandataire d'adaptation de base de donnees de ldap a sql et methode connexe
US20070005555A1 (en) Method and mechanism for supporting virtual content in performing file operations at a RDBMS
WO2002021332A2 (fr) Systeme et procede de gestion centralisee d'utilisateurs et authentification, autorisations et comptabilite bases sur des services de repertoires et des protocoles centraux
JP4492569B2 (ja) ファイル操作制御装置、ファイル操作制御システム、ファイル操作制御方法及びファイル操作制御プログラム
US7836084B1 (en) Central database routing for distributed applications
JP2002049641A (ja) 複数プロファイル管理装置，管理方法，複数プロファイル管理用プログラム記録媒体および複数プロファイル管理用プログラム
KR20020004060A (ko) 데이터 베이스 관리방법 및 그에 따른 시스템

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ CZ DE DE DK DK DM DZ EC EE EE ES FI FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PH PL PT RO RU SD SE SG SI SK SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP