XSL transformation files providing examples of how the Essential Integration Server can be used to import and synchronise information from external sources.
The XSL aims to demonstrate how the library of helper functions in standardFunctions.txt can be used to transform a source XML into the integration scripts, in particular when a direct transformation to the standard Essential XML schema is not straight-forward.
To use the examples:
- Put the XSL files in the IntegrationScripts/XSL folder of the Essential Integration Server
- Put the XML files in the IntegrationScripts/XML folder of the Essential Integration Server
- Invoke the Essential Integration Server using a HTTP request. The easiest way to achieve this is to add an additional link the index.html file of Essential Integration Server following the format of the 'standard' Essential Instances import, as follows:
e.g. http://:8080/EssentialIntegrationServer/RepositoryImportService?
xslFile=importEssentialInstances.xsl&
scriptFile=essentialImport&externalRepository=XML/reportXML.xml&
externalRepositoryName=External%20Essential%20Repository&
externalRepositoryDesc=External%20Essential%20Repository%20Source
The fields are:
- xslFile: Your XSL file. You do not need the path, just the filename.
- scriptFile: the prefix of the script file that will be created to run in the Protege Script Tab
- externalRepository: the path to the XML source file, from the root of the "EssentialIntegrationServer" folder. If you've put it in the XML folder, then use: XML/{yourXMLFile}.xml
- externalRepositoryName: the name of the source that you are importing from. This is used for synchronisation and updates.
- externalRepositoryDesc: a description of the source repository.