Products
Canonical Model Management
XML Messages Built from the Canonical Model
The eventual output of a Canonical Model is an XML message or Schema. Canonical Models are often large and complex, designed to meet the integration needs of an enterprise, line of business, or project. The key to their widespread usage is the ability to easily and quickly build subset XML schema from the model for use in payloads and WSDL. igniteXML addresses this challenge with a simple web interface built for consumers of the Canonical Model. Business analysts are able to navigate the model, understand data lineage, and specificify which parts of the model should be used to the integration developers. The integration developer can easily search and navigate the model to pick the components they need and automatically build run-time optimized subset schema from the model. If the model has the correct vocabulary relationships added, they can even navigate to the required components using the Database Model vocabulary they are familiar with and igniteXML will point them to the approved definition from the Canonical Model. The result is a model derived XML schema that only contains what is needed for the XML message requirement. In addition igniteXML includes in the download pack, details of how the message maps to back end data models.
Subset XML Schema and Message Payload Development
The Canonical Model is too large for effective use in message development. Instead, a subset schema that only contains what is required by the message while maintaining alignment to the model is required. igniteXML has removed the manual process of creating subset schemas using an easy to use web interface that allows anyone to search and navigate the model (directly or through the application vocabulary familiar to them), find the components within the model that meet their message requirements, add the components to a pick list, and auto-generate a run-time optimized XML Schema. Valid message payloads are developed at a fraction of the time.
Governance and Reuse
For the Canonical Model to be used as the starting point for integration, it is essential that everyone involved in planning, building, and maintaining SOA based applications can easily access and use the model. Developers building interfaces that map two data sources don't want to think about the controlled vocabulary they're supposed to use; they want an easy way to find what they need, be able to use it, and move on to the next requirement. igniteXML has made this easy. And, because the model is easy to navigate and build from, one-off definitions resulting in silos of data that break interoperability are no longer a concern.
Run-Time Optimization
igniteXML produces run-time optimized schemas that are aligned to the model without schema bloat and because they are automatically built from the model they are valid and complete. This means that deployed applications are no longer slowed down by overcomplicated XSD payloads and that testing cycles are dramatically reduced.
Business Buy-In
Most developers and analysts (model users) that may be required to move to a Canonical Based approach, would prefer to continue to use the vocabulary they are familiar with, rather than learn the additional vocabulary of the Canonical Model and have to map the two together.With igniteXML is possible to overlay several different vocabularies onto the Canonical Model. This way the model users can search the model using the vocabulary they know and will be taken to the appropriate part of the model. For example their vocabulary may refer to Client and the Model may refer to Customer.
