Data processing: database and file management or data structures – Database design – Data structure types
Reexamination Certificate
2000-12-14
2004-04-06
Amsbury, Wayne (Department: 2171)
Data processing: database and file management or data structures
Database design
Data structure types
C709S219000
Reexamination Certificate
active
06718331
ABSTRACT:
BACKGROUND OF THE INVENTION
1. Technical Field
The present invention relates to enterprise resources and, in particular, to accessing resources with disparate sources and technologies. Still more particularly, the present invention provides a method, apparatus, and program for locating inter-enterprise resources using text-based strings.
2. Description of Related Art
Enterprise Java Beans (EJB) is a component software architecture from Sun that is used to build Java applications that run in a server. EJB uses a “container” layer that provides common functions such as security and transaction support and delivers a consistent interface to applications regardless of the type of server. Components are program modules that are designed to interoperate with each other at runtime. Components may be written by different programmers using different development environments and they may or may not be platform independent. Components can be run in stand-alone machines, on a LAN, intranet or the Internet.
The terms component and object are used synonymously. Component architectures have risen out of object-oriented technologies, but the degree to which they comply to all the rules of object technology is often debated. Component architectures may use a client/component model, in which the client application is designed as the container that holds other components or objects. The client container is responsible for the user interface and coordinating mouse clicks and other inputs to all the components. A pure object model does not require a container. Any object can call any other without a prescribed hierarchy.
Common Object Request Broker Architecture (CORBA) defines the communication protocols and datatype mappings for EJBs. CORBA is a standard from the Object Management Group (OMG) for communicating between distributed objects. CORBA provides a way to execute programs (objects) written in different programming languages running on different platforms no matter where they reside in the network. Technically, CORBA is the communications component of the Object Management Architecture (OMA), which defines other elements such as naming services, security service, and transaction services.
A naming service is software that converts a name into a physical address on a network, providing logical to physical conversion. Names can be user names, computers, printers, services, or files. The transmitting station sends a name to the server containing the naming service software, which sends back the actual address of the user or resource. The process is known as name resolution. A naming service functions as a White Pages for the network.
CORBA defines an Inter-ORB-reference (IOR), which may be externalized as a text string; however, an IOR is not human-readable or interpretable and applies only to CORBA objects. Microsoft Component Object Model (COM), which defines a structure for building program routines that can be called up and executed in a Windows™ environment, defines a moniker as a generalized resource handle that can be externalized as human readable. However, monikers require binding to the resource and apply only to COM objects. The prior art fails to provide a standard method for identifying and accessing resources across technologies, such as EJB, CORBA, and COM.
Therefore, it would be advantageous to provide a method, apparatus, and program for locating inter-enterprise resources using human readable text-based strings.
SUMMARY OF THE INVENTION
The present invention provides a standard format for a text string called an enterprise identifier, which acts as a handle to access resources from disparate sources and technologies. Enterprise identifiers use extensible markup language (XML) format to allow a resource identifier to be created manually without accessing the resource. The identifier may be easily passed between enterprises via business-to-business connection, e-mail, telephone, or facsimile. Data may be extracted from the identifier for display or programmatic use without accessing the resource, thus avoiding unnecessary data access and transfer.
REFERENCES:
patent: 5860072 (1999-01-01), Schofield
patent: 5878219 (1999-03-01), Vance et al.
patent: 5964891 (1999-10-01), Caswell et al.
patent: 5987247 (1999-11-01), Lau
patent: 5987471 (1999-11-01), Bodine et al.
patent: 5999944 (1999-12-01), Lipkin
patent: 6023578 (2000-02-01), Birsan et al.
patent: 6064977 (2000-05-01), Haverstock et al.
patent: 6094649 (2000-07-01), Bowen et al.
patent: 6101537 (2000-08-01), Edelstein et al.
patent: 6125400 (2000-09-01), Cohen et al.
patent: 6185598 (2001-02-01), Farber et al.
patent: 6212556 (2001-04-01), Arunachalam
patent: 6222533 (2001-04-01), Notani et al.
patent: 6338082 (2002-01-01), Schneider
patent: 6339423 (2002-01-01), Sampson et al.
patent: 6348927 (2002-02-01), Lipkin
patent: 6496867 (2002-12-01), Beser et al.
patent: 2002/0161745 (2002-10-01), Call
Davis Nathan Eugene
Herman Peter W.
Amsbury Wayne
Bailey Wayne P.
International Business Machines - Corporation
Mims Jr. David A.
Nguyen Cam-Linh
LandOfFree
Method and apparatus for locating inter-enterprise resources... does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Method and apparatus for locating inter-enterprise resources..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Method and apparatus for locating inter-enterprise resources... will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-3264419