Diploma Thesis Santiago Gómez Sáez - IAAS

Appendix B.
Messages
In this chapter we provide an overview of the requests which are sent to, and received
from the extended ServiceMix-mt. For MySQL requests we provide the TCP packets which
are transferred between the application, ServiceMix-mt, and the backend MySQL database
system. For NoSQL requests we present messages samples which are in JSON format, but its
content varies among the different backend Cloud data store providers.
B.1. Normalized Message Format Content Description
In this section we provide an overview of the data structures which are sent in the NMF.
The sections of the NMF where the data and meta-data are sent are the properties, and the
attachment. In the Listing B.1 we detail the contents sent in each of the sections, and the data
structures in which the data and meta-data are stored.
1 ########## Normalized Message Adaptation for CDASMix ###########
2
3 Properties for the backend connections are stored in this format. At this time, only joins
4
which involve tables in the same backend db are supported:
5 ////////////////////////////////////////////////////////////////////////
6
7 - MySQL || NoSql -> NMF (Request Message)
8 // Main properties
9 - target_data_sources : number of target data sources. This number will set the length
of the properties vector and will set the length of the vector queries
10 - tenantId : string (UUID)
11 - userId : string (UUID)
12 if (mysql)
13 - mysqlServerPropsQueries:vector // server configuration queries that the
14
proxy has received from the jdbc driver, e.g. SET names, SET character_set_*
15 // Backend datasource dependent properties : stored as Properties in vector.
16 - Tenant configuration data
17 - source & target dataSource name : string
18 - source & target dataSource type : family-mainInfoStructure-secondaryInfoStructureversion
19 - source & target dataSource protocol : mysql | http.[xml|rest]
95