Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

To automate the import and publish process, you will need to use the Signifikant Server Publisher REST API. Here is a description of its functionality.

...

  • http://<servername>/AssertServer/api/v1/Publisher/Transform/<sitename>/<directoryname>/<languagecode>/{<sourcename>}

  • http://<servername>/AssertServer/api/v1/Publisher/Status/<sitename>/<directoryname>/Transform/{<sourcename>}

  • http://<servername>/AssertServer/api/v1/Publisher/Import/<sitename>/<directoryname>/<languagecode>/{<sourcename>}

  • http://<servername>/AssertServer/api/v1/Publisher/Status/<sitename>/<directoryname>/Import/{<sourcename>}

  • http://<servername>/AssertServer/api/v1/Publisher/PublishSitePublish/<sitename>/<publicationlabel>

  • http://<servername>/AssertServer/api/v1/Publisher/Status/<sitename>/<publicationlabel>/Publish/<publicationlabel>

Where:

  • v1 is version one of the api, later revision may define a v2 etc.

  • servername = host name or ip address of the server running AssertServer web application

  • directoryname = name of the directory that is placed in the Export directory that contains the xml import files

  • sitename = name of the site as it is registered within the editorial environment (Signifikant Server and/or Manager)

  • publicationlabel = label of the publication object that, defined in Signifikant Manager

  • languagecode: language code, e.g. en-US, language to use for the imported information.translated text

  • sourcename: when several export data folders are used, the source name identifies the one we are targeting - OPTIONAL

...

Publication label is set in the Manager. This way it is possible to predefine several publications that can be triggered using APIs.

...

Call the Signifikant Publisher REST API using a simple Web GUI

...

If you want to see which sites are registered within the editorial environmantenvironment, you can use the following method:

...

  1. The external system creates an export file and drops it in the designated Export folder with directory name "xyz"

  2. The external system calls Signifikant Publisher REST API to transform the files in directory "xyz" and save the result in the Import folder

  3. The external system calls status method to see if transformation is finished. Waits until it is finished.

  4. The external system calls Signifikant Publisher REST API to import the files from Import folder to the designated site.

  5. The external system calls status method to see if import is finished. Waits until it is finished.

  6. The external system calls Signifikant Publisher REST API to publish the designated catalogue of the site to the web environment.

  7. The external system calls status method to see if publish is finished. Waits until it is finished.

Authentication

When enabled, api services may be protected by basic authentication; login and password are passed as api call header information.

...

Filter by label (Content by label)
publish REST import automatic server
showLabelsfalse
max5
spacescom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@1ecd09
showSpacefalse
sortmodified
typeshowSpacepagefalse
reversetruelabels
typepage
cqllabel in ( "rest" , "server" , "publish" , "import" , "automatic" ) and type = "page" and space = "ASKB"
labelspublish REST import automatic server


Page Properties
hiddentrue


Related issues



...