International Business Machines Corporation

Cognos, Inc.

IBM Canada Limited - IBM Canada Limitee

Glenn D Rasmussen

Paul S Donis

David C Dewar

Katherine Wallace

Henk Cazemier

Richard F Blackwell

Katherine A Wallace

An application model build processor generates one or more application model build artifacts based on an application model. In one example, a method includes receiving inputs identifying application model subsets and audiences, and associating application model subsets with the audiences. The method further includes receiving inputs identifying semantic constructs of the application model with the application model subsets. The method further includes generating application model build artifacts based on the application model and defined subsets. The method further includes generating documentation topics for semantic constructs in the application model based on the semantic construct, the subsets to which it belongs, the audiences associated with those subsets, and other semantic constructs in those subsets.

Generating application model build artifacts

At least one processor may determine one or more issues in one or more of a plurality of documentation topics that document at least one software functionality based at least upon applying one or more business rules to the one or more of the plurality of documentation topics. Responsive to determining the one or more issues, one or more entries may be inserted into an issues report, wherein the one or more entries include information regarding the one or more issues.

Content validation for documentation topics using provider information

A target drill-through metadata manager has a target drill-through metadata handler and a target specification processor. The target drill-through metadata handler defines and manages target drill-through metadata in a metadata model for model constructs that are selected as drill-through target constructs. The target specification processor processes a target report definition using the target drill-through metadata to locate a data item that refers to a drill-through target construct or part of a drill-through target construct, and automatically adds one or more target filters associated with the drill-through target construct to a target report.

Managing drill-through targets

The present disclosure provides a system and method of generating a transformation specification document describing transformations for transforming a received message conforming to a second interface definition to a message conforming to a first interface definition. The system and method comprise loading the first interface definition into memory; loading the second interface definition into memory; determining all additional elements of the second interface definition loaded into memory not contained in the first interface definition loaded into memory; generating processing logic for removing all of the determined additional elements from the received message; and generating the transformation specification document using the generated processing logic. The present disclosure further relates to a computer program product generating a transformation specification document.

Generating a transformation description document for transforming messages

A mechanism is provided for generating a filter expression using tree parameters receives an expression wherein operators of the expression bind multiple data items to a single parameter to form a received expression, generates a default prompt control using received metadata and the received expression and prompts for an input selection using the default prompt control. Responsive to receiving selected values in response to the default prompt control to form received values the computer-implemented process generates a native database query using the received expression with the single parameter and the received values, wherein the single parameter is a tree parameter.

Managing parameters in filter expressions

Transformations are provided for transforming a metadata model that contains model objects. The metadata model has a multiple layers including a lower layer containing one or more lower abstraction model objects having a lower abstraction level and a higher layer containing one or more higher abstraction model objects having a higher abstraction level. The transformations transform the model objects from the lower layer to the higher layer.

Methods and transformations for transforming metadata model

A method and system for mapping datasources in a metadata model that provides datasource connections that are structurally isolated from the metadata model and which incorporate physical datasource addressing information for mapping a logical datasource structured within the metadata model to a particular physical datasource 'on-the-fly', and in a run-time environment. In an embodiment of the present invention, security can be implemented to limit user access leveraging an organization's security regime.

Method and system for mapping datasources in a metadata model

A metadata model defines model objects to represent one or more data sources. The metadata model comprises a data access layer, a business layer and a package layer. The data access layer contains data access model objects. The data access model objects include a data access model object that describes how to retrieve data from the data sources. The business layer contains business model objects. The business model objects include a business model object that describes a business view of data in the data sources. The package layer contains package model objects which reference subsets of business model objects.

Metadata model

A query engine formulates a data source query to obtain data from one or more data sources. The query engine uses a metadata model containing model objects that represent the data sources. The metadata model has a data access layer, business layer and package layer. The model objects of the business layer are constructed based on the model objects contained in the data access layer. The query engine interacts to the metadata model at the business layer, and formulates a data source query based on a query specification provided by a client application. Thus, the query engine allows use of different type of client applications to obtain reports from one or more data sources.

Growing community of inventors

Ottawa, Canada

Glenn D Rasmussen