Skip to main content
Skip table of contents

HTTP server service


Activate the webserver service to dynamically add servlets, servlet filters, and REST services.

Overview

The HTTP-Server is already activated by default and also used for censhare Web.

Note: Although the censhare log indicates that changes were applied during the restart of the service, you must restart the entire censhare server for the changes to take effect in the httipserver services.

You can activate the REST Interface in the censhare Admin Client under Configuration - Services - HTTP Server - Configuration. Activate the service and update the server with the configuration change. The Jetty webserver will start at port 9000. You can access it with http://<censhareserver>:9000/ws and a valid censhare user.

Activate SSL to the REST webserver

To configure the jetty.xml to a different keystore:

Always copy your new keystore to ~/cscs/app/services/httpserver. Do not use ~/css/app/config nor ~/cscs/app/config to implement a different keystore for this service. While the jetty home is predefined in the default jetty.xml, you need to adapt this entry so that it points to a different path.

Copy the jetty.xml to the custom area:

CODE
cp ~/css/app/services/httpserver/jetty.xml ~/cscs/app/services/httpserver/

Adapt the path pointing to the keystore file:

CODE
cd ~/cscs/app/services/httpserver/ vi jetty.xml

Adjust the following two entries to your needs:

CODE
# default <Set name="Keystore"><SystemProperty name="jetty.home" default="." />/app/config/keystore</Set>
<Set name="Password">password</Set>
<Set name="truststore"><SystemProperty name="jetty.home" default="." />/app/config/keystore</Set>
<Set name="trustPassword">password</Set>
# custom
<Set name="Keystore">/opt/corpus/cscs/app/services/httpserver/keystore</Set>
<Set name="Password">password</Set>
<Set name="truststore">/opt/corpus/cscs/app/services/httpserver/keystore</Set>
<Set name="trustPassword">password</Set>
    


JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.