Customizable Content Management Platform
Integrated File Collaboration
File Management Software

Similar to how a relational database provides the necessary infrastructure to manage structured information, the Xythos WebFile Server is the necessary content management platform that can be customized to manage unstructured content, documents and files. It's range of benefits and features incorporate the single versioning and management of legal forms, invoices, medical images, presentations, media files and more.

Xythos WebFile Server offers customizable content management software technology and components that can be integrated into any number of enterprise applications, enabling collaborative document and file management capabilities for all sorts of data. WebFile Server was designed to support large-scale deployments of enterprise applications for thousands of users from a single instance, and provide a set of useful and immediately deployable services to application developers.

WebFile Content Management Server Components

The WebFile Server consists of three main components:

• Web Server:

  The content management web server component of WebFile Server fields incoming HTTP requests. WebFile Server is delivered with a bundled Tomcat servlet container that also functions as the web server; however, it is also possible to install WebFile Server with a separate web server. The web server functionality may be split among several machines by making use of an HTTP load balancer, by using round-robin IP addressing, or by using some other feature native to the web server software or operating system.

• Application Server:

  The Application Server (or Java Servlet Container) component of WebFile Server runs the servlet engine and APIs and hosts the WebFile Server servlets and JSPs. The Application Server component allows communication through the WebDAV extensions to the HTTP specification as well as all other headers and methods supported under the HTTP 1.1 and WebDAV protocols. Since WebFile Server does not store state information in the application server, the system can be scaled by adding multiple, independent application servers that run together or by clustering application servers within the same WebFile Server installation.

• Database:

  WebFile Server uses a relational database to persist configuration information and to store all file metadata, such as permissions, versions, properties, comments and logging information. Supported databases include DB2, Oracle, PostgreSQL and MS SQL Server. WebFile Server can be scaled across multiple, independent databases and can also be run in any high availability configuration. There is no limitation on the volume of files and associated metadata that can be managed by the WebFile Server system.

The following components are optional for a WebFile Server deployment

• File System:

  WebFile Server can store all file content directly onto a storage device, rather than in the chosen database. The WebFile Server was designed to scale its storage capacity by simply adding storage devices. Therefore, there is no limitation on the amount of space and the number of storage devices that WebFile Server can manage. WebFile Server can easily scale to store any size file and any number of files.

• LDAP Server:

  Although WebFile Server does provide its own user model, a directory server may be used in order to provide a single place across multiple systems, in order to manage user accounts, group membership, and logon credentials. Centralized account management and a single secure user credential eliminates the problem of requiring users to remember multiple passwords, as well as requiring IT managers to handle multiple system accounts and passwords for one set of users. Xythos WebFile Server helps address this goal by integrating with any directory server that conforms to the LDAP specification v2 or v3.

• Load Balancer:

  If there is more than one Application Server in the system, a load balancer should be used in front of WebFile Server. To improve performance, the WebFile Server makes extensive use of caches.