GB2333865A - Synchronised updating of interoperating software - Google Patents

Abstract

Provided is a method and mechanism for automatic updating of computer programs and synchronising updates of computer programs and their pre-requisite programs to maintain interoperability. Conventionally, computer programs have been distributed on a recording medium for users to install on their computer systems. Each time fixes, additions and new versions for the programs were developed, a new CD or diskette was required to be delivered to users to enable them to install the update. More recently some software has been downloadable across a network, but the effort for users obtaining and installing updates and the effort for software vendors to distribute updates remains undesirable. The invention provides an updater agent which is associated with a computer program and which accesses relevant network locations and automatically downloads and installs any available updates to its associated program if those updates satisfy predefined update criteria of the updater agent. The updater agents are able to communicate with each other and the update process include the updater agent of a first computer program determining whether pre-requisite programs require updating to maintain interoperability and then requesting updates to the first program's pre-requisites programs when required.

Description

A METHOD AND A MECHANISM FOR SYNCHRONISED UPDATING OF INTEROPHRATING SOFTWARE Field of Invention The present invention relates to synchronised updating of interoperating computer programs to maintain interoperability when the programs are updated.

Background Software has conventionally been distributed in the form of programs recorded on a recording medium such as a diskette or compact disk. Customers buy the recording medium and a licence to use the software recorded on the medium, and then install the software onto their computers from the recording medium. The manufacture and distribution of the pre-recorded recording media are expensive, and this cost will be passed on to the customer. Also, the effort for customers of ordering or shopping for the software is undesirable.

The distribution cost is particularly problematic because most software products are frequently updated, both to correct bugs and to add new features, after the software has been delivered to the user. Some types of software products are updated many times each year. The cost of sending a new diskette or CD to all registered customers every time the software is upgraded or corrected is prohibitive and, although many customers want their software to be the most up-to-date, highest performance version and to be error free, not all customers want to receive every update. For example, the vendor may charge more for updates than the customer wants to spend, or new versions may require upgrading of other pre-requisite software products which the customer does not want to buy, or migrating to new versions may require migration of data which would disable the customer's system for a period of time.

Thus, software vendors tend to publicise the availability of new versions of their software and leave it for the customer to decide whether to purchase the latest upgraded version. For some software products, however, it is appropriate for the software vendor to proactively send out upgraded versions, or at least error correction and enhancement code (known as "patches") for their software products.

Whatever a particular company's policy, significant costs and effort are involved in releasing these various types of software updates.

Increasingly, software distributors are using the Internet as a mechanism for publicising the availability of updates to their software, and even for distributing some software. The Internet is a network of computer networks having no single owner or controller and including large and small, public and private networks, and in which any connected computer running internet Protocol software is, subject to security controls, capable of exchanging information with any other computer which is also connected to the Internet. This composite collection of networks which have agreed to connect to one another relies on no single transmission medium (for example, bidirectional communication can occur via satellite links, fiber-optic trunk lines, telephone lines, cable television wires and local radio links).

The World Wide Web Internet service (hereafter 'the Web) is a wide area information retrieval facility which provides access to an enormous quantity of network-accessible information and which can provide low cost communications between Internet-connected computers. It is known for software vendors' customers who have Internet access to access the vendors' Web sites to manually check lists of the latest available versions of products and then to order the products on-line. This reduces the amount of paperwork involved in ordering software (and is equally applicable to other products) . Some companies have also enabled their software to be downloaded directly from a Web site on a server computer to the customer's own computer (although this download capability is often restricted to bug fixing patches, low cost programs, and demonstration or evaluation copies of programs, for security reasons and because applying patches tends not to require any change to pre-requisite software or any data migration).

Information about the World Wide Web can be found in "Spinning the Web by Andrew Ford (International Thomson Publishing, London 1995) and "The World Wide Web Unleashed" by John December and Neil Randall (SAMS Publishing, Indianapolis 1994). Use of the www is growing at an explosive rate because of its combination of flexibility, portability and ease-of-use, coupled with interactive multimedia presentation capabilities. The www allows any computer connected to the Internet and having the appropriate software and hardware configuration to retrieve any document that has been made available anywhere on the Internet.

This increasing usage of the Internet for ordering and distribution of software has saved costs for software vendors, but for many software products the vendor cannot just rely on all customers to access his Web pages at appropriate times and so additional update mechanisms are desirable.

As well as the problem of manufacture and distribution cost associated with distributing media, there is the problem that customers typically need to make considerable proactive effort to find out whether they have the best and the latest version and release of a software product and to obtain and apply updates. Although this effort is reduced when Internet connections are available, even a requirement for proactive checking of Web sites is undesirable to many users since it involves setting up reminders to carry out checks, finding and accessing a software provider's Web site, navigating to the Web page on which latest software versions and patches are listed, and comparing version and release numbers within this list with the installed software to determine whether a relevant product update is available and to decide whether it should be ordered. There may be an annoying delay between ordering an update and it being available for use, and even if the update can be downloaded immediately the task of migrating to an upgraded version of a software product can be difficult. If these steps have to be repeated for every application, control panel, extension, utility, and system software program installed on the system then updating becomes very tedious and time consuming. Therefore, manual updating tends not to be performed thoroughly or regularly.

There is the related problem that software vendors do not know what version of their software is being used by each customer. Even if the latest version of their software has been diligently distributed to every registered customer (by sending out CDs or by server-controlled on-line distribution), there is still no guarantee that the customer has taken the trouble to correctly install the update. This takes away some of the freedom of software developers since they generally have to maintain backward compatibility with previous versions of their software or to make other concessions for users who do not upgrade.

It is known in a client-server computing environment for a systemadministrator at the server end to impose new versions of software products on end users at client systems at the administrator's discretion. However, this has only been possible where the administrator has access control for updating the clients system. This takes no account of users who do not want upgrades to be imposed on them.

Yet a further related problem is that software products often require other software products to enable them to work. For example, application programs are typically written to interoperate with a specific operating system. Since specific versions of one product often require specific versions of other products, upgrading a first product without upgrading others can result in the first product not working.

"Insider Updates 2.0" is a commercially available software updater utility from Insider Software Corporation which, when triggered by the user, creates an inventory of installed software on a user's Apple Macintosh computer and compares this with a database of available software update patches (but not upgraded product versions) and downloads relevant updates. "Insider Updates" shifts the responsibility for finding relevant updates from the user to the database maintainer, but the access to update patches is limited to a connection to an individual database and the tasks of scanning the Internet and on-line services to find updates and of maintaining the database of available updates require significant proactive effort. "Insider Updates" does not install the updates or modify the user's software in any way. "Insider Updates" does not address the problem of unsynchronised pre-requisite software products.

A similar product which scans selected volumes of a computer system to determine the installed software and which connects to a database of software titles for the Apple Macintosh, but does not download updates, is Symmetry Software Corporation's "Version Master 1.5".

An alternative update approach is provided by "Shaman Update Server 1.1.6" from Shaman Corporation, which consists of: a CD-ROM (updated and distributed monthly) that users install on a PowerMac file server; client software for each Macintosh computer to be inventoried and updated; and means for accessing an FTP site storing a library of current updates.

"Shaman Update Server" creates an inventory of networked computers and downloads and distributes latest versions of software to each computer.

Network administrators centrally control this inventory and updating process. The distribution of CD-ROMS has the expense problems described earlier.

Marimba Inc's software product "Castanet UpdateNow"'M' implements a combination of transmission of updates to client systems and support for the development of client applications following the instructions of administrator defined update command files to achieve either centralised or user controlled update management. Castanet UpdateNow does not provide for synchronized updating of collaborative software products.

Novadigm Incus "Enterprise Desktop Manager"M (EDM) provides for desktop software packages to be updated by means of an 'actual state' model and a 'desired state' model, which are administrator-created definitions of existing and desired desktop configurations. These object models are placed on a server computer and the server, at some predefined time, communicates with client computer systems and compares their actual state model and desired state model. The differences are translated into a list of required resources (software components, configuration files, etc) which are then downloaded and installed on the client system. EDM provides a centralised resource management which relies on server control and manual effort by an administrator to set and test configuration models and to install update resources at the server.

Summarv of Invention According to a first aspect of the invention there is provided an updater component and a method, implemented by an updater component installed on a computer system connected within a computer network, for synchronising updates to computer programs installed on the computer system, the method comprising: in response to initiation of an update of a first one of said installed computer programs, the updater component accessing a list of said first computer program's pre-requisite computer programs, comparing the listed pre-requisite computer programs with computer programs installed on the computer system, and determining positively or negatively whether performing the requested update of the first computer program requires updating of pre-requisite computer programs; and if the determination is positive, the updater component initiating an update of said pre-requisite computer programs.

Controlling synchronisation of updates of computer programs and their pre-requisite programs by means of an updater component installed on the local system represents an improvement over prior art methods which implement server-controlled distribution of updates since a greater degree of automation and client control is achievable. With known servercontrolled distribution, synchronisation of updates is only possible with manual setting of configuration models which define desired desktop configurations (as well as installation and testing of update software at a distribution server), followed by server-controlled distribution. The predefinition and maintenance of desired state desktop configurations represents a significant overhead. with the present invention, updating of computer programs and their pre-requisite programs can be initiated and controlled by a locallyinstalled updater component which accesses a list of the pre-requisite products for each enhanced version of the programs. Initiation of an update may be in response to a timer expiry for periodic update attempts, or may be part of the computer system's boot-up procedure, or may be at other times as defined by an update policy for the system.

According to a second aspect of the invention, there is provided a method of updating computer programs and an updater component for use in updating computer programs installed on a computer system connected within a computer network, the updater component including: means for initiating access to a first set of identifiable network locations at which are provided identifications of software resources required for applying updates to at least a first computer program and identifications of any computer programs which are pre-requisites for the operation of said first computer program when updated; means for comparing the identified software resources and identified pre-requisite computer programs with computer programs installed on said computer system, to identify computer programs to be updated; means for initiating access to a second set of identifiable locations within the network (which may be the same locations as the first set, and either 'set' may be a single location) at which are provided said identified software resources, to retrieve said identified software resources for applying updates; means for triggering updating of said pre-requisite computer programs; and means for applying updates to said installed computer programs using the retrieved software resources.

The triggering of updating of pre-requisite computer programs is preferably implemented by the updater component of a first computer program communicating an update requirement to an updater component of the identified pre-requisite computer program. According to a preferred embodiment of the invention, updater components register themselves with a repository within the computer system when the updater components are installed, and installation of updater components is preferably an integral part of installation of the updater component's associated computer program. Since the updater components for all installed computer programs register with the repository, each updater component is identifiable and contactable by other updater components by reference to registration information in the repository.

A distinct advantage of the present invention over servercontrolled update mechanisms which rely on administrator defined system configurations is that the present invention has the flexibility to automatically deal with any depth of inter-dependency in the relationship between pre-requisite products. That is, updating a first program may require updating of a second, which may require updating of a third, and this can be implemented by updater components communicating their update requirements to each other and consequent triggering of updates without any input from the administrator or user.

Furthermore, the invention according to the preferred embodiment deals with cyclic dependencies (such as where a first product A at version 2.1 requires product B at version 2.1, and B at 2.1 also requires A at 2.1). Indeed, the method of the present invention according to the preferred embodiment imposes no constraint over the topology of the update sequence of mutually dependent interoperating products.

An updater component according to a preferred embodiment of the invention thus controls upgrading of, and fixing of bugs within, an associated software product or products automatically without requiring any interaction by the user after an initial agreement of update criteria. The update criteria can be associated with the products' licensing terms and conditions. This ensures that users who adopt a suitable update policy can always have the most up-to-date software available, with errors being corrected automatically from the viewpoint of the user. The user does not need to know where software updates come from, how to obtain them or how to install them since the update component takes care of this. The software vendor avoids having to ship special CDs or diskettes to correct errors or provide additional features; the vendor can easily release code on an incremental basis such that customers receive new product features sooner and with no effort.

An updater component according to a preferred embodiment of the invention performs a comparison between available software updates and installed software on the local computer system to identify which are relevant to the installed software, compares the available relevant updates with update criteria held on the local computer system (these update criteria are predefined for the current system or system user), and then automatically downloads and applies software updates which satisfy the predefined criteria.

This automatic applying of software updates preferably involves installing available software patches and/or upgraded versions in accordance with both the predefined update criteria and instructions for installation which are downloaded together with the program code required for the update. This feature of executing dynamically downloaded instructions provides flexibility in relation to the types of updates that can be handled by an updater component. It can also be used to enable a single generic updater component to be used with many different software products. Alternatively, the installation instructions for certain software updates may be pre-coded within the updater component.

The "software resources are typically a combination of program code, machine readable installation instructions and any required data changes such as address information.

A system according to the invention preferably retrieves update resources for implementing an update of an installed computer program by sending an update request to one or more computer systems at network locations at which the required software resources are provided (together with a list of update resources and pre-requisites). The information used to identify the network locations may be explicit network location information held by the updater component, or it may be a software vendor name or any other information which can be used as a search parameter for identifying the location. In the preferred embodiment, the information is a product identifier which is provided by the updater component to a network search engine to initiate a search to identify the relevant network location at which are stored software resources for implementing an update to that product. This search may be performed by a conventional Internet (or other network) search engine which is called by the updater component. When the search engine returns an identification of the network location, the updater component retrieves from this location a list of available relevant updates, checks the list against the locally held software product version and against predefined update criteria, and retrieves the update resources onto the local computer system if those criteria are satisfied.

According to a preferred embodiment of the invention, a standardised naming convention is used for software resources from which to build software updates, and the updater component can search for these resources on a Network Operating System filesystem. This allows software resources to be stored at multiple locations to mitigate against network availability problems and makes it easier for developers and distributors to provide their error-fixing patches and upgraded versions of software products. For example, a developer can make new software updates available via a public network disk drive on their LAN using a known filename or via a published Uniform Resource Locator (URL) which can be searched for using known key words.

Updater components are preferably an integral part of the products they will serve to update. Hence, the updater component is distributed to software users together with an initial version of a software product, the updater component then automatically obtaining and applying software updates in accordance with preset criteria (such as a time period between successive searches for updates, and whether the particular user has selected to receive all updates or only certain updates - such as to receive updating patches but not replacement product versions for example).

The updater component's update capability preferably includes updating itself. Indeed, the update criteria may be set such that the updater component always accesses appropriate network locations to obtain updates to itself before it searches for software resources for updating its associated software products.

An updater component according to the invention preferably includes means for checking whether pre-requisite products are available, and are synchronised to the required version, as part of the process of selecting an update path for the current product. In a preferred embodiment, as well as checking their availability, the updater component is capable of instructing the updater components associated with pre-requisite software products to initiate updates to their software where this is the agreed update policy. If each software product's updater component is capable of triggering updates to pre-requisite products, then updates can ripple through the set of installed software products without the user having to be involved in or aware of the updates. This capability is a significant advantage over prior art updater agents which do not deal with the problem of unsynchronised software versions when one updates, and supports the increasing desire within the software industry for collaboration between distributed objects to perform tasks for the end user.

The updater component preferably also includes a mechanism for verifying the authenticity of downloaded software, using cryptographic algorithms. This avoids the need for dedicated, password-protected or otherwise protected software resource repository sites. The software resources can be anywhere on the network as long as they are correctly named and or posted to the network search engines.

Thus, the present invention provides an agent and a method for synchronising software updates which significantly reduces the cost and effort for software distributors of distributing and tracking software updates and significantly reduces the effort for system administrators and end users of applying updates to installed software.

Brief Descristion of Drawings The present invention will now be described in more detail, by way of example only, with reference to the accompanying drawings in which: Figure 1 is a schematic representation of a computer network including a local computer system having an installed updater component, server computers storing lists of available updates and storing software resources for applying updates, and a search engine for locating the servers; Figure 2 is an example of a software vendor's list of their software versions and the resources and prerequisites for building from one version to another; Figure 3 represents the sequence of operations of an updater component according to an embodiment of the invention; and Figure 4 is a further representation of the sequence of operations of an updater component.

Detailed Description of Preferred Embodiments As shown in Figure 1, an updater component 20 is installed in system memory of a conventional network-connected computer system 10, together with an associated computer program 30. The updater component may have been delivered to the user of the local computer system on a storage medium (diskette or CD) for him to install, or it may have been explicitly downloaded from another computer system. In preferred embodiments of the invention, updater components are integrated within the computer program they are intended to maintain (or are otherwise delivered via the same mechanism and at the same time as their associated program). The updater component is then installed as part of the installation procedure of its associated program, such that the user is not required to take any special action to obtain or activate it. The installation of each updater component includes the updater component registering itself with the operating system or another repository 40 on the local computer system. Thus, at least the updater components on the local system are identifiable and contactable by address information, and/or their product identifier, within the register entry. In alternative embodiments of the invention, the repository 40 may be a central or distributed repository for the network, as will be discussed below.

It is a feature of the preferred embodiment of the invention that each updater component can locate, can be located by, and can communicate with other updater components which manage other software products. This capability is used when one updater component requires another one to update to a specific level before the former can execute its own update, as will be discussed below. This is enabled by the updater components registering within the operating system or other repository 40.

In the preferred embodiment, each registration entry contains two items: the updater path and the updater network address. The path is the location of the updater component binary file so that the updater component can be launched by the operating system during the boot up process. This ensures that the updater component is always active and ready to perform work or handle requests issued to it from other updater components. The network address is the address used by components on other computer systems in the network to locate it on the network and to communicate with it.

An example of such registration using a UNIX (TM) operating system and the TCP/IP protocol suite uses the following naming convention for updater components: SoftwareVendorNamet~product~name+~updater.

Path registrations can be entered in the UNIX/etc/inittab file to store the path entry. When, for example, the updater component for IBM Corporation's DB2 (TM) database product is installed it will add an entry to the /etc/inittab file of the form: ibm~db2pe~updater:2:respawn:/usr/abin/db2~updater~binary Every time the computer system reboots it will read this file and launch the DB2 updater component. The "respawn" keyword in the updater entry ensures that, should the updater component process fail for some reason during general system operation, it will be restarted by the operating system automatically. This approach will ensure that all updater components for all installed applications are always active.

Network Location registrations can be entered in the UNIX/etc/services file. For example when the DB2 updater component is installed it will add an entry to the /etc/services file of the form: ibm~db2pe~updater 5000/tcp #net location of DB2 updater component When another updater component wishes to communicate with the DB2 updater component it will find it by searching this /etc/services file for the DB2 updater component name ibm~db2pe~updater (actually done indirectly by the UNIX call getservbyname() - the name is built by the caller according to the standard naming convention) . When it is found it knows that the DB2 updater is listening for connections on port number 5000 and will use the TCP protocol. This allows the updater component in question to establish a link to the DB2 updater component and start a conversation (described later).

For an updater component to find and talk to another updater component on another remote machine the above information would have to be augmented by having a repository 40' which is accessible from both machines (preferably a central or distributed database accessible from anywhere in the network, such as a Web Page or pan-network file) and is available to all updater components that require it. Entries would be of the form updater~name machineipgddress (OR DNS entry), port number, protocol.

For example, the manufacturing department of an organisation may have three computer systems on which distributed software products collaborate with each other, the systems being called a, b and c. Typical entries in the Web page or file manufacturing~collaborators.html might be: ibm~catia~updater a.mznufacturing.com 5000 tcp ibm~db2pe~updater <RTI ID=13

Updater components include data fields for an identifier and version number for their associated software products. The updater components may be delivered to customers with these fields set to null values, and then the installation procedure includes an initial step of the updater component interrogating its software product to obtain an identifier and current program version and release number. Alternatively, the software vendor may pre-code the relevant product ID and version number into the updater component.

The system 10 of Figure 1 is shown connected within a network 100 of computers including a number of remote server systems (50,50') from which software resources are available for applying updates to programs installed on the local system 10. Each server system includes within storage a list 60 of the latest versions of, and patches for, software products which are available from that server. Each vendor is assumed here to make available via their Web sites such a list 60 of software updates (an example of which is shown in Figure 2) comprising their product release history, in a format which is readable by updater components, and to make available the software resources 70 required to build the releases from a given level to a new level (this transition from a software product release to a new level will be referred to hereafter as a 'growth' path). The entries in the software updates list 60 include for each software product version 110 an identification 120 of the software resources required for applying the update and an identification 130 of its prerequisite software products and their version numbers. In some cases, the required resources are complete replacement versions of software and associated installation instructions, and deletion instructions for the software being replaced.

In other cases, the resources comprise patch code for modifying an existing program (e.g. for error correction) and the patch's installation instructions.

For the current example, we will assume that the network 100 is the Internet, although the invention may be implemented within an Intranet or any computer network. Also shown within the network 100 is a server system 80 on which a search engine 90 is installed for use in finding update source locations on the network. This is shown located remotely from the local system 10, although it need not be. In the Figure, each updater component 20 is shown associated with a single program 30, and it is a feature of this embodiment of the invention that all installed software products have associated updater components which manage them, but neither of these features is essential to the invention as will be explained later.

The operation of an updater component will now be described, with reference to Figures 3 and 4. When an installed updater component executes, in response to completion of a cycle period or in response to a request from another software product's updater component, its first action is to initiate 200 a search for available updates to the particular software product. It provides to one or more search engines 90 search arguments comprising the product identifier and product version release number obtained by the updater component at install time.

Software vendors wishing to benefit from the services of the updater component provide via their Web sites a list 60 of available product updates referenced by product identifier and release number 110 (or some other consistent naming convention is used). The search identifies the relevant Web site 140 on which the update information is available. A URL identifying the relevant Web site 140 for update information is returned 210 to the updater component as a result of the search. If the initial attempt to start a search engine is unsuccessful, then the updater component will attempt to start a different search engine (which may be in a different geographical location to the first), but in alternative embodiments could wait for a preset time period and then retry.

The updater component uses the URL to access 220 the list 60 and downloads 230 a file 160 comprising the portion of the list 60 of available updates which relates to the particular product. The updater component then performs steps 240-280 as shown in Figure 4. Each file 160 contains message digests (e.g. MD5) which are digitally signed. The retrieved file 160 is then analyzed 240 using a digital signature checking algorithm (such as the algorithm described in US patent 5231668). This verifies that the file 160 represents the correct software updates list for the particular software product, and that the file has not been tampered with since signing. Also, checking for the digital signature is a useful way of filtering the results of the search since these may include a plurality of Web page URLs other than the correct one (the search may find other pages which have a reference to the named product version, including pages not published by the software vendor).

If an attempt to download and verify a file is not successful, then the updater component moves on to the next URL found in the search.

The updater component then performs on the local computer system a comparison 250 between the current installed software product's identifier and release number and the listed available updates in the retrieved file 160. This comparison determines possible growth paths from the current to updated versions, but these possible growth paths are then compared 260 with predefined update criteria, and any possible paths which do not satisfy the update criteria are discarded. Thus, the updater component determines whether it is possible to migrate from a current software product to the available new versions and whether it is possible to apply patches to the current version under the currently agreed licence terms and conditions.

For example, the software product licence may enable migration to any future version of the product and application of any available patches, or only migration up to a specified version, or it may only permit applying of available patches which modify or correct errors in the current version. Possible update paths which are unavailable due to current license limitations are notified 270 as a system generated message sent to the software asset manager (who may be an end user or IT procurement manager) of the currently installed version, to enable them to make decisions about whether the current licence is adequate.

As well as licence restrictions as to the updates that are possible, an updater component's update criteria or growth policy includes a cycle period (for example weekly or monthly) and criteria for determining which of a plurality of possible growth paths to select (such as always select latest version permitted by licence, or always select latest patch and only notify availability of new versions, or only select new versions if prerequisite software is already available on local system). The growth criteria may also include control information such as when to upgrade to new versions that are downloaded by the updater component - if data migration is required when migrating to a new software product version it may be essential for this to be done outside of office hours or only at a single scheduled time each month or each year and this can be controlled by the updater component.

The growth policy definition may also include a parameter determining that updating of pre-requisite software products should be requested when required to maintain synchronisation with the current product. This will be described in more detail below. Persons skilled in the art will appreciate that there is great flexibility in the criteria that can be set and applied by the updater component.

The updater component then decides 280 on a particular growth path (i.e. which available version to upgrade to) from the set of possible growth paths using the update criteria. For example, the updater component may select the highest possible version or release number of the available updates which is permitted by the update criteria, if that is the update policy.

The updater component performs 290 (see Figures 3 and 4) a scan of the operating system file system to check whether the required software resources are already available on the local computer system. The required resources are the software update artifacts required to bring the current application software to the new level, and the software updates required for updating pre-requisite software to required levels.

Each updater component associated with pre-requisite installed products is contacted 300 to ensure (a) that it is installed on the local system, and (b) that it is at or greater than the version level required for interoperability. If all required resources are available locally (or on another machine in the case of software relying on some pre-requisite software operating on a remote machine), and have been verified, then the updater component progresses to the step 310 (see Figure 4) of building the updated software version. If not, the update component must obtain the required resources.

As shown in Figures 3 and 4, if required software resources for building the updated version are not found on the local system, the updater component submits 320 a further request to one or more search engines to find the required resources. The search engine returns 330 one or more URLs and the updater component uses these to retrieve 340,350 the software resources into storage of the local computer system. At this stage, the updater component or the user need not have any knowledge of what corrections or enhancements may be included in the new version - the update criteria determine what type of updates are required such that the user is spared the effort of studying the content of every update. In practice, it is desirable for users to be able to determine the effects of updates and so the software resources for the update include a description of these effects which a user or administrator can read.

As examples, the software product to be updated may be a word processor application program. If the word processor as sold missed certain fonts or did not include a thesaurus, patches may subsequently be made available for adding these features. The updater component has the capability to add these to the word processor, subject to the update criteria.

In alternative embodiments of the invention, the search for required software resources is unnecessary following the initial search for the updates list (or is only necessary where there are pre-requisite software products as well as patches or new versions for the current product - see below). This is because the update software resources required directly by the current product are stored in association with the list of required resources. That is, the list includes a pointer to the network location of the required resources such that a selection of a growth path from the list involves a selection of a pointer to the network location of the required updates (and possibly also pointers to the locations of pre-requisite software products).

A second verification by digital signature checking is performed 360 (see Figure 4), this time on the downloaded resources. After verifying 360 the legitimacy of the downloaded resources, the updater component automatically builds 310 the installation in the target environment in accordance with the update policy. In practice, this may require information from the user such as an administration password, or a database usage parameter value, but in the preferred embodiment of the invention installing of the downloaded code is automatic in the sense that it does not require the user to know or obtain from elsewhere any installation information and in that it generally enables the user to be freed from making any decisions at run time if the predefined update criteria enable the updater component to automatically apply updates.

It is well known to include machine readable installation instructions encoded in a shell (for example as Script, or an interpretive language such as PERL, or an executable such as setup.exe in the case of applications on Microsoft's Windows (TM) operating system).

Updater components according to the invention will download 350 the machine readable instructions together with the relevant software resources and will automatically execute them 310. The updater component thus automatically processes installation instructions, avoiding the input from a person which is conventionally required. The Scripts can be adapted to reuse information gleaned from the first human installer who installed the first version of the updater component (for example, information such as user name and password of application administrator, installation directory, etc).

The method of updating according to the preferred embodiment of the invention requires software vendors to organise the software resources required to build from one product level to another. For example, a move from version 1.1.1 to 1.1.4 would typically include a series of patches to be applied, and the required order of installation if any would advantageously be encoded in machine processable installation instructions. The user is then spared the effort and the risk of human error which are inherent in methods which require the user to control the order of application of fixes and enhancements. The problem of how to migrate from one product level to another is thus dealt with by the software vendor instead of the customer, and updater components can only move to levels supported by the vendor (i.e. those growth paths published by the software vendor for a specific existing product level).

The updater generates 380 a report and writes 390 to log records, and then quits execution 400 (in the preferred embodiment the updater goes into a sleep or idle state) until activated again 410 upon expiry of a predetermined update cycle period (the repeat period parameter is configured when the updater component is installed).

Structure of updater component The structure of an updater component comprises data, methods for operating on that data, and a public application programming interface (API) which allows other updater components to contact and communicate with it. This structure will now be described in detail.

UPDATER COMPONENT DATA: The updater component includes the following persistent data: Product~ID : an identifier of the software product which is managed by this updater component Current~Installed~Version : a version identifier for the installed software (e.g. version 3.1.0) Current~License : a version identifier corresponding to the software product version up to which the current software license allows the user to upgrade (e.g. version 4.0.z). Alternatively, this may be a licence identifier (e.g. LIC1) for use when accessing machine readable licence terms.

Installation~Environment: a list of attribute name/attribute value pairs.

This is used by the updater component to store values entered by the user when the updater was used for the first time. For example, the updater installation userid and password, possibly the root password, the installation directory, the web-proxy server address, search engine URLs, log file name, software asset manager e-mail address etc. This data will be re-used when subsequent automatic updates are required.

Growth policy parameters: a. Growth~Cycle: data determining whether the updater component should attempt to update its software product every day, week or month, etc. b. Growth~Type: data determining whether the updating is limited to bug fixing and enhancements (i.e. patches) only or requires upgrading to the latest release in each growth cycle. c. Force~Growth: (YES/NO) a parameter determining whether to force other software resources to upgrade if that is a pre-requisite for this software to upgrade. (Some implementations will provide more flexible controls over forcing other software to update than this simple YES/NO) Last~Growth~Time: Date and time when updater component last executed The updater component also includes the following non-persistent data: Possible~Growth~Paths: transient data representing the available upgrade paths (e.g. version numbers 3.l.d, 3.2.e, 4.0.a) Update~Thread: string containing the update thread information. It has the following structure: < Product~Id #1,version *1 > < Product~Id #2, version*2 > < Productid *n- l,version#n-1 > < Product~id &num;n,version&num;n > The thread information lists the products (i.e.

Product~Ad #x) which are participating in the synchronisation transaction on this component and the versions they are attempting to grow to (i.e. version&num;y). It represents a thread of forced updates originating from component 1 (or root component) which is attempting to update unilaterally through component 2 which is being forced to update by component 1 and component 3 which is being forced to update by component 2 and so on to the nth component being forced by the n-lth component. It is the nt component in this Update thread which is forcing this component to update to a specific level. This string is empty if this is the first component attempting to update unilaterally (i.e. it is not being forced to update). This information is assembled to guard against cyclic dependencies in between products. See the "example of update synchronisation" section to find out how it is used to accomplish this.

PRIVATE UPDATER FUNCTIONS: The updater component logic includes the following methods: Discover~Possible~Growth~Paths() Search for Growth Path information for this software product on the Internet (or Intranet or other network).

This search method initiates a search via a standard search engine server. The information returned is a list of newer versions and associated pre-requisite product information The Growth~Path information is then reduced in accordance with the Growth policy parameters. For all members in the Growth~Paths list, a check is performed of whether appropriate versions of pre-requisite products are available on the local and/or remote computer. The updater components managing these pre requisite products are accessed and forced to grow if this is the policy.

If all pre-requisite products exist locally at the correct level, or are available remotely on the network and there is with a "force growth" policy, then i identifiers for newer versions of the software product are added to the Possible~Growth~Paths list.

Avoiding cyclic update deDendencies If one of the pre-requisite software components is found in the UpdateThreads string with a version which complies with the required version level then it is deleted from the pre-requisite list to ensure that a force update is not attempted on it.

If the prerequisite software is in the Update~thread list but with an insufficient version number then this is not a valid growth path. The final chosen growth path will have all pre-requisite software components elements which are either already available locally or already specified in the current Update~Thread or can be forced to update to the required version via an in place force update policy.

Decide Growth Path() Interpret the growth policy and select a single growth path. Some implementations of the invention will involve user interaction to select the path, for example if there are considerations such as whether to force updates to other programs.

Get Resources(Parameter: Chosen~Growth~Path) Given Chosen~Growth~Path (e.g.3.2.0), search for required resources (Parameters ProductID, Current~Installed~Version, Chosen~Growth Path), download all resources to local computer. This will include software required for the new version plus machine processable installation instructions.

Install Resources() Process installation instructions including installing required files in correct locations, possibly compilation of the files and modifying the configuration of the existing system to accommodate the software, logging all actions to a file (and enabling an "uninstall" method to undo all actions).

Grow () Initiates methods: Discover~Possible~Growth~Paths() //uses Update~Thread information to avoid update //dependency cycles if no possible growth paths exist then updater component becomes idle else Decide~Growth~Path() Get~Resources(Parameter: Chosen~Growth~Path) Install~Resources().

Then Grow() writes all completed actions to log and finishes execution of the updater component. The updater component becomes idle either until time to check again for new update requirements or until prompted by another updater component to do so.

PUBLIC UPDATER COMPONENT API: The updater component includes the following public API. These functions would be callable using existing network communications software, such as remote procedure calls, message oriented middleware, ORB (Object request broker), etc.

Get~Release() This function is called by other updater components and returns the release level of the product managed by this updater component.

Update(update thread,new~level) Other updater components call this function to move the product managed by this updater component to a new level indicated by the new~level parameter value. The update~thread parameter is a string containing the update thread information. It is of the form < product~Id,version > < productId,version > ... . The thread information lists the products (i.e. Product Id &num;x) which are participating in the synchronisation transaction and the versions they are attempting to grow to (i.e. version#y).

When a software component calls this function on another software component it must append its own Product~Id and version to its copy of the string before passing it as a parameter (This string will only contain one Product~id and version if the calling component is the root component or first component in the update task). This will call the private function Grow().

Receive Event(event details) When an updater component receives a request to update, it must inform the calling updater component when it has completed the update or otherwise e.g. if it failed for some reason. The updater component performing the update on behalf of another updater component will call this function of the requesting updater component to communicate success of the update or otherwise. Event details can be a string like "product id, new release level, ok" or "product id, new release level, failure".

The automatic handling of the potential problem of unsynchronised pre-requisite products by enabling forcing of updates (or, if forcing of updates is not part of the update policy, sending of notifications to the software asset manager) is a significant advance over prior art update schemes.

Since the updates list file 160 returned to the updater component in response to an initial search includes an identification 130 of prerequisite software, that information enables the aforementioned examination 290 of the updater component registration database 40,40' to check whether pre-requisite software is available locally or remotely. If it finds all the updater components located locally or remotely, it can be sure that the software pre-requisites are available and it next needs to contact each updater component for each software product to be sure all pre-requisites are at the correct level. If an updater component 20' having a required product identifier for pre-requisite software 30' but not having the required version number is found locally or remotely, and if forcing of updates is the update policy, then the updater component 20 of the first computer program contacts 300 this pre-requisite updater component 20' and requests that it attempt to update its associated prerequisite software product 30'. This updater component 20 can, if necessary, request other updater components of its pre-requisite software to update their versions, and so on.

If at some stage no relevant updater component is found locally or remotely, then a message is sent to the asset manager to inform him/her of the requirement for a new product in order to grow the associated product further. If at some stage during the chain of updater requests to grow to a new level one updater component fails to move to the required level then this failure is reported back to its calling updater component, prompting failure of that component's update operation, and so on back to the updater component which initiated the whole transaction.

Thus, as well as their autonomous behaviour defined by their update criteria, updater components can react to external stimuli such as requests from other updater components.

ExamDle of update synchronisation An example of the implementation of update synchronisation between two products will now be described. This example shows how one updater component can communicate with another to synchronise pre-requisite software so that all products are present and at compatible release levels.

A CORBA (Common Object Request Broker Architecture) ORB (Object Request Broker) is used for location of and communication between two updater components. Using the above public API it is a simple matter for those familiar with the art of CORBA programming to develop communication code so that one updater component can talk to another updater component anywhere on a network. In this example the component updater registration database 40 is a directory or folder available over the network (e.g. via NFS) which contains for each installed updater component a file called taupdater~component~name.iop" (iop stands for interoperable object reference).

This file contains a sequence of bytes which can be converted into a reference to the updater component by any updater component which reads the file using for example the CORBA function: CORBA::Object::~string~to~object() in C++ Furthermore this reference can be to an updater component anywhere on the network as it represents a unique address for the corresponding updater component. When updater component A has manufactured a reference to updater component B then updater component A can call a public API function simply by using, for example, a C++ mapping A- > Get~Release() which will then return the value of the release level of the software managed by the A updater component.

In this example we will consider two products - IBM Corporation's DB2 database product and a Query Tool called "Query Builder", on different machines M and N respectively. (Machines M and N could be the same machine; the present example merely shows that they may also be separate). Both products have updater components which use a CORBA ORB architecture as briefly outlined above. An ORB communication daemon is active on participating systems M and N.

Step 1) Registration phase: The DB2 Updater Component starts when the operating system starts on system M and immediately creates a file called ibm~db2updater.iop (according to some naming standard used to aid subsequent searches for the file) in the network file system folder or directory. This directory could be hosted on any machine and not necessarily M or N. The file contains a series of bytes which can be used to manufacture a reference to the updater component.

[pseudocode] Filehandle = open("/network/filesystem/directory", "ibm~db2~updater.iop"); ReferenceBytes = CORBA::Object::~object~to~string(); vrite(FileHandle, ReferenceBytes); close(Filehandie); QueryBuilder Updater component starts and writes its registration to the same directory or folder, again in this case calling the file ibm~querybuilder~updater.iop.

At this stage both updater components are active and have registered their presence and location in the network directory.

SteD 2).

QueryBuilder attempts to grow from version 1 to version 2 but a prerequisite is DB2 version 2.1 or higher. The following sequence of actions will occur. QueryBuilder is denoted QB and DB2 as DB2.

QB : searches for file ibm~db2~updater.iop (file name manufactured according to standard) in network directory. It finds the file, reads it and

Give up on trying to grow to new version. endif. steP 3).

At this stage we know that DB2 exists somewhere in our set of networked computers. Now we need to know if it is at the right level. We simply do this by executing its public API function Get~Release() defined above, from within the QB updater, the QB updater is therefore a client requesting the DB2 updater to do something for it, i.e. tell it what release it is.

[pseudocode] db2~release = dbref- > Get~Release (); Let us say this returns the value "2.0".

Stes 4) Client Side: The QB Updater Component knows that this is not sufficient , it requires version 2.1. It examines its Force~Growth parameter which is, for example, "YES" meaning it should force pre-requisite software to grow to the level required before it can perform its own update procedure.

Therefore the QB updater tells the DB2 updater to grow to the new release, and then waits until the pre-requisite has grown to the new release or failed in doing so.

Epseudocode] dbref- > Update("QB,2. 0", "2.1", QBref); //the first parameter is the update thread parameter, so far only //one product is participating in the update chain, i.e. Query //Builder which is attempting to grow to version 2.1. The DB2 //updater component will use this information in this parameter to //avoid the problem of update cycles. See server side for how this //information is processed. QBref is a ready made reference to the //QB Updater. It is passed to the DB2 updater so that it can //Quickly send the results, success or failure, when the DB2 //Updater has finished trying to update itself.

EVENT= null; While (EVENT equals null) i do nothing; ) if (EVENT equals "SUCCESS") then attempt to grow software managed by this updater component i.e. Query Builder. else Write failure to log; do not attempt to grow; go to sleep and try later; endif.

Server Side: The DB2 Updater component receives the request to grow. Which it attempts to do.

It reports the result to the calling client (it knows how to contact the calling client as it is receives a reference to the caller in the function call.) [pseudocode] DB2 updater component Update~Thread is set to equal update~thread passed to it via the update call. i.e. Update~Thread = "QB,2.0 //see private grow function for details on how this Update~Thread //information is processed.

DB2 attempts to grow. if Growth Successful then QBRef- > ReceiveEvent("SUCCESS); // Note the implementation of the // function Receive~Event simply sets the variable // called EVENT in the QB Updater component to the // value of the parameter passed in the API call , i.e.

// "SUCCESS" if in this section of the IF statement. else QBREF- > Receive~Event ("FAILURE") end if As noted previously, predefined update criteria may determine which of an available set of updates should be applied and which should be disregarded. The update criteria may include an instruction to the updater component to send a notification to the end user or system administrator when a software update is identified as being available but applying this update is not within the update policy or is impossible.

One of the examples given previously is that the update policy may be not to install full replacement versions of software products since that may require upgrading of pre-requisite software products or migration of data (for example if the software product is a database product), whereas it may be intended policy to install any error-correction patches.

Notification rather than automatic installation of updates may also be implemented where to upgrade one product to a new version would require upgrading of other pre-requisite complementary products.

The update policy can also determine the degree of automation of the updating process, by defining the circumstances in which the updater requests input from the user or administrator.

The execution of a particular example updater component will now be described in more detail by way of example. This updater component's function is to keep an installed product called "Test" totally up-to-date with all released patches, but not to install replacement versions of Test. Firstly, the updater component is configured with the following data instantiations: Product~ ID: Test Current~Installed~Version: 1.0.a Current~License: LIC1 Installation~Environment:"USERID:TestOwner, USERPASSWORD:easy" "INSTALLPATH: /usr/bin/testapp/" Growth~Cycle: weekly Growth~Type: patches, latest, automatically Force~Growth: no Last~GrowthTime: Monday 08/10/97.

The updater then executes weekly, for example each Monday night at 3am (it is the system administrator who decides the timing).

The following represents a possible execution trace for this example updater component.

Example execution trace Step 1) The growth cycle starts: > > > > START : Discoverqossible~Growth~Paths() * Execute search on remote search engine (e.g. Internet Search Engine) using Phrase ("IBM Test 1.0.a Growth Paths") Search returns URL published by software vendor outlining current growth paths for product; * Download URL: File contents are "l.0.b,none; 2.0, other~required productgroduct~id 1.0.c;" * Authenticate URL file using hashing algorithm and digital signature.

If not authentic, return to search for another URL matching criteria * Build growthqath~list : growthqath list = "l.0.b,none; 2.0,other requiredproduct~id 1.0.c;" * Remove all but patch level increases (according to Growth~Policy) from Growthgath list (i.e. only those with the first version and second release number matching 1.0).

* growth~path list = "1.O.b,none;" * For all members in list, ensure prerequisites exist. In this example, all members of list meet this criteria trivially.

(Note : If this was a forced update then the Update~Thread would be examined to see if any pre-requisite component for any path existed already in the Update~Thread, if it does and at a level greater than or equal to the level required by the growth path then that prerequisite is assumed to exist (as will be in place once the update transaction is complete).) * Place candidate growthoaths into Possible~Growth~Paths list = 1.0.b each END : Discover-possible-Growth-paths() Step 2) Next the updater component decides on the Growth Path to pursue: > 2 > > START Decide~Growth~Path() * The growth policy dictates that we should grow to latest patched revision. (In this example, determining the latest revision is trivial i.e. it is 1.0.b) * chosen~growthath = 1.0.b (NOTE : For all pre-requisites which are not already in place at the required revision level, an update is forced on their associated updater agents to make them migrate to the required level. Note that, because items in the Update~Thread are considered to already exist, no software component which is already on the Update~Thread is forced to update - thus preventing cyclic dependencies between products.) < < < < END : Decide Growth~Path() Step 3) The updater component then obtains the required resources to revise the current software level to the new one.

> > > > Get~Resources() * Execute search on remote search engine (e.g. Internet Search Engine) using Phrase ("IBM Test REVISION 1.0.a to 1.0.b RESOURCES").

* Search returns URL say ftp://ftp.vendor-site/pub/test/resources/1.0.a-bfw * Updater downloads file pointed to by URL and places in secure holding area where it verifies authenticity.

* Updater verifies authenticity (using, for example, digital signatures based on RSA algorithm, or any method) If files not authentic, then return to search (see Note 1 below) * Updater unpacks resources into a temporary directory (see Note 2 below). These resources include machine processible installation instructions (for example, instructions written in a script language such as a UNIX shell script or MVS REXX) and files (either binary or requiring compilation) which actually contain the software fix.

< < < < END : Get~Resources() Notes on above tasks Note 1 - To save time the updater looks for a standard file before downloading the URL ,called "signature", which contains the URL ftp://ftp.vendor-site/pub/test/resources/1.0.a-b and a listing of its contents. This is hashed and signed.

Using this signature, the Updater component can quickly establish authenticity of the URL (to some extent) before downloading it and use the information i.e. file listings to corroborate the final downloaded resources after they have been unpacked into the temporary directory. When the final URL is downloaded it is also checked again for authenticity (to guard against someone placing a bogus artefact in an authentic URL location).

Note 2 - Part of the unpacking is that the updater component will examine the installation scripts and modify them based on the contents of its installation environment data where required. For example if the installation instructions were coded in a shell script it will replace all instances of INSTALLPATH with the token ^#/usr/bin/testapp/". Again Naming conventions of attributes are standardised as it the method of token substitution in installation instructions. This makes totally automatic installation possible.

Step 4) The updater component then implements the actual software upgrade: > > > > START Install Resources() * execute the installation instructions.

* update the values of Current Installed Version = 1.0.b Last~Growth~Time = Date+Time.

* send an e-mail to software asset manager informing of installation and whether or not a reboot of the Operating System or restart of the application is required before the upgrade takes affect.

< < < < END Install~Resources() This is the end of this current growth cycle. The seed updates the Last Growth Time value the current time and then exits. The time taken for this cycle could be anything from a few seconds where the updater component found no upgrade paths for the currently installed version to several hours if a totally new release from the current one is to be downloaded and installed together with new pre-requisite software.

An alternative to the embodiment described above in detail does not require an independent updater component for every different software product, but uses a single generic updater component installed on a system together with product-specific plug-in objects and instructions which are downloaded with each product. These objects interoperate with the generic code to provide the same functions of the product-specific updater components described above. It will be clear to persons skilled in the art that the present invention could be implemented within systems in which some but not all application programs and other software products installed on the system have associated updater components, and that other changes to the above-described embodiments are possible within the scope of the present invention.

Claims (18)

1. CLAIMS 1. A method, implemented by an updater component installed on a computer system connected within a computer network, for synchronising updates to computer programs installed on the computer system, the method comprising: in response to initiation of an update for a first one of said installed computer programs, the updater component initiating access to a list of said first computer program's pre-requisite computer programs, comparing the listed pre-requisite computer programs with computer programs installed on the computer system, and determining positively or negatively whether performing the requested update of the first computer program requires updating of pre-requisite computer programs; and if the determination is positive, the updater component initiating an update of said pre-requisite computer programs.
2. 2. A method according to claim 1, wherein the updater component initiates the update for the first installed computer program in accordance with predefined update criteria.
3. 3. A method according to claim 2, wherein the updater component initiates update attempts periodically according to a set cycle period for the computer programs.
4. 4. A method according to any one of claims 1 to 3, wherein the step of initiating access to a list of pre-requisites includes the step of the updater component providing to a network search engine a search parameter for identifying one or more network locations at which are provided a list of software resources required for applying updates and a list of pre-requisite computer programs.
5. 5. A method according to claim 4, including the step of the updater component initiating access to one or more network locations at which are provided the software resources required for applying an update, and the steps of downloading the software resources from said one or more locations onto the computer system and building the first computer program to a new version using the retrieved software resources.
6. 6. A method according to any one of the preceding claims, wherein the step of determining whether updating of pre-requisite computer programs is required includes comparing said listed pre-requisite computer programs with predefined update criteria stored on said computer system.
7. 7. A method according to any one of the preceding claims, including registering updater components with a repository, wherein the step of initiating an update of pre-requisite computer programs comprises the updater component of the first computer program communicating an update request to registered updater components of the pre-requisite computer programs.
8. 8. A method according to claim 7, including the following steps implemented by an updater component in response to an update request from another updater component: initiating access to a list of the updater component's respective computer program's pre-requisite computer programs, comparing the listed pre-requisite computer programs with computer programs installed on the computer system, determining positively or negatively whether performing the requested update of the updater component's respective computer program requires updating of pre-requisite computer programs; and if the determination is positive, initiating an update of said prerequisite computer programs.
9. 9. An updater component for installation on a computer system connected within a computer network, for synchronising updates to computer programs installed on the computer system, the updater component including: means responsive to initiation of an update for a first one of said installed computer programs for initiating access to a list of said first computer program's pre-requisite computer programs; means for comparing the listed pre-requisite computer programs with computer programs installed on the computer system and determining positively or negatively whether performing the requested update of the first computer program requires updating of pre-requisite computer programs; and means for initiating an update of said pre-requisite computer programs if the determination is positive.
10. 10. A computer system including an updater component for synchronising updates to computer programs installed on the computer system, the updater component including: means responsive to initiation of an update for a first one of said installed computer programs for initiating access to a list of said first computer program's pre-requisite computer programs; means for comparing the listed pre-requisite computer programs with computer programs installed on the computer system and determining positively or negatively whether performing the requested update of the first computer program requires updating of pre-requisite computer programs; and means for initiating an update of said pre-requisite computer programs if the determination is positive.
11. 11. An updater component for use in updating computer programs installed on a computer system connected within a computer network, the updater component including: means for initiating access to a first set of identifiable network locations at which are provided identifications of software resources required for applying updates to at least a first computer program and identifications of any computer programs which are pre-requisites for the operation of said updated first computer program; means for comparing the identified software resources and identified pre-requisite computer programs with computer programs installed on said computer system, to identify computer programs to be updated; means for initiating access to a second set of identifiable locations within the network at which are provided said identified software resources, to retrieve said identified software resources for applying updates; means for triggering updating of said pre-requisite computer programs; and means for applying updates to said installed computer programs using the retrieved software resources.
12. 12. An updater component according to claim 11 wherein said means for triggering updating of pre-requisite computer programs comprises means for communicating an update requirement to an updater component associated with the identified pre-requisite computer program.
13. 13. An updater component according to claim 12, adapted to register itself with a repository within the computer system with which the updater components for other installed computer programs are also registrable, thereby enabling updater components to be identifiable and contactable by other updater components by reference to registration information in the repository.
14. 14. An updater component according to any one of claims 11 to 13, wherein said means for comparing identified software resources with installed computer programs for identifying computer programs to be updated is adapted to compare said provided software resources with said installed computer programs and with predefined update criteria stored on said computer system.
15. 15. An updater component according to any one of claims 11 to 14, wherein said identifiable locations are identifiable from product identification information within said installed computer programs or within said updater component, the updater component being adapted to provide said product identifier information to a search engine and the product identifier information serving as a search parameter for use by said search engine to identify network locations.
16. 16. An updater component according to any one of claims 11 to 14, wherein said identifiable locations are identifiable from network location information within said installed computer programs or within said updater component.
17. 17. A computer system connected within a computer network and including an updater component for use in updating computer programs installed on the computer system, the system including: means for initiating access to a first set of identifiable locations within the network at which are provided identifications of software resources required for applying updates to at least a first computer program and identifications of any computer programs which are pre-requisites for the operation of said updated first computer program; means for comparing the identified software resources and identified pre-requisite computer programs with computer programs installed on said computer system, to identify computer programs to be updated; means for initiating access to a second set of identifiable locations within the network at which are provided said identified software resources, to retrieve said identified software resources for applying updates; means for triggering updating of said pre-requisite computer programs; and means for applying updates to said one or more installed computer programs using the retrieved software resources.
18. 18. A method for updating computer programs installed on a computer system connected within a computer network, the method including: initiating access to a first set of identifiable network locations at which are provided identifications of software resources required for applying updates to at least a first computer program and identifications of any computer programs which are pre-requisites for the operation of said updated first computer program; comparing the identified software resources and identified prerequisite computer programs with computer programs installed on said computer system, to identify computer programs to be updated; initiating access to a second set of identifiable locations within the network at which are provided said identified software resources, retrieving said identified software resources for applying updates; triggering updating of said pre-requisite computer programs; and applying updates to said first installed computer program using the retrieved software resources.