Last modified by Robert Jan Daams on 2025/03/05 18:02
<
From version < 6.6 >
edited by Robert Jan Daams
on 2022/08/23 11:18
To version < 1.4 >
edited by Roelof Zwaan
on 2021/11/22 10:45
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,1 @@
1 -Implementation documentation.WebHome
1 +Implementatie dcoumentatie.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.RjDaams
1 +XWiki.RoelofZwaan
Content
... ... @@ -16,22 +16,6 @@
16 16  (((
17 17  (% class="col-xs-12 col-sm-8" %)
18 18  (((
19 -== Changelog ==
20 -
21 -=== Update 2022-08-23 ===
22 -
23 -As part of on-going efforts to improve performance and scalability, we have introduced a dedicated version of DataWS named DataWSExternals.  This new service should be used for external API consumers.
24 -
25 -| |**URL**|
26 -|**Old**|{{code language="none"}}https://web.terraindex.com/DataWS/{{/code}}|(((
27 -[[https:~~/~~/web.terraindex.com/DataWS/ITWDataRestService_V1_0/GetProjectsJSON>>https://web.terraindex.com/DataWS/ITWDataRestService_V1_0/GetProjectsJSON]]
28 -)))
29 -|**New**|​{{code language="none"}}https://web.terraindex.com/DataWSExternals/{{/code}}|(((
30 -[[https:~~/~~/web.terraindex.com/DataWSExternals/ITWDataRestService_V1_0/GetProjectsJSON>>https://web.terraindex.com/DataWSExternals/ITWDataRestService_V1_0/GetProjectsJSON]]
31 -)))
32 -
33 -== ==
34 -
35 35  == 1. Retreive all changed project from TerraIndex ==
36 36  
37 37  To retreive all changed project from the TerraIndex database since a specific timestamp, there is a webservice call you can do. This will return all project rows that have changes since the timestamp you send within the request.
... ... @@ -38,7 +38,7 @@
38 38  This way you only download projects that have changes, and it will not request project that are not needed, so it won’t keep our servers busy with exports that are not necessary.
39 39  
40 40  To start connecting this webservice, you should use this URL:
41 -[[https:~~/~~/web.terraindex.com/DataWSExternals/ITWDataRestService_V1_0/GetProjectsJSON>>https://web.terraindex.com/DataWSExternals/ITWDataRestService_V1_0/GetProjectsJSON]]
25 +[[https:~~/~~/web.terraindex.com/DataWS/ITWDataRestService_V1_0/GetProjectsJSON>>url:https://web.terraindex.com/DataWS/ITWDataRestService_V1_0/GetProjectsJSON]]
42 42  
43 43  Fill the **Body **of a **POST **HTTP call with:
44 44  
... ... @@ -52,7 +52,7 @@
52 52   "Language": "en"
53 53   },
54 54   "LanguageCode": "en",
55 - "WebserviceVersion": "1.0",
39 + "WebserviceVersion": 1,
56 56   "SearchFilter": "",
57 57   "ArchiveID": 0,
58 58   "PageSize": 30,
... ... @@ -254,10 +254,10 @@
254 254  == 2. Retreive the project export from TerraIndex ==
255 255  
256 256  To request the export from TerraIndex we have a SOAP webservice. This webservice is called the ExportService, and it will provide a full project in TerraIndex Format.
257 -The format of the projectfile is documentated here: [[Documentation TerraIndex Export format - dsFieldProject.xsd>>Implementation documentation.Documentation TerraIndex Export format - dsFieldProject\.xsd.WebHome]]
241 +The format of the projectfile is documentated here: [[Documentation TerraIndex Export format - dsFieldProject.xsd>>Implementatie dcoumentatie.Documentation TerraIndex Export format - dsFieldProject\.xsd.WebHome]]
258 258  
259 259  To start connecting this webservice, you should use this URL of the Import Export Webservice:
260 -[[https:~~/~~/web.terraindex.com/DataWSExternals/ITWImportExportServiceASMX_V1_0.asmx>>https://web.terraindex.com/DataWSExternals/ITWImportExportServiceASMX_V1_0.asmx]]
244 +[[https:~~/~~/web.terraindex.com/DataWS/ITWImportExportServiceASMX_V1_0.asmx>>url:https://web.terraindex.com/DataWS/ITWImportExportServiceASMX_V1_0.asmx]]
261 261  
262 262  With this URL many IDE’s can create a proxy for you, just by providing the URL. Once this proxy is created, you will have a few classes looking like the call in the image below.
263 263  
... ... @@ -272,15 +272,12 @@
272 272  Also fill the license and the applicationCode. //(These two fields can be requested at the TerraIndex Servicedesk.)//
273 273  5; Fill the **ExportType **'**Export_FIELD_XML_v1_0_0**’. This export corresponds with dsFieldProject.xsd and is the best XML to connect TI with.
274 274  Create at least create 2 parameters as in the image. Beacause 2 parameters are needed.
275 -//If JSON is prevered use: ExportType = 'Export_FIELD_JSON_v1_0_0'//
276 276  6; Fill the parameter with the FileName.
277 277  7; Fill the parameter with **projectID**. Instead of ‘ProjectID' it’s also possible to fill the parameter ‘ProjectCode'.
278 278  8; Send the request and wait for the reponse. In response field ‘ResultCode’ should be 'SUCCES’ when it all went OK. If not it will tell what went wrong.
279 279  9; The response field 'Filecontent’is filled if it went OK, and it contains XML you can serialize.
280 -10; an extra parameter is added calles: **UseZipStream**. The result data is default Base64 encoded, if you add UseZipStream = true, the result string is GZIPSTREAMED Base64 encoded. **At the end of this page, we have added an class as code, to parse the base64 or ZIPStream Base64 to a normal string.**
281 -*Username and password are known by each TI user and the application manager of your company can create new usernames.
263 +\\*Username and password are known by each TI user and the application manager of your company can create new usernames.
282 282  
283 -
284 284  **EXAMPLE CODE**
285 285  
286 286  ExportType:
... ... @@ -326,7 +326,7 @@
326 326  <soapenv:Envelope
327 327   xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
328 328   xmlns:itw="https://wsterraindex.terraindex.com/ITWorks.TerraIndex/">
329 - <soapenv:Header></soapenv:Header>
310 + <soapenv:Header/>
330 330   <soapenv:Body>
331 331   <itw:Export>
332 332   <itw:request>

Navigation

TerraIndex
asd