In part 4, we discussed our application integration framework design pattern at the level of the Connection object.  A Connection represents a logical connection to each Application, and physically to the Applications Adapter.  A Connection contains 1 or more DataFlows.  A DataFlow is a collection object that contains 1 to 4 schemas (i.e. XSDs), 0 or more rules, and 0 to 2 maps depending on DataFlow communication type.

 

With respect to rules, for anyone that has used Microsofts Outlook Rules and Alerts functionality will recognize our GUI Rules Designer.  As mentioned in another post, its been done before, you just have to go look for it .  The Rules Designer contains a Rules Manager that allows the BA to add, edit or delete rules in an ordered list, a Rules Editor that allows the BA to declaratively make rules, A Fact Editor that allows a BA to declaratively name a rule, and A Rule Expression Editor that allows the BA to define expressions, and if required, provides the facility to upload custom rules (i.e. .NET assemblies).

 

This diagram shows a screen shot of our Rules Designer:

 

 

At this level we also provide the capability for BAs to upload test XML documents that can be validated against the specified schemas.  The BA can also test the (XSL) map for proper transformations.  Any errors for schema validation and/or map transformation are returned to BA in the Designer.  In fact, if the BA provides a valid XML document with test values that represent what the real values are likely to be, business rules can also be executed, in which the return values are the resulting actions that would occur for the rule processing.

 

Thats it.  The BA has now declaratively configured a complete application integration scenario using our DSL Visual Designer tool that implements our application integration framework design pattern.  As mentioned before, our Visual Designer is exposed over the internet as a Rich Internet Application (RIA).  This allows a BA easy access to their application integration solutions from anywhere in the world, in a secured manner.  This approach models the software as a service scenario where there are no requirements for an organization to use the Visual Designer other than a browser.

 

Now what?  After the BA has completed defining the application integration model and saved the model, the BA can now order the integration definition to be built (i.e. code generated) from our Software Factory.  The order includes pricing based on the number of application integration connections modeled in the scenario.  Once the order has been placed, the turnaround time could be a few hours to a few days, depending on options ordered.  The BA then returns to the Visual Designer web site and can download the resulting MSI to be installed on their target system.  Once installed, the BA and/or System Administrator can run a self-test to verify and certify the application integration solution for correctness. 

 

The runtime installation also includes other tools to manage and monitor the application integration solution.  This includes Business Activity Monitoring for monitoring the application integration scenario, a Centralized Exception Manager that handles any runtime messaging exchange exceptions, complete with notifications, and an Integration Manager that allows runtime configuration of security credentials and application end point locations.

 

With respect to making any changes to the application integration scenario, the BA can launch the Visual Designer again, load up the existing model, that has been versioned, make modifications (to a schema for example) and save, then order and get another MSI that performs the upgrade process on the installed application integration solution.

 

Next post I will discuss our Software Factory for taking application integration scenarios based on our framework design pattern (as realized by our DSL Visual Designer and output as an XML definition) and walk through the steps on how we configure our Software Factory template to code generate the specified solution.