Powered by Zoomin Software. For more details please contactZoomin

Semaphore Publisher

Publishing models hosted in Semaphore Cloud

  • Last Updated: May 13, 2026
  • 2 minute read
    • Semaphore
    • Documentation

If you have a model hosted in the Semaphore Cloud but want to publish it from a Publisher installation on-premise (for instance, you want it to update an internal Semantic Enhancement Server or Classification Server instance) then follow these instructions. Please keep in mind that resources that are defined on-premise such as the the Classification Server or Semantic Enhancement Server location may be different for the in-cloud and on-premise Publisher installations. It is therefore worth designing the publisher configurations with this in mind.

Tip: Because of the way the configuration is done, it is possible to “include” files into the main configuration file. By including separate files with the same name but different contents in the in-cloud versus on-premises installations, you can minimize the effort needed to keep the configurations between the two in-synch.

To publish a Semaphore Cloud-hosted model to an on-premise installation of Semaphore:

  1. Install the “Publisher” product on the on-premise server if not already installed.
  2. In the “<Publisher installation directory>/resources/import” move away the file “ModelDefinition.xml” (rename it for backup purposes) then rename the “CloudModelDefinition.xml” file to “ModelDefinition.xml”.
  3. Within the “ModelDefinition.xml” file, update the session token key value to be that available from your Semaphore Cloud Administration page (see here for details on how to obtain this value).
  4. Create a copy of “<Publisher installation directory>/bin/RunPublisherCloud.bat” (Windows) or “<Publisher>/bin/RunPublisherCloud.sh” (Linux) and name it “RunPublisherCloud<<Model Name>>.bat (Windows) or .sh (Linux)”. Then edit the newly created file so that it has the following information set correctly:
    • <<SPARQL Endpoint>> - As obtained from the Knowledge Model Management instance. Make sure that you set the expiration date on this to be sufficiently far into the future so that it will continue working.
    • <<Model Name>> - The name of the model
    • Publication configuration file location - If required, make sure the path is set correctly in the “config-file” parameter.
      These changes only need to be done when the product is first installed or when it is upgraded.
  5. Copy the configuration files from the Cloud installation to the on-premise “<Publisher SES>/config” directory so that your main configuration file is in the directory “<Publisher SES installation directory>/config/<<Model Name>>/”
  6. Copy the “kid” files that are referenced in the config file to “<Publisher SES>/config/<<Model Name>>/templates - Publish your model by running the command ”bin/RunPublisherCloud.bat” (Windows) or “bin/RunPublisherCloud.sh” (Linux) from the command line. Note that because the server cannot see your on-premise server, there is no way to start the Publisher from within a Knowledge Model Management service based in Semaphore Cloud.

The publisher needs to be able to read the SEMAPHORE_LICENCE_DIR environment variable. This needs to be set to the location of the Semaphore licence directory. It will have been set on installation of Semaphore products, but may not have been made visible to the user running Publisher from the command line.

TitleResults for “How to create a CRG?”Also Available inAlert