Difference between revisions of "ECC"
| Line 60: | Line 60: | ||
Configuration of REST endpoints at: | Configuration of REST endpoints at: | ||
<code>/var/www/html/sites/all/ecompass/functions.php</code> | <code>/var/www/html/sites/all/ecompass/functions.php</code> | ||
| + | |||
| + | === Operation === | ||
| + | ==== Service startup procedure ==== | ||
| + | * Apache (web server): <code>service httpd stop| start | restart</code> | ||
| + | * Mysql (mysql server): <code>service mysqld stop| start | restart</code> | ||
| + | |||
| + | ==== Restarting the service ==== | ||
| + | see above | ||
| + | ==== Service Logs ==== | ||
| + | … | ||
| + | ==== Recurring Manual Actions / Maintenance Tasks ==== | ||
| + | '''Maintenance tasks''' (Login as admin): | ||
| + | * User management: http://ecompass.exus.co.uk/admin/people | ||
| + | * Check for module updates: http://ecompass.exus.co.uk/admin/reports/updates/update | ||
| + | |||
| + | Module updates are performed using the url above, via the web interface. Always run the update script each time a module is updated: http://ecompass.exus.co.uk/update.php?op=info | ||
| + | |||
| + | The drupal core cannot be updated via the web interface. To update the drupal core follow the instructions at: https://www.drupal.org/node/1494290 | ||
| + | |||
| + | === Other === | ||
| + | … | ||
| + | |||
| + | === Limitations of the service === | ||
| + | ; How many concurrent E-Shops with how many concurrent products are possible without causing loss in quality/speed for the hardware described above? | ||
| + | : There is no limitation for the number of concurrent users. All information is stored in different back-ends and is transferred on demand via http rest services to the ECC. The problem is that the user may experience delays when a large amount of data is requested. | ||
| + | ; If higher scaling was wanted, which of the hardware parameters would need to be increased? | ||
| + | : Currently none of the hardware parameters is the bottleneck in the ECC performance. The bottleneck is the network. | ||
| + | ; What else would be adjusted for higher scalability? | ||
| + | : A solution would be to store the data in a central database (or a clustered database) and use SQL queries instead of http REST services. All data from the various services of the distributed Ecompass platform should be saved in a central database (or a clustered database). This solution would significantly speed up the ECC. | ||
| + | ; Which further configuration would be necessary? | ||
| + | : … | ||
| + | |||
| + | === Contact Information E-COMPASS Cockpit === | ||
| + | Odysseas Bournas, [mailto:obour@exus.co.uk obour@exus.co.uk], +30 ……… | ||
Revision as of 20:04, 8 December 2015
Contents
Physical Hardware Characteristics
| Model: | DELL SERVER PE R420 |
| Processor: | (2x) Intel Xeon E5-2407 2,20GHz |
| RAM: | 128 |
| Hard Drive Space: | .. |
| Network Connection: | 1 network interface, Intel PRO / 1000 MT Desktop (82540EM) – 1Gbit |
| Hypervisor used: | VirtualBox 5.0.8 |
| Physical Load Balancing: |
Virtual Machine Hardware Specifications and Operating System
| Guest Operating System: | CentOS 6.6 - x86_64 |
| Processor: | 2 Processors, 4 Cores 2.20GHz |
| RAM: | 8 GB |
| Hard Drive Space VM: | 68,36GB (SAN/NAS configuration) |
| Network Connection: | 1Gbit |
| 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
Preparation
Service Configuration
Configuration script
availability / location
README / User Manual
availability / location
Configuration steps
The CMS is based on Drupal 7.x. and is installed at /var/www/html. There is a custom theme created and installed at /var/www/html/sites/all/ecompass.
The theme contains the CSS of the Cockpit and the custom templates/code of the site. Custom templates:
node--sales_optimiser.tpl.phpnode--price_monitor.tpl.phpnode--visitor_profiler.tpl.phpnode--product_characterisation.tpl.phpnode--price_monitor_configurator.tpl.phpnode--competitor_profiler.tpl.phpnode--dashboard.tpl.php
Configuration of REST endpoints at:
/var/www/html/sites/all/ecompass/functions.php
Operation
Service startup procedure
- Apache (web server):
service httpd stop| start | restart - Mysql (mysql server):
service mysqld stop| start | restart
Restarting the service
see above
Service Logs
…
Recurring Manual Actions / Maintenance Tasks
Maintenance tasks (Login as admin):
- User management: http://ecompass.exus.co.uk/admin/people
- Check for module updates: http://ecompass.exus.co.uk/admin/reports/updates/update
Module updates are performed using the url above, via the web interface. Always run the update script each time a module is updated: http://ecompass.exus.co.uk/update.php?op=info
The drupal core cannot be updated via the web interface. To update the drupal core follow the instructions at: https://www.drupal.org/node/1494290
Other
…
Limitations of the service
- How many concurrent E-Shops with how many concurrent products are possible without causing loss in quality/speed for the hardware described above?
- There is no limitation for the number of concurrent users. All information is stored in different back-ends and is transferred on demand via http rest services to the ECC. The problem is that the user may experience delays when a large amount of data is requested.
- If higher scaling was wanted, which of the hardware parameters would need to be increased?
- Currently none of the hardware parameters is the bottleneck in the ECC performance. The bottleneck is the network.
- What else would be adjusted for higher scalability?
- A solution would be to store the data in a central database (or a clustered database) and use SQL queries instead of http REST services. All data from the various services of the distributed Ecompass platform should be saved in a central database (or a clustered database). This solution would significantly speed up the ECC.
- Which further configuration would be necessary?
- …
Contact Information E-COMPASS Cockpit
Odysseas Bournas, obour@exus.co.uk, +30 ………