International Business Machines Corporation

Martin Paul Nally

Lawrence Scott Rich

Michael Beisiegel

Jean-Sebastien Michel Delfino

Peter David Niblett

Daniel Christopher Berg

Geoffrey M Clemm

Simon Kurt Johnston

Jason Robert McGee

Schuyler Bruce Matthews

Darcy L Wiborg Weber

Nicholas D J Crossley

Frank J Budinsky

James J Des Rivieres

Daniel D J Leroux

Scott Rich

Joseph P Winchester

Edison Lao Ting

Michael L Fraenkel

Ritchard Leonard Schacher

David John Vines

Piotr Przybylski

Timo J Salo

Zhaohui Feng

Robbert Van Der Linden

David Andrew Booz

James Peter Branigan

David Paul Charboneau

Randy W Carroll

Susan Franklin Griffin

Jenny Ming Chow

Arrangements described herein relate to managing versions of artifacts stored across disparate tools. In a multi-dimensional configuration space, dimensions can be defined. The dimensions can represent respective variations of respective versions of a plurality of artifacts for at least a first configuration of a system. Via the dimensions, versions of the plurality of artifacts can be mapped to at least a corresponding first configuration of the system, the mapped versions of the plurality of artifacts corresponding to the versions of the artifacts used in the first configuration. The first configuration can be identified by a point in the multi-dimensional configuration space defined by the respective dimensions. At least a first of the plurality of artifacts can be stored by a first tool, and at least a second of the plurality of artifacts can be stored by a second tool disparate from the first tool.

Managing versions of artifacts stored across disparate tools

A data indexing system including a plurality of servers and a tracked resource set client is provided. Each of the servers includes a plurality of resources that are part of a resource set. Each of the servers also includes a tracked resource set corresponding to the resource set. The tracked resource set describes the plurality of resources located in the resource set. The server identifies the plurality of resources using rules of linked data. The tracked resource set client is in communication with the plurality of servers. The tracked resource set client has a data index. The data index is built and kept up to date using the tracked resource set of each of the plurality of servers.

Data index using a linked data standard

In the present solution, as set of SDLC resources can be established, where each is separately addressable through a unique URL and is able to be managed through a simple set of operations. For example, a set of RESTful operations (GET, POST, PUT, and DELETE) can be used for the operations. Database management technologies can be leveraged for storing and indexing resources, but the underlying database schema for the solution can operate on a resource level, which results in the resources being stored as-is. Thus, storage (even when database based) of resources for the solution can be considered an Internet server exposing a space of URL addressable objects. Because the solution leverages Internet technologies and standards, it is scalable, standards based, extensible, and traceable.

Representing models in systems development lifecycle (SDLC) tools using a network of internet resources

Resources are typically stored in homogenous data structures by shredding resource data into database tables destroying a native format of the resources. Typical approaches to indexing the resources rely on users indicating properties that should be indexed, using full text searches to create resource index documents, and other such labor and computation intensive processes. Functionality can be implemented to dynamically generate the resource index documents based on resource properties with minimal user input. The resource index documents can be in a common format to facilitate access to resources stored in heterogeneous native resource formats.

Indexing heterogeneous resources

An apparatus and system are disclosed for implementing service qualifiers that define on-demand management requirements for a loosely coupled software service in a service component architecture (SCA) for an integration server by associating a service qualifier with one or more of an SCA service reference, an SCA wire, an SCA interface, or an SCA implementation based on an SCA component definition, requiring the integration server to augment an implementation execution for the SCA service to honor the service qualifier; and accepting user modification and definition of declarative service qualifiers. By allowing the association of service qualifiers with SCA service references, SCA wires, SCA interfaces, and SCA implementations, additional quality of service with which components are executed can be maintained.

Apparatus, system, and method for service component qualifiers for the declarative specification of quality of service

Provided are a method, system, and article of manufacture, wherein a client component including at least one client interface is provided. Also provided is a target component including at least one service interface, wherein the at least one client interface is capable of matching the at least one service interface. A service interface implementation corresponding to the at least one service interface is provided, wherein the service interface implementation is a dynamic service interface implementation. The dynamic service interface implementation is executed to allow access to the client component to a service provided by the target component.

Method, system, and article of manufacture for providing service components

An apparatus, system, and method are disclosed for accessing enterprise information system (EIS) resources in a service component architecture (SCA) for an integration server by selectively binding a service import to a low-level EIS resource adapter (RA) resource of an EIS service provider in response to a declarative binding definition, selectively binding a service import to an EIS service of the EIS service provider in response to a declarative binding definition, and selectively binding a service import to one or more EIS resources through an EIS service mapping configured to transform a service request from the service component client to satisfy an interface pattern of the EIS service provider. By allowing access to resources at different levels and allowing mappings of resources, the requirements of service clients can be met.

Apparatus, system, and method for a programming model for accessing EIS systems as services

Provided are a method, system, and program for generating asynchronous interfaces and methods from synchronous interfaces and methods receiving a synchronous interface to a target component having a synchronous method used by a client component to synchronously invoke the target component. An asynchronous interface is generated for the synchronous interface of the target component. An asynchronous method is generated for the generated asynchronous interface having arguments to invoke the target component, wherein the client calls the generated asynchronous method to cause an asynchronous execution of the synchronous method.

Generating asynchronous interfaces and methods from synchronous interfaces and methods

Mapping information that describes the mapping of referenced projects to their container project is included in the container project, using a 'module mapping' file. A module mapping file is a simple meta-data file, for use at development time only, which stores data that maps relative URIs to IDE project names. The module mapping file contains entries for the location of nested archives, relative to the virtual archive defined by the container project, mapped to the uniquely named referenced project within the IDE. The paths of the archive files are computed 'on the fly' just before the application server is started, rather than being simply written into an extensions file, located within the container project, in a fixed form when the enterprise application is written/developed.

Method and system for dynamically mapping archive files in an enterprise application

Methods, systems, and computer program products for programmatically enforcing referential integrity constraints defined for classes of an arbitrary modeling framework (such as the Meta Object Facility, or 'MOF') when associations among class instances are modified. The present invention relieves the application programmer of the burden of writing code to maintain the links between instances, and applications are therefore considerably easier to write and to maintain, and programmatically maintains inverse links. This reduces the amount of data to be serialized, as the other link can be automatically resolved at the time the inverse link is reconstituted, and also helps in maintaining referential integrity among serialized instances (e.g. where associations are specified in one or more XML Metadata Interchange, or 'XML', documents) because redundant information about the values of the same association will not have to be written across different documents or storage repositories.

Automatic link maintenance to ensure referential integrity constraints

Methods systems and computer program products are provided which provide a transacted variable. The transacted variable is associated with a specific transaction such that actions on the underlying object of the transacted variable do not affect the contents of the transacted variable unless the actions are carried out in the context of the specific transaction associated with the transacted variable. Furthermore, the transacted variable allows for actions to be taken in the context of its specific associated transaction irrespective of an active transaction.

Methods, systems and computer program products for controlling variables associated with transactions in a multiple transaction environment

Methods, systems and computer program products for controlling variables associates with transactions in a multiple transaction environment

A packaging algorithm for providing software applications having reduced footprints is presented. The algorithm determines the minimum required set of methods and classes from the development environment necessary for the application to run. The application is then packaged with only those necessary methods and classes. The resulting application has a reduced footprint which serves to reduce memory requirements needed to store the application and enhance performance of the application at run-time.

Growing community of inventors

Laguna Beach, CA, United States of America

Martin Paul Nally