|
Harmonized Business
Information
Businesses today are
challenged by inconsistent versions of corporate
information. This inconsistency is created by
acquisitions and/or separate lines of business
that have different systems to manage their
businesses. Harmonizing the business information
across these different systems is an extremely
difficult data architecture process. The
harmonized information allows for interoperability
between these lines of businesses.
Companies can either define these harmonized data
models in-house or purchase them from third
parties.
Once companies harmonize
their data they either persist it to a Master Data
Management (MDM) hub or they persist it
to their
network for an Enterprise Service Oriented
Architecture (SOA) Initiative. The key is both
need to harmonize their business information. Each
approach allows the company to share business
information for creating applications that have a
single view of the corporation. MDM uses a master
data model to describe the business information
and SOA uses an XML Schema model to describe
uncoupled business information.
ObjectRiver addresses the
need for building transactional Web/SOA
applications using your harmonized data models
that describes the business information. We have
pioneered a best practice that leverages your
investment in data architecture. It uses your data
models for building web applications by actually
discovering your business
vocabulary from your data model.
At
the core of our technology is a programmable
metadata compiler that extends the generation of
code typically generated from a data model. This
new code facilitates data access layers for MDM,
as well as Web access layers for SOA.
ObjectRiver's sales process
includes a development workshop, where we start
from your data model and generate a complete MDM
& SOA implementation with a demo running Web
applications and data services with your
data!
|
Logical Data Models used for SOA Information Exchange
Logical Data Modeling (LDM) is the well accepted practice of designing business data models that are independent
of application and physical database implementations. LDMs are conceived by Data Architects, Business Analysts
and end users who analyze business processes and information for the purpose of defining a harmonized (logical)
data model that represents the business.
Up until
now, the next step in development of LDM would be to create a physical database design. But what if we want to persist the
logical model onto a network instead of a database?
Logical Data Models can be
used to implement an
independent data exchange SOA implementation.
The LDM can serve as the data
exchange contract that allows applications to share information.
The LDM also defines the vocabulary
for building new business processes which can be defined
as services. Implementing your SOA
exchange architecture with this method allows
it to be totally defined
from the business, top down, and the business
controls the changes to the
implementation.
If you think this makes
sense! You're right! Replay the following webinar
for the
full presentation.
Logical Data Models used
for SOA Exchange Webinar Replay
|
|
ObjectRiver SOA Release 1.0 Announced!
ObjectRiver is leveraging its expertise in database metadata, by creating a new product
that operates on SOA metadata. ObjectRiver SOA 1.0 is a new standalone product for SOA
development.
The ObjectRiver SOA solution allows creation of web services in minutes from interface
descriptions. Version 1.0 generates Java based Axis2/STaX compliant services that may
be integrated into any application server.
ObjectRiver SOA Webinar Replay
|
|
ObjectRiver MDM Release 4.0 with XPath
Version 4 MDM
solution represent JDO business objects as XML
DOM's (Document Object Model). ObjectRiver has
implemented a Jaxen XPath complient solution for
quering these objects with XPath language. Now
application programmers can write URL like XPath
queries to extract or calculate infomation
contained in the JDO business objects, without
the overhead of parsing XML.
ObjectRiver MDM Webinar Replay
|
|
|
|
4 Day Proof Of Concept Pilot
ObjectRiver has a repeatable practice to implement a POC from an ERwin data model in 2-3 man days. This is more then a POC, because the delivered infrastructure is completely ready for creating production Web/SOA applications against your ODS. The POC identifies your business objects, domains, and codes tables from your data model, and generates a data dictionary that corresponds to your business vocabulary. It also generates a complete JDO CRUD, and data services layer.
We have completed over 40 of these POC's and are actively working with integrators which are creating repeatable MDM/SOA practices to leverage our process. This POC process will accelerate your web portal or SOA development project by at least 10 months.
We offer a 4 day pilot, where the POC is brought in-house, with two of our architects, to integrate the POC into your development environment. Your data architects as well as your Java architects will learn to use the ObjectRiver MDM/SOA solution to rapidly build the data access infrastructure for creating Web and event-driven applications. It also trains the developers on the process for implementing future changes or implementing the ObjectRiver MDM/SOA solution with new data models.
|
|
