Electrical computers and digital processing systems: multicomput – Computer network managing – Network resource allocating
Reexamination Certificate
1998-10-19
2001-04-10
Sheikh, Ayaz (Department: 2155)
Electrical computers and digital processing systems: multicomput
Computer network managing
Network resource allocating
C709S223000
Reexamination Certificate
active
06216162
ABSTRACT:
BACKGROUND OF THE INVENTION
1. Technical Field
The present invention relates generally to computer networks and more particularly to the creation and access of resources in a server network which consists of a central server and a set of managed servers running native and non-native operating systems by the creation of an alias which is extendable across a heterogeneous server network.
2. Description of the Related Art
The client-server model of computing is a well-known environment. In the model, the user of a computer utilizes a “client” system. The client system runs any of a number of computer operating systems to manage the basic functions that users execute (such as accessing files, executing programs, system administration and the like) as well as to serve as the base against which programs are written. Well-known client operating systems include Microsoft Windows 3.1, Windows for Workgroups, Windows 95, Windows 98, IBM® OS/2® Warp, Apple Macintosh, DOS, many variations of UNIX, and Microsoft Windows NT. The client system serves as the user's workstation, and it may execute programs as well as store some user data.
The server system can also run any of a number of computer operating systems. Well-known server operating systems include Novell Netware, IBM OS/2 Warp Server, IBM AS/400®, Microsoft Windows NT, and many variations of OSF UNIX. The server system is accessed by the client system for specific functions. The functions include, but are not limited to, storage and retrieval of data, storage and execution of applications, and storage of and access to user information.
Server networks are increasingly becoming heterogeneous due to differing problems that can be solved by different servers. User management in these environments requires the creation of different user accounts on the different types of servers. These user accounts eventually have different passwords and possibly different user I.D.'s. A mechanism is needed to allow a single user account definition to be used as the base for any additional user accounts that exist in the network. The mechanism needs to go beyond current technology options and allow the accounts on all servers to be continuously updated. As the user accounts become common across the network of servers, a mechanism is needed to easily refer to the access resources that exist within the heterogeneous set of servers.
A common term used to refer to a network of related servers is a domain. Within the server domain is a central server acting as the primary domain controller and a plurality of “managed” servers sometimes called secondary servers. Industry standards have been developed (for critical and common functions) to aid in the access from different types of client systems to different types of server systems. The use of these standards on the client and server afford users the opportunity to carry out functions in a consistent manner on a variety of common client and server operating systems. One of the activities that has been standardized is the “authentication” of users. Authentication refers to the process in which a user is validated as being able to complete a log-on and/or access a system. Standard protocols have been defined within the X/Open Server Message Block (SMB) specification and the Open systems Foundation (OSF) Distributed Computing Environment (DCE) specification.
While many products and operating systems have been developed that utilize the standard protocols, not all products have used the standards. When this occurs, either additional work must be done by the other operating system to implement the unique commands used by a vendor, or access to the other new system and/or product is not allowed if the unique commands are not made available to other vendors. When the commands and/or protocol are not made available, that aspect of the system and/or product is sometimes characterized as being “closed”. In regards to user management and authentication, the Microsoft Windows NT operating system is becoming an example of a closed server system that is used in many enterprise computer networks.
The creation and access of network shared resources by multiple users in a multiple server environment is a concern for both system administrators and users. The universal naming convention (UNC) names are a common mechanism used to define and seek resources in a server environment. A shortened, and more simplified naming convention that is used in many homogeneous server environments is often called an “alias.” The present invention extends the alias concept to a heterogeneous server environment and dynamically keeps all servers within the domain synchronized as new aliases are created or existing aliases are changed as users are given access to resources
defined by aliases and as users utilize aliases to connect to network shared resources.
SUMMARY OF THE INVENTION
It is a general object of this invention to provide a user-friendly access to resources across a heterogeneous server network.
It is a more specific object to provide for the creation and access of resources from a central server to a managed server within a heterogeneous server network.
A still more specific object of the invention is to allow an IBM OS/2 Warp Server acting as a primary domain controller to define aliases that point to a resource field held at a managed Microsoft Windows NT server.
These and other objects, features and advantages are provided by a method of creating and accessing network shared resources based upon a simplified alias name versus the full universal naming convention name. A system administrator logging on with administrator privileges on a central server displays a management screen. The initial creation of aliases is done at the central server according to various rules. Access to the server where targeted stored resources exist is made. A determination of the type of target server is made and the appropriate request mechanism to create a network shared resource is made. The alias definition on the central server then corresponds to the targeted server store and any user request to use the resource is based upon the alias name. At any time, the system administrator may update the actual location of the network shared resource without user notification or intervention,
REFERENCES:
patent: 4718005 (1988-01-01), Feigenbaum et al.
patent: 5434974 (1995-07-01), Loucks et al.
patent: 5535375 (1996-07-01), Eshel et al.
patent: 5627996 (1997-05-01), Bauer
patent: 5745888 (1998-04-01), Bauer et al.
patent: 5745902 (1998-04-01), Miller et al.
patent: 5764906 (1998-06-01), Edelstein et al.
patent: 0578205 A2 (1994-01-01), None
patent: 0821309 A1 (1996-02-01), None
Dutcher David Paul
Sinclair, Jr. William H.
Smith Stanley Alan
International Business Machines Corp.
LaBaw Jeffrey S.
Sheikh Ayaz
Venable
Winder Patrice
LandOfFree
Extending alias support to heterogeneous servers does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Extending alias support to heterogeneous servers, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Extending alias support to heterogeneous servers will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-2494419