1882 results about "Software package" patented technology

Methods, systems, and computer program products for improving installation of software packages using an incremental conditional installation process (and optionally, caching of installation components). An object model is disclosed which enables specification of the conditional installation information as one or more elements of the model (and therefore of an object, document, etc., which is created according to the model). Conditional installation information may be defined at a suite level and / or at a component level. The identified checking process then executes to determine whether the corresponding suite or component should be installed. One or more components may be cached, if desired. Resource utilization is improved using the conditional installation and optional caching techniques, enabling reductions in disk space usage, CPU consumption, and / or networking bandwidth consumption.

A method and system for software and data distribution are described in which an original software and / or data package is provided to a first device. The first device installs the original software package, which includes installing a package builder kit. The package builder kit allows a software distribution kit to be built by the first device. The software distribution kit can be transmitted from the first device to a second device for installation on the second device. The package builder kit includes a copy of an original configuration file from the original software package, details as to the installed files, addresses of the installed files on the first device, details of the internal structure of the original software package, and provides an executable program to build the software distribution kit.

The present invention discloses efficient devices, systems, and methods for updating digital information sequences that are comprised by software (110a), devices (104a), and data (110c). In addition, these digital information sequences may be stored and used in various forms, including but not limited to files, memory locations, and / or embedded storage locations. The disclosed invention is thus suitable for updating many types of digital information sequences and in the context of updating software comprised of multiple files. Furthermore, the devices, systems, and methods described herein provide a developer skilled in the art with an improved ability to generate update information as needed and, additionally, allow users to proceed through a simplified update path, which is not error-prone, and may be performed more quickly than through the use of existing technologies.

A method includes receiving a text description of a system capability request, and converting the text description into a normalized description of the system capability request. A repository is then queried, based on the normalized description and using a search algorithm, to identify multiple candidate application software units (ASUs). The candidate ASUs are displayed to a user for selection. The user-selected ASU is then deployed, either locally or to at least one remote compute device, in response to receiving the user selection. Deployment can include the user-selected candidate ASU being integrated into a local or remote software package, thus defining a modified software package that is configured to provide the system capability.

A customized VM image, for example of Linux software, is created by allowing a user to select packages that the user is interested in installing. During the process, the user is informed if two of the packages that were selected will not be interoperable at run-time. The user is then given an opportunity to resolve the conflict. The user is also informed if selected packages depend on other packages that were not selected in order to run properly, and given the opportunity to include those needed packages in the VM image. Once the selected packages have been validated that they will interoperate and all dependencies are satisfied, the system can build and install the VM image. The VM image can also include applications, and not just packages used in assembling an operating system image.

A software vendor freely distributes software to users and issues smart cards to be used with the software. The smart card includes at least one software module missing from the software package and a list of allowed functionality dictating the capabilities of the software package. A user authenticates, using, e.g., public key cryptography, the smart card, which authorizes the use of the software. Once authorized, the module missing from the software is reunited with the rest of the software package. The software can be used limited to the allowed functionality included with the card. If more or different functionality is needed, the user can purchase another card authorizing such additional functionality, and then transfer the new functionality to the old smart card.

Virtualization platforms and management clients therefor are communicatively coupled to one another via a control layer logically disposed therebetween. The control layer is configured to proxy virtualization management commands from the management clients to the virtualization platforms, but only after successful authentication of users (which may include automated agents and processes) issuing those commands and privileges of those users as defined by access control information accessible to the control layer. The control layer may be instantiated as an application running on a physical appliance logically interposed between the virtualization platforms and management clients, or a software package running on dedicated hardware logically interposed between the virtualization platforms and management clients, or as an application encapsulated in a virtual machine running on a compatible virtualization platform logically interposed between the virtualization platforms and management clients.

Computer-based methods and systems for performing automated distribution of a software package to one or more target machines in one or more regions of a distributed network of target machines, comprises the following steps. First, a base software package is prepared for each of the one or more regions based on at least one of: (i) policy data indicating which of the one or more regions are candidates for receiving the software package, (ii) dependency information indicating requisites for a service provided by the software package, and (iii) configuration information for each of the candidate regions. The base software package is then distributed to each of the candidate regions of the distributed network. The base software package received at each of the candidate regions is then customized based on at least one of: (i) regional distribution policies, (ii) dependency information specific to one or more roles performed by the target machines in that region, and (iii) individual target machine configuration information. Lastly, the software package customized in each of the candidate regions is distributed to at least one of the target machines in the candidate regions of the distributed network.

A method for dynamic installation and activation of software packages in a distributed networking device. A master node provides a software package database that contains software packages for all nodes. It notifies a node that a software update is being requested, which examines the package identifiers and the dependencies and determines the running processes that will be affected by the update. The processes evaluate the effect that the update will have on their operation. If any of the processes determine that the update will degrade or have a negative impact on the operation of the node, the process will veto the update. If the master node receives no vetoes, it updates the node which installs and activates without interrupting the normal operation of the node.

An application software installation method and an application software installation apparatus are used to solve problems of operation complexity and high implementation difficulty in an existing installation process of application software. The method includes: mounting mirror data of a virtual machine, and mapping the mirror data as one virtual disk in a local file system; updating a registry file in a virtual disk according to registry change record data in an application software package; and updating a file structure in the virtual disk according to the file change record data and the file in the application software package, thereby implementing installation of the application software in the virtual machine. In the process of installing the application software, a user of the virtual machine does not need to perform complex operations, thereby reducing software installation difficulty.

One embodiment of the present invention provides a system that facilitates automated software installation on a remote computer over the Internet. The system operates by first initializing the remote computer with a custom operating system, which allows access to the remote computer over the Internet. Next, the system provides an archive locator to the remote computer, wherein the archive locator is a uniform resource locator (URL) or a proprietary resource locator. The system then requests an archive from the site specified by the archive locator. This archive includes an operating system and desired software packages pre-configured for the remote computer. The system downloads this archive to the remote computer and re-initializes the remote computer with the operating system and software packages in the archive.

The claimed inventions relate generally to computer systems having facilities for providing virtual portions of file systems and configuration settings to applications. More particularly, the claimed inventions relate to methods of capturing software packages using layered computing systems and software package products produced by those methods.

A software application distributed as a virtual appliance is automatically installed, updated and removed in a virtual machine system running on top of a virtual machine monitor in a computer. The software application virtual appliance comprises a virtual disk, which is automatically detected and installed or removed at the customer by a virtual disk activation manager program, which executes scripts including commands through an API to the virtual machine monitor. The virtual appliance virtual disk is also created automatically by the software manufacturing using the virtual disk activation manager program. The virtual appliance virtual disk stores the binaries of the software application, a software package created by the software manufacturer using a software package tool, an installer to execute the software package, installation and un-installation scripts and a unique identifier which is a signature for the virtual machine virtual disk.

A device receives configuration information associated with software to be installed in a network, builds a software package based on the configuration information, determines one or more devices of the network to perform installation of the software package, sends a command, to perform installation of the software package, to the determined one or more devices, receives one or more software package installation results from one or more other devices of the network where the software package is installed, and generates one or more reports based on the one or more software package installation results.

Methods, systems, and computer program products for improving installation of software packages by performing dynamic, remote validation of various installation data before building an installation image. The remote validation occurs in the target environment, such that the values for various installation parameters can be analyzed in the context of that target environment. Creation and distribution of the installation package can then be suppressed until the configuration parameters have acceptable values. This immediate feedback approach allows for a more efficient installation process. In preferred embodiments, structured markup language syntax is used to specify which configuration values are subject to remote validation. Structured markup language documents are preferably used to describe the data that is to be transmitted from a staging server to the remote environment, where an installation agent is adapted for processing the document and determining the corresponding validation routine(s) to be invoked on the remote system. Similarly, structured markup language documents are preferably used for describing results of the validation to the staging server.

Computer-based methods and systems for performing automated distribution of a software package to one or more target machines in one or more regions of a distributed network of target machines, comprises the following steps. First, a base software package is prepared for each of the one or more regions based on at least one of: (i) policy data indicating which of the one or more regions are candidates for receiving the software package, (ii) dependency information indicating requisites for a service provided by the software package, and (iii) configuration information for each of the candidate regions. The base software package is then distributed to each of the candidate regions of the distributed network. The base software package received at each of the candidate regions is then customized based on at least one of: (i) regional distribution policies, (ii) dependency information specific to one or more roles performed by the target machines in that region, and (iii) individual target machine configuration information. Lastly, the software package customized in each of the candidate regions is distributed to at least one of the target machines in the candidate regions of the distributed network.

A system and method for providing an efficient and robust interface that allows banking transactions to be processed by an online banking system and third party accounting software packages via a single user point of entry. The system is configured to receive a transaction request from a third party accounting software, the transaction request including one or more transactions; verify, based on information stored in a first database, that the transaction request is from a valid source; store information regarding the one or more transactions from the transaction request in a second database; process the one or more transactions; and provide a response to the third party accounting software indicating a status of at least one transaction in the transaction request.

A software package manager uses a distribution unit containing components for a software package and a manifest file that describes the distribution unit to manage the installation, execution, and uninstallation of software packages on a computer. Information in the manifest file pertaining to a software package is stored in a code store data structure upon installation of the package. The manifest file also contains information that permits the software package manager to resolve any software dependencies upon installation. The software package manager uses the code store data structure to locate the required components when the software is executed and to remove the components appropriately when the software is uninstalled.

Systems, methods, and computer-readable media are provided for automatically downloading and launching a new version of software package on components in a network environment. In some examples, an upgrade server of a network environment keeps a copy of all versions of software packages running on nodes or sensors of the network environment, identifications of corresponding nodes or sensors, and public keys associated with the software packages. The upgrade server can authenticate a new version of a software package using a two-step process.

Software device groups allow owners and administrators to be defined for various intelligent devices, instead of tracking by primary user. A software license compliance management system obtains discovery information for these devices to determine software installed or active on these devices. The management system also obtains the number of licenses for each software package and determines whether the software is in compliance, or if the number of instances exceeds the number of licenses. This determination is flexible and can handle various license types, such as per user, per device, and per processor. For any exception, the group owner is informed and then can re-allocate licenses, purchase additional licenses, or request the uninstalling of a software instance(s). Device groups also can include sub-groups with sub-group owners responsible for handling any exception in that sub-group.

An automated management system for managing data, outage repair, load switching, job workflow and crew dispatching, crew workflow, installation, maintenance and restoration of utility services by integrating geographic information systems (GIS) data with many other data sources so as to gather, transform, manipulate, analyze, and produce desired information for continuously supplying utility and relevant services. The data sources include customer information systems (CIS) and billing data, interactive voice recognition (IVR) call management data, supervisory control and data acquisition (SCADA), mobile crew management (MCM) data, automatic meter reading (AMR) data, automated vehicle location (AVL) data, engineering analysis data supported by 3rd party software packages (such as load monitoring and balancing), etc. In particular, the system allows an on-site engineer to retrieve data (ex. field maps, work orders, codes) or enter, via a portable device, inspection data (ex. such as poles or underground facilities, code violations).

Methods, systems, and computer program products for improving installation of software packages using a directory (such as a Lightweight Directory Access Protocol, or "LDAP", directory). A model and framework are described, where the objects of the data model may be uncoupled from the framework, allowing individual objects to be separately stored and retrieved in the directory is association with access rights or privileges. Multiple versions of each object may therefore be created and stored, and may be easily retrieved using the built-in mechanisms of the directory, when access rights which are appropriate for a particular requester are known. Optionally, built-in authentication mechanisms of the directory may be used to authenticate the requester.

A method of controlling access to data comprises: a) in a first platform wrapping selected data content and at least one information flow control policy in a software wrapper; b) interrogating a second platform for compliance with a trusted platform specification; c) on successful interrogation of the second platform, sending the wrapped data content to the second platform; and d) unwrapping the wrapped data content within the trusted environment of the second platform for use.

The platform supports a wide variety of merchants who are interested in a loyalty and / or value card products. The platform is an integrated set of software packages and tools that allows merchants to develop and offer loyalty award and payment products. The platform consists of a series of sub-systems that form the operating environment for the loyalty and payment products, collectively called common systems herein. These systems work together to customize and orchestrate product functionality. The platform processes real-time messages from devices, such as point-of-sale and CRIND / ICR / ICR (gas pump) devices, that are modified to work with the platform. The platform responds to the messages from the devices with a range of actions from approval of the pending purchase to addition of loyalty points into an account. In the case of the system-based service, messages are formatted according to defined standards so that they can be received by the platform. Other devices currently supported by the platform include Kiosk, IVR, API, and Web. New modules may be added to the platform that allow it to accept translations in any data format.

A method and system for packaging software using a graphical user interface (GUI) to simplify the creation and modification of System V and Red Hat Package Manager (RPM) software packages. The software packaging system provides a fully interactive graphical interface portable across many platforms including Linux, Unix System V, Solaris, and AIX. RPM is a popular and powerful packaging system that installs and removes system software, enforces dependencies, and is freely available on a number of different platforms. The software packaging system of the present invention simplifies and speeds the creation of deployable RPM software packages, a complex and time consuming task if created using the RPM command line method. The GUI provides for the collection of information required for RPM software package creation, modification, and feature manipulation reducing the skill level and time that needed to perform these functions using the RPM command line.

A system and method for providing digital receipts for purchase transactions are provided. The method includes the steps receiving information for a first credit card account for executing a transaction; retrieving a first customer record from a database using information from the first credit card account; charging an amount of the transaction to the first credit card account; and transmitting a receipt to a predetermined location of the customer. The predetermined location may be an e-mail address of the customer or a server residing on the network. By receiving digital receipts, a customer or end-user will be able to digitally store these receipts and view or print the receipts out when necessary. Furthermore, the customer will be able to manage the receipts with conventional software packages.

A method for a user computer to selectively activate a feature of a software package executing on the user computer includes receiving a feature activation license from a remote server and activating an inactive feature originally present in the software package.

One embodiment of the present invention provides a system to facilitate cross-domain push deployment of software in an enterprise environment. The system operates by receiving a machine name and a domain name associated with a client at a server. Next, the system creates an entry in a database, which associates the machine name with the domain name. This entry establishes what software to deploy to the client. The system then accepts a user name and a password from the server administrator to gain access to the client. The system authenticates the server to the client using the user name and password. After authenticating the server to the client, the system pushes the software package to the client.

A method for software change modeling for network devices provides dynamic (on the device) and static (computer) change modeling. The same source code and libraries are used for both modeling applications, allowing a user to see the impact of activating or deactivating specific software modules without affecting the actual node. A master node passes a node the identity of the software package(s) to be updated and the dependencies. The node notifies its running processes about the update. If any of the processes determine that the update will degrade or have a negative impact on the operation of the node, it returns a veto to the node which sends a list of the processes that are impacted along with the reasons why to the master node.