Documentation Center

Publishing process overview

The publishing process starts with the user then is handed to Content Manager which automates the remainder of the process. The publishing flow and steps are described along with examples from associated files, and the events that can be seen in the event log.

The user interaction when publishing involves the following, shown in the diagram below in the first three (3) steps circled in white.
  • Assemble the structure by creating the map and the publication object.
  • Select the versions to use in the publication; create the baseline
  • Define the context by selecting the conditions and variables to apply.
  • Select the type of publication and click the publish button.

After the user completes the first three steps then presses the publish option, the process is automated.

Phase I of the publish process is EXPORTFORPUBLICATION and is configured in XML Background Task Settings. The entries in EXPORTFORPUBLICATION are used to validate links, conrefs, keys, and so on. If validation fails, the publication status is set to Draft until all references are resolved.

After the publication is published, you can download it to your system or upload to the repository.

When publishing to Knowledge Center, the publication is automatically added and displayed in the Knowledge Center application.

When a publishing job is created, it is put on a centralized queue in the database. The message is picked up by a Trisoft InfoShare BackgroundTask service. Depending on your configuration, this can be on the Content Manager main server or on a batch server. The number of simultaneously publish actions can be configured via XML Background Task Settings. So, you can adapt the number of simultaneously publish actions per service or add extra services. However be aware that the more jobs run simultaneously, the more resources it takes on the server (content is retrieved from the database which means more load on the database server and network, content is dumped onto the file system which means increased I/O, multiple java processes are running which means higher memory consumption) and all these jobs compete with each other for resources. So if you double the number of simultaneous processes, it does not necessarily mean that your overall publishing speed doubles.