DataXtend 8.4 and Beyond

1. DataXtend 8.4 and Beyond Tomáš Kučera Principal Solution Architect November 11, 2009

2. Agenda • What‘s New in DataXtend 8.4 • Ideas for Future Releases

3. Overview: What‘s New in DataXtend 8.4 • Collaboration Improvements • Development Enhancements • Import / Export Improvements • Low Impact Data Distribution • ACCORD Model Browser Support • Support for Artix Data Services • Creating and Maintaining Service Interfaces • Runtime and Other Improvements

4. Collaboration Improvements • Three-way comparison and synchronization • View the differences between two versions of a project and their common ancestor in the compare editor • Provides better control when merging multiple changes made by several developers working on the same project • Filtering • Can adjust filtering options in the compare editor to create a tree view that focuses on differences between certain items in a project

5. Collaboration Improvements • Searching • Provides a search capability so you can search your project for specific files, directories or items • Comparison Report • Comparison Report now more closely resembles the view you see in the Compare Editor • User Preferences to control what you see in compare editor

6. Overview: Development Enhancements • Text Based Expression Builder • Project Properties • Support for Exporting Diagrams • Operations Added to the Model Map View • Computed Attributes Shown in Mapping View • Map to SubClass Attributes

7. Text Based Expression Editor

8. Project Properties

9. Support for Exporting Diagrams • Supported Views: • Schema View sub views (component, graph and tree) • All three map views • The project view • The Tester's "Sequence" diagram

10. Operations Added to the Model Map View

11. Computed Attributes Shown in Mapping View

12. Map to SubClass Attributes • In 8.4 you can create a transformation to and from an attribute of a subclass • Previously, validation did not allow this type of mapping • You would have to map to the parent class instead

13. Enhancements in Importing and Exporting XML • Upon import of XML • All simple types, elements, complex types, and attributes are converted to DataXtend-specific elements • Upon export of the DataXtend XML schema • Some of these elements remain DataXtend specific • For other elements, DataXtend now retains enough information from the source schema that when exported these element match the original

14. Low Impact Data Distribution Improvements • Improved platform support for LIDD • Oracle 11g Change Capture • WebLogic 10 Deployment • Bi-directional Transfers of Database Changes now allowed • OnRamp and Resolver for Oracle Database can be on the same machine

15. ADS and DataXtend SI Integration • DXSI developers can make use of ADS data models • Standards libraries downloaded and installed into ADS Designer or • Customer-developed models • ADS developer generates DOD (Data Object Definition) file and then imports it into DXSI Workbench as a • Data Service, Data Source OR Common Model • ADS DOD Importer plug-in is installed into DXSI workbench when you install ADS unless you • Installed ADS first or • Didn’t specify a license file upon install • Once the plug-in is installed, you can import DOD files into DXSI as you would any other type of schema file supported by DXSI • In effect, any schema that can be imported to ADS is now importable to DXSI also

16. ADS and DataXtend SI Integration • In ADS Designer, you do the following: • Create a model • Download a standards library data model (.dod) file from the Home page • Create a model by importing a supported file format • Create your own data model • Build Java class instances of your data model • If planning to use test data that comes with standards libraries, decrypt it first using ADS Designer Tools  Decrypt menu option • In DataXtend SI, you do the following: • Import the ADS schema files (.dod) into your DXSI eclipse project, including any required test data • Import an ADS data model (DOD File) into your Exchange Model • Add the JAR file(s) that you generated from your data model in ADS to your DataXtend SI project's Java build path

17. ACORD Model Browser

18. Creating and Maintaining Service Interfaces • Previously, to create a service interface based on some portion of the common model • You could export all or part of your common model and re-import it as a data source or data service • DXSI 8.4 provides a new XML Schema Editor • May be used to create and maintain service interfaces based on the common model • GUI editor interface makes it easy to select portions of the source (common) model for inclusion in your target model • Dependencies may be indicated for you as you build your model • Auto-map generation feature can automatically map to common • Can include reverse relationship attributes instead of or in addition to normal relationship attributes • Can select a computed attribute from the common model and make it a physical attribute in your XML schema

19. Service Isolation • Enables creation of service specific runtime artifacts • A service or set of services can be identified for minimized packaging • Runtime artifacts dependent on these exported services can be significantly smaller than those for the entire exchange model • Can be deployed and managed independently

20. Model Class Loading Isolation • DXSI was previously using one class loader to load all model sessions and related classes • Can cause collision between two data source archives • Runtime might behave in an unexpected way • This new feature loads each model in its own class loader • Avoids class name collisions between two or more models • Resolves issues such as loading the models for different versions of the same software or different pieces of software containing the same java packages / classes • For example, two similar SQL databases turned out to have namespace collisions at runtime • Also helps users that want to build their own extensions • Minimizes challenges faced regarding classpath collisions

21. Stopping Data Source Invocation on Validation Failure • Previously rule configuration property “Validate Data Sources”, required validation of each data source before calling any on-insert operations • Does not address need to do the same with Common Model or Data Service validation • Rule configuration property was renamed to “Enforce Validation Rules” • Allows user to have more control of timing and runtime consequences of rule evaluation • A rule if reported, should prevent data source callouts or commit • On by default, so for old configurations not specifying a rule configuration, we will create one with this option unchecked

22. JMS Adapter Support for Non-XML Message (binary) • Previously, to send a JMS Message to DXSI through the JMS adapter containing Cobol Copybook • Data had to be converted to an ASCII XML format for DXSI to be able to parse it • As of 8.4, DXSI supports “binary over JMS” • The JMS Message may contain EBCDIC formatted data • No longer has to be converted to ASCII for DXSI to parse it

23. Improved Configuration Usability • New Runtime Environment • Contains properties for • Data source connection information • Transactional behavior • Decouples information to make it easier by having different runtime environments associated with a single data source

24. New Platform and Tools Support • JMS Adapter Supports Non-XML Message (binary) • Message can contain COBOL Copybook formatted data in EBCDIC format • Red Hat Enterprise Linux 5 Support • Support Import / Export of XMI • Added Magic Draw to list of supported UML Editors • Added ability to export XMI to RSM, RSA and Enterprise Architect • GlassFish ESB V2 • HSQLDB 1.8 • Open source, lightweight relational database that can be configured to run in-memory • Improved platform support for LIDD • Oracle 11g Change Capture • WebLogic 10 Deployment

25. Agenda • What‘s New in DataXtend 8.4 • Ideas for Future Releases

26. Overview: Ideas for Future Releases • ADS and DataXtend Unification • Corporate Metadata Solution • Delete support • Metadata Repository Support • Modularize Architecture • Rearchitect Metamodel • Runtime Optimization • Support New Application Types • Support for Flat Files • Tooling for Non-Developers

27. Overview: Ideas for Future Releases • Content types • Mapping Standards • Runtime debugging • Selling Content • Spring and DXSI • Streaming options

28. Tomáš Kučera tku@progress.com