US20040249926A1 - System and methd for common information model object manager proxy interface and management - Google Patents
System and methd for common information model object manager proxy interface and management Download PDFInfo
- Publication number
- US20040249926A1 US20040249926A1 US10/882,508 US88250804A US2004249926A1 US 20040249926 A1 US20040249926 A1 US 20040249926A1 US 88250804 A US88250804 A US 88250804A US 2004249926 A1 US2004249926 A1 US 2004249926A1
- Authority
- US
- United States
- Prior art keywords
- information
- object manager
- remote
- information provider
- transmitting
- 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.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/563—Data redirection of data network streams
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
Definitions
- the invention relates to a system and method for common information model object manager (CIMOM) proxy interface and management. More particularly, the present invention utilizes a CIMOM proxy to enable and simplify communications between remote providers and common information model (CIM) client applications.
- CIMOM common information model object manager
- FIG. 1 is an example implementation of a network in which communications is established utilizing CIM.
- provider A 40 in managed system A 10 through CIM object manager (CIMOM) 50 communicates to CIM client application 140 in CIM client 100 , CIM client application 150 in CIM client 110 , and CIM client application 160 in CIM client 120 .
- CIM common information model
- provider B 60 in managed system B 20 through CIMOM 70 communicates to CIM client application 140 in CIM client 100 , CIM client application 150 in CIM client 110 , and CIM client application 160 in CIM client 120 .
- provider C 80 in managed system C 30 through CIMOM 90 communicates to CIM client application 140 in CIM client 100 , CIM client application 150 in CIM client 1 10 , and CIM client application 160 in CIM client 120 .
- managed system A 10 , managed system B 20 , managed system C 30 , CIM client 100 , CIM client 110 , and CIM client 120 are all depicted as independent computer systems or processors communicating with each other over a LAN, WAN, PSTN or any other suitable communications mechanism.
- CIMOM 50 , 70 , 90 comprise all software, logic and hardware required for communications.
- each management system requires the use of an enormous amount of memory throughout all the systems. Further, there is no limit on the number of management systems and CIM client applications that may exist within a network. Further, each management system would be required to not only utilize its own memory to store each CIMOM but also its own processor to execute the logic involved in CIMOM.
- FIG. 1 is an example of the prior art in common information model (CIM) communications
- FIG. 2 is a systems diagram of a communications network using a proxy CIMOM to facilitate communications between managed systems and CIM client applications in an example embodiment of the present invention
- FIG. 3 is a flowchart of a remote provider registering with a CIM lookup service and determining the location of the proxy CIMOM in an example embodiment of the present invention
- FIG. 4 is a flowchart of the logic executed by the CIMOM discovery module shown in FIG. 6 in an example embodiment of the present invention
- FIG. 5 is a flowchart of the interaction between the CIM client application and the proxy CIMOM in an example embodiment of the present invention
- FIG. 6 is a data flow diagram between the proxy CIMOM, the remote provider, the CIM lookup service and the CIM client;
- FIG. 7 is an alternate configuration of the systems diagram provided in FIG. 2 depicting possible hardware that may be used.
- FIG. 2 is a systems diagram of a communications network using a proxy CIMOM 210 in a server 200 to facilitate communications between managed systems A 10 , managed systems B 20 , and managed systems C 30 and CIM client applications 100 , 110 , and 120 in an example embodiment of the present invention.
- the proxy CIMOM 210 does not need to be contained in a separate processor or computer system.
- the proxy CIMOM 210 may reside in any server, processor, or computer system in which it is a common resource for use by the other managed systems in the network.
- communications between, for example, provider A 40 and CIM client application 140 would occur through server 200 using proxy CIMOM 210 .
- the precise communications mechanism used between any of the systems shown in FIG. 2 would include any form of communications utilized to communicate from one computer to another. This would include both serial and parallel communications over, but not limited to, twisted pair, coax cable, fiber optic cable and all forms of wireless communications.
- Provider A 40 would also communicate to CIM client application 150 and CIM client 160 through proxy CIMOM.
- provider B 60 provider C 80 would communicate to CIM client application 140 , 150 and 160 through proxy CIMOM 210 .
- the precise manner by which the proxy CIMOM 210 operates will be discussed in further detail in reference to FIGS. 3 through 6 ahead.
- FIG. 3 is a flowchart of a remote provider 750 , shown in FIG. 6, registering with a CIM lookup service 700 , shown in FIG. 6, and determining the location of the proxy CIMOM 200 in an example embodiment of the present invention.
- the remote provider 750 shown in FIG. 6, may be provider A 40 , provider B 60 or provider C 80 shown in FIG. 2 or some other provider not shown.
- execution begins by the remote provider 750 , such as provider A 40 , shown in FIG. 2, registering with a CIM lookup service 700 in operation 300 .
- this registration process would entail the remote provider 750 transmitting certain information to CIM lookup service 700 .
- This information would include the remote provider 750 name, the system identification number, such as an Internet Protocol (IP) address, the communications protocol, and the CIM management object format (MOF) file.
- IP Internet Protocol
- the communications protocol would include additional parameters such as a TCP/IP (Transmission Control Protocol/Internet Protocol) Port number or a JAVA remote method invocation object.
- the MOF file would be used by the Proxy CIMOM 200 to facilitate communications.
- processing then proceeds from operation 300 to operation 310 .
- the remote provider 750 queries the CIM lookup service 700 for information regarding the proxy CIMOM 200 .
- This information would include the proxy CIMOM system identification such as the IP address for the proxy CIMOM 200 .
- This information would further include the communications protocol that should be used when communicating to the proxy CIMOM 200 , such as TCP/IP or Java remote method invocation.
- processing proceeds to operation 320 , where it is determined if the proxy CIMOM 200 has registered itself with the CIM lookup service 700 . If the proxy CIMOM 200 has not registered itself with the CIM lookup service 700 then processing proceeds to operation 330 .
- the remote provider 750 registers at the request of the CIM lookup service 700 , as a result of receiving a negative response from the CIM lookup service in operation 320 , for a proxy CIMOM registration event notification.
- the registration of the proxy CIMOM 200 has occurred by the proxy CIMOM 200 registering with the CIM lookup service 700 causing the generation of a proxy CIMOM registration event which notifies the remote provider 750 of the registration event.
- This registration event causes the transmission of proxy CIMOM system identification, such as IP address, and the communication protocol to the remote provider 750 .
- processing proceeds to operation 350 from either operation 340 or from operation 320 .
- the remote provider 750 stores the proxy CIMOM information for future remote provider event delivery in either the case that the proxy CIMOM 200 should change its registration information or should the proxy CIMOM 200 register for the first time with the CIM lookup service 700 .
- the registration process shown in FIG. 3 then terminates.
- FIG. 4 is a flowchart of the logic executed by the CIMOM discovery module 710 , shown in FIG. 6, in an example embodiment of the present invention.
- the CIMOM discovery module 710 begins execution in operation 400 where the proxy CIMOM 200 registers with the CIM lookup service 700 and transmits the appropriate information required. This information would include the proxy CIMOM 200 system identification such as, but not limited to, its system identification number, the IP address and additional parameters. Processing then proceeds to operation 410 where the proxy CIMOM 200 registers with the CIM lookup service 700 for remote provider registration event notification discussed in further detail in reference to FIG. 5. Thereafter in the discovery module 710 , in operation 420 , the proxy CIMOM 200 queries for information relating to each remote provider 750 .
- the communication protocol may be, but not limited to TCP/IP including a port number or a JAVA remote method invocation object.
- processing in the discovery module 710 then proceeds to operation 430 where the MOF file is loaded into a new name space in the proxy CIMOM 200 along with the information transmitted in operation 420 .
- the CIM lookup service 700 will notify the proxy CIMOM 200 of the new remote provider.
- the discovery module 710 would loop back to and repeat operation 430 . This process continues until such time as the network or the proxy CIMOM 200 are taken offline.
- FIG. 5 is a flowchart of the interaction between the CIM client application 760 , shown in FIG. 6, and the proxy CIMOM 200 , shown in FIGS. 2 and 6, in an example embodiment of the present invention.
- the CIM client application 760 may be any CIM client application 140 , 150 , and 160 shown in FIG. 2.
- Processing begins in operation 500 where the CIM client application 760 queries the CIM lookup service 700 for information related to the proxy CIMOM 200 and required to connect the CIM client application 760 to the proxy CIMOM 200 .
- This information includes the proxy CIMOM 200 identification number, such as Internet Protocol (IP) address, and the communications protocol.
- IP Internet Protocol
- the communications protocol would include additional parameters such as a TCP/IP port number or a JAVA remote method invocation object.
- processing proceeds to operation 510 where it is determined if the proxy CIMOM 200 has registered with the CIM lookup service 700 .
- the proxy CIMOM 200 has not registered with the CIM lookup service 700 , then processing proceeds to operation 520 where the CIM client application 760 registers with the CIM lookup service 700 for a proxy CIMOM 200 registration event notification and the CIM client application 760 then waits for the event notification to take place.
- the CIM lookup service 700 transmits the proxy CIMOM 200 identification number, such as Internet Protocol (IP) address, and the communications protocol.
- IP Internet Protocol
- the communications protocol would include additional parameters such as a TCP/IP port number or a JAVA remote method invocation object.
- Processing then proceeds to operation 540 from operation 530 or from operation 510 , if the proxy CIMOM 200 has registered with the CIM lookup service 200 .
- the CIM client application 760 connects to the proxy CIMOM 200 via the connection authentication module (CAM) 720 and supplies a user name and password to the CAM 720 .
- CAM connection authentication module
- processing proceeds to operation 560 , otherwise processing returns to operation 540 which is repeated until a correct user name and password is entered.
- the CAM 720 would simply bar further attempts for the CIM client application 760 to receive authentication during this session.
- processing proceeds to operation 560 .
- the proxy CIMOM 200 returns the proxy CIMOM 200 name spaces which may include the address or identification of the remote providers 760 .
- the remote providers 760 may be any of the managed systems 10 , 20 , and 30 shown in FIG. 2.
- operation 570 it is determined if the CIM client application 760 desires to receive asynchronous remote provider 750 events. If the CIM client application 760 desires to receive asynchronous remote provider 750 events then processing proceeds to operation 580 where the CIM client application 760 registers with the event module 740 contained within the proxy CIMOM 200 .
- the event module is given the CIM client application 760 name, the CIM client application 760 system identification, such as the IP address, and the communication protocol to use.
- the communication protocol may be, but not limited to TCP/IP, including a port number, or a JAVA remote method invocation object.
- processing proceeds to operation 590 from either operation 580 or operation 570 in the case that the CIM client application 760 does not desire to receive asynchronous remote provider 750 events.
- the CIM client application 760 selects the name space of the remote provider 750 of interest. Thereafter, in operation 600 , the CIM client application 760 requests data of the particular CIM class in the selected name space associated with the remote provider 750 from the proxy CIMOM 200 .
- the request processing module (RPM) 730 in the proxy CIMOM 200 queries the remote provider 750 for delivery of the CIM class data requested by the CIM client application 760 . Thereafter, processing proceeds to operation 620 where the proxy CIMOM 200 receives the asynchronous events and data from the remote provider 750 and thereafter delivers the data to the CIM client application 760 which has registered for these particular events.
- RPM request processing module
- FIG. 6 is a data flow diagram illustrating the flow of information between the proxy CIMOM 200 , the remote provider 750 , the CIM client application 760 , and the CIM lookup service 700 .
- FIG. 6 contains modules representing software, commands, firmware, hardware, instructions, computer programs, subroutines, code and code segments previously discussed in reference to the example flowcharts FIGS. 3 through 5.
- the modules shown in FIG. 6 may take any form of logic executable by a processor, including, but not limited to, programming languages, such as C++.
- a CIM client application 760 will attempt to discover the location of the proxy CIMOM 200 by accessing and registering with a CIM lookup service 700 .
- the proxy CIMOM 200 also accesses the CIM lookup service 700 to discover the location of the remote providers 750 .
- the CIM client application 760 is provided with the location (address) of the proxy CIMOM 200 .
- the CIM client application 760 queries the proxy CIMOM 200 for remote provider 750 CIM data.
- the proxy CIMOM 200 queries the remote provider 750 for the CIM data.
- the remote provider 750 then delivers the data to the proxy CIMOM 200 and in turn the proxy CIMOM 200 delivers the remote provider 750 data to the CIM client application 760 .
- the remote provider 750 Prior to access and delivery of such remote provider 750 data, the remote provider 750 must register with a CIM lookup service 700 which in turn updates the proxy CIMOM 200 with the location of the remote provider 750 .
- FIG. 7 is an alternate configuration of the systems diagram provided in FIG. 2 depicting possible hardware that may be used.
- FIG. 7 contains a proxy CIMOM 200 server connected through a LAN or WAN to a managed system A 10 , a managed system B 20 , a managed PDA system 810 , and a server used for the CIM lookup service 700 .
- FIG. 7 illustrates a connection to LAN, WAN or wireless access 830 to the proxy CIM 200 .
- This WAN or wireless access 830 may be through any communication means that allows at least two computer systems to communicate with each other.
- This wireless access 830 or WAN may be a cellular telephone network or a satellite telephone network.
- the personal digital assistant (PDA) 810 is a managed system like managed system A 10 .
- a remote provider runs on the PDA providing the managed data of the PDA to the proxy CIMOM.
- a laptop communicating through a cellular phone may act as a CIM client application 760 . Therefore, the hardware utilized to implement the embodiments of the present invention is not intended to limit the present invention strictly to that herein described.
- the benefit resulting from the present invention is that a simple, reliable, fast system and method is provided for computers and processors to communicate to each other. Further, the sending and receiving computers require the use of minimal space and processor time to send and receive information through the use of a proxy CIMOM.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Computer And Data Communications (AREA)
Abstract
A system, method and computer program for transmitting and receiving information between computer systems. This is accomplished using a common information model object manager (CIMOM) proxy that serves to receive and transmit information from one computer on the network to another. The CIMOM proxy relies on both managed system providers and client applications to register with the CIMOM proxy. Once registered the client application may request information and receive it from managed system providers.
Description
- The invention relates to a system and method for common information model object manager (CIMOM) proxy interface and management. More particularly, the present invention utilizes a CIMOM proxy to enable and simplify communications between remote providers and common information model (CIM) client applications.
- In the rapid development of computers many advancements have been seen in the areas of processor speed, throughput, communications, and fault tolerance. Initially computer systems were standalone devices in which a processor, memory and peripheral devices all communicated through a single bus. Later, in order to improve performance, several processors were interconnected to memory and peripherals using one or more buses. In addition, separate computer systems were linked together through different communications mechanisms such as, shared memory, serial and parallel ports, local area networks (LAN) and wide area networks (WAN). Further, with the development of the Internet and advancements in cellular and wireless communications, it is now possible for computers to communicate without the use of wires, such as provided by the public switched telephone network (PSTN), over great distances.
- In order to facilitate communications between providers of different hardware and software, schemas and standards have been established. One such schema is the common information model (CIM) which is a common data model of an implementation-neutral schema for describing the overall management of information in a network/enterprise environment. FIG. 1 is an example implementation of a network in which communications is established utilizing CIM. In this example,
provider A 40 in managedsystem A 10 through CIM object manager (CIMOM) 50 communicates toCIM client application 140 inCIM client 100,CIM client application 150 inCIM client 110, andCIM client application 160 inCIM client 120. Further in this example,provider B 60 in managedsystem B 20 through CIMOM 70 communicates toCIM client application 140 inCIM client 100,CIM client application 150 inCIM client 110, andCIM client application 160 inCIM client 120. Still further in this example,provider C 80 in managedsystem C 30 through CIMOM 90 communicates toCIM client application 140 inCIM client 100,CIM client application 150 inCIM client 1 10, andCIM client application 160 inCIM client 120. It should be noted that managedsystem A 10, managedsystem B 20, managedsystem C 30,CIM client 100,CIM client 110, andCIM client 120 are all depicted as independent computer systems or processors communicating with each other over a LAN, WAN, PSTN or any other suitable communications mechanism. It should also be noted that CIMOM 50, 70, 90 comprise all software, logic and hardware required for communications. - However, the requirement that separate copies of CIMOM50,70,90 in each management system requires the use of an enormous amount of memory throughout all the systems. Further, there is no limit on the number of management systems and CIM client applications that may exist within a network. Further, each management system would be required to not only utilize its own memory to store each CIMOM but also its own processor to execute the logic involved in CIMOM.
- Therefore, what is required is a system and method whereby the need for each management system to have its own copy of CIMOM is eliminated. This system and method should also minimize the processor time required to establish communications with CIM client applications.
- The foregoing and a better understanding of the present invention will become apparent from the following detailed description of exemplary embodiments and the claims when read in connection with the accompanying drawings, all forming a part of the disclosure of this invention. While the foregoing and following written and illustrated disclosure focuses on disclosing example embodiments of the invention, it should be clearly understood that the same is by way of illustration and example only and the invention is not limited thereto. The spirit and scope of the present invention are limited only by the terms of the appended claims.
- The following represents brief descriptions of the drawings, wherein:
- FIG. 1 is an example of the prior art in common information model (CIM) communications;
- FIG. 2 is a systems diagram of a communications network using a proxy CIMOM to facilitate communications between managed systems and CIM client applications in an example embodiment of the present invention;
- FIG. 3 is a flowchart of a remote provider registering with a CIM lookup service and determining the location of the proxy CIMOM in an example embodiment of the present invention;
- FIG. 4 is a flowchart of the logic executed by the CIMOM discovery module shown in FIG. 6 in an example embodiment of the present invention;
- FIG. 5 is a flowchart of the interaction between the CIM client application and the proxy CIMOM in an example embodiment of the present invention;
- FIG. 6 is a data flow diagram between the proxy CIMOM, the remote provider, the CIM lookup service and the CIM client; and
- FIG. 7 is an alternate configuration of the systems diagram provided in FIG. 2 depicting possible hardware that may be used.
- Before beginning a detailed description of the subject invention, mention of the following is in order. When appropriate, like reference numerals and characters may be used to designate identical, corresponding or similar components in differing figure drawings. Further, in the detailed description to follow, exemplary sizes/models/values/ranges may be given, although the present invention is not limited to the same. As a final note, well-known components of computer networks may not be shown within the FIGS. for simplicity of illustration and discussion, and so as not to obscure the invention.
- FIG. 2 is a systems diagram of a communications network using a proxy CIMOM210 in a
server 200 to facilitate communications between managedsystems A 10,managed systems B 20, and managedsystems C 30 andCIM client applications - Still referring to FIG. 2, communications between, for example,
provider A 40 andCIM client application 140 would occur throughserver 200 using proxy CIMOM 210. The precise communications mechanism used between any of the systems shown in FIG. 2 would include any form of communications utilized to communicate from one computer to another. This would include both serial and parallel communications over, but not limited to, twisted pair, coax cable, fiber optic cable and all forms of wireless communications. Provider A 40 would also communicate toCIM client application 150 andCIM client 160 through proxy CIMOM. In a similarmanner provider B 60,provider C 80 would communicate toCIM client application - FIG. 3 is a flowchart of a
remote provider 750, shown in FIG. 6, registering with aCIM lookup service 700, shown in FIG. 6, and determining the location of the proxy CIMOM 200 in an example embodiment of the present invention. Theremote provider 750, shown in FIG. 6, may beprovider A 40,provider B 60 orprovider C 80 shown in FIG. 2 or some other provider not shown. - Still referring to FIG. 3, execution begins by the
remote provider 750, such asprovider A 40, shown in FIG. 2, registering with aCIM lookup service 700 inoperation 300. Inoperation 300, this registration process would entail theremote provider 750 transmitting certain information to CIMlookup service 700. This information would include theremote provider 750 name, the system identification number, such as an Internet Protocol (IP) address, the communications protocol, and the CIM management object format (MOF) file. The communications protocol would include additional parameters such as a TCP/IP (Transmission Control Protocol/Internet Protocol) Port number or a JAVA remote method invocation object. The MOF file would be used by the Proxy CIMOM 200 to facilitate communications. - Still referring to FIG. 3, processing then proceeds from
operation 300 tooperation 310. Inoperation 310, theremote provider 750 then queries the CIMlookup service 700 for information regarding the proxy CIMOM 200. This information would include the proxy CIMOM system identification such as the IP address for the proxy CIMOM 200. This information would further include the communications protocol that should be used when communicating to the proxy CIMOM 200, such as TCP/IP or Java remote method invocation. Thereafter, processing proceeds tooperation 320, where it is determined if the proxy CIMOM 200 has registered itself with the CIMlookup service 700. If the proxy CIMOM 200 has not registered itself with the CIMlookup service 700 then processing proceeds tooperation 330. Inoperation 330, theremote provider 750 registers at the request of the CIMlookup service 700, as a result of receiving a negative response from the CIM lookup service inoperation 320, for a proxy CIMOM registration event notification. Inoperation 340, the registration of the proxy CIMOM 200 has occurred by the proxy CIMOM 200 registering with theCIM lookup service 700 causing the generation of a proxy CIMOM registration event which notifies theremote provider 750 of the registration event. This registration event causes the transmission of proxy CIMOM system identification, such as IP address, and the communication protocol to theremote provider 750. Thereafter, processing proceeds tooperation 350 from eitheroperation 340 or fromoperation 320. Inoperation 350, theremote provider 750 stores the proxy CIMOM information for future remote provider event delivery in either the case that theproxy CIMOM 200 should change its registration information or should theproxy CIMOM 200 register for the first time with theCIM lookup service 700. The registration process shown in FIG. 3 then terminates. - FIG. 4 is a flowchart of the logic executed by the
CIMOM discovery module 710, shown in FIG. 6, in an example embodiment of the present invention. TheCIMOM discovery module 710 begins execution inoperation 400 where theproxy CIMOM 200 registers with theCIM lookup service 700 and transmits the appropriate information required. This information would include theproxy CIMOM 200 system identification such as, but not limited to, its system identification number, the IP address and additional parameters. Processing then proceeds tooperation 410 where theproxy CIMOM 200 registers with theCIM lookup service 700 for remote provider registration event notification discussed in further detail in reference to FIG. 5. Thereafter in thediscovery module 710, inoperation 420, theproxy CIMOM 200 queries for information relating to eachremote provider 750. This information would include the remote provider=s 750 name, the remote providers=s 750 system identification, the communication protocol to be used, and the MOF file. The remote provider=s system identification may be, but not limited to, an IP address. The communication protocol may be, but not limited to TCP/IP including a port number or a JAVA remote method invocation object. - Still referring to FIG. 4, processing in the
discovery module 710 then proceeds tooperation 430 where the MOF file is loaded into a new name space in theproxy CIMOM 200 along with the information transmitted inoperation 420. This information would include the remote provider=s 750 name, the remote providers=s 750 system identification, the communication protocol to be used. Thereafter, inoperation 440, whenever a newremote provider 750 registers with theCIM lookup service 700, theCIM lookup service 700 will notify theproxy CIMOM 200 of the new remote provider. This notification would include the remote provider=s 750 name, the remote providers=s 750 system identification, the communication protocol to be used, and the MOF file. Thereafter, thediscovery module 710 would loop back to and repeatoperation 430. This process continues until such time as the network or theproxy CIMOM 200 are taken offline. - FIG. 5 is a flowchart of the interaction between the
CIM client application 760, shown in FIG. 6, and theproxy CIMOM 200, shown in FIGS. 2 and 6, in an example embodiment of the present invention. It should be noted that theCIM client application 760 may be anyCIM client application CIM client application 760 queries theCIM lookup service 700 for information related to the proxy CIMOM 200 and required to connect theCIM client application 760 to theproxy CIMOM 200. This information includes theproxy CIMOM 200 identification number, such as Internet Protocol (IP) address, and the communications protocol. The communications protocol would include additional parameters such as a TCP/IP port number or a JAVA remote method invocation object. Thereafter, processing proceeds tooperation 510 where it is determined if theproxy CIMOM 200 has registered with theCIM lookup service 700. - Still referring to FIG. 5, if the
proxy CIMOM 200 has not registered with theCIM lookup service 700, then processing proceeds tooperation 520 where theCIM client application 760 registers with theCIM lookup service 700 for aproxy CIMOM 200 registration event notification and theCIM client application 760 then waits for the event notification to take place. Once theproxy CIMOM 200 registration event notification takes place by theproxy CIMOM 200 registering with the CIM lookup service, as previously discussed, then in operation 530 theCIM lookup service 700 transmits theproxy CIMOM 200 identification number, such as Internet Protocol (IP) address, and the communications protocol. The communications protocol would include additional parameters such as a TCP/IP port number or a JAVA remote method invocation object. Processing then proceeds tooperation 540 from operation 530 or fromoperation 510, if theproxy CIMOM 200 has registered with theCIM lookup service 200. Inoperation 540, theCIM client application 760 connects to theproxy CIMOM 200 via the connection authentication module (CAM) 720 and supplies a user name and password to theCAM 720. - Still referring to FIG. 5, in
operation 550, if the CIM client provides a correct user name and password then processing proceeds tooperation 560, otherwise processing returns tooperation 540 which is repeated until a correct user name and password is entered. As would be appreciated by one of ordinary skill in the art, after some number of failed attempts are made theCAM 720 would simply bar further attempts for theCIM client application 760 to receive authentication during this session. However, if it is determined that the user name and password are valid, inoperation 550, then processing proceeds tooperation 560. Inoperation 560, theproxy CIMOM 200 returns theproxy CIMOM 200 name spaces which may include the address or identification of theremote providers 760. As previously discussed theremote providers 760 may be any of the managedsystems - Still referring to FIG. 5, thereafter in
operation 570, it is determined if theCIM client application 760 desires to receive asynchronousremote provider 750 events. If theCIM client application 760 desires to receive asynchronousremote provider 750 events then processing proceeds tooperation 580 where theCIM client application 760 registers with theevent module 740 contained within theproxy CIMOM 200. The event module is given theCIM client application 760 name, theCIM client application 760 system identification, such as the IP address, and the communication protocol to use. The communication protocol may be, but not limited to TCP/IP, including a port number, or a JAVA remote method invocation object. Thereafter, processing proceeds tooperation 590 from eitheroperation 580 oroperation 570 in the case that theCIM client application 760 does not desire to receive asynchronousremote provider 750 events. - Still referring to FIG. 5, in
operation 590, theCIM client application 760 selects the name space of theremote provider 750 of interest. Thereafter, inoperation 600, theCIM client application 760 requests data of the particular CIM class in the selected name space associated with theremote provider 750 from theproxy CIMOM 200. Inoperation 610, the request processing module (RPM) 730 in theproxy CIMOM 200 queries theremote provider 750 for delivery of the CIM class data requested by theCIM client application 760. Thereafter, processing proceeds tooperation 620 where theproxy CIMOM 200 receives the asynchronous events and data from theremote provider 750 and thereafter delivers the data to theCIM client application 760 which has registered for these particular events. It should be noted that more than oneCIM client application 760, such as managed systems A 10, managedsystem B 20, or managedsystem C 30, may request the same data from aremote provider 750. - FIG. 6 is a data flow diagram illustrating the flow of information between the
proxy CIMOM 200, theremote provider 750, theCIM client application 760, and theCIM lookup service 700. FIG. 6 contains modules representing software, commands, firmware, hardware, instructions, computer programs, subroutines, code and code segments previously discussed in reference to the example flowcharts FIGS. 3 through 5. The modules shown in FIG. 6 may take any form of logic executable by a processor, including, but not limited to, programming languages, such as C++. Typically, aCIM client application 760 will attempt to discover the location of theproxy CIMOM 200 by accessing and registering with aCIM lookup service 700. Theproxy CIMOM 200 also accesses theCIM lookup service 700 to discover the location of theremote providers 750. TheCIM client application 760 is provided with the location (address) of theproxy CIMOM 200. TheCIM client application 760 then queries theproxy CIMOM 200 forremote provider 750 CIM data. Theproxy CIMOM 200 queries theremote provider 750 for the CIM data. Theremote provider 750 then delivers the data to the proxy CIMOM 200 and in turn theproxy CIMOM 200 delivers theremote provider 750 data to theCIM client application 760. Prior to access and delivery of suchremote provider 750 data, theremote provider 750 must register with aCIM lookup service 700 which in turn updates theproxy CIMOM 200 with the location of theremote provider 750. - FIG. 7 is an alternate configuration of the systems diagram provided in FIG. 2 depicting possible hardware that may be used. FIG. 7 contains a
proxy CIMOM 200 server connected through a LAN or WAN to a managedsystem A 10, a managedsystem B 20, a managedPDA system 810, and a server used for theCIM lookup service 700. In addition, FIG. 7 illustrates a connection to LAN, WAN orwireless access 830 to theproxy CIM 200. This WAN orwireless access 830 may be through any communication means that allows at least two computer systems to communicate with each other. Thiswireless access 830 or WAN may be a cellular telephone network or a satellite telephone network. The personal digital assistant (PDA) 810 is a managed system like managedsystem A 10. A remote provider runs on the PDA providing the managed data of the PDA to the proxy CIMOM. In addition, a laptop communicating through a cellular phone may act as aCIM client application 760. Therefore, the hardware utilized to implement the embodiments of the present invention is not intended to limit the present invention strictly to that herein described. - The benefit resulting from the present invention is that a simple, reliable, fast system and method is provided for computers and processors to communicate to each other. Further, the sending and receiving computers require the use of minimal space and processor time to send and receive information through the use of a proxy CIMOM.
- While we have shown and described only a few examples herein, it is understood that numerous changes and modifications as known to those skilled in the art could be made to the example embodiment of the present invention. Therefore, we do not wish to be limited to the details shown and described herein, but intend to cover all such changes and modifications as are encompassed by the scope of the appended claims.
Claims (27)
1. A system for communicating component management data between computers in a network, comprising:
a plurality of remote managed systems comprising one or more information providers to supply system management data from one or more components;
a plurality of client management applications;
an object manager, connected to the plurality of remote managed systems and to the plurality of client management applications, to store information models of the components of one or more of the managed systems, and to relay requests for data between the information providers and client management applications; and
a lookup service, communicatively coupled with the plurality of remote managed systems, the plurality of client management applications, and the object manager, to discover the locations of the information providers and of the object manager, and to register the remote information providers and the client management applications with the object manager.
2. The system recited in claim 1 , wherein the object manager further comprises:
a connection authentication module to authenticate the client systems management applications by checking a client management application user name for a match with a plurality of user names entered into a file located on the object manager by the lookup service.
3. The system recited in claim 1 , wherein the object manager further comprises:
a discovery module to register the the object manager with the lookup service and to determine the locations of the plurality of remote managed systems.
4. The system recited in claim 1 , wherein the object manager further comprises:
a request processing module to query a selected remote information provider for information requested by a querying client management application.
5. The system recited in claim 1 , wherein the object manager further comprises:
an event module to receive information from a selected remote information provider and to transmit the information to a querying client management application.
6. The system recited in claim 5 , wherein a client management application requests that asynchronous remote information provider events be received from a selected remote information provider by transmitting to the event module the client management application identifier and a selected communication protocol.
7. The system recited in claim 4 , wherein a remote information provider registers with the object manager by transmitting to the lookup service an information provider identifier, a selected communication protocol, and information regarding corresponding components which the lookup service relays to the object manager.
8. A method of communicating component management data between computers in a network, comprising:
storing information models of components of a plurality of managed systems in an object manager;
registering with the object manager via a plurality of remote information providers from a plurality of managed systems and a plurality of client management applications sending information to a lookup service;
discovering the location of the object manager by the lookup service and transmitting the registration information received from the plurality of remote information providers and the plurality of client management applications to the object manager;
transmitting the location of the object manager to the plurality of remote information providers and to the plurality of client management applications;
requesting information of a selected remote information provider by a querying client management application transmitting a request to the object manager;
relaying the request to the selected remote information provider with the object manager; and
transmitting the information to the querying client management application upon receipt by the object manager.
9. The method recited in claim 8 , wherein relaying the request to the selected remote information provider with the object manager, further comprises:
checking a database contained in the object manager to determine the location of the selected remote information provider; and
transmitting the request for information to the selected remote information provider.
10. The method recited in claim 9 , wherein checking the database contained in the object manager to determine the location of the selected remote information provider, further comprises:
queuing the request for information in a file when a match for the selected remote information provider cannot be found in the database.
11. The method recited in claim 10 , wherein registering with the object manager by a remote information provider, further comprises:
checking the file containing the queued requests for information to determine whether a request for information corresponding to the remote information provider exists in the file; and
transmitting the request for information to the remote information provider upon completing the registration of the remote information provider.
12. The method recited in claim 8 , wherein registering with the object manager by a client management application sending information to a lookup service, further comprises:
transmitting a client management identifier and a selected communication protocol to the lookup service; and
relaying the client management application identifier and the selected communication protocol to the object manager by the lookup service.
13. The method recited in claim 8 , wherein registering with the object manager by a remote information provider sending information to a lookup service, further comprises:
transmitting a remote information provider identifier, information regarding corresponding components, and a selected communication protocol to the lookup service; and
relaying the remote information provider identifier, the component information, and the selected communication protocol to the object manager by the lookup service.
14. A computer program embodied on a computer readable medium executable by a computer for communicating component management data between computers in a network, comprising:
storing information models of the components of a plurality of managed systems in an object manager,
registering with an object manager via a plurality of remote information providers from a plurality of managed systems and a plurality of client management applications sending information to a lookup service;
discovering the location of the object manager by the lookup service and transmitting the registration information received from the plurality of remote information providers and of the plurality of client management applications to the object manager;
transmitting the location of the object manager to the plurality of remote information providers and to the the plurality of client management applications;
requesting information of a selected remote information provider by a querying client management application transmitting the request to the object manager;
relaying the request to the selected remote information provider with the object manager; and
transmitting the information to the querying client management application upon receipt by the object manager.
15. The computer program recited in claim 14 , wherein relaying the request to the selected remote information provider with the object manager, further comprises:
checking a database contained in the object manager to determine the location of the selected remote information provider; and
transmitting the request for information to the selected remote information provider.
16. The computer program recited in claim 15 , wherein checking the database contained in the object manager to determine the location of the selected remote information provider, further comprises:
queuing the request for information in a file when a match for the selected remote information provider cannot be found in the database.
17. The computer program recited in claim 16 , wherein registering with the object manager by a remote information provider, further comprises:
checking the file containing the queued requests for information to determine whether a request for information directed to the remote information provider exists in the file; and
transmitting the request for information to the remote information provider upon completing the registration of the remote information provider.
18. The computer program recited in claim 14 , wherein registering with the object manager by a client management application sending information to a lookup service, further comprises:
transmitting a client management application identifier and a selected communication protocol to the lookup service; and
relaying the client management application identifier and the selected communication protocol to the object manager.
19. The computer program recited in claim 14 , wherein registering with the object manager by a remote information provider sending information to a lookup service, further comprises:
transmitting a remote information provider identifier, information regarding corresponding components, and a selected communication protocol to the lookup service; and
relaying the remote information provider identifier, the component information, and the selected communication protocol to the object manager by the lookup service.
20. The computer program of claim 19 , wherein transmitting information regarding managed system components corresponding to the information provider comprises transmitting a CIM Managed Object Format (MOF) file.
21. The system of claim 1 , wherein the object manager stores information about the components of the managed systems according to the Common Information Model (CIM) specification and schema.
22. The system of claim 1 , wherein the lookup service is a CIM lookup service.
23. The system of claim 1 , wherein the managed systems are personal computers
24. The system of claim 7 , wherein the information model is a CIM Managed Object Format (MOF) file.
25. The method of claim 8 , wherein storing information models of the components of a plurality of managed systems comprises storing CIM models of the components.
26. The method of claim 13 , wherein transmitting information regarding managed system components corresponding to the information provider comprises transmitting a CIM Managed Object Format (MOF) file.
27. The computer program of claim 14 , wherein storing information models of the components of a plurality of managed systems comprises storing CIM models of the components.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/882,508 US20040249926A1 (en) | 2001-03-27 | 2004-06-30 | System and methd for common information model object manager proxy interface and management |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/817,023 US6775700B2 (en) | 2001-03-27 | 2001-03-27 | System and method for common information model object manager proxy interface and management |
US10/882,508 US20040249926A1 (en) | 2001-03-27 | 2004-06-30 | System and methd for common information model object manager proxy interface and management |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/817,023 Continuation US6775700B2 (en) | 2001-03-27 | 2001-03-27 | System and method for common information model object manager proxy interface and management |
Publications (1)
Publication Number | Publication Date |
---|---|
US20040249926A1 true US20040249926A1 (en) | 2004-12-09 |
Family
ID=25222191
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/817,023 Expired - Lifetime US6775700B2 (en) | 2001-03-27 | 2001-03-27 | System and method for common information model object manager proxy interface and management |
US10/882,508 Abandoned US20040249926A1 (en) | 2001-03-27 | 2004-06-30 | System and methd for common information model object manager proxy interface and management |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/817,023 Expired - Lifetime US6775700B2 (en) | 2001-03-27 | 2001-03-27 | System and method for common information model object manager proxy interface and management |
Country Status (1)
Country | Link |
---|---|
US (2) | US6775700B2 (en) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070185967A1 (en) * | 2006-02-08 | 2007-08-09 | International Business Machines Corporation | Multiple login instant messaging |
US7966394B1 (en) * | 2008-04-24 | 2011-06-21 | Hewlett-Packard Development Company, L.P. | Information model registry and brokering in virtualized environments |
US20120054319A1 (en) * | 2010-08-31 | 2012-03-01 | International Business Machines Corporation | Efficient response of common information model (cim) server |
US20120233304A1 (en) * | 2008-05-26 | 2012-09-13 | International Business Machines Corporation | Registering a Common Information Model Provider to a Common Information Model Object Manager |
US8601108B1 (en) * | 2011-06-29 | 2013-12-03 | Emc Corporation | Credential authentication and authorization in a server device |
Families Citing this family (34)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020199022A1 (en) * | 2001-06-26 | 2002-12-26 | Simon Tsang | System and method for establishing and managing communications between mangement protocol different system |
US20030033398A1 (en) * | 2001-08-10 | 2003-02-13 | Sun Microsystems, Inc. | Method, system, and program for generating and using configuration policies |
US20030033346A1 (en) * | 2001-08-10 | 2003-02-13 | Sun Microsystems, Inc. | Method, system, and program for managing multiple resources in a system |
US7133907B2 (en) * | 2001-10-18 | 2006-11-07 | Sun Microsystems, Inc. | Method, system, and program for configuring system resources |
US6965559B2 (en) * | 2001-10-19 | 2005-11-15 | Sun Microsystems, Inc. | Method, system, and program for discovering devices communicating through a switch |
US20030135609A1 (en) * | 2002-01-16 | 2003-07-17 | Sun Microsystems, Inc. | Method, system, and program for determining a modification of a system resource configuration |
US7043738B2 (en) * | 2002-03-05 | 2006-05-09 | Sun Microsystems, Inc. | Method and apparatus for managing a data imaging system using CIM providers in a distributed computer system |
US7155501B2 (en) * | 2002-05-16 | 2006-12-26 | Sun Microsystems, Inc. | Method and apparatus for managing host-based data services using CIM providers |
US7290045B2 (en) * | 2002-07-01 | 2007-10-30 | Sun Microsystems, Inc. | Method and apparatus for managing a storage area network including a self-contained storage system |
US7103889B2 (en) | 2002-07-23 | 2006-09-05 | Sun Microsystems, Inc. | Method, system, and article of manufacture for agent processing |
US7143615B2 (en) * | 2002-07-31 | 2006-12-05 | Sun Microsystems, Inc. | Method, system, and program for discovering components within a network |
US20040024887A1 (en) * | 2002-07-31 | 2004-02-05 | Sun Microsystems, Inc. | Method, system, and program for generating information on components within a network |
US20040022200A1 (en) * | 2002-07-31 | 2004-02-05 | Sun Microsystems, Inc. | Method, system, and program for providing information on components within a network |
US7383551B2 (en) * | 2002-09-27 | 2008-06-03 | International Business Machines Corporation | Method and system for integrating non-compliant providers of dynamic services into a resource management infrastructure |
US7480921B1 (en) | 2003-03-12 | 2009-01-20 | Microsoft Corporation | Method, system, and apparatus for customizing web parts |
US7281252B1 (en) * | 2003-03-12 | 2007-10-09 | Microsoft Corporation | Method, system, and apparatus for implementing object interfaces at runtime |
US7493492B2 (en) * | 2004-04-17 | 2009-02-17 | International Business Machines Corporation | Limiting access to publicly available object-oriented interfaces via password arguments |
CN100343803C (en) * | 2004-07-26 | 2007-10-17 | 国际商业机器公司 | Method and syste mfor transplanting prsonalized computation environment from source platform to target platform |
US7865880B2 (en) * | 2004-11-16 | 2011-01-04 | Lsi Corporation | System and/or method for implementing efficient techniques for testing common information model providers |
US20060168216A1 (en) * | 2004-12-09 | 2006-07-27 | Alexander Wolf-Reber | Digital management system and method for managing access rights in such a management system |
US7627593B2 (en) * | 2005-08-25 | 2009-12-01 | International Business Machines Corporation | Method and system for unified support of multiple system management information models in a multiple host environment |
US8387069B2 (en) * | 2006-07-28 | 2013-02-26 | Dell Products L.P. | Method to support dynamic object extensions for common information model (CIM) operation and maintenance |
US20080033972A1 (en) * | 2006-08-04 | 2008-02-07 | Jianwen Yin | Common Information Model for Web Service for Management with Aspect and Dynamic Patterns for Real-Time System Management |
US8019791B2 (en) * | 2006-11-22 | 2011-09-13 | Oracle International Corporation | Method and system for transforming metadata modeled in the common information model into grid control target metadata |
US20080184264A1 (en) * | 2007-01-26 | 2008-07-31 | Dell Products L.P. | Method, Apparatus and Media for Information Model Data Retrieval |
US8103698B2 (en) * | 2007-02-28 | 2012-01-24 | Jianwen Yin | Methods, apparatus and media for system management of object oriented information models |
US8087032B2 (en) * | 2008-03-31 | 2011-12-27 | International Business Machines Corporation | Automated recovery process initiation for data consumers of a common information model (CIM) managed component |
JP2010157996A (en) * | 2008-12-05 | 2010-07-15 | Canon Inc | Original scanning apparatus and method of controlling the same |
CN101989923B (en) * | 2009-07-31 | 2013-08-28 | 国际商业机器公司 | Method and system for registering computer integrated manufacturing (CIM) agency to management agency and management system |
US9049182B2 (en) | 2009-08-11 | 2015-06-02 | Novell, Inc. | Techniques for virtual representational state transfer (REST) interfaces |
US8423735B2 (en) | 2010-05-21 | 2013-04-16 | International Business Machines Corporation | Space reservation in a deduplication system |
US9654473B2 (en) | 2013-06-28 | 2017-05-16 | Bmc Software, Inc. | Authentication proxy agent |
CN105045246B (en) * | 2015-08-20 | 2017-12-29 | 京东方科技集团股份有限公司 | CIM systems and control method, production information system |
CN105575305B (en) | 2016-03-17 | 2018-10-30 | 京东方科技集团股份有限公司 | A kind of signal wire broken wire repairing circuit, method and display panel |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6004477A (en) * | 1996-10-14 | 1999-12-21 | Mitsubishi Gas Chemical Company, Inc. | Oxygen absorption composition |
US6760733B1 (en) * | 1998-09-10 | 2004-07-06 | Fujitsu Limited | Object management system and data processing system with centralized mechanism for managing containment relationships among objects |
US6862736B2 (en) * | 1998-02-06 | 2005-03-01 | Microsoft Corporation | Object manager for common information model |
US6996809B2 (en) * | 2000-07-10 | 2006-02-07 | Microsoft Corporation | Method and apparatus for providing instrumentation data to an instrumentation data source from within a managed code environment |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6317748B1 (en) * | 1998-05-08 | 2001-11-13 | Microsoft Corporation | Management information to object mapping and correlator |
US6081900A (en) * | 1999-03-16 | 2000-06-27 | Novell, Inc. | Secure intranet access |
US6493719B1 (en) * | 1999-07-26 | 2002-12-10 | Microsoft Corporation | Method and system for scripting for system management information |
US6427168B1 (en) * | 1999-07-26 | 2002-07-30 | Microsoft Corporation | Architecture for system monitoring using high-performance providers |
AU2001261084A1 (en) * | 2000-04-27 | 2001-11-07 | Brio Technology, Inc. | Method and apparatus for processing jobs on an enterprise-wide computer system |
US20020123966A1 (en) * | 2000-06-23 | 2002-09-05 | Luke Chu | System and method for administration of network financial transaction terminals |
US7627865B2 (en) * | 2000-07-10 | 2009-12-01 | Microsoft Corporation | Method and apparatus for accessing instrumentation data from within a managed code environment |
US7370364B2 (en) * | 2000-07-31 | 2008-05-06 | Ellacoya Networks, Inc. | Managing content resources |
US20020046352A1 (en) * | 2000-10-05 | 2002-04-18 | Ludwig George Stone | Method of authorization by proxy within a computer network |
US7146635B2 (en) * | 2000-12-27 | 2006-12-05 | International Business Machines Corporation | Apparatus and method for using a directory service for authentication and authorization to access resources outside of the directory service |
-
2001
- 2001-03-27 US US09/817,023 patent/US6775700B2/en not_active Expired - Lifetime
-
2004
- 2004-06-30 US US10/882,508 patent/US20040249926A1/en not_active Abandoned
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6004477A (en) * | 1996-10-14 | 1999-12-21 | Mitsubishi Gas Chemical Company, Inc. | Oxygen absorption composition |
US6862736B2 (en) * | 1998-02-06 | 2005-03-01 | Microsoft Corporation | Object manager for common information model |
US6760733B1 (en) * | 1998-09-10 | 2004-07-06 | Fujitsu Limited | Object management system and data processing system with centralized mechanism for managing containment relationships among objects |
US6996809B2 (en) * | 2000-07-10 | 2006-02-07 | Microsoft Corporation | Method and apparatus for providing instrumentation data to an instrumentation data source from within a managed code environment |
Cited By (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070185967A1 (en) * | 2006-02-08 | 2007-08-09 | International Business Machines Corporation | Multiple login instant messaging |
US7953803B2 (en) * | 2006-02-08 | 2011-05-31 | International Business Machines Corporation | Multiple login instant messaging |
US7966394B1 (en) * | 2008-04-24 | 2011-06-21 | Hewlett-Packard Development Company, L.P. | Information model registry and brokering in virtualized environments |
US20120233304A1 (en) * | 2008-05-26 | 2012-09-13 | International Business Machines Corporation | Registering a Common Information Model Provider to a Common Information Model Object Manager |
US9054299B2 (en) * | 2008-05-26 | 2015-06-09 | International Business Machines Corporation | Registering a common information model provider to a common information model object manager |
US9401847B2 (en) | 2008-05-26 | 2016-07-26 | International Business Machines Corporation | Registering a common information model provider to a common information model object manager |
US20120054319A1 (en) * | 2010-08-31 | 2012-03-01 | International Business Machines Corporation | Efficient response of common information model (cim) server |
US9501528B2 (en) * | 2010-08-31 | 2016-11-22 | International Business Machines Corporation | Efficient response of common information model (CIM) server |
US8601108B1 (en) * | 2011-06-29 | 2013-12-03 | Emc Corporation | Credential authentication and authorization in a server device |
Also Published As
Publication number | Publication date |
---|---|
US20020144009A1 (en) | 2002-10-03 |
US6775700B2 (en) | 2004-08-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6775700B2 (en) | System and method for common information model object manager proxy interface and management | |
US10244058B2 (en) | Extending functionality of applications | |
CN102394872B (en) | Data communication protocol | |
US7571208B2 (en) | Creating proxies from service description metadata at runtime | |
US6115744A (en) | Client object API and gateway to enable OLTP via the internet | |
EP0956687B1 (en) | Web request broker controlling multiple processes | |
US7987278B2 (en) | Web services device profile on a multi-service device: dynamic addition of services | |
US6795864B2 (en) | System using lookup service proxy object having code and request rate for managing rate at which client can request for services from server are transmitted | |
JP4938418B2 (en) | Data communication protocol | |
CN101400109B (en) | General service opening interface system and general service opening method | |
US8666940B2 (en) | Method and apparatus for communicating data between computer devices | |
US20130117835A1 (en) | Image Forming Apparatus, Image Forming System, and Method for Realizing Pseudo Single Sign-On | |
RU2344473C2 (en) | Network system, proxy-server, method of session control | |
US7523492B2 (en) | Secure gateway with proxy service capability servers for service level agreement checking | |
WO2002060200A1 (en) | Method and system for wireless information exchange and management | |
JP2000132473A (en) | Network system using fire wall dynamic control system | |
EP1684482B1 (en) | System and method for managing communication for component applications | |
US7873647B2 (en) | Web services device profile on a multi-service device: device and facility manager | |
CN112181681A (en) | Remote calling method and device, computer equipment and storage medium | |
KR100597405B1 (en) | System and method for relaying data by use of socket applicaton program | |
US8499023B1 (en) | Servlet-based grid computing environment using grid engines and switches to manage resources | |
KR100317748B1 (en) | Access control method of zone data for transmission control protocol query/response in secure dns, and naming services server | |
JP2002032468A (en) | System, device and method for information processing, and storage medium | |
JP3576000B2 (en) | Computer system | |
EP1936922B1 (en) | Discovery and addition of services in a multi-service device |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: INTEL CORPORATION, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CHENG, HEUNG-FOR;RAMACHANDRAN, MAHENDRA;VUPPULA, SRINIVAS;REEL/FRAME:015546/0046 Effective date: 20010516 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |