Skip to Content
Last modified by Alexander Schulz-Rosengarten on 2023/07/11 10:33
From version 4.1
edited by msp
on 2012/04/23 14:09
Change comment: There is no comment for this version
To version 9.1
edited by uru
on 2013/12/18 01:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.msp
1 +XWiki.uru
Content
... ... @@ -1,5 +3,3 @@
1 -Using the public server that is provided by the KIELER project may introduce a significant latency to the layout process, depending on the size and structure of the models you are using and the type of internet connection you have. Another aspect is confidentiality. You may not want to send your models to a public server, even if the connection is being secured by HTTPS. For these reasons you may want to set up your own server that is providing layout in your internal network. In the following we will take a look at what it takes to set up the server in your environment and how you can configure it to your needs.
2 -
3 3  = Download and Installation =
4 4  
5 5  If you want to use service-based layout inside your network, you can download the latest build of the server that fits to your platform from
... ... @@ -29,13 +29,12 @@
29 29  de.cau.cs.kieler.kwebs.graphviz.path=/usr/bin/dot
30 30  {{/code}}
31 31  
32 -The next step is to decide which //service variants// you want to provide. There are three of them:
30 +The next step is to decide which //service variants// you want to provide. There are two of them (plus the HTTP Post which is available via the support server):
33 33  
34 34  * SOAP over HTTP,
35 -* SOAP over HTTPS, and
36 -* jETI.
33 +* SOAP over HTTPS
37 37  
38 -As the following listing shows, you can define the variants to be published by the server in the provider configuration. In the given example, SOAP over HTTP and jETI are available:
35 +As the following listing shows, you can define the variants to be published by the server in the provider configuration. In the given example, SOAP over HTTP is available:
39 39  
40 40  {{code language="bash"}}
41 41  # Use this option to configure whether the JAXWS layout will be published HTTP based
... ... @@ -44,11 +44,9 @@
44 44  # Use this option to configure whether the JAXWS layout will be published HTTPS based
45 45  de.cau.cs.kieler.kwebs.jaxws.publishHttps=false
46 46  
47 -# Use this option to configure whether the layout will be published jETI based
48 -de.cau.cs.kieler.kwebs.publishJeti=true
49 49  {{/code}}
50 50  
51 -The next step is to define how the variants are being published. All variants per default only accept requests from {{code language="none"}}localhost{{/code}}. In order to make them publicly available you need to configure from which IPs the variants are accepting requests from. You can also define the port a variant is listening on and the HTTP context it is bound to. In the following example they are accepting requests from {{code language="none"}}0.0.0.0{{/code}}, meaning that they accept incoming requests from any client. The SOAP over HTTP variant is bound to port {{code language="none"}}8442{{/code}} and the context {{code language="none"}}layout{{/code}}. You cannot define a context for the jETI variant due to the proprietary nature of the transport protocol jETI uses.
46 +The next step is to define how the variants are being published. All variants per default only accept requests from {{code language="none"}}localhost{{/code}}. In order to make them publicly available you need to configure from which IPs the variants are accepting requests from. You can also define the port a variant is listening on and the HTTP context it is bound to. In the following example they are accepting requests from {{code language="none"}}0.0.0.0{{/code}}, meaning that they accept incoming requests from any client. The SOAP over HTTP variant is bound to port {{code language="none"}}8442{{/code}} and the context {{code language="none"}}layout{{/code}}.
52 52  
53 53  {{code language="bash"}}
54 54  # Use this option to configure the address, port and context under
... ... @@ -55,13 +55,6 @@
55 55  # which the SOAP variant will be published over HTTP
56 56  de.cau.cs.kieler.kwebs.jaxws.httpAddress=http://0.0.0.0:8442/layout
57 57  
58 -# Use this option to configure the address under which the jETI
59 -# variant will be published
60 -de.cau.cs.kieler.kwebs.jeti.server.hostname=0.0.0.0
61 -
62 -# Use this option to configure the port under which the jETI
63 -# variant will be published
64 -de.cau.cs.kieler.kwebs.jeti.connector.sepp.port=9867
65 65  {{/code}}
66 66  
67 67  If you decide to publish the SOAP over HTTPS variant you need a server certificate in order to secure the connection. While a certificate that has been officially signed by a Certificate Authority (CA) is preferable, the server provides a java key store containing a self signed certificate. It is located in the folder {{code language="none"}}server/kwebs/security/keystores{{/code}} beneath the root directory of your server installation, the name of the key store is {{code language="none"}}server.jks{{/code}}. Furthermore, due to the nature of the SSL-implementation of the java platform, the server provides the corresponding client trust store that clients can use to add the server certificate to the list of certificates the java runtime implicitly trusts ({{code language="none"}}client.jks{{/code}}). The server also contains a script ({{code language="none"}}GenerateCertsAndKeystores.sh{{/code}}) that allows you to generate these by yourself. You can find it in the folder {{code language="none"}}server/cmd{{/code}} beneath the root directory of your server installation. The script requires the presence of OpenSSL ([[http:~~/~~/www.openssl.org/>>url:http://www.openssl.org/||shape="rect"]]). While it is generally already installed on Linux platforms, for a Windows based server you need to download and install the OpenSSL toolkit ([[http:~~/~~/www.openssl.org/related/binaries.html>>url:http://www.openssl.org/related/binaries.html||shape="rect"]]).
... ... @@ -77,3 +77,15 @@
77 77  {{/code}}
78 78  
79 79  In the given example the key store is located at {{code language="none"}}security/my.jks{{/code}} relative to the servers root directory and the password is {{code language="none"}}MyPassword{{/code}}.
68 +
69 +== Using the Start/Stop Scripts ==
70 +
71 +After an initial start of the {{code language="none"}}kwebs{{/code}} binary, kwebs_start.* and kwebs_stop.* scripts will be unpacked to the root directory. They can be used to properly start and stop the server via a management application. The application can only be contacted via local host. For the stop script to work properly the correct password and keystore have to be passed. The default values are shown next.\\
72 +
73 +{{code}}
74 +-kp=mserver -kl=server/kwebs/security/keystores/mserver.jks
75 +{{/code}}
76 +
77 +\\
78 +
79 +-kp=mserver -kl=server/kwebs/security/keystores/mserver.jks
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -8650871
1 +8651463
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/8650871/Setting up Your Own Server
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/8651463/Setting up Your Own Server