- General Information
- Connecting Third-party Systems
- crossConnect for content systems
- crossConnect for External Editing
- Purpose and usage
- Requirements
- Implementation
- 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
- APIs
- APIs - Technology
- crossTank API v1
- crossTank API v2
- crossTerm API v1
- crossTerm API v2
- crossAPI SI
- Requirements
- Function Return Types
- crossAPI SI and Java
- List of Objects in crossAPI SI
- Sample - transferring checkout files via FileManager
- Sample - VBS
- Text Preprocessing API
Testing the crossTank API installation
As crossTank API does not need a separate installation but a special product key, you can test if everything is there after you got the licence.
- To test the installation you can do the following:
- Open a browser and browse to http://localhost/Across/CrossTank/Help.
This should display the Web API help page. - Browse to http://localhost/Across/CrossTank/api/v1/$metadata.
This should show the meta data document which describes the data model exposed as HTTP endpoints by the service. - Using a browser that is able to display JSON results directly, you can also perform a test with this simple URL, which will return first translation from your database: http://localhost/Across/CrossTank/api/v1/Translations(1).
Therefore ensure that there is a translation with ID=1 in the database.