Abstract: A process evaluation device, comprising: a development process definition storage unit which stores definition information on a plurality of processes for developing software and sequence numbers thereof; a transition information acquiring unit which acquires identification information or a sequence number of a new process after a backward transition occurs, wherein a process transition from a certain process referred hereafter as an evaluation origin to said new process is said backward transition when a sequence number of said new process is smaller than a sequence number of said evaluation and a transition information analysis unit which calculates and thereby outputs a backing-away distance which is a difference between a sequence number of said evaluation origin and a sequence number of said new process, is provided, in order to apprehend what are real causes of the development delay.

Abstract: A software version management system comprising a host driver and at least one software module. The host driver comprises migration means to start, stop and replace the software modules on a computer system in response to replacement actions.

Abstract: When customer transport requests are included in an update procedure performed on a customer-customizable business software architecture, versioning of the objects and other features imported via such transport requests can require an extended period of business downtime using conventional methods. Additional downtime can result if the objects of the customer transports are not automatically generated. Consistent with features described herein, versioning can be done for many object types in a second shadow system or instance during uptime. The generation of objects in the customer transports can also done in the second shadow system or instance during uptime.

Abstract: A system may include computer code for analyzing an upgrade from a first version to a second version of a software program that has been customized without performing the upgrade. The system may provide default state information of default program objects. The default program objects would be included in a default installation of the second version of the software program. The computer code may retrieve current state information of current program objects from an application database. The software program that has been customized may include the current program objects. The system may generate upgrade information based on a comparison between the current state information and the default state information. The upgrade information may identify a subset of the current program objects that would be impacted by the upgrade.

Abstract: To provide a secure installation and execution software environment, locked version numbers are maintained. A locked version number associated with a software program may be stored. When a request is received to update the software program with an update package, a package number of the update package may be compared to the locked version number. The software program may be updated with the update package if the package number is at least as recent as the locked version number, and the updating of the software program with the update package may be restricted if the package number is earlier than the locked version number.

Abstract: At the time of a maintenance work, a user computing machine does not give user data to a person (maintainer) who carries out maintenance and does not accept operations and data that are not relevant to the maintenance work so as to prevent the leakage of user data. Specifically, a user computing machine includes: a user data determination section determining whether a file of a VM of a computing machine used by a user is data created by the user, and a VM copy section, creating a copy of a VM which does not include data created by the user by calling the user data determination section. The maintenance is performed by supplying the VM which does not include data created by the user to a computing machine of the maintainer.

Abstract: An energy management and control system that may manage versioning firmware for devices. The system may be structured in a hierarchy of enterprise, site and field levels, with one or more computing platforms at the various levels. An enterprise supervisor may detect and obtain new version firmware for the devices at the field level. The new version firmware may be transferred from the supervisor to one or more site controllers. The one or more site controllers may transfer the new version firmware to eligible field devices. The devices may report to their respective site controllers a status of a transfer of the new version hardware. The site controllers may report to the supervisor the status of the transfer. Detection of new version firmware may be automatic. Transfer of the new version firmware to virtually all of the eligible devices may be automatic.

Abstract: A system for assembling an update for a software release is described, comprising a processor and memory configured to define classes of software components, each class having a plurality of instances, each instance having a unique identifier (UID) and representing a software component having a plurality of versions; for each version of the software component, assign time stamps and indicator identifying release status of the version; introduce a flexible coupling between versions of software components and instances of classes using a pointer between a version of the software component and a UID associated with the version; select versions of software components from which pointers originate; for each instance of the class, to which the pointer points, select one version of the software component based on the assigned indicator; and assemble the selected versions of software components into the update of the software release. A corresponding method is also provided.

Abstract: In-service upgrade of software can be achieved efficiently when software modules pass data using message or data queues. The use of data queues facilitates the transition from a software module's old behavior to a new behavior without risking a deadlock or dropped module call. Upgradeable objects connect to process objects that maintain the queues and their state data, and upgrade objects connect to the process objects of their predecessors.

Abstract: In an illustrative embodiment of a process for software version recommendation, a computer receives information representative of a software instance at a target machine, analyzes the received information using a set of predefined rules and a set of available updates metadata associated with a particular updates agent and target machine to identify information pertinent to a combination of a respective target machine associated with the particular updates agent. The computer, responsive to a determination to send the identified information as a recommendation to the respective target machine, sends the recommendation to the combination of the respective target machine associated with the particular updates agent.

Abstract: The disclosure provides a system, a method and a computer program product that facilitate access to one or more applications by a computing device. The disclosure includes a step of determining one or more contexts associated with the computing device or a user of the computing device, such that the one or more contexts describe environment or activity of the user or the computing device. The disclosure also includes a step of generating at least one contextual tag corresponding to the one or more contexts, after which the one or more applications associated with the at least one contextual tag are identified and the computing device is enabled to access the one or more applications.

Abstract: A lighting system controller is provided that is adapted to upgrade a lighting controller with a software component having multiple upgrade dependencies. According to one example, the lighting system controller is configured to generate an upgrade plan based on the current configuration of the lighting controller and the upgrade dependencies associated with the software component. Further, according to this example, the lightings system controller executes the upgrade plan to install the software upon with the software component is dependent prior to installing the software component.

Abstract: A method for automatically provisioning a platform implementation package to a client device may include receiving from an application executing on the client device, a request for functionality. The request may be received via a client library distributed with the application, and may be for functionality provided by the platform implementation package. The platform implementation package may provide functionality that is not provided by the client library. It may be further automatically determined, by the client device, that the functionality requires an update to the platform implementation package. In response, a request for the update to the platform implementation package may be communicated to a computing system. The update to the platform implementation package may be received from the computing system and installed on the client device. The requested functionality may be provided to the application by the updated platform implementation package.

Abstract: A tool supports management of engineering project changes using a current design diagram with links to implementation components, a proposed design diagram, and a work list of tasks for transforming the current design into the proposed design. Tasks recite intended changes such as add, remove, or refactor, with reference to implementation components to be changed, and tracking information. Work list tasks may be automatically generated based on design model differences correlated with project code, automatically generated based on tracked user design actions correlated with project code, and/or manually generated by users. Work lists may be exported. Users can mark a relationship for removal and view a corresponding updated work list. Users can trace impact of a work list on project context such as testing coverage, database structures, and user scenarios.

Abstract: The present invention discloses a method and an apparatus for packing a version upgrade software package.

Abstract: Virtual applications are automatically kept up to date with the current version of a virtual application. Instead of the client having to obtain the entire version of the current virtual application, the client obtains the portions of the current virtual application that are changed from its version of the virtual application. After obtaining the changes needed to update its version of the virtual application, the client integrates those changes into its version of the virtual application.

Abstract: An information processing apparatus stores configuration information including sets of version information of modules of firmware in the apparatus; obtains, based on the configuration information, firmware information including sets of version information of modules of firmware in a latest version; compares the sets of version information in the configuration information with those in the firmware information, and, when the sets of version information in the configuration information are not coincident with those in the firmware information, determines that it is possible to update the firmware in the apparatus; downloads the firmware in the latest version; and compares the sets of version information in the downloaded firmware with those in the configuration information, and updates only the module of the firmware in the apparatus for which the version information in the downloaded firmware is different from that in the configuration information.

Abstract: Techniques for securely updating a boot image without knowledge of a secure key used to encrypt the boot image.

Abstract: Systems and methods for providing point in time rollback and un-installation of software within computer networks are disclosed. The system comprises a plurality of elements which perform data migration operations and a rollback and un-installation manager which monitors the elements and software installations. Upon detection of a software installation, the rollback and un-installation manager identifies the installation, obtains records of the computer network files modified by the installation, and causes copies of the modified files to be generated. At future dates, the records and copies are utilized to return the computer network to a state prior to the installation. In this manner the risks associated with removal single or multiple updates are greatly reduced.

Abstract: Technologies are generally described for data filtering for communication devices. In one example, a method of receiving data from a data source on a communication device is disclosed. The method includes determining, at the communication device, a domain name of the data source. The method also includes determining, at the communication device, one or more communication networks the communication device is connected to. The method further includes processing, at the communication device, the domain name for acceptance based on the one or more connected communication networks. The method also includes receiving the data from the data source, at the communication device, if the domain name is accepted.

Abstract: According to one embodiment of the invention, a method for altering stored firmware within a network device comprises receiving, by a first network device, information to download firmware. This information is provided from the first network device to at least a second network device, which is communicatively coupled to the first network device. The information enables the second network device to access a second version of firmware different than a first version of firmware installed on the second network device.

Abstract: Propagation of software updates in a wireless mesh network is handled according to an “informed push” model. Nodes are given the software update that they need, but this is done in response to a sequence of propagating reports on the need for the upgrade (i.e., that node devices have old versions). Each node device executes a reporting cycle in which a report is sent to its neighbors that indicates the types and versions of software items that reside on the device; and for non-resident software items, the lowest versions of which the node device received knowledge from its neighbors. If a node device determines that its reporting neighbor has an old version of a software item and the node device contains a newer version of that software type residing locally, then it sends its neighbor the upgrade. Otherwise, the node “gossips” about the old version to its own neighbors.

Abstract: This disclosure relates to a method, article of manufacture, and apparatus for automated handling of a hotfix. In some embodiments, this includes obtaining defects submitted to a defect repository, querying the defect repository to obtain a defect, permitting the users to approve the defect as a cumulative hotfix candidate, receiving and storing check-in data corresponding to the cumulative hotfix candidate to a source code repository, approving the check-in data, triggering an automated compiling of a build of the version of the software, examining the build, triggering an automated testing of the build based on a determination that the build is clean, storing the build in a build repository when the automated testing of the build completes without error, and publishing the build.

Abstract: A system and method for guiding a user through a procedure for updating firmware on an uninterruptible power supply. In one example, the system includes a computer system and a communication link to connect the computer system to the uninterruptible power supply. The computer system includes a discovery component, which is configured to detect a version of the firmware installed on the uninterruptible power supply and to detect a model type of the uninterruptible power supply. The computer system also includes a firmware update component, a preparation sequence and an instruction component corresponding to the model type of the uninterruptible power supply and the version of the firmware installed on the uninterruptible power supply. The preparation sequence is configured to prepare the uninterruptible power supply for the firmware update component. The instruction component is configured to display instructions that guide the user through the procedure for updating the firmware.

Abstract: A computer-implemented method in a distributed network system is disclosed. The computer-implemented method includes: receiving, at a server, a first object update message from a server-side application, wherein the first object update message includes a first object identifier; identifying, among a plurality of object-client registration records, an object-client registration record that includes the first object identifier; updating the object-client registration record in accordance with the first object update message; selecting a set of client identifiers associated with the first object identifier from the object-client registration record; and, for a first client identifier in the selected set of client identifiers, sending a second object update message to a first client device associated with the first client identifier, wherein the second object update message includes the first object identifier.

Abstract: A software development application determines whether routine name and version number parameters have been identified (33). If so, the application determines whether the specified version of the routine can be accessed (35). If the specified version cannot be accessed, the application locates a substitute version of the routine (37) and compiles and links the routines and a source file to produce an executable file (39).

Abstract: A method, data processing system, and computer program product are presented for planning upgrades to a network data processing system. A processor unit identifies configuration information for hardware and software programs for a plurality of computers in the network data processing system. The processor unit obtains end of life dates for the software programs, release dates for the replacement software programs, and prerequisites for replacement software programs for the software programs identified in the configuration information. The processor unit identifies at least one change to the plurality of computers based on the configuration information and a set of prerequisites in the prerequisites for each of a plurality of replacement software programs for a plurality of software programs in the software programs.

Abstract: A device may include a first manager to store attribute information of a first program in a first storage in response to an install request to install the first program, and a second manager to store attribute information of a second program in a second storage in response to an install request to install the second program. The second manager may store attribute information of a third program and attribute information of the second program included in the third program in the second storage, and store attribute information of the first program included in the third program in the first storage, in response to an install request to install the third program that includes the first program and the second program.

Abstract: Methods and apparatus, including computer program products, are provided for updating virtual appliances. In one aspect, there is provided a computer-implemented method. The method may include receiving, under the control of a first update manager of a first virtual appliance, a second virtual appliance including a second update manager. The second virtual appliance may be received as an update to replace the first virtual appliance. Control of the update may be transferred from the first update manager to the second update manager, when the first update manager receives an indication representing completion of the update. Related apparatus, systems, methods, and articles are also described.

Abstract: A method of conducting a software update of a gaming machine, including: starting a boot process of the gaming machine; determining during the boot process that a memory device potentially containing at least one software component more recent than a corresponding software component currently stored in gaming machine memory is in data communication with the gaming machine; determining that the memory device contains at least one authentic, more recent software component; and updating gaming machine memory with each more recent software component.

Abstract: Unique context-based code enhancement of the core functionality of standard source code objects is performed at any position in the code. Desired insertion/replacement position(s) input by a user trigger the generation of a unique context for an enhancement. The unique context is based on characteristics of the code in the standard source code objects, such as the statements proximate to the insertion/replacement position(s). The unique context is associated with one or more extension source code objects that, when integrated into the existing source code at the insertion/replacement position(s), will provide the enhancement. At compile-time, the unique context used to unambiguously locate the insertion/replacement position(s). The extension source code objects can include industry or customer extensions, add-ons, plug-ins, and the like.

Abstract: Management of applications on remote devices is performed independently of managing platform software. A per platform player using a common protocol to communicate and receive applications is installed on a device. The player is developed and installed independently of applications which run using commands supported by the player. On player startup, the player obtains boot instructions, fetches an application manifest, and obtains player and application resources using the application manifest from a content and application server. The content and application server determines application resources to send to the player and tracks applications and application versions installed on a per user/per platform basis.

Abstract: In one aspect, this application describes a method for determining a version of a software application targeted for a computing device. The method includes receiving, at an application marketplace system and from a user associated with a computing device that operates remotely from the application marketplace system, a request that corresponds to a software application distributed by the application marketplace system, the software application having multiple versions on the application marketplace system. The method also includes determining one or more device attributes that are associated with the computing device, and identifying a particular version of the software application, from among the multiple versions on the application marketplace system, that is targeted for the computing device based on the device attributes. The method also includes providing, for display to the user and in response to the request, information related to the particular version of the software application.

Abstract: A method, computer program product, and system for non-blocking dynamic update of statically-typed class-based object-oriented software executing as byte-code on a virtual machine within an actively running computer system is provided. A set of objects instantiated from an existing module or multiple modules (identifiable collections of application resources and class definitions in the form of byte-code representations) is ready for execution on a virtual machine in an actively running computer system. New versions of one or more modules corresponding to those already loaded into the actively running virtual machine are dynamically loaded into the virtual machine for the purpose of updating the running software. The class definitions within the loaded modules are prepared for dynamic update by inserting byte-code that enables; transparent state transfer and shared object identity between objects of a former version and the new version of a class.

Abstract: Firmware updates for, e.g., thin client devices may be achieved in a seamless, non-disruptive manner using a two-stage firmware loader, including a base loader pre-installed on the device and a caching loader downloaded, by the base loader, from a firmware server and thereafter responsible for downloading and updating other firmware application packages.

Abstract: A print controlling device is provided. The present print controlling device includes a storage unit to store information regarding software or firmware installed in an image forming apparatus, a search unit to search and identify whether there is firmware version newer than or later than that installed in the image forming apparatus using the stored firmware information, a determination unit to determine whether the searched or identified firmware of the newer or latest version is compatible with an application program installed in the print controlling device using compatibility information when firmware of the newer or latest version is identified, an interface unit to request and receive firmware of the newer or latest version from a firmware providing server according to the determination result, and an upgrade unit to upgrade the firmware of the image forming apparatus using the received firmware of the newer or latest version.

Abstract: In a system and a method, a request from a client device to generate a downloadable file representing an offline version of a web-based application hosted by a web server is received. Application components and data used by the web-based application are packaged into the downloadable file, and the downloadable file is transmitted to the requesting client device. The web-based application is locked to prevent access to the web-based application. A revised downloadable file is received that includes changes to at least one of the application components and the data contained in the downloadable file. As applicable, the application components and data used by the web-based application are updated with the changes to the at least one of the application components and the data contained in the revised downloadable file. Subsequent to the updating, the web-based application is unlocked, and the downloadable file is invalidated.

Abstract: Embodiments are directed to ensuring that only one version of an application is running on a cluster. In one scenario, a computer system includes a configuration agent that generates service instance version queries upon startup to determine which service instance version to activate, maintains a service instance version table that includes a listing of service instance versions currently running on the computer system as part of one or more application instances and activates specified service instances. The computer system also includes a failover manager that manages service instance version queries. The failover manager indicates which service instance version to activate to ensure that the appropriate, current version is activated for each service instance. The computer system further includes a cluster manager that creates, deletes and upgrades service instances as part of an application instance upgrade.

Abstract: A method for transparently upgrading derived database objects commences upon analysis of the data dictionary definition for an initial derived database object as compared to the data dictionary definition for a patched derived database object, then determining if a regenerated instance of the derived database object would be logically different from the initial derived database object. The determination is based on comparisons of the definitions of the initial derived database objects and patched definitions of respective database objects. The method produces a regenerated instance of the derived database object when a regenerated instance of the patched derived database object would be logically different from the initial derived database object. The method will suppress the production of a regenerated instance when a regenerated instance of the derived database object would not be logically different from the initial derived database object.

Abstract: High availability for a network may be achieved, for example, during a hitless upgrade by creating a replica controller virtual machine of an operating controller virtual machine (source controller). The replica controller virtual machine may be on a same or different server as the source controller virtual machine. The replica controller virtual machine may be copied with processes present in the source controller virtual machine and synchronized for runtime state. Upgrades or changes to software applications run in the source controller virtual machine may be provided to the replica controller virtual machine. Once enabled, the replica controller virtual machine may be operated without suspension of the source controller virtual machine.

Abstract: Methods, apparatuses, and systems for managing digital content in hierarchies are described. A first version of a digital image is received from an external device which tracks changes to the first version. It is determined that a second version of the digital image, changes to which have been tracked, exists. Based on comparing the tracked changes of both versions, the versions are combined. The first version is created by splitting the second version, which is stored in a master hierarchy, and transmitting the split version to the external device. During splitting, a child hierarchy of information is split from the master hierarchy, the child hierarchy including portions of the master hierarchy to access the second version such that the second version can be accessed independent of the master hierarchy. Changes to the versions are tracked in change tables, for example, using values that are mashed into a single record.

Abstract: A server rack system module is provided. Each rack internal device at least includes a control chip, and the rack internal devices include a plurality of servers. An integrated management module (IMM) is respectively coupled to the control chips, where the IMM stores integrated management firmware, and the integrated management firmware has latest version firmware of the control chip integrated therein and records latest version serial numbers of the latest version firmware. When the server rack system is started, the IMM reads a current version serial number of currently installed firmware of each control chip, and compares the current version serial number with the corresponding latest version serial number, so as to determine whether to update the currently installed firmware.

Abstract: The present invention extends to methods, systems, and computer program products for providing update notifications on distributed application objects. When a new version of an object is created that another object depends on, a notification can be added to the dependent object to alert a person that manages the dependent object of the creation of the updated object. Dependent objects can include template objects, such as virtual machine template objects that refer to virtual disk objects and service template objects that refer to one or more virtual machine template objects, as well as service instance objects that represent service instances that are instantiated from template objects. Versions of objects within a family can be identified by sharing a family name and having different releases. A timestamp is used to represent when an object is released to determine which version of an object is the newest version in a family.

Abstract: A method and apparatus are provided that allow the user to quickly load new versions of applications on a scan tool. The latest versions of the applications that a scan tool can operate are loaded onto a memory device. The scan tool verifies which versions of the applications are authorized and allows the scan tool to only access information related to the authorized versions.

Abstract: A method of updating firmware that is included in a memory apparatus that includes first and second volatile memories and a non-volatile memory, can be provided by storing new firmware in the second volatile memory when old firmware is loaded into the first volatile memory and determining on a component basis which of a plurality of components of the old firmware is an updated component in the new firmware.

Abstract: One embodiment of the present invention provides a system for facilitating an upgrade of a cluster of servers in the presence of one or more inaccessible nodes in the cluster. During operation, the system receives an instruction to upgrade an older version of a distributed software program installed on each of a plurality of nodes forming the cluster. The system installs and activates a newer version of software on a subset of the plurality of nodes, the subset having fewer nodes than the entire cluster. The system receives an instruction to forcibly upgrade the cluster. Subsequently, the system upgrades the cluster so that the subset of nodes operate with the newer version of software, in which each node remains a member of the cluster during the upgrade.

Abstract: A facility for applying a software patch is described. Using an automatic patching agent, the facility receives the software patch. In response to receiving the software patch, without user intervention, the facility performs the following acts: First, the facility identifies an instance of an executable module that is currently loaded, and to which the received software patch pertains. Second, the facility applies the received software patch to the identified loaded executable module instance to modify the behavior of the identified executable module instance.

Abstract: Updating of a software object is described. A first version of a software object is instantiated. User-inputted data used by the first version of the software is received from a user, and a current configuration state and the user-inputted data are registered. A second version of the software object is instantiated and the current configuration state and the user-inputted data of the first version of the software object are exported to the second version of the software object.

Abstract: A continuously operating system is provided and includes a processor and a computer readable medium to which the processor is operatively coupled, the computer readable medium having executable instructions stored thereon which, when executed, cause the processor to continuously load an operating system and to simultaneously operate as at least first and second mechanisms. The first mechanism loads a new module, which is a new version of an in-memory module of the operating system, into the operating system, and the second mechanism isolates and interrupts current access to the in-memory module such that subsequent access is to the new module.

Abstract: A method for automatically registering the runtime environment and related component applications with an application gateway when transferring the applications from a first wireless device to a second wireless device is provided. Applications installed on the first wireless device are registered with an application gateway, which maintains a registration list of identification information for all registered wireless devices and applications installed thereon. A back-up is created of the applications and registration information for the runtime environment installed on the first wireless device for transfer to a second wireless device. An application container of the second wireless device determining installation and communicating to the application gateway identification information regarding the second wireless device and the restored applications.