DESIGNING AND CROSS-CONFIGURING SOFTWARE
First Claim
1. A system for creating a cross-configuration software module for cross-configuring software entities, the system comprising:
- a memory;
a processor communicatively coupled to the memory; and
a connector creation tool communicatively coupled to the memory and the processor, wherein the connector creation tool is configured to perform a method comprising;
retrieving a semantic representation of a set of systems capable utilizing the cross-configuration software module;
retrieving a functional representation of a set of operations, each operation in the set of operations is to be performed on a set of software entities associated with the set of systems during at least one connector life-cycle phase in a set of connector life-cycle phases, wherein the set of operations cross-configure at least a first of the set of software entities with at least a second of the set of software entities;
identifying a set of artifacts comprising at least one of a set of metadata and a set of executable instructions associated with the set of operations; and
storing the semantic representation, the functional representation, and the set of artifacts, in the cross-configuration software module.
1 Assignment
0 Petitions
Accused Products
Abstract
Various embodiments create a cross-configuration software module for cross-configuring software entities. In one embodiment, a first set of requirements and at least a second set of requirements are obtained. Each of the first and second set of requirements identify at least one of a set of software entities and a set of hardware components required to be present on at least one system including software entities to be cross-configured. At least one set of operations is obtained. The set of operations includes at least one executable instruction that configures a first software entity with a second software entity. A first configuration definition is generated including at least the first set of requirements and the at least one set of operations. A second configuration definition is generated including at least the second set of requirements. The first and second configuration definitions are stored within a cross-configuration software module.
-
Citations
14 Claims
-
1. A system for creating a cross-configuration software module for cross-configuring software entities, the system comprising:
-
a memory; a processor communicatively coupled to the memory; and a connector creation tool communicatively coupled to the memory and the processor, wherein the connector creation tool is configured to perform a method comprising; retrieving a semantic representation of a set of systems capable utilizing the cross-configuration software module; retrieving a functional representation of a set of operations, each operation in the set of operations is to be performed on a set of software entities associated with the set of systems during at least one connector life-cycle phase in a set of connector life-cycle phases, wherein the set of operations cross-configure at least a first of the set of software entities with at least a second of the set of software entities; identifying a set of artifacts comprising at least one of a set of metadata and a set of executable instructions associated with the set of operations; and storing the semantic representation, the functional representation, and the set of artifacts, in the cross-configuration software module. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
9. A system for creating a cross-configuration software module for cross-configuring software entities, the system comprising:
-
a memory; a processor communicatively coupled to the memory; and a connector creation tool communicatively coupled to the memory and the processor, wherein the connector creation tool is configured to perform a method comprising; receiving a selection of at least one system comprising a set of software entities; identifying a plurality of cross-configuration software modules, wherein each cross-configuration software module comprises at least two configuration definitions each comprising at least a set of requirements and identifying at least one software module to be cross-configured; comparing the set of software entities of the at least one system to the set of requirements for each of the plurality of cross-configuration software modules; identifying, based on the comparing, at least one of the plurality of cross-configuration software modules having the set of requirements being satisfied by at least two of the set of software entities of the at least one system; and automatically cross-configuring the at least two software entities based on the at least two configuration definitions of the at least one identified cross-configuration software module. - View Dependent Claims (10, 11, 12, 13, 14)
-
Specification