- The Across Language Server
- Across Standard Components
- Across Access Modes
- Installation Scenarios
- Installation of the Microsoft SQL Server
- Customer Product Key and Product Activation
- Across Server
- crossTerm Server
- crossTank Server
- crossVPN Server
- crossVPN Proxy
- crossAPI SI
- crossTerm Web
- Setting up Across Modes
- Generating crossGrid Certificates
- Creating Generic Softkeys
- Changing the Across Database User
- Defragmenting Database Files
- Running a Backup
- Automatic Client Update
- Windows Authentication
- Reference: Menus in crossAdmin
- crossTank Performance Counter
- SQL Server Optimization
- Integration in Other Programs
- Web-based Components with HTTPS
- E-Mail Transmission in Across
- Integration Into the Network
- Across Support and Across Services
- Across SDK
- The Toolbox: Useful Tools for Across
Preconfigured standard connectors are available for diverse editorial, catalog, and content management systems. These connectors enable the automatic transfer of source documents to Across, the setup of projects in Across, and the subsequent automatic retransfer of finished translations from Across.
In the crossConnect module, the connectors can be started, stopped, and configured.
Integration steps that exceed the functional range of these connectors require customer-specific solutions based on crossAPI and/or crossAutomate. These are separately documented. Therefore, please contact our Across Consulting team.
When using a connector for data exchange of content either to or from Across there are two standard options to choose from: data exchange via local directories or data exchange via an FTP server.
Data exchange via local directories
The connector monitors a local input folder. As soon as a project is placed in this folder and conforms to the rules – i.e., the data are located in a subfolder and an instruction.xml file exists – the import is started in Across and a project is automatically set up. After the project has been processed according to the instructions in the instruction.xml file, the completed data are checked out of Across and placed in an output folder.
Data exchange via FTP server
The procedure is the same as for data exchange via local folders. However, instead of local folders, an FTP download folder is monitored. After the project has been processed in Across, the finished data are then copied into an FTP upload folder.
For further information, please consult your contact at Across Systems GmbH.
General information on Across services is available at www.across.net/en/services/.