Difference between revisions of "Data Analyser"
| Line 53: | Line 53: | ||
1. MySQL general schema | 1. MySQL general schema | ||
| + | |||
[[File:01.png|255px]] | [[File:01.png|255px]] | ||
2. SQL Server general schema | 2. SQL Server general schema | ||
| + | |||
[[File:02.png|332px]] | [[File:02.png|332px]] | ||
| Line 112: | Line 114: | ||
Figure 8: Visitors table CREATE code for SQL Server | Figure 8: Visitors table CREATE code for SQL Server | ||
| + | |||
[[File:11.png|484px]] | [[File:11.png|484px]] | ||
| + | |||
Figure 9: | Figure 9: | ||
Revision as of 22:20, 21 December 2015
Contents
Physical Hardware Characteristics
| Model: | |
| Processor: | |
| RAM: | |
| Hard Drive Space: | |
| Network Connection: | |
| Hypervisor used: | |
| Physical Load Balancing: |
Virtual Machine Hardware Specifications and Operating System
| Guest Operating System: | |
| Processor: | |
| RAM: | GB |
| Hard Drive Space VM: | |
| Network Connection: | |
| Minimum required Network Connection: |
Service Environment and Set-up on VM1
| Software | Download |
|---|---|
| Software-Name | Software-Link |
| Software-Name | Software-Link |
| Software-Name | Software-Link |
Software Licenses
Please indicate if a commercial provider would need to buy commercial licenses of a certain software used for operating the service and – if so – what cost this may produce approximately
OS Environment Variables
…
Installation
This following chapter provides detailed explanations for different technical modules developed by CICtourGUNE for the Data Analyser Module within the E-Compass Data Mining Services.
The Following subsections are described:
- Database
- REST services in JAVA
- Data Mining in R
In order to have a better understanding of the different developments, their location, distribution and used protocols are commented.
DATABASE
First of all, a MySQL or SQL Server database must be configured so that REST services an R data mining processes can both properly work. Currently those two database types are supported in both JAVA REST services and R processes, but other database types could be considered (if necessary).
1. MySQL general schema
2. SQL Server general schema
In the following lines, required database schema and tables will be described.
MySql
After creating a new database in a MySQL server, those are needed code sentences in order to create the required tables:
1. E-shops table
Figure 1: E-Shops table CREATE code for MySQL
2. Competitors table
Figure 2: Competitors table CREATE code for MySQL
3. Products table
Figure 3: Products table CREATE code for MySQL
4. Visitors table
Figure 4: Visitors table CREATE code for MySQL
SQL Server
After creating a new database in a SQL Server server, those are needed code sentences in order to create the required tables: 1. E-shops table
Figure 5: E-Shops table CREATE code for SQL Server
2. Competitors table
Figure 6: Competitors table CREATE code for SQL Server 3. Products table
Figure 7: Products table CREATE code for SQL Server
4. Visitors table
Figure 8: Visitors table CREATE code for SQL Server
Figure 9:
Preparation
…
Service Configuration
…
Configuration script
availability / location
README / User Manual
availability / location
Configuration steps
… Configuration of REST endpoints at: …
Operation
Service startup procedure
…
Restarting the service
…
Service Logs
…
Recurring Manual Actions / Maintenance Tasks
…
Other
…
Limitations of the service
- With which parameters does the service scale?
How many concurrent E-Shops, how many concurrent products and how many users/E-Shop customers are possible without causing loss in quality/speed for the hardware described above?
- …
- If higher scaling was wanted, which of the hardware parameters would need to be increased?
- …
- What else would be adjusted for higher scalability?
- …
- Which further configuration would be necessary?
- …
Contact Information Data Analyser
José Manuel García Nieto, jnieto@lcc.uma.es, +34 951 952924
