System and method for inventory services

In accordance with embodiments, there are provided mechanisms and methods for determining a select set of changes from a set of changes made to an application instance to propagate to one or more other application instances. These mechanisms and methods can enable embodiments to propagate changes from a first application instance in a first environment to a second application instance in a second environment. For example, an embodiment can enable changes to be made to a test version in a test environment, tested and then propagated to a production version of the application residing in a production environment. The ability of embodiments to propagate changes to other application instances across environments can enable easy capture and transferal of changes to an application.

CROSS REFERENCE TO RELATED APPLICATIONS

The following commonly owned, co-pending U.S. patents and patent applications, including the present application, are related to each other. Each of the other patents/applications are incorporated by reference herein in its entirety:

U.S. patent application Ser. No. 11/121,143 entitled SYSTEM AND METHOD FOR INVENTORY SERVICES, by Peter Laird, filed on May 5, 2005; and

U.S. patent application Ser. No. 11/210,855 entitled SYSTEM AND METHOD FOR APPLICATION PROPAGATION, by Peter Laird, filed on May 5, 2005.

FIELD OF THE INVENTION

The present invention relates generally to systems, methods, and computer readable media for managing portal applications. The present invention relates particularly to the propagation of portal application data.

BACKGROUND OF THE INVENTION

Since its inception in 1995, the Java® programming language (Java® is a registered trademark of Sun Microsystems, Inc.) has become increasingly popular. Java, which is an interpreted language, enabled the creation of applications that could be run on a wide variety of platforms, i.e., so called “platform independent applications.” This ability to function across a variety of different client platforms and Java's relatively easy implementation of network applications has resulted in its use in endeavors as basic as personal webpages to endeavors as complex as large business-to-business enterprise systems.

As Java has become more commonplace, a wide variety of tools and development platforms have been created to assist developers in the creation and implementation of platform independent applications using Java or other languages that support platform independent applications. One such type of platform independent application is the web portal. A web portal is a World Wide Web site whose purpose is to be a starting point for a wide variety of users when these users connect to the Web. Thus, a number of products have arisen to assist in the design of customized web portals that provide tools and integrate previously generated content. These products provide graphics, content, sample portlets, i.e., applications that can run within a web portal, and tools for interacting with and modifying the same.

One commonly used function of such tools is the backup and propagation of portal applications. Often a developer will wish to modify an application in a development and testing environment first before propagating the changes to a version of the application that is part of a working portal, i.e., the “working setting” or “production environment.” After testing the modified application in the testing environment, the developer then passes the changes to the version of the application in the working setting.

However, these applications can be difficult to configure and often store relevant data in a variety of difficult-to-identify locations. This makes the task of accurately propagating the changes to the version of the application in the working setting highly unreliable and time consuming.

What is needed is a tool for propagating portal applications that allows for the easy capture and transferal of changes to an application.

DETAILED DESCRIPTION

In accordance with embodiments, there are provided mechanisms and methods for determining a select set of changes from a set of changes made to an application instance to propagate to one or more other application instances. These mechanisms and methods can enable embodiments to propagate changes from a first application instance in a first environment to a second application instance in a second environment. For example, an embodiment can enable changes to be made to a test version in a test environment, tested and then propagated to a production version of the application residing in a production environment. The ability of embodiments to propagate changes to other application instances across environments can enable easy capture and transferal of changes to an application.

In an embodiment, a method for determining a select set of changes made to an application to propagate. The method includes determining a unique identifier for at least one item of information related to a first version of an application. One or more unique identifiers can form a first inventory associated with the first version of the application. In response to receiving a second inventory comprising at least one unique identifier for at least one item of information related to a second version of the application, a set of differences between the first version of the application and the second version of the application can be determined by comparison of the first inventory and the second inventory. The set of differences can be provided as changes to be propagated to a second version of the application.

As used herein, the term application is intended to be broadly construed to include any data entry, update, query or program that processes data on behalf of a user, including without limitation network based applications, web based server resident applications, web portals, search engines, photographic, audio or video information storage applications, e-Commerce applications, backup or other storage applications, sales/revenue planning, marketing, forecasting, accounting, inventory management applications and other business applications. Users may be human or computational entities. As used herein, the term environment is intended to be broadly construed to include a set of any characteristics of a computer configuration, including hardware and software characteristics, such as without limitation, operating system, Central Processor Unit (CPU) model, data communications systems, database systems, programming languages and any applicable standards. As used herein, the term residing is intended to be broadly construed to include applications loaded into active memory, persisted in storage, being executed by a processor and other associations between applications and environments known in the computing arts. As used herein the term inventory is defined as one or more identifiers associated with one or more data items. The term data items is intended to be broadly construed to include without limitation configuration data, render data, user customization information, user data, and any other data capable of being associated with an application.

In another embodiment, a method for propagating changes from an application instance in a first environment to an application instance in a second environment is provided. The method includes generating a first inventory of data items by associating a unique identifier with each data item accessible to a first version of the application residing in the first environment. A second inventory of data items is generated by associating a unique identifier with each data item accessible to the second version of the application residing in the second environment. For example, the second version may be formed by migrating the first version of the application to the second environment. A set of changes to be made to the second version is determined by comparing corresponding unique identifiers from the first inventory and the second inventory to determine a difference. The difference indicates changes made to the first version of the application that can be propagated to the second version of the application.

In an embodiment, the inventories comprise an inventory services layer that is located within an application deployed in source and destination environments. The inventory services layer can be configured to locate and return configuration data and other data for the application and return it to a requesting agent. The inventory services layer abstracts the requests for data such that the requesting agent does not need to know the location of the data. Using the inventory services layer in both source and destination environments, a propagation tool can compare data sets referenced by corresponding unique identifiers within the inventories and determine the differences between the environments based upon the inventory. The propagation tool may utilize the inventory services layer in the destination environment to propagate changes from one environment to another environment.

FIG. 1illustrates a high-level overview of an interaction between a source environment105and a destination environment145in an embodiment. The source environment105and destination environment145are environments in which portal applications are deployed in association with a central portal. In some embodiments, the source environment105is a testing and deployment environment in which applications are tested and evaluated and the destination environment145is an environment in which applications are deployed for their intended functions.

The applications108,110,120,125are portal applications stored in the source environment that perform various services and functions in association with the central portal. The propagation tool140is a utility that is used to propagate applications and changes to applications from the source environment105to the destination environment145. In one embodiment, the propagation tool140copies an entire application from the source environment to the destination environment to generate one of the applications150,155stored in the destination environment. In an alternate embodiment, the propagation tool140compares an application120in the source environment to a corresponding application150in the destination environment145, determines the differences between the two applications, and modifies the application150in the destination environment to match the application in the source environment105.

FIG. 2illustrates another high-level overview of the application120and its interaction with the propagation tool140and a backup tool205in an embodiment. The application120includes an inventory services layer210and portal Application Programming Interfaces (APIs)215. It additionally includes various inventory data sources, namely external data sources220, extensible Markup Language (XML) files225, datasync data230, internal Lightweight Directory Access Protocol information235, and Content Management (CM) information. The inventory data sources store inventory data, which includes configuration data, render data, user customization information, and user data such as profiles, behavior tracking, and ad views.

The backup tool205is configured to generate backups of portal applications. In some embodiments, when restoring from a backup, the backup tool205compares a current application to an existing backup and modifies those aspects of the current application that differ from those of the backup. When generating a backup, the backup tool can perform the reverse function and modify those aspects of an existing backup that differ from a current application.

In some embodiments, the backup205and propagation140tools operate through a client/server model, with the tools using source data on a client to modify destination data on the server. These tools can store inventory data, configuration differences and proposed configuration changes as XML files. The backup tools can be invoked from a user interface, such as a Graphical User Interface (GUI) or a script. While in the embodiments illustrated herein, the user interface is a GUI, in alternate embodiments any number of interfaces, including text interfaces, voice interfaces, touchscreens, or any other type of interface can be used.

The external data sources220are data sources outside the application120that are used to configure or otherwise support the application. WhileFIG. 2illustrates the external data sources as being within the application, in some embodiments they are associated with the application, but located outside of the application. The XML files225are files storing data and configuration information for the application. The datasync data230is data that has been generated by or stored for a runtime configuration utility. The internal LDAP235stores security values indicating who is able to access resources associated with the application120. The CM240includes graphics and rendering information that is displayed in association with the portal application.

The portal APIs are used to access and manipulate the various inventory data sources220,225,230,235. In some cases, the portal APIs are utilized by the inventory services210, but primarily they are utilized during the normal creation and utilization of the application120.

The inventory services layer210is configured to receive requests from the propagation tool140and backup tool205. These requests take the form of requests to retrieve inventory data stored in the various inventory data sources and requests to modify the inventory data stored in the various inventory data services. The inventory services layer abstracts all of the data access to the sources below it, so that the propagation tool140only needs to submit a request for certain data, and the inventory services layer locates and either provides or modifies the data.

The inventory services layer210performs a certain number of information retrieval services. These services include a listing service that indicates all of the subcategories within a particular category, such as all the portlets defined for a particular web application. The services further include a dependency service that indicates what elements are needed to run a particular application, such as which portlets are associated with particular pages or portals. It additionally includes an identity function that can provide previous names for particular data values. In addition to the functions above that retrieve particular pieces of data, the inventory services layer also includes update services that can delete, modify, or create inventory data. While the above services are discussed for illustrative purposes, the inventory services layer210can be configured to perform any number of retrieval or updating services.

FIG. 3illustrates a high-level overview of a system for propagating changes from a source application to a backup application in an embodiment. The propagation tool140is configured to propagate changes between a source application120in the source environment105ofFIG. 1and a destination application150in the destination environment ofFIG. 1. While in the present embodiment the two applications are located in different environments, in alternate embodiments, the two applications can be located in the same environment. In one embodiment, the source application120is a modified or adjusted version of the destination application150, that having been tested in a testing environment, is having its configuration changes propagated to the destination application.

The propagation tool includes a number of Inventory Services Consumers (ISCs)340,345,380that are configured to communicate with the inventory services layers210,315of the source120and destination150applications. These consumers340,345,380are configured to perform the varying inventory retrieval and update services discussed with respect toFIG. 2and are the primary mechanism by which the propagation tool140interacts with the applications120,150.

Two ISCs340,345gather inventory data from the applications through the inventory services layers210,315and store the information in the inventory archives315. While in one embodiment, this inventory data is selected from the inventory sources described inFIG. 2, in alternate embodiments, other data sources may be utilized as well. The first ISC340develops a “snapshot” of all of the inventory data in the source application120and stores the data in an XML file in the archives350. The second ISC345generates a similar snapshot of all of the data stored in the destination application150and similarly stores the information in the archives350.

An inventory difference engine325reads the XML data stored in the archives350, compares the source and destination inventory data gathered by the ISCs340,345, and determines the differences between the two applications. In some embodiments, the archives350also store historical data about the state of the two applications120,150throughout different points in time and the inventory difference engine utilizes this information to determine the differences between the two applications120,150.

These differences can be viewed through a change election user interface320. The change election user interface provides a graphical listing of some or all differences between the two applications. The differences can be organized according to types of information, sources of information, or any other system of organization.

The change election user interface320can then be utilized to select which inventory data in the source application120should be propagated to the destination application150. In one embodiment, a user can manually select through the user interface which differences will modified or which configuration values that are in the source application120should be propagated to the destination application150.

In an alternate embodiment, a user can designate preselected rules which indicate which differences should be propagated from the source application to the destination application and which changes should be ignored.

A resolver360allows the designation of post-processing changes to be performed on various pieces of inventory data once the data is on the destination server. For example, an administrator adding a portlet to a desktop page in staging could set a rule that any visitor-customized view of the page should updated to view the new portlet. A transform engine355can designate changes that should be performed on inventory data as it is transferred to a new environment.

The changes that are selected are then stored in a change manifest.xml file by a first change manifest persistor365. While in the present embodiment, the changes are stored in an XML file, in alternate embodiments, any number of file formats can be used.

The propagation tool user interface allows a user to invoke a propagation request. A second change manifest persistor385reads all of the changes stored in the change manifest370and passes them to a third ISC380. The third ISC380updates the relevant inventory data in the application150through its inventory services315. At this point, any requested changes have been propagated from the source application120to the destination application.

FIG. 4Aillustrates a flowchart that provides a high-level overview of processing for propagating changes to an application in an embodiment. The technique for propagating changes shown inFIG. 4Ais operable with a propagation tool, such as propagation tool140ofFIG. 1, for example. As shown inFIG. 4A, a first inventory of data items is generated by associating a unique identifier with each data item accessible to a first version of the application residing in the first environment (block402). A second inventory of data items is generated by associating a unique identifier with each data item accessible to the second version of the application residing in the second environment (block404). In an embodiment, the second version can be formed by migrating the first version of the application to the second environment. In other embodiments, the versions may be created independently or derived from a third common version or the like. A set of changes to be made to the second version is determined (block406) by comparing corresponding unique identifiers from the first inventory and the second inventory to determine a difference. The difference indicates changes made to the first version of the application that can be propagated to the second version of the application.

FIG. 4Billustrates a flowchart that provides a high-level overview of processing for determining changes to propagate in an embodiment. The technique for propagating changes shown inFIG. 4Bis operable with a propagation tool, such as propagation tool140ofFIG. 1, for example. As shown inFIG. 4B, a unique identifier is determined for at least one item of information related to a first version of an application to form a first inventory associated with the first version of the application (block412). In response to receiving a second inventory comprising at least one unique identifier for at least one item of information related to a second version of the application, a set of differences between the first version of the application and the second version of the application is determined (block414) by comparison of the first inventory and the second inventory. The set of differences is provided (block416) as changes to be propagated to a second version of the application.

FIG. 5illustrates a high-level overview of a user interface for performing propagation activities in an embodiment. An object type setting505enables a user to select different types of inventory data to be displayed in a main window510. The main window510displays a text tree listing objects of a particular type. The interface optionally includes a series of color or shaded codes indicating how a particular item differs between the source and destination sites and whether the differences should be propagated to the source application or destination application as indicated in the legend525for the shading codes. The differing items also have markers530indicating whether the changes indicated by the color codes have been accepted or rejected by a user through an acceptance/rejection interface520adjoining the main window500.

Other features, aspects and objects of the invention can be obtained from a review of the figures and the claims. It is to be understood that other embodiments of the invention can be developed and fall within the spirit and scope of the invention and claims.

In addition to an embodiment consisting of specifically designed integrated circuits or other electronics, the present invention may be conveniently implemented using a conventional general purpose or a specialized digital computer or microprocessor programmed according to the teachings of the present disclosure, as will be apparent to those skilled in the computer art.

Included in the programming (software) of the general/specialized computer or microprocessor are software modules for implementing the teachings of the present invention.