Data Exchange (DEX)
What is Data Exchange (DEX)?:
Our CRM Data Farm Inc. technical team is introducing a new concept called Data Exchange (DEX). We need to address the following to the IT community:

       What is Data Exchange (DEX)?
       What are goals of building and standardizing Data Exchange (DEX)?

What is DEX?
To understand what is our DEX, our audience need to understand Web Services which is using XML as a communication tool and web services is defined as follows:

A web service is any piece of software that makes itself available over the internet and uses a standardized XML messaging system. XML is used to encode all communications to a web service. For example, a client invokes a web service by sending an XML message, then waits for a corresponding XML response.

Our DEX is an Intelligent Upgrade of Web Services. DEX is a set of software tools which help the communication and the exchange of data. The data exchange is not limited to XML, but it encompasses the following data structures:

       Java Data Access Object (DAO)
       Java Set
       Message Queues
       Misc - We are also open to other data format

DEX also provides data exchange parsers and convertors to resolve any data exchange issues and communication. DEX should be a virtual service running on a virtual server with parsers and convertors to handle any data exchange parsing and formatting. Our DEX's convertors build XML format with No Schema regardless of its sizes and complexities.

What are goals of building and standardizing DEX?
Building and standardizing DEX would pave the road for intelligent and faster communication media the same way web services did for the IT community.

Excel Sheet-DAO-XML Data Exchange Seed Framework
We had built our "ICM_DB_TestComponents" project using NetBeans (8.2). The following are the actual code of our for "ICM_DB_TestComponents" project. We created our first Parser-Converter Java code and we called "Using Business Rule #1".

The following are our "ICM_DB_TestComponents" project input-out files and Java code files.
We welcome any feedback or comments and our contact email is:

Input Files:
       1.     SimpleInputExcelSheet.xlsx
       2.     BusinessToken_ID.txt

Java Constant Classes:

Package: Java DAO Classes - unstructured_data_idao:

Package - unstructured_data_parser:

Output Files:
       2.     SimpleInputExcelSheet_XML.xml
       2.     Debugger Tracking of Input and Output

       1.     ICM_DB_TestComponents javadoc link

ICM_DB_TestComponents Architect-Design in a Nutshell
Our goal of "ICM_DB_TestComponents" project to automate the parsing-converting of any excel sheet to DAO and SOAP-XML file. It has to perform the following:

Business key words are stored in a Business Token ID text files to help with parsing, naming the fields, possibilities and accuracy of how to name the fields, methods and intelligent parsing and tracking.
Parse the excel sheet horizontally to figure out the DAO field's names, types and values and possible values, percentage of accuracy using the Business Token ID text files.
Using the excel row and column numbers (row * Constant + column) to create an ID index for formulas and functions to track and access.
Parse the excel sheet vertically to figure out formulas and functions, parameters, comments and labels
Parse the excel sheet vertically to figure out tables, rows and comments and label
Create fields (class privet variables) , methods (get() and set())
Create Java DAO
Compile and store the .class file
Create with excel sheet values and store SOAP-XML file
XML file tags are created with structure and ID to help with conversions to DAO. The size of XML files must be managed and automated for optimizing the two conversion XML-SOAP and DOA-IDAO