Abstract: Techniques are provided for versioning and refactoring of mashups. During the design phase of a mashup that is operable to access multiple external services, design information that defines or modifies a plurality of design elements included in the mashup is received from a user. Without receiving from the user any input that causes the plurality of design elements to be versioned, current versions of the plurality of design elements are automatically stored in a repository when the plurality of design elements are saved during development of the mashup. The mashup is deployed to one or more servers. Without receiving any input from the user that causes the mashup to be versioned, deploying the mashup comprises automatically storing in the repository a current version of the mashup and versioning information that associates the current version of the mashup with the current versions of the plurality of design elements.

Abstract: Techniques are provided for determining dependencies in a mainframe development environment. While executing a first build file to generate a first build of a software program from files in a file system, the activity in the file system is monitored to determine a plurality of files that are being accessed, and first information about the plurality of files is recorded. The first information is sent to a configuration management server. From the configuration management server, second information is received that indicates one or more dependencies which are determined among the plurality of files based on the first information. Based at least on the second information, a second build file is generated. The second build file is executed to generate a second build of the software program, where the second build is generated more efficiently by using less computing resources than the first build of the software program.

Abstract: Techniques are provided for designing a mashup. In an example embodiment, a user input is detected. The user input relates a first GUI object, which represents a first widget, to a second GUI object that represents a second widget. The first widget conforms to a first widget specification and the second widget conforms to a second widget specification that is different than the first widget specification. In response to the user input, a variable is defined, where, at run-time, a value of an output parameter of the first widget is assigned to the variable and the variable is used as an input parameter of the second widget. An event definition that defines an event is generated based on the user input, where the event, when detected at run-time, causes contents of at least one of the first widget and the second widget to be refreshed.

Abstract: Techniques are provided for baselining across multiple domains. Relationship information that associates a collection of requirement objects with a set of configuration management objects is stored. The collection of requirement objects is defined in a requirement management system for a software product, and the set of configuration management objects is defined in a configuration management system that is operable to manage the development of the software product. A particular requirement object from the collection of requirement objects is determined. Based on the relationship information, one or more configuration management objects that are associated with the particular requirement object are determined. A baseline that includes copies of the one or more configuration management objects is created and stored, where the copies include specific versions of the one or more configuration objects.

Abstract: Techniques are provided for identifying suspect links between objects from multiple domains. A plurality of links that associates a collection of requirement objects with a set of configuration management objects is stored. The collection of requirement objects is defined in a requirement management system for a software product, and the set of configuration management objects is defined in a configuration management system that is operable to manage the development of the software product. A determination is made that a particular requirement object was changed. In response to determining that the particular requirement object was changed, one or more links of the plurality of links are automatically determined. The one or more links respectively associate one or more configuration management objects, of the set of configuration management objects, with the particular requirement object. The one or more links are then identified as suspect.

Abstract: An approach is provided for proactive notification of contract changes in a software service. According to the approach, when the executable code of a composite application operable to access the service is generated, an initial copy of a contract that describes the service is retrieved. A baseline representation of the contract is generated based on the initial copy of the contract. When the composite application is being executed, a determination is made based on the baseline representation whether the contract has experienced any changes. In response to determining that the contract has experienced a change, a notification is sent indicating that the contract has experienced the change.

Abstract: Methods and systems for managing and analyzing multi-dimensional data are provided. Example embodiments provide a Meta-Object Data Management System “MODMS,” which enables users to arrange and to rearrange hierarchical relationships of the data on an ad-hoc basis and allows the data to be analyzed using any set of attributes (dimensions) while the system is running. The MODMS represents heterogeneous data in a normalized (standardized) fashion using an object type management system that allows the arbitrary coercion of one type of object into another different type of object and automatically resolves attribute dependencies. In one embodiment, the MODMS comprises an object type management subsystem; a meta-object instantiation subsystem; one or more data repositories; and an input/output interface. These components cooperate to allow the creation, management, and analysis of relationships between many different types of single and multi-dimensional data.

Abstract: Methods and systems for managing and analyzing multi-dimensional data are provided. Example embodiments provide a Meta-Object Data Management System “MODMS,” which enables users to arrange and to rearrange the hierarchical relationships of the data on an ad-hoc basis and allows the data to be analyzed using any set of attributes (dimensions) while the system is running. The MODMS represents heterogeneous data in a normalized (standardized) fashion using an object type management system that allows the coercion of one type of object into another different type of object and automatically resolves attribute dependencies. The MODMS supports object transitions for transforming an object from one type to another based upon meeting a defined set of criteria and subject to approval by designated entities. In one embodiment, the MODMS is used to implement an enterprise portfolio management system.

Abstract: A system and method converts database commands from one language and dialect to another and verifies the results of the conversion. If the results are accurate, changes may be committed to the database and otherwise, changes may be rolled back.

Abstract: A system and method converts database commands from one language and dialect to another and verifies the results of the conversion. If the results are accurate, changes may be committed to the database and otherwise, changes may be rolled back.

Abstract: A method and apparatus allows a file to be transferred from a mainframe computer to a client computer. A folder is set up on the client computer with a list of filenames and/or filters that designates some of the files on the mainframe computer as belonging to the folder. Conversion properties are assigned to the folder. A file is requested using the folder name and filename, and the file is transferred from the mainframe to the client computer and converted according to the properties of the folder to which the file belongs.

Abstract: A method and apparatus allows files stored on a mainframe computer system to be manipulated from a client computer system such as a personal computer. The mainframe may be represented by a UNC identifier or drive letter and a hierarchical folder structure may be arranged for the UNC identifier or drive letter in a manner consistent with the manner for arranging folders for locally stored files. Filenames or templates capable of describing multiple filenames may be associated with each folder to allow files on the mainframe to be manipulated using the hierarchical folder structure in a manner similar to that of locally stored files.

Abstract: A method and apparatus provides random access to mainframe files that are accessed using an operating system that does not provide random access. This allows a computer system such as a mainframe on which random access is not supported to act as a file server for a computer system on which random access is supported without requiring the entire file to be downloaded to the client computer system.