Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
cloudappliance/appladmin [2020_06_25 13:20]
jim
cloudappliance/appladmin [2020_06_25 13:51]
jim
Line 3: Line 3:
 ## 1 Software Stack  ## 1 Software Stack 
  
-{{:/​cloudappliance:steps:​sme_smearch.png}}+{{ ::sme_enterprise_file_fabric_logical_architecture.png?600 |}} 
  
 The File Fabric is built using open Internet technologies. The base operating system used s hardened Linux CentOS. HTTPD Apache Server is used for serving http requests and for temporary caching memcached is used. File Metadata is stored using a MySQL database. The File Fabric is built using open Internet technologies. The base operating system used s hardened Linux CentOS. HTTPD Apache Server is used for serving http requests and for temporary caching memcached is used. File Metadata is stored using a MySQL database.
Line 16: Line 17:
  
 The Apache server is stateless and can run on a separate host from the MySQL DB Server. This allows flexibility in deployment topologies for scalability and high availability using proven deployment configurations supported by Apache web server (e.g. multiple web servers behind a load balancer) and MySQL DB (replication,​ data sharding). The Apache server is stateless and can run on a separate host from the MySQL DB Server. This allows flexibility in deployment topologies for scalability and high availability using proven deployment configurations supported by Apache web server (e.g. multiple web servers behind a load balancer) and MySQL DB (replication,​ data sharding).
 +
 +{{ ::​sme_enterprise_file_fabric_replication_new.png?​600 |}}
  
 ## 2 Components ## 2 Components
  
-{{:/​cloudappliance:steps:​sme_2_appliance_architectu.png}}+{{ ::logical-architecture.png?600 |}}
  
 The File Fabric is built as an open modular platform. All the functionality is available via the File Fabric API and major components have hook points to integrate external system .e.g authentication , a new storage provider, payment gateway etc. The File Fabric is built as an open modular platform. All the functionality is available via the File Fabric API and major components have hook points to integrate external system .e.g authentication , a new storage provider, payment gateway etc.
Line 29: Line 32:
 **Protocol Adaptors** **Protocol Adaptors**
  
-At the top of the File Fabric Architecture diagram are protocol adapters These allow to access data using multiple protocols and work with any configured storage provider.+At the top of the File Fabric Architecture diagram ​adjacent to the REST API are protocol adapters These allow to access data using multiple protocols and work with any configured storage provider.
  
 Out of the box the File Fabric supports: Out of the box the File Fabric supports:
  
-  * REST/XML and REST/JSON: File Fasbric ​proprietary API. This is used by all the File Fabric tools, is fully documented and can be used to develop custom applications.+  * REST/XML and REST/JSON: File Fabric ​proprietary API. This is used by all the File Fabric tools, is fully documented and can be used to develop custom applications.
  
-  * WebDav/​HTTPS:​ Standard WebDav is protocol especially useful for integrating into user desktops without an Appl deployment+  * WebDav/​HTTPS:​ Standard WebDav is protocol especially useful for integrating into user desktops without an Application ​deployment
  
   * FTP/FTPS: Standard FTP and FTP Secure protocol   * FTP/FTPS: Standard FTP and FTP Secure protocol