| ... |
... |
@@ -27,7 +27,7 @@ |
| 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: |
|
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): |
| 31 |
31 |
|
| 32 |
32 |
* SOAP over HTTP, |
| 33 |
33 |
* SOAP over HTTPS |
| ... |
... |
@@ -65,3 +65,15 @@ |
| 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}}. |
|
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 |