[go: up one dir, main page]

EP1684177A1 - Verwaltungsverfahren und -system in einer JMX-Umgebung mit einer Verwaltungsanwendung und zu verwaltenden Softwaresystemen - Google Patents

Verwaltungsverfahren und -system in einer JMX-Umgebung mit einer Verwaltungsanwendung und zu verwaltenden Softwaresystemen Download PDF

Info

Publication number
EP1684177A1
EP1684177A1 EP06290141A EP06290141A EP1684177A1 EP 1684177 A1 EP1684177 A1 EP 1684177A1 EP 06290141 A EP06290141 A EP 06290141A EP 06290141 A EP06290141 A EP 06290141A EP 1684177 A1 EP1684177 A1 EP 1684177A1
Authority
EP
European Patent Office
Prior art keywords
administration
component
mbeans
hierarchical structure
mbeanserver
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.)
Withdrawn
Application number
EP06290141A
Other languages
English (en)
French (fr)
Inventor
Nicolas Rivierre
Thierry Coupaye
Francois Horn
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.)
Orange SA
Original Assignee
France Telecom SA
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 France Telecom SA filed Critical France Telecom SA
Publication of EP1684177A1 publication Critical patent/EP1684177A1/de
Withdrawn legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • 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
    • H04L41/02—Standardisation; Integration
    • H04L41/0213—Standardised network management protocols, e.g. simple network management protocol [SNMP]

Definitions

  • the present invention is in the field of administration (management) of software systems. It relates more particularly to the administration of complex platforms typically corresponding to the integration of several software systems with various resources and distributed over a network, developed separately and therefore in an uncoordinated manner for their administration.
  • JMX Java 2 Enterprise Edition
  • the JMX standard defines an architecture, services, and application programming interface (API) for administering software system resources. It gave rise to several achievements.
  • the JMX standard is currently defined by the Java Specification Request 03 specification (see http://java.sun.com/products/JavaManagement/).
  • a software object is associated with attributes and operations. It is an abstraction of a resource, such as an equipment, component, or service.
  • An MBean is a software object associated with attributes and operations for administering said resource; in the context of the present invention, these attributes and administration operations will be called “configuration elements”.
  • configuration elements The choice of the particular configuration elements that one wishes to associate with a resource is called “instrumentation" of said resource.
  • An MBean can be registered (still called “exposed") in an administration server, named MBeanServer, under a name to identify it.
  • MBeanServer provides a standard means of access to perform administrative acts on a resource represented by an MBean that it exposes. In fact, the exhibition gives access to the attributes and administration operations associated with such an MBean.
  • JMX standardizes several services that are also represented by MBeans.
  • Such particular MBeans are for example control elements (in English, " monitoring "), which emit a notification as soon as they observe that an attribute of a resource reaches a certain state.
  • JMX also standardizes the way to access an MBeanServer through connectors or adapters (Java Specification Request 160, JMX remote). It is thus possible to administer a system from a browser, via the HTTP ("HyperText Transfer Protocol") protocol, a remote Java client, via the Remote REM invocation Java mechanism ("Remote Method Invocation”) or to change information model and protocol by interconnecting with other administration standards such as SNMP or WEBM / CIM.
  • HTTP HyperText Transfer Protocol
  • remote Java client via the Remote REM invocation Java mechanism ("Remote Method Invocation")
  • Remote Method Invocation Remote Method Invocation
  • JMX can be used to administer a Java application in an ad hoc or standardized way.
  • the information exposed to the administrators, the naming convention of the MBeans representing this information, their distribution in one or more MBeanServers and the connectors allowing to access them are chosen freely.
  • J2EE Java Specification Request 77
  • IBM IBM or Weblogic from BEA
  • This model describes the information exposed to administrators, such as generic J2EE concepts (J2EEServer, J2EEResources, EJB %), and normalizes access to this information via a particular component, called Management EJB (MEJB).
  • J2EEServer J2EEResources
  • EJB Management EJB
  • ProxyMBean proposed by the known products of the domain that are JDMK (Sun MicroSystem) or MX4J (cf mx4j.sourceforge.net).
  • JDMK Sun MicroSystem
  • MX4J cf mx4j.sourceforge.net
  • This feature allows cascading MBeanServers by exposing, in a MBeanServer, a proxyMBean representing an MBean exposed in another MBeanServer.
  • WO0077632 describes how to dynamically treat Java objects, by introspection, to make them manipulable in the form of MBeans.
  • the JMX specification essentially details the administration of server-side software systems. On the client side, it only standardizes the access to information exposed by these systems through MBeanServers or connectors / adapters / MEJB in the case of distributed access.
  • the client that is to say the administration application, must perform various operations such as selecting the relevant information or subscribe to notification services signaling particular events (alarms ...) .
  • it must handle the addition of non-server-side services, such as monitoring (monitoring) a particular attribute. It must also manage multiple connections if the information it wishes to exploit is spread over several systems.
  • server-side changes such as the names used to identify information or the setting of connections to access them.
  • a difficulty encountered in the context of JMX administration concerns the possibility of federating the administration of target systems by offering a single access allowing to aggregate the administration information coming from several target systems, to carry out actions of administration on these systems in a homogeneous way.
  • Another difficulty encountered concerns the flexibility of such a federated administration, which must make it possible to adapt dynamically to the scalability of the target systems and to change the logical view of administration on these systems as needed.
  • the invention aims to solve these difficulties.
  • the invention proposes a method of administration in a JMX environment comprising a plurality of software systems to be administered, represented by respective first MBeans and at least one administration application, in which the acts Administer the MBeans exposure in at least one MBeanServer.
  • An administration component is a Java software object that can be manipulated in a development environment, to construct a hierarchical structure in combination with other administration components.
  • at least one first administration component is a node-type component, that is to say that at least one second hierarchical subordinate administration component can be connected to it by a subordinate link .
  • This second component is a direct descendant (or son) of the first component.
  • a third administration component that is a direct descendant of the second component is also a descendant of the first administration component (grandson).
  • an administration component X is a descendant of a management component Y and this administration component Y is itself a descendant of a management component Z, then the component X is a
  • the invention thus makes it possible for an administration application, by simply providing the name of an administration component, access to a set of resources administered by the MBeans represented by, on the one hand, the named administration component and on the other hand all the administration components that come from it (sons, grandsons, etc.).
  • the invention also allows a logical administration view that meets the needs of the administrator, defined by the administration component in the superior hierarchical position.
  • the invention also makes it possible to add services relating to the administration of these software systems, by creating administration components that represent such services.
  • the administration components are themselves MBeans.
  • the hierarchical structure is defined based at least on configurable configuration elements of these MBeans. This arrangement makes it possible to administer both the software systems and the mediation device in accordance with the JMX standard.
  • the name of an administration component is a function of the associated path in the hierarchical structure, which makes it possible to obtain unambiguous designations and allows an easy use of the mediation device by several applications. administration, regardless of the changes made on the software systems, for example modifications made on MBeans representing these systems (first MBeans).
  • the invention proposes an administration system in a JMX environment comprising a plurality of software systems to be administered, represented by respective first MBeans and at least one administration application, in which the administration acts produce the exposure of MBeans in at least one MBeanServer.
  • Figure 1 shows a set of 12 software systems to administer. Three of these software systems are shown in Figure 1, with references 120, 121 and 122.
  • the software system 120 is for example a Java application represented by a MBean M0 locally exposing information from a MBeanServer provided with a RMI connector.
  • the system 121 is for example an application hosted by a J2EE application server (for example Websphere of IBM or Weblogic of BEA) and represented locally by an MBean M1 exposing information from a MEJB (Management Enterprise Java Bean).
  • the software system 122 is for example a Java application represented by a M2 MBean locally exposing information from an MBeanServer provided with a RMI connector. Subsequently, only one MBean per software system is considered, but the invention also applies in the presence of several MBeans per software system.
  • FIG. 1 shows a set of administration applications capable of interfacing with standard JMX adapter connectors. Each of these administration applications is intended to administer several of the software systems 12. Two of these administration applications 100, 101 are represented. They can be a browser using an HTTP adapter, a Java client using an RMI connector or an SNMP manager (such as HP OpenView or IBM Tivoli) using an SNMP adapter.
  • SNMP manager such as HP OpenView or IBM Tivoli
  • a mediation device 11 comprises in the embodiment considered here two adapter connectors standards 110 and 114.
  • the mediation device 11 furthermore comprises two MBeanServers administration servers 111 and 115.
  • the mediation device 11 further comprises a workshop 117 comprising factories for creating administration components.
  • Each factory makes it possible to create administration components of a given type, and to parameterize them.
  • Each type is associated with a particular administrative function, such as creating MBeans proxy on remote MBeans, adding custom services (eg a controller to monitor an attribute of a particular resource), or dynamically exploiting resources. local. It is possible to introduce a new type of administration component into the mediation device 11 by adding the appropriate factory in the workshop 117.
  • FIG. 2 indicates the various steps implemented in one embodiment of the invention, in the mediation device 11. These steps correspond firstly to an initialization mode, then to an exploitation mode and finally to a management mode of the mediation device 11.
  • a hierarchical logic view of functions of the software systems of the set of software systems 12 is defined.
  • This logical view is then translated into a persistent representation 113 of an organization of administration components according to a hierarchical structure reflecting said view.
  • This persistent representation makes it possible to initialize the mediation device 11. It can be produced manually or with the aid of the device 11 itself, as described below and is stored in a memory of the mediation device 11.
  • this persistent representation 113 is an XML (eXtended Markup Language) file describing the organization of the administration components according to the hierarchical structure. Nodes in this hierarchy are named to form an unambiguous naming space (a node can not have two child nodes with the same name). In a sheet of this hierarchy are included the data necessary for the establishment of the technical chain allowing the exposure of information representing, as the case may be, proxies on information already exposed by a software system of the set of systems software, an administration service added by the mediation device 11 or any other information.
  • XML Extended Markup Language
  • Step P22 traverses the persistent representation 113 produced in step P21, to create an assembly of administration components reflecting the hierarchical structure described in this representation.
  • the design pattern used to create and assemble these components is shown in Figure 5, and is based on libraries for composing graphical objects (for example the Java swing API).
  • any administration component is an MBean that implements the View 500 business interface, whose two "expose” and “unexposed” operations each have the role of exposing to an MBeanServer and removing a MBeanServer, the MBeans represented by this administration component.
  • Each sheet of the hierarchy leads to create, using a factory 117, a dedicated LeafView 502 type administration component and parameterized with the data entered in step P21 for this sheet.
  • Each node of the hierarchy - excepted sheets - leads to create a CompositeView 503 type component implementing the View 500 and Composite 501 interfaces.
  • This second interface makes it possible to add to the component created (or to remove some components from type View 500.
  • An administration component (the parent component) which has a direct descendant (child component) according to the hierarchical structure, is thus an administration component defined as a component containing the child component.
  • Step P23 consists of instance MBeanServers servers 111 and 115 and to expose JMX connectors / adapters 110 and 114 allowing an application of administration of the set of applications 10 to access device 11 according to two respective modes .
  • the operating mode is initialized by exposing in the MBeanServer 111 a particular management component 116, described below, for controlling the information being exposed.
  • the management mode is initialized by exposing in the MBeanServer 115 the particular administration components 117 and 118 described below, making it possible to control the reconfiguration actions of the mediation device 11.
  • Steps P24, P25 and P26 represent the use of the mediation device 11 by an administration application.
  • This application The administrator can use the device exclusively in operating mode or exclusively in management mode, or alternatively can use it.
  • the client application 100 accesses the device 11 in operating mode only.
  • the client application 101 accesses the device in operating and management modes.
  • the step P250 consists, for an administration application of the set of applications 10, to access the device via the adapter connector 110, which causes the selection of the MBeanServer 111 for the exploitation
  • the step P251 consists in exposing in the MBeanServer 111 the information represented by an administration component, by traversing the assembly of components that it contains if the latter is composite.
  • the administration application for example the administration application 101, uses the component 116 exposed in the MBeanServer 111 during the step P23.
  • This component 116 provides an operation for triggering the exposure of the MBeans represented by an administration component. This operation takes as argument the absolute name of this administration component, provided by the administration application 101, and making it possible to locate it in the global assembly 112.
  • this administration component propagates the exposure command to the administration components that it contains, which propagate it if they are composite, and so on.
  • Each administration component encountered during this propagation exposes in the MBeanServer 111 the MBeans that it represents, by using a convention of designation specific to each type of administration component. For example, in the case of proxy MBeans representing remote MBeans, the name of a proxy can be identical to the name of the remote MBean it represents.
  • the exposure control will be transmitted in fact to the hierarchical assembly 112 constituted by the parent component C1, the component components C2, C3 of the components component C1, and then by the component elements C4, C5, C6 of the administration component C3.
  • the component C4 is for example a leaf component representing the MBean M0 initially exposed in the software system 120. It is therefore configured with the address of this system and possibly with a filter (so as not to repatriate everything). When it receives this exposure command, it will then expose in MBeanServer 111 a MBean proxy on the M0 MBean of the software system 120.
  • Step P252 represents the administration phase by the administration application 110 of the information then exposed in the MBeanServer 111.
  • step P251 new information
  • step P253 withdraw from the MBeanServer 111, by the triggering by the administration application 110 of a new operation on the component 116.
  • the step P253 consists of removing information represented by an administration component 112, by traversing the assembly of components that it contains if the latter is composite.
  • the method is symmetrical to that used in step P251 using an operation of the dedicated component 116 for this purpose.
  • the naming convention used in step P251, to expose MBeans in the MBeanServer 111, is now used to find and remove these MBeans.
  • the mediation device 11 ensures that the global hierarchical assembly of the administration components forms a non-designation space. ambiguous. Indeed, there is a unique path leading from the root of this hierarchy to a component. This path represents the absolute name of the component that can be used by the administration application to identify the administrative components it wants to use.
  • the method used to implement the mediation device 11 in management mode is illustrated in FIG. 4.
  • the administration application 101 accesses the mediation device 11 via the adapter-connector 114, which causes the selection of the MBeanServer 115 for the management mode exposure and the passage of the mediation device 11 in management mode.
  • Step P261 then consists in exposing in the MBeanServer 115 the current configuration of the administration components themselves of the hierarchical structure.
  • Each component then exposes its configuration elements, such as a threshold in the case of a component representing a controller, a filter (pattern on JMX ObjectName) in the case of a component to select MBeans, or any other parameter .
  • This exposure step is triggered by the administration application 101 using the component 118 (exposed in the MBeanServer 115 during the step P23) which provides a dedicated operation for this purpose, or is triggered automatically by the mediation device 11 after the steps P265 and 266 detailed below modifying the structure of the assembly of the administration components.
  • the step P262 consists of saving the current configuration of the administration components 112. This optional step can be triggered by the administration application 101 using the component 118 which provides a dedicated operation for this purpose, producing a persistent representation of the current configuration similar to 113.
  • Step P263 represents a choice on the possible actions in management mode.
  • the administration application 101 modifies the setting of a management component exposed in the MBeanServer 115. It may be to modify the value of a threshold in the case a component representing a controller, the value of a filter (pattern on JMX ObjectName) in the case of a component to select MBeans, or any other parameter value.
  • the administration application 101 creates a new administration component using a plant 117 exposed in the MBeanServer 115 during the step P23.
  • Each factory is dedicated to the creation of a component of a given type and provides one (or more) "create" operation (s) taking as argument the data allowing to parameterize this component.
  • the arguments will indicate the alarm threshold (s), the periodicity of observation, the name of the attribute to be observed, the name of the MBeans to observe, etc. .
  • Each "create" operation of a plant also has an argument to immediately place the new component in the assembly 112 of the administration components.
  • this argument represents a path in the hierarchical structure of the assembly and makes it possible to locate where to add the new component.
  • the administration application 101 performs a step P266, which consists of modifying the current assembly 112 of the administration components by a "cut / copy / paste" type manipulation. inspired by the graphical interface of office tools.
  • these manipulations are triggered by the administration application 101 using the component 118 which provides three similar operations, each taking an argument representing a path in the hierarchical structure of the component assembly.
  • the creation step P265
  • the implementation of these operations is based on the "composite" design pattern used to assemble the administration components in a hierarchical structure.
  • the "cut" operation makes it possible to remove from the assembly the component found by following the path given in argument, and to keep it in memory.
  • the operation "copy” makes it possible to keep in memory the component found in the assembly by following the path given in argument.
  • the "paste” operation is used to add in the assembly the last component stored in memory, at the location found by following the path given as an argument. In the case of an erroneous path or name conflict, these operations fail.
  • any modification made to the administration components during the steps P264, P265 and P266 can be tested immediately in the operating mode (P25) of the mediation device 11 or lead to a backup of the new configuration (step P262).
  • the invention makes it possible to administer several software systems 120, 121, 122 by exposing in the MBeanServer 111 the information represented by the administration components.
  • a (composite) administration component may represent a service not provided by a J2EE application (eg, the software system 121), such as monitoring an attribute of a particular resource.
  • a J2EE application eg, the software system 121
  • JMX set with alert thresholds, attribute names and proxy to be controlled.
  • the basic components used by this assembly are simple.
  • a controller is a basic function of JMX that just configure using an administration component to expose it in the MBeanServer 111.
  • a resource exposed via a MEJB can be represented in the MBeanServer 111 by an MBean proxy implementing the "DynamicMBean" and "DynamicMBean” interfaces.
  • NotificationBoadcaster "of the JMX API see Figure 6
  • the implementation delegates each of the operations of these two interfaces to a MEJB informed during the construction of the proxy.
  • the administration component responsible for exposing this proxy therefore has the necessary parameters to create the JNDI context for connecting to the MEJB and for identifying the resource by its name. More complex assembly examples, such as linking MBeans exposed by independent software systems, can also be created using the mediation device 11.
  • the device can be reconfigured dynamically by exposing the administration components themselves in the MBeanServer 115.
  • This mode is accessed by a client (eg 101) via the adapter connector (114). and controlled by the particular components 117 and 118.
  • the access to these two modes is differentiated in the described embodiment so as not to mix the information and allow to associate an access policy according to the administration application.
  • the invention does not require distinguishing the MBeanServer used in operating mode - (previously described via the MBeanServer 111) - from that used in management mode - (previously described via the MBeanServer 115).
  • access to each of these two modes can be given by a single MBeanServer.
  • the administration application 100 or 101 can reside in the same Java virtual machine as the mediation device 11 and directly access the MBeanServers 111 or 115 via local Java references.
  • an administration component of the hierarchical assembly of components may represent information about a local Java application (residing in the same Java virtual machine as the device 11) and conventionally instrumented with JMX or dynamically by this component (for example as described by patent WO0077632).
  • At least one software system to be administered (for example 122) or at least one administration application (for example 101) may be a mediation device similar to 11.
  • each administration component can add to the name of the MBeans that it represents its own name (for example under prefix or property form) in the component hierarchy structure 112. This information, different for any leaf component, avoids name collisions with MBeans exposed by other leaf components.
  • the invention provides a device and a method of mediation for administering software systems instrumented with JMX - including the mediation device itself constructed using an MBeans assembly.
  • the invention avoids relying on server-side connections and does not require ad-hoc development to aggregate relevant information or add administrative services not intended by target systems.
  • the device is reconfigurable in that it dynamically changes the logical view of an administrator on the systems it administers (by reconfiguring the hierarchical assembly of administration components) and these reconfiguration functions are accessible from outside the device by the same JMX access mode (and not an ad hoc access mode) as the access mode to the administered target systems.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)
EP06290141A 2005-01-25 2006-01-20 Verwaltungsverfahren und -system in einer JMX-Umgebung mit einer Verwaltungsanwendung und zu verwaltenden Softwaresystemen Withdrawn EP1684177A1 (de)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
FR0500764 2005-01-25

Publications (1)

Publication Number Publication Date
EP1684177A1 true EP1684177A1 (de) 2006-07-26

Family

ID=34954504

Family Applications (1)

Application Number Title Priority Date Filing Date
EP06290141A Withdrawn EP1684177A1 (de) 2005-01-25 2006-01-20 Verwaltungsverfahren und -system in einer JMX-Umgebung mit einer Verwaltungsanwendung und zu verwaltenden Softwaresystemen

Country Status (2)

Country Link
US (1) US7539743B2 (de)
EP (1) EP1684177A1 (de)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017054501A1 (zh) * 2015-09-30 2017-04-06 中兴通讯股份有限公司 一种应用管理方法、装置及系统

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2300991B (en) * 1995-05-15 1997-11-05 Andrew Macgregor Ritchie Serving signals to browsing clients
US7941521B1 (en) * 2003-12-30 2011-05-10 Sap Ag Multi-service management architecture employed within a clustered node configuration
US8015280B2 (en) * 2007-10-01 2011-09-06 Ebay Inc. Method and system for intelligent feature degradation in response to a network deficiency detection
US8566439B2 (en) * 2007-10-01 2013-10-22 Ebay Inc Method and system for intelligent request refusal in response to a network deficiency detection
US7958145B2 (en) * 2007-11-20 2011-06-07 International Business Machines Corporation Creating multiple MBeans from a factory MBean
US8694623B1 (en) * 2008-07-23 2014-04-08 Oracle America, Inc. Methods and apparatuses for remote caching
US8499294B2 (en) * 2009-09-30 2013-07-30 Red Hat, Inc. Persisting the changes for managed components in an application server
CN109862131B (zh) * 2019-02-20 2022-03-04 北京奇艺世纪科技有限公司 服务器访问地址的分配方法、装置及计算机可读存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0909057A2 (de) 1997-10-06 1999-04-14 Sun Microsystems, Inc. Auf Beans basiertes Verwaltungssystem
WO2000077631A1 (en) 1999-06-15 2000-12-21 Sun Microsystems, Inc. Computer software management system
US20040019669A1 (en) * 2002-07-25 2004-01-29 Sridatta Viswanath Event notification in an administration framework for server systems

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6795791B2 (en) * 2001-06-22 2004-09-21 Bea Systems, Inc. System and method for testing time-varying signals
US7376671B2 (en) * 2003-04-15 2008-05-20 Bea Systems, Inc. Method for common management model for distributed server network
US7356562B2 (en) * 2003-04-30 2008-04-08 International Business Machines Corporation Dynamic generator for fast-client static proxy from service interface definition document
US20040230973A1 (en) * 2003-04-30 2004-11-18 International Business Machines Corporation Mechanism to provide adminstrative control in a multi-process application server
CA2586333A1 (en) * 2003-11-04 2005-05-19 Captech Ventures, Inc. System and method for rfid system integration
US20050273668A1 (en) * 2004-05-20 2005-12-08 Richard Manning Dynamic and distributed managed edge computing (MEC) framework

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0909057A2 (de) 1997-10-06 1999-04-14 Sun Microsystems, Inc. Auf Beans basiertes Verwaltungssystem
WO2000077631A1 (en) 1999-06-15 2000-12-21 Sun Microsystems, Inc. Computer software management system
WO2000077632A1 (en) 1999-06-15 2000-12-21 Sun Microsystems, Inc. Management of non-mbeam objects in jmx environment
US20040019669A1 (en) * 2002-07-25 2004-01-29 Sridatta Viswanath Event notification in an administration framework for server systems

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ANONYMOUS: "Java Dynamic Management Kit 5.1 Tutorial", SUN MICROSYSTEMS, June 2004 (2004-06-01), pages 1-14,33-44,73-100,233-244,485 - 494, XP002334093, Retrieved from the Internet <URL:http://java.sun.com/products/jdmk/docs/JDMK51TUTOR.pdf> *
GAMMA ET AL: "Design Patterns", DESIGN PATTERNS, September 1999 (1999-09-01), pages 163-173,223-232,257 - 271, XP002334094, ISBN: 0201633612 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017054501A1 (zh) * 2015-09-30 2017-04-06 中兴通讯股份有限公司 一种应用管理方法、装置及系统

Also Published As

Publication number Publication date
US7539743B2 (en) 2009-05-26
US20060184662A1 (en) 2006-08-17

Similar Documents

Publication Publication Date Title
EP1684177A1 (de) Verwaltungsverfahren und -system in einer JMX-Umgebung mit einer Verwaltungsanwendung und zu verwaltenden Softwaresystemen
Hall et al. An architecture for post-development configuration management in a wide-area network
US8407349B2 (en) Discovering and identifying manageable information technology resources
Hnětynka et al. Dynamic reconfiguration and access to services in hierarchical component models
CA2102538A1 (fr) Dispositif de traitement de l&#39;information permettant la gestion d&#39;une ressource informatique par un systeme d&#39;administration
US10025689B2 (en) Enhanced policy editor with completion support and on demand validation
JP7416845B2 (ja) Ｇｕｉ応答時間を改善するために予測ベースのｇｕｉを生成するシステム及び方法
Baude et al. Programming distributed and adaptable autonomous components—the GCM/ProActive framework
US20080229274A1 (en) Automating Construction of a Data-Source Interface For Component Applications
Bellanger et al. Service Oriented Architecture: impacts and challenges of an architecture paradigm change
EP2169569B1 (de) Verfahren und System zur Kommunikation zwischen verschiedenen Web-Anwendungen
Wallin et al. Automating network and service configuration using {NETCONF} and {YANG}
Falcarin et al. Software architecture evolution through dynamic aop
Adams et al. Scalable management—Technologies for management of large-scale, distributed systems
WO2009007620A2 (fr) Systeme de gestion automatique des reseaux sur une grille informatique
US20070011618A1 (en) GUI-supplying management beans
Fang et al. A version-aware approach for web service client application
CA2543938A1 (en) Programming and development infrastructure for an autonomic element
WO2016207520A1 (fr) Technique de reconfiguration d&#39;un modele d&#39;application pour un deploiement d&#39;une application logicielle
Gladun Optimal Use of Apache Camel for the Best Business Web Applications
Cipolla et al. Web service based asynchronous service execution environment
FR2801704A1 (fr) Procede de communication sous plusieurs protocoles entre une application et une ressource de systeme
Deussen et al. An on-line test platform for component-based systems
Mengusoglu et al. Automated management and service provisioning model for distributed devices
Baude et al. Large-Scale Service Deployment--Application to OSGi

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL BA HR MK YU

17P Request for examination filed

Effective date: 20070111

AKX Designation fees paid

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

17Q First examination report despatched

Effective date: 20080116

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20100317