- General Information
- Connecting Third-party Systems
- crossConnect for content systems
- crossConnect for External Editing
- Purpose and usage
- Across XLIFF format
- Across-specific Extensions
- <xliff> Element Attributes
- <file> Element Extensions
- <trans-unit> Element Extension
- Paragraph States
- Paragraph State Flags
- <source> and <target> Element Content
- <bpt> Element Attributes
- <ph> Element Attributes
- <x> Element Attributes
- Across-specific Properties
- Analysis Results
- Sample Files
- Across XLIFF - import, export and segmentation
- Context information
- Exporting best matches in Across XLIFF
- Hyperlinks to XLIFF
- Secure file handling with C#
- Secure file handling with JAVA
- Workflow and vendor configuration
- Sample code - Integrated solution
- Across XLIFF format
- Generic File Connector
- Display Texts
- Solution approaches
- The Across solution in detail
- The display text format
- The display text package
- APIs - Technology
- crossTank API v1
- crossTank API v2
- crossTerm API v1
- crossTerm API v2
- crossAPI SI
- Function Return Types
- crossAPI SI and Java
- List of Objects in crossAPI SI
- ObjectManager - Overview
- ProjectManager - Overview
- WanGridManager - Overview
- Sample - transferring checkout files via FileManager
- Sample - VBS
- Text Preprocessing API
crossAPI SI was developed to facilitate system integration. This means that crossAPI SI is ideal for the use with comprehensive server systems in order to integrate Across smoothly in the customer's workflows.
For this purpose, crossAPI SI offers various objects that allow most administrative tasks such as check-in, check-out, project creation, etc. to be carried out. crossAPI SI has been conceived in such a way that the actual translation is still done in crossDesk. For this reason, crossAPI SI does only offer limited possibility to access crossTerm and crossTank.
Typical cases for utilizing crossAPI SI are so-called "crossConnect" solutions for integrating with content systems or the alignment with 3rd party workflow management systems.
- crossAPI SI can be used in various ways:
- COM, DCOM
- SOAP Web Service, running on local IIS
Introduction of WCF web service for crossAPI SI
The Windows Communication Foundation (WCF) service was implemented into Across Language Server and released with v7.0 15444.
The WCF service is stricter for method parameters. The previously used SOAP web service did not check the data types of crossAPI SI function parameters strictly. Now the service will throw an exception in case the provided data type does not match the expected data type.
Across Setup Configuration tool installs an additional MSI package (IIS Rewrite module) to redirect the old URL (http://server/crossAPI/crossAPI.wsdl) to the new one (http://server/crossapi/crossapi.svc?wsdl) for backward compatibility.
The parameters and types of the functions in the WSDL were not changed. Nevertheless, it should be avoided using null parameters instead of empty strings.
The WSDL metadate example is attached to this document.
The previously used SOAP web service was based on the MS SOAP Toolkit. Their components require the installation of MSXML4 (deprecated by Microsoft) which represented a critical security gap.
Windows Communication Foundation (WCF) is a framework for building service-oriented applications. Using WCF, you can send data as asynchronous messages from one service endpoint to another. A service endpoint can be part of a continuously available service hosted by IIS, or it can be a service hosted in an application. An endpoint can be a client of a service that requests data from a service endpoint.