Method and system for partitioning asset management plugins

Patent metadata

Field	Value
Publication number	US-9218100-B2
Application number	US-71736610-A
Country	US
Kind code	B2
Filing date	Mar 4, 2010
Priority date	Mar 4, 2010
Publication date	Dec 22, 2015
Grant date	Dec 22, 2015

Abstract

An embodiment of the invention includes a system for partitioning asset management plugins. The system includes an application program interface for performing basic CRUD functions on assets having multiple asset types. At least one plugin having plugin components is provided, wherein the plugin manages at least one asset having a specific asset type (of the multiple asset types). The plugin components include a CRUD component, a state component, an actions component, and/or a view component. The system further includes plugin containers for hosting the plugin components, the plugin containers include at least one client-side plugin container and at least one server-side plugin container. The plugin components are partitioned and distributed from the plugin components to the plugin containers by a plugin server based on capabilities of the client.

First claim

What is claimed is:

1. An apparatus for partitioning plug-ins in a client-server asset management environment, said apparatus comprising:
an asset management system for storing assets having multiple asset types;
an application program interface for performing generic create, read, update and delete (CRUD) functions on assets, plugin containers for hosting at least one plugin component of at least one plugin that manages at least one asset type for interacting with said asset management system, the plugin containers including at least one client-side plugin container, and at least one server-side plugin container a processor connected between said plugin containers and said asset management system, said processor partitions and distributes plugin components from the at least one plugin into at least one plugin container said create, read, update and delete component performs replaces, extends, and removes the generic create, read, update and delete functions provided by said application program interface;
said state component does: prevents a state transition of the asset having the specific asset type managed by the plugin, executes some asset type specific Ionic after a state transition has occurred on an asset having the specific asset type managed by the plugin, and performs replaces, extends, and removes the, generic create, read, update and delete functions after a state transition of the asset having the specific asset type associated with the plugin managed by the plugin;
said actions component provides specialized high-level actions for the asset having the specific asset type managed by the plugin, the specialized high-level actions including deploying an executable artifact, transforming artifacts, and performing a type-specific analysis; and
Said view component provides a visual rendering of the asset having the specific asset type managed by the plugin.

2. The apparatus according to claim 1 , wherein the processor partitions the plugin components to the plugin containers dynamically based on capabilities of a client.

3. The apparatus according to claim 1 , wherein the plugin components include a CRUD component for overriding the generic CRUD functions used for interacting with an asset having the specific asset type associated with one of the at least one plugins, and
the CRUD component of the plugin performs at least one of replaces, extends, and removes at least one of the generic CRUD functions of the application program interface.

4. The apparatus according to claim 1 , wherein said application program interface provides generic state transition functions to the assets, and
the plugin components include a state component for overriding the generic state transition functions of the asset having the specific asset type associated with one of the at least one plugins.

5. The apparatus according to claim 4 , wherein said state component of the plugin prevents a state transition of the asset having the specific asset type associated with the plugin.

6. The apparatus according to claim 4 , wherein said state component of the plugin allows a state transition of the asset having the specific asset type associated with the plugin.

7. The apparatus according to claim 4 , wherein said state component of the plugin executes at least one asset type specific action after a state transition has occurred on an asset having the specific asset type associated with the plugin.

8. The apparatus according to claim 4 , wherein said state component of the plugin does at least one of replaces, extends, and removes at least one of the generic CRUD functions after a state transition of the asset having the specific asset type associated with the plugin.

9. The apparatus according to claim 1 , wherein the plugin components include an actions component for providing specialized high-level actions for the asset having the specific asset type associated with the plugin.

10. The apparatus according to claim 9 , wherein the specialized high-level actions include at least one of deploying an executable artifact, transforming artifacts, and performing a type-specific analysis.

11. The apparatus according to claim 1 , wherein the plugin components include a view component for providing at least one of
a visual rendering of the asset having the specific asset type associated with the plugin,
a user interface for interacting with the asset having the specific asset type associated with the plugin, and
a user interface that assists users use additional actions provided by an action component of the plugin for the asset having the specific asset type associated with the plugin.

12. The apparatus according to claim 1 , wherein the plugin components of the plugin are hosted within more than one of the plugin containers,
the plugin containers provide said application program interface to the plugin components, and
the processor mediates interactions between the plugin components hosted within more than one of the plugin containers.

13. A system comprising:
an application program interface for performing generic create, read, update and delete functions on assets having multiple asset types;
at least one plugin having plugin components, the plugin manages at least one asset type, the plugin components including:
a create, read, update and delete component,
a state component,
an actions component, and
a view component;

plugin containers for hosting the plugin components, the plugin containers including
at least one client-side plugin container of at least one client and
at least one server-side plugin container; and

a processor for dynamically partitioning the plugin components to the plugin containers based on capabilities of the at least one client,
said create, read, update and delete component performs replaces, extends, and removes the generic create, read, update and delete functions provided by said application program interface;
said state component does:
prevents a state transition of the asset having the specific asset type managed by the plugin,
executes some asset type specific logic after a state transition has occurred on an asset having the specific asset type managed by the plugin, and
performs replaces, extends, and removes the generic create, read, update and delete functions after a state transition of the asset having the specific asset type associated with the plugin managed by the plugin;

said actions component provides specialized high-level actions for the asset having the specific asset type managed by the plugin, the specialized high-level actions including deploying an executable artifact, transforming artifacts, and performing a type-specific analysis; and
said view component provides a visual rendering of the asset having the specific asset type managed by the plugin.

14. The system according to claim 13 , wherein said state component is capable of:
allows a state transition of the asset having the specific asset type managed by the plugin,
executes some asset type specific logic after a state transition has occurred on an asset having the specific asset type managed by the plugin, and
performs replaces, extends, and removes the generic create, read, update and delete functions after a state transition of the asset having the specific asset type managed by the plugin.

15. The system according to claim 13 , wherein the plugin components of the plugin are hosted within more than one of the plugin containers, and
the processor manages interactions between the plugin components hosted within more than one of the plugin containers.

16. A method comprising

Assignees

• Diament Judah M
• Larsen Grant J
• Iyengar Arun K
• Mikalsen Thomas A
• Rouvellou Isabelle M
• Silva-Lepe Ignacio
• Subramanian Revathi
• IBM

Inventors

• Diament Judah M
• Larsen Grant J
• Iyengar Arun K
• Mikalsen Thomas A
• Rouvellou Isabelle M
• Silva-Lepe Ignacio
• Subramanian Revathi

Classifications

• G06F15/173

  using an interconnection network, e.g. matrix, shuffle, pyramid, star, snowflake · CPC title

• G06F3/048 Primary

  Interaction techniques based on graphical user interfaces [GUI] · CPC title

• G06F9/44526

  Plug-ins; Add-ons · CPC title