Overview
Before you install DS Server or connect an application to it, the Overview explains what the product is, how it is built and which of its two builds fits your servers. It is meant for developers, architects and administrators who evaluate DS Server or have just bought it and haven't worked with it yet.
DS Server is a document server that runs on your own infrastructure. Your applications use its DocumentProcessing Web API to convert, merge and create documents and embed its Document Editor and Document Viewer in web pages, and its built-in OAuth server controls which applications may use them. After reading this section, you know which parts DS Server has, how clients connect to it, whether to install the Core or the Classic build, which document formats it reads and writes, and how it is licensed.
Find the Right Page
| If you want to | Read |
|---|---|
| Learn what DS Server does, what you build with it and how it differs from TX Text Control .NET Server | Introduction |
| Understand the server application, its worker processes, ports, OAuth and how clients connect | Architecture |
| Choose between the Core build for Linux and Windows and the Classic build for Windows | Core and Classic |
| Check which formats each Web API endpoint accepts and returns, and the limits on Linux | Supported File Formats |
| Understand server licenses, the license period, the trial token and the trial version | Licensing Overview |
Where to Start
- Read the Introduction to decide whether DS Server fits your project.
- Read Architecture for the terms the other pages use, such as security profile, service URL and worker process.
- Try DS Server without installing it: request a Trial Token and build a first application in Getting Started.
- Choose a build in Core and Classic and install it with the Installation Guide.
Pages in This Section
- Introduction: what DS Server is, its parts, typical workflows and the comparison with TX Text Control .NET Server.
- Architecture: the ASP.NET Core application, worker processes, ports, OAuth, plugins and client connections.
- Core and Classic: operating systems, hosting, limits on Linux, fonts and runtime requirements of the two builds.
- Supported File Formats: the input and output formats of every DocumentProcessing endpoint.
- Licensing Overview: per-server licensing, the license period, client-side libraries and evaluation.