Integrating the Widget into Arcopole Builder¶
The widget is also compatible with Arcopole Builder.
However, it cannot be hosted by Isogeo and called up in the application as with the Esri Portal, so it must be installed on the Arcopole server (see official documentation).
Here are the installation steps:
- Edit the
Isogeo/config.jsonfile to enter your share's parameters. For example, for our demo Widget whose generated url is https://widget-eb.isogeo.com/1.17.0/8d491301f61249139918e3710cd39eb7/wak8OBU2hQX6F6rtIe3fWiRCvzFH0/manifest.json, this gives :
"proxyApiUrl":https://widget-eb.isogeo.com/api,
"useToken":false,
"share":"8d491301f61249139918e3710cd39eb7",
"token":"wak8OBU2hQX6F6rtIe3fWiRCvzFH0",
- Place the Widget code (
Isogeodirectory) in Arcopole's Widgets directoryrepertoire_arcopole_builder\aob-exb\widgets\ - Declare the widget in the
widgets-info.jsonfile by adding a comma after the last closing brace, then the content provided by Isogeo, which should look like this JSON:
{
"name": "Isogeo",
"manifest": {
"name": "Isogeo",
"label": "Isogeo",
"type": "widget",
"version": "1.17.0",
"exbVersion": "1.19.0",
"author": "arx iT",
"description": "Main widget",
"copyright": "arx iT",
"dependency": "jimu-arcgis",
"license": "http://www.apache.org/licenses/LICENSE-2.0",
"properties": {
"hasSettingPage": false
},
"translatedLocales": [
"en",
"fr",
"fr-fr",
"es",
"pt-br",
"pt",
"pt-pt"
],
"extensions": [
{
"name": "Map store",
"point": "REDUX_STORE",
"uri": "store/mapStore"
}
],
"defaultSize": {
"width": 800,
"height": 500
}
},
"i18nLabel": {
"en": "Catalog",
"fr": "Catalogue",
"fr-fr": "Catalogue",
"es": "Catálogo",
"pt-br": "Catálogo",
"pt": "Catálogo",
"pt-pt": "Catálogo"
},
"i18nDescription": {
"en": null,
"fr": null,
"fr-fr": null,
"es": null,
"pt-br": null,
"pt": null,
"pt-pt": null
},
"uri": "widgets/Isogeo/",
"icon": "widgets/Isogeo/icon.svg",
"order": 700,
"group": 7
}
- Restart the Arcopole Builder Windows service
- Create a new application from the
Option Boxtemplate and add the customCatalogWidget
Update¶
As the code is deposited on the Arcopole server, updates cannot be automated as with the Esri Portal. The Widget's source code must therefore be replaced each time a new version is received, taking care to preserve the parameters in the Isogeo/config.json file.