- Release notes
- Getting started
- Installation
- Configuration
- Integrations
- Authentication
- Working with Apps and Discovery Accelerators
- AppOne menus and dashboards
- AppOne setup
- TemplateOne 1.0.0 menus and dashboards
- TemplateOne 1.0.0 setup
- TemplateOne menus and fashboards
- TemplateOne 2021.4.0 setup
- Purchase to Pay Discovery Accelerator menus and dashboards
- Purchase to Pay Discovery Accelerator Setup
- Order to Cash Discovery Accelerator menus and dashboards
- Order to Cash Discovery Accelerator Setup
- Basic Connector for AppOne
- SAP Connectors
- Introduction to SAP Connector
- SAP input
- Checking the data in the SAP Connector
- Adding process specific tags to the SAP Connector for AppOne
- Adding process specific Due dates to the SAP Connector for AppOne
- Adding automation estimates to the SAP Connector for AppOne
- Adding attributes to the SAP Connector for AppOne
- Adding activities to the SAP Connector for AppOne
- Adding entities to the SAP Connector for AppOne
- SAP Order to Cash Connector for AppOne
- SAP Purchase to Pay Connector for AppOne
- SAP Connector for Purchase to Pay Discovery Accelerator
- SAP Connector for Order-to-Cash Discovery Accelerator
- Superadmin
- Dashboards and charts
- Tables and table items
- Application integrity
- How to ....
- Working with SQL connectors
- Introduction to SQL connectors
- Setting up a SQL connector
- CData Sync extractions
- Running a SQL connector
- Editing transformations
- Releasing a SQL Connector
- Scheduling data extraction
- Structure of transformations
- Using SQL connectors for released apps
- Generating a cache with scripts
- Setting up a local test environment
- Separate development and production environments
- Useful resources
Server architecture
When using a single server, all users connect to this server, and no additional servers are needed.
See the illustration below.
Development on the platform is done collaboratively. To facilitate this, and to keep track of changes, the Git server on the production server can be hosted, or a separate Git Server can be used.
See illustration below.
When using multiple servers, a typical scenario is to use a production and a development server. The development server is used by application developers, the production server by business users. In this case, it becomes necessary to move applications and data between servers.
See illustration below.
Applications can be released by the application developers. These releases can be downloaded as a single file from the development server and uploaded to the production server. On the production server, the release can be deployed in a single action.
For development, data is required. Data sources can be used directly in the development environment. It is also possible to export an (anonymized) version of the production data to the development server.
It is also possible to use multiple production servers, multiple development servers, and multiple Git servers, or to add test and acceptance servers.