- Introduction
- Installation
- crossAdmin
- Setting up Across Modes
- Softkeys
- Generating crossGrid Certificates
- Creating Generic Softkeys
- Changing the Across Database User
- Defragmenting Database Files
- Running a Backup
- Auto-Deployment
- Automatic Client Update
- Windows Authentication
- Uninstalling
- Reference: Menus in crossAdmin
- Appendix
crossGrid
By means of the temporary connection and interaction of Across installations, crossGrid enables the flexible distribution of projects and tasks beyond the borders of the own organization (and the own Across installation). For this purpose, the projects and tasks are delegated from one Across Server – the Master Server – to another Across Server – the Trusted Server.
The data transfer via a crossGrid connection is always initiated by the Across Clients of the Trusted Server, which also establish the network connection to the Master Server. Accordingly, the respective Across Clients must be able to access the "third-party" Across Server. However, this does not apply to the crossGrid classic mode, for which – as with crossWAN classic – there is no direct connection between the Master Server on the one hand and the Trusted Server or the Across Clients on the other hand and the data are exchanged in the form of Grid Working Units (GWU files) or Grid Response Units (GRU files).
To use crossGrid, the option Enable crossGrid users must be activated in the crossWAN/Grid section of the Server Administration settings of the Across Server.