Skip to Content
Last modified by Alexander Schulz-Rosengarten on 2023/07/11 10:33
From version 7.1
edited by uru
on 2013/12/04 01:10
Change comment: There is no comment for this version
To version 12.1
edited by uru
on 2023/07/06 14:36
Change comment: Renamed back-links.

Summary

Details

Page properties
Parent
... ... @@ -1,0 +1,1 @@
1 +KWebS Server
Content
... ... @@ -11,6 +11,10 @@
11 11  * the latest release of the reference implementation of JAX-WS, currently version 2.2.6 ([[http:~~/~~/jax-ws.java.net/>>url:http://jax-ws.java.net/||shape="rect"]]), and
12 12  * the current version of graphviz ([[http:~~/~~/www.graphviz.org/Download.php>>url:http://www.graphviz.org/Download.php||shape="rect"]]).
13 13  
14 +{{info title="Note for Mac OS Users"}}
15 +In case you start the server under Mac OS and have Security issues, try this [[fix >>doc:KIELER Pragmatics Release 0\.11\.0]]described in the //Viewing Ptolemy Models// section.
16 +{{/info}}
17 +
14 14  The server of KWebS is implemented in java. Therefore we begin the installation with the java runtime environment. The server uses a SOAP web service based on JAX-WS and the java platform comes with support for JAX-WS already. The included version is quite old, therefore, after you installed the java runtime, you need to update the built-in version by using the endorsed-mechanism from java:
15 15  
16 16  1. create a folder named {{code language="none"}}endorsed{{/code}} in the {{code language="none"}}lib{{/code}}-directory of the java runtime, and
... ... @@ -20,7 +20,7 @@
20 20  
21 21  = Setting required configuration options =
22 22  
23 -The server supports a set of configuration options. They are listed in [[Configuration options for the server>>doc:Configuration Options for the Server]]. For most of these the //default configuration//, which is part of the server, defines a default value. The one option that depends on your installation is the path to the {{code language="none"}}dot{{/code}} executable of the Graphviz package. Therefore you need to tell the server where it can find the package. In order to do so, you use the //provider configuration//. It is located in the file {{code language="none"}}kwebs.user{{/code}} in the root folder where you extracted the server to. For example, in the following listing the executable is located at {{code language="none"}}/usr/bin/dot{{/code}}:
27 +The server supports a set of configuration options. They are listed in [[Configuration options for the server>>doc:KIELER.Home.Discontinued Projects.Web Services (KWebS).KWebS Server.Configuration Options for the Server.WebHome]]. For most of these the //default configuration//, which is part of the server, defines a default value. The one option that depends on your installation is the path to the {{code language="none"}}dot{{/code}} executable of the Graphviz package. Therefore you need to tell the server where it can find the package. In order to do so, you use the //provider configuration//. It is located in the file {{code language="none"}}kwebs.user{{/code}} in the root folder where you extracted the server to. For example, in the following listing the executable is located at {{code language="none"}}/usr/bin/dot{{/code}}:
24 24  
25 25  {{code language="bash"}}
26 26  # Use this option to configure the path to the graphviz dot executable
... ... @@ -27,12 +27,12 @@
27 27  de.cau.cs.kieler.kwebs.graphviz.path=/usr/bin/dot
28 28  {{/code}}
29 29  
30 -The next step is to decide which //service variants// you want to provide. There are three of them:
34 +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):
31 31  
32 32  * SOAP over HTTP,
33 33  * SOAP over HTTPS
34 34  
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 and jETI are available:
39 +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:
36 36  
37 37  {{code language="bash"}}
38 38  # Use this option to configure whether the JAXWS layout will be published HTTP based
... ... @@ -65,3 +65,11 @@
65 65  {{/code}}
66 66  
67 67  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}}.
72 +
73 +== Using the Start/Stop Scripts ==
74 +
75 +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.\\
76 +
77 +{{code}}
78 +-kp=mserver -kl=server/kwebs/security/keystores/mserver.jks
79 +{{/code}}
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -8651412
1 +885158
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/8651412/Setting up Your Own Server
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/885158/Setting up Your Own Server