ObjectRiver’s products are developed around a unique programmable metadata compiler technology. Our whitepaper discusses our process of discovering business objects and vocabulary within a data model. This is how we harvest metadata from the data model to feed our compiler. We typically start with a data model like ERwin, because our process includes adding additional subject areas and user defined properties to the model which allows us to define business objects and correct inconsistencies within the metadata. This process is done without changing the logical or physical data model. One of the artifacts of this process is a generated object oriented data dictionary. It is completely created from the data model and contains object definitions, master code sets and domain types.

Both of our products have extremely small runtime components because the majority of the runtime is generated from the model. The products are metadata compiler centric and can be thought of as framework generators.

ObjectRiver MDM Product

• Programmable Database Metadata Compiler
• Integrated with ERwin for Business Object Mapping
• Generated Business Object Data Dictionary
• Java language object mapping.
  • XPath 1.0
  • Visitor Design Patterns for logic and rules
  • SDO coming soon!
• Physical Data Models (Database persistence)
  • Generates JDO CRUD data access layer
  • Business Object Auditing
  • Business Event Database Queue
  • XML Schema, XML Parsers
• Logical Data Models (Network persistence)
  • SOA Data Exchange Layer
  • XML Schema, XML Parsers

The MDM product addresses the need for building a data access layer to an ODS (Operational Data Stores) for the purpose of creating web applications. For MDM projects ObjectRiver needs to be used in conjunction with an ETL (Extract Transform Load) product.

The product takes business objects as documented from the data dictionary and generates a complete JDO (Java Data Objects) transactional CRUD (Create, Read, Update and Delete) data access layer, with auditing and business events.

All object definitions are hierarchal and can be represented in XML, with generated XML Schema and WSDL for creating web applications.
Whitepaper: Leveraging Data Models to Create a Business Vocabulary for SOA Exchange

Webinar: ObjectRiver MDM

 
Logical Data Model used for SOA Information Exchange
 

We are seeing a trend where companies are using Logical Data Models as the foundation for creating SOA exchange models. In a SOA exchange model the business objects are persisted to a bus architecture instead of a database. This use case uses both the ObjectRiver MDM and SOA products.

Whitepaper: Logical Data Models for SOA Information Exchange

Webinar: Logical Data Models for SOA Exchange



ObjectRiver SOA Product

• Programmable Services Metadata Compiler

The SOA product operates on services metadata while using database objects, codes and domain types as perameters to the services. In short, the data model is used as a metadata repository to supplement the SOA metadata service definitions.

This product is much more than a WSDL generator. In its first version it generates a complete Axis2/STaX soap stack. 
 

Webinar: ObjectRiver SOA