Solutions with JBoss DNA

Often the best solution is one that is tailored for the problem domain.  With JBoss DNA, you don't need to write a ton of code or even build new applications.  (Of course, you can if you want, and we can help there, too.)  Instead, JBoss DNA is designed to make custom solutions by specializing a DNA installation involves customizing the way information is presented and the way information is processed.

Creating the Solution

JBoss DNA uses views to control how the information is presented, and JBoss DNA stores the views as data within its repository. So changing existing views or adding new views is a matter of changing data, not programming.  Some very usable views come already installed, but it's easy to make your own.

Customizing how the information is processed is a matter of creating custom "[sequencers|DOC-9495]" to extract the useful information from the content that's uploaded to the repository.  This does require writing code, but we've tried to make that as easy as possible.

So redeploying those customizations is as easy as seeding a new JBoss DNA installation with the customized views and the custom sequencers.

Example Solutions

Here are a few solutions that add value to the existing family of JBoss products.  Of course, other solutions are certainly possible.  We'd recommend creating them as part of an open source project or having JBoss Solution Architects create the solution for you.

Solution 1: Service Oriented Architecture (SOA)

Specializing a DNA installation involves creating the views and implementation of various components necessary to understand and present the information for a domain. Here are a few solutions that add value to the existing family of JBoss products:

• The Service Oriented Architecture (SOA) solution turns DNA into a SOA Repository by enabling DNA to work with the information describing the web services, schemas, processes, components, applications and policies found in a SOA environment. With this solution, DNA is able to understand SOA-related artifacts, including WSDL, XSD, BPEL, jPDL, Drools rules, etc.

• The Data Services solution turns DNA into a metadata repository of database schemas, data sources, data services, and transformation/mapping relationships. This repository is integrated into the MetaMatrix version control system, and models are automatically sequenced to extract their structured information. Users can then use this repository to visualize, search, analyze, build reports, and even edit the data services metadata.

• The Rules Repository solution turns DNA into a rules management system.

These and other solutions can be created as part of open source project or by JBoss solution architects as part of a customization effort.