Abstract: A system and method for storing and providing metadata. Metadata may be retrieved from multiple sources. The metadata is stored in facets in a repository and tagged to indicate one or more of the source, a time frame, or an associated data object. In response to receiving a request for metadata, a system selects metadata based on the specified object, source, or time frame. Access permissions corresponding to the requester are used to select and provide metadata for which the requester has permissions.

Abstract: A system and method for facilitating execution of one or more data integration projects in multiple environments or an environment that undergoes changes. Each project has a set of project parameters, which are bound to environment variables. Each environment has a corresponding environment representation with environment variables and corresponding values. Each project is mapped to an environment representation. Values of environment variables are provided to projects with corresponding parameters. When one or more projects are changed to a different environment with a different corresponding environment representation, the environment variable values of the new environment representation are provided to the projects. When an environment change is reflected in the environment representation, the changed variable values are provided to mapped projects.

Abstract: The method including receiving, at a first node of a plurality of computing nodes, a message ownership migration request for a first message. The message ownership migration request can originate from a second node of the plurality of computing nodes. The first node can be an owner of the first message in a first instance of a message queue at the first node. The first message can be published from a first publisher to the message queue at one of the nodes of the plurality of computing nodes. The first message in the first instance of the message queue at the first node can be replicated at a second instance of the message queue at the second node. A first subscriber can be subscribed to the second instance of the message queue at the second node. The method also can include designating the second node as a new owner of the first message such that the first node is no longer the owner of the first message.

Abstract: A system and method for facilitating execution of one or more data integration projects in multiple environments or an environment that undergoes changes. Each project has a set of project parameters, which are bound to environment variables. Each environment has a corresponding environment representation with environment variables and corresponding values. Each project is mapped to an environment representation. Values of environment variables are provided to projects with corresponding parameters. When one or more projects are changed to a different environment with a different corresponding environment representation, the environment variable values of the new environment representation are provided to the projects. When an environment change is reflected in the environment representation, the changed variable values are provided to mapped projects.

Abstract: The method including receiving, at a first node of a plurality of computing nodes, a message ownership migration request for a first message. The message ownership migration request can originate from a second node of the plurality of computing nodes. The first node can be an owner of the first message in a first instance of a message queue at the first node. The first message can be published from a first publisher to the message queue at one of the nodes of the plurality of computing nodes. The first message in the first instance of the message queue at the first node can be replicated at a second instance of the message queue at the second node. A first subscriber can be subscribed to the second instance of the message queue at the second node. The method also can include designating the second node as a new owner of the first message such that the first node is no longer the owner of the first message.

Abstract: A system and method for facilitating execution of one or more data integration projects in multiple environments or an environment that undergoes changes. Each project has a set of project parameters, which are bound to environment variables. Each environment has a corresponding environment representation with environment variables and corresponding values. Each project is mapped to an environment representation. Values of environment variables are provided to projects with corresponding parameters. When one or more projects are changed to a different environment with a different corresponding environment representation, the environment variable values of the new environment representation are provided to the projects. When an environment change is reflected in the environment representation, the changed variable values are provided to mapped projects.

Abstract: A system and method for storing and providing metadata. Metadata may be retrieved from multiple sources. The metadata is stored in facets in a repository and tagged to indicate one or more of the source, a time frame, or an associated data object. In response to receiving a request for metadata, a system selects metadata based on the specified object, source, or time frame. Access permissions corresponding to the requester are used to select and provide metadata for which the requester has permissions.

Abstract: A system and method for storing and providing metadata. Metadata may be retrieved from multiple sources. The metadata is stored in facets in a repository and tagged to indicate one or more of the source, a time frame, or an associated data object. In response to receiving a request for metadata, a system selects metadata based on the specified object, source, or time frame. Access permissions corresponding to the requester are used to select and provide metadata for which the requester has permissions.

Abstract: A system and method for facilitating execution of one or more data integration projects in multiple environments or an environment that undergoes changes. Each project has a set of project parameters, which are bound to environment variables. Each environment has a corresponding environment representation with environment variables and corresponding values. Each project is mapped to an environment representation. Values of environment variables are provided to projects with corresponding parameters. When one or more projects are changed to a different environment with a different corresponding environment representation, the environment variable values of the new environment representation are provided to the projects. When an environment change is reflected in the environment representation, the changed variable values are provided to mapped projects.

Abstract: A system and method for facilitating execution of one or more data integration projects in multiple environments or an environment that undergoes changes. Each project has a set of project parameters, which are bound to environment variables. Each environment has a corresponding environment representation with environment variables and corresponding values. Each project is mapped to an environment representation. Values of environment variables are provided to projects with corresponding parameters. When one or more projects are changed to a different environment with a different corresponding environment representation, the environment variable values of the new environment representation are provided to the projects. When an environment change is reflected in the environment representation, the changed variable values are provided to mapped projects.

Abstract: A system and method for extracting data from an input source, transforming the data, and loading the transformed data to an output destination. A schema contract including constraints is used to validate a set of input data column types and translate them into a set of actual types. Mapping data in the schema contract enable mapping input data columns to data columns used by data integration components. The constraints and mapping data provide flexibility in transforming sets of data having different sets of input data column types, while providing a fixed set of types for use during dataflow executions. Flexibility may enable optional columns, sets of one or more columns, varying arrangements of columns, and variations in type definitions of each column.

Abstract: A system and method for facilitating execution of one or more data integration projects in multiple environments or an environment that undergoes changes. Each project has a set of project parameters, which are bound to environment variables. Each environment has a corresponding environment representation with environment variables and corresponding values. Each project is mapped to an environment representation. Values of environment variables are provided to projects with corresponding parameters. When one or more projects are changed to a different environment with a different corresponding environment representation, the environment variable values of the new environment representation are provided to the projects. When an environment change is reflected in the environment representation, the changed variable values are provided to mapped projects.

Abstract: A system and method for storing and providing metadata. Metadata may be retrieved from multiple sources. The metadata is stored in facets in a repository and tagged to indicate one or more of the source, a time frame, or an associated data object. In response to receiving a request for metadata, a system selects metadata based on the specified object, source, or time frame. Access permissions corresponding to the requester are used to select and provide metadata for which the requester has permissions.

Abstract: A system and method for extracting data from an input source, transforming the data, and loading the transformed data to an output destination. A schema contract including constraints is used to validate a set of input data column types and translate them into a set of actual types. Mapping data in the schema contract enable mapping input data columns to data columns used by data integration components. The constraints and mapping data provide flexibility in transforming sets of data having different sets of input data column types, while providing a fixed set of types for use during dataflow executions. Flexibility may enable optional columns, sets of one or more columns, varying arrangements of columns, and variations in type definitions of each column.

Abstract: A system, method, and program product are provided that generates population data by receiving a desired human population description from a user. The system, method, and program product then randomly generates attributes corresponding to a number of generated individuals, based on the received population description. The system, method, and program product relate some individuals to some of the generated individuals. In order to relate the related individuals to the generated individuals, the system, method, and program product select attributes corresponding to one of the generated individuals, include some of the selected attributes as attributes of the related individual, and retrieve additional attributes for the related individual, the additional attributes being different than the selected attributes. Finally, the system, method, and program product store the attributes corresponding to the generated and related individuals in a data store.