SAFE X3 V2 configuration console > Documentation server 

The documentation server provides the documentation for implementing the configured solution. This documentation is supplied in a compressed format (CHM format) under windows and decompressed (HTML) for UNIX.

From the version V7 on, the product documentation is available on line. A documentation server component exists and can be configured for the product, even though it is neither configured nor managed by the Configuration console Safe X3 V2.

Configuration

To implement the Documentation server, it is necessary to:

  • load the Documentation Server component,
  • configure the Documentation Server component,
  • publish the solution on the Documentation server.

Loading

To change this component click Add in the documentation server panel.

For more information on the component loading dialog box, see the documentation on the Parameters entry component.

The Console loads the different parameters of the Documentation server component:

The status of the Documentation component is Idle. Once configured, this value changes to Active.

Configuration

Documentation formatDocumentation format

If the application is destined to be used via Web, the documentation format must be ‘decompressed’. To change this format, click "Decompress (HTML)". After the documentation has been decompressed, the value of the Decompressed documentation parameter moves to Yes.

This operation is used to extract all the documentation in HTML format from the CHM file. Once the decompressed documentation parameter changes to Yes and so the generated HTML files as well, it is no longer possible to go back to the previous compressed documentation status.

It is possible to decompress the documentation at any time using the Decompress (HTML) button. This operation will nevertheless overwrite the HTML files already present if the documentation has already been decompressed.

It is also possible to "compress" the documentation in order to create a CHM file from the existing HTML files. This operation overwrites the original CHM file and replaces it with the new CHM file generated from the existing HTML files. It is not possible to compress a Documentation that has has not been broken down. To compress a documentation, click Compress (CHM). In order for the CHM generation to take into account new documentation HTML files, these must be indexed in the current documentation. As a matter of fact, the CHM generator works in "spider" mode and finds the new documentations by following the HTML links of the current documentation. Simply add the links in the HTML document of the general index.

Note: These operations can take a while if the documentation is installed in several languages. In effect, the compression or breaking down of the documentation is applied to all the languages installed for the documentation.

Documentation format

Documentation format

If the application is destined to be used via the Web, the documentation format must be "decompressed". To change this format, click on the "Decompress (HTML)" button. After the documentation has been broken down, the value of the 'documentation decompressed' setup moves to 'yes'.

This operation is used to extract all the documentation in HTML format from the CHM file. Once the 'documentation decompressed' setup moves to yes, and thus the generated HTML files as well, it is no longer possible to go back to the previous compressed documentation status.

It is possible to decompress the documentation at any time using the "Decompress (HTML)" button. This operation will nevertheless overwrite the html files already present if the documentation has already been decompressed.

It is also possible to "compress" the documentation in order to create a CHM file from the aleady present html files. This operation overwrites the original CHM file and replaces it with the new CHM file generated from the present html files. It is not possible to compress a Documentation that has has not been broken down. To compress a documentation, click on the "Compress (CHM)" button. In order for the CHM generation to take into account new documentation html files, these must be indexed in the current documentation. As a matter of fact, the CHM generator works in "spider" mode and finds the new documentations by following the html links of the current documentation. Simply add the links in the html document of the general index.

note: These operations can take a while if the documentation is installed in several languages. In effect, the compression or breaking down of the documentation is applied to all the languages installed for the documentation.

Publish

Solution publication

To publish the solution on the documentation server, click Documentation Server and then Publish.

Click Add in the toolbar and select the solution to publish in the list of the solutions managed by the console.

Following the publication, the documentation is automatically available in the help menu of the SAFE X3 client.

Update

To update the documentation server, follow these steps:

  • Install the update (check out the installation procedures for further information) in order to replace your version with the new one.
  • Select the documentation server to be configured in the Documentation servers panel.
  • For Windows, decompress the CHM if necessary by clicking Uncompress (HTML).
  • Click Configure in order to update the configuration of the component and the existing publications.

Note: During the configuration, all the published solutions should be accessible in order to update the documentation information. If some solutions cannot be accessed or are locked, warnings will be sent upon configuration of the Documentation server component.

Unconfiguration

To unconfigure the Documentation Server component, follow the steps described below:

  • Unpublish all the solutions published on the Documentation Server in the Publication screen.
  • Click Deconfigure in the configuration screen of the Documentation server component: the component switches from the Active to the Idle status. 
  • Uninstall your component on the host server.