Plug-in configuration manager

• US 20040073782A1
• Filed: 04/29/2003
• Published: 04/15/2004
• Est. Priority Date: 05/02/2002
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Garagan, Sean, Price, Adrian
• Granted Patent: US 7,650,397 B2
• Time in Patent Office: Days
• US Class Current: 713/1
• CPC Class Codes: G06F 2209/544 Remote
• CPC Class Codes: G06F 9/4862 the task being a mobile agent, i.e. specifically designed to migrate
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 41/0843 based on generic templates
• CPC Class Codes: H04L 41/0856 by backing up or archiving configuration information
• CPC Class Codes: H04L 41/0869 Validating the configuration within one network element

Abstract

Plug-in information can be synchronized on each node in a cluster by utilizing a migratable plug-in configuration manager and a migratable global MBean. The configuration manager can change the configuration on a master server, such as loading or unloading a plug-in. The configuration manager stores the configuration as an MBean attribute, which is accessible across the cluster. The configuration manager can direct the global MBean to notify a plug-in manager on each node in the cluster, whereby each plug-in manager can execute the change locally.

This description is not intended to be a complete description of, or limit the scope of, the invention. Other features, aspects, and objects of the invention can be obtained from a review of the specification, the figures, and the claims.

Claims

1. A system for managing plug-ins across a cluster of servers, comprising:

a global management bean capable of storing plug-in configuration for the cluster;

a plug-in manager on each server in the cluster of servers, each plug-in manager capable of receiving configuration change notifications from the global management bean and executing the configuration change on the server containing that plug-in manger; and

a plug-in configuration manager existing once in the cluster, the plug-in configuration manager adapted to update the plug-in configuration stored by the global management bean and direct the global management bean to broadcast a configuration change notification to each plug-in manager.

2. A system according to claim 1, wherein:

the global management bean is further capable of storing the plug-in configuration as an attribute of the management bean.

3. A system according to claim 2, wherein:

the global management bean is further capable of allowing cluster-wide access to the attribute.

4. A system according to claim 1, wherein:

the global management bean is further capable of broadcasting configuration change notifications to each plug-in manager.

5. A system according to claim 1, wherein:

each plug-in manager has a notification listener for receiving notifications from the global management bean.

6. A system according to claim 1, wherein:

each plug-in manager is further adapted to request the current plug-in configuration from the global management bean.

7. A system according to claim 1, further comprising:

a master server in the cluster adapted to allow for a change in the plug-in configuration.

8. A system according to claim 7, wherein:

the master server is further adapted to allow the change in the plug-in configuration on the master server before the change is broadcast by the global management bean.

9. A system according to claim 1, wherein:

the global management bean is migratable throughout the cluster.

10. A system according to claim 1, wherein:

the plug-in configuration manager is migratable throughout the cluster.

11. A system according to claim 1, further comprising:

a persistent data store for holding plug-in configuration information, the persistent data store accessible by the global management bean if the global management bean needs to obtain state information.

12. A system according to claim 1, wherein:

the plug-in configuration manager is adapted to execute a change selected from the group consisting of loading, unloading, and reconfiguring plug-ins across the cluster.

13. A system according to claim 1, wherein:

the global management bean is adapted to broadcast a configuration change notification to each server in the cluster, the notification containing the plug-in configuration for the cluster.

14. A system according to claim 1, wherein:

the global management bean is adapted to broadcast a configuration change notification to each server in the cluster, the notification containing only the change to the plug-in configuration for the cluster.

15. A system according to claim 1, wherein:

the plug-in configuration manager is implemented as a management bean.

16. A system according to claim 1, further comprising:

a state object capable of storing plug-in configuration state for the global management bean.

17. A system according to claim 1, wherein:

the global management bean is adapted to broadcast a configuration change notification to each server in the cluster, the notification being a JMX notification.

18. A method for managing plug-ins across a cluster of servers, comprising:

changing the plug-in configuration state of a cluster on a master server using a plug-in configuration manager;

storing the plug-in configuration state change as an attribute of a global management bean;

sending a notification of the change from the global management bean to each managed server in the cluster; and

making the change on each managed server.

19. A method according to claim 18, further comprising:

receiving a request to change the plug-in configuration state of the cluster.

20. A system for managing plug-ins across a cluster of servers, comprising:

means for changing the plug-in configuration state of a cluster on a master server using a plug-in configuration manager;

means for storing the plug-in configuration state change as an attribute of a global management bean;

means for sending a notification of the change from the global management bean to each managed server in the cluster; and

means for making the change on each managed server.

21. A computer-readable medium, comprising:

means for changing the plug-in configuration state of a cluster on a master server using a plug-in configuration manager;

means for storing the plug-in configuration state change as an attribute of a global management bean;

means for sending a notification of the change from the global management bean to each managed server in the cluster; and

means for making the change on each managed server.

22. A computer program product for execution by a server computer for deploying an adapter, comprising:

computer code for changing the plug-in configuration state of a cluster on a master server using a plug-in configuration manager;

computer code for storing the plug-in configuration state change as an attribute of a global management bean;

computer code for sending a notification of the change from the global management bean to each managed server in the cluster; and

computer code for making the change on each managed server.

23. A computer system comprising:

a processor;

object code executed by said processor, said object code configured to;

change the plug-in configuration state of a cluster on a master server using a plug-in configuration manager;

store the plug-in configuration state change as an attribute of a global management bean;

send a notification of the change from the global management bean to each managed server in the cluster; and

make the change on each managed server.

24. A computer data signal embodied in a transmission medium, comprising:

a code segment including instructions to change the plug-in configuration state of a cluster on a master server using a plug-in configuration manager;

a code segment including instruction to store the plug-in configuration state change as an attribute of a global management bean;

a code segment including instructions to send a notification of the change from the global management bean to each managed server in the cluster; and

a code segment including instructions to make the change on each managed server.