| ... |
... |
@@ -1,26 +1,28 @@ |
| 1 |
1 |
{{panel borderStyle="dashed" title="Project Overview"}} |
| 2 |
|
-Responsible: |
| 3 |
|
- |
| 4 |
|
-* [[Miro Spönemann>>url:http://www.informatik.uni-kiel.de/rtsys/kontakt/msp/||shape="rect"]] |
| 5 |
|
- |
| 6 |
6 |
Related Theses: |
| 7 |
7 |
|
| 8 |
8 |
* Stephan Wersig, //Ein Web Service für das automatische Layout von Graphen//, October 2011 ([[pdf>>url:http://rtsys.informatik.uni-kiel.de/%7Ebiblio/downloads/theses/swe-dt.pdf||shape="rect"]]) |
| 9 |
9 |
{{/panel}} |
| 10 |
10 |
|
| 11 |
|
- |
|
7 |
+\\ |
| 12 |
12 |
|
| 13 |
|
-The KWebS project aims at delivering the automatic layout of the KIELER project to users on a platform independent basis. The main component of the project is the //server//. It is based on an Eclipse Rich Client Application (RCA) and encapsulates the KIELER Infrastructure for Meta Layout ([[KIML>>doc:Infrastructure for Meta Layout (KIML)]]) in order to expose the layout over a network. To make the layout accessible for other platforms, the server hides the java nature of the layout behind a web service and supports a variety of //formats// for the representation of user models. The server provides access to the layout based on two architectures: |
|
9 |
+The KWebS project aims at delivering the automatic layout of the KIELER project to users on a platform independent basis. The main component of the project is the //server//. It is based on an Eclipse Rich Client Application (RCA) and encapsulates the KIELER Infrastructure for Meta Layout ([[KIML>>doc:KIELER.Home.Discontinued Projects.Infrastructure for Meta Layout (KIML).WebHome]]) in order to expose the layout over a network. To make the layout accessible for other platforms, the server hides the java nature of the layout behind a web service and supports a variety of //formats// for the representation of user models. The server provides access to the layout based on two architectures: |
| 14 |
14 |
|
| 15 |
|
-* the SOAP web service uses the reference implementation of the //Java API for XML - Web Services (JAX-WS)//, which is being maintained by the Metro project ([[jax-ws.java.net>>url:http://jax-ws.java.net/||shape="rect"]]), and provides the layout on a sessionless basis, and |
| 16 |
|
-* the jETI service gives its users more flexibility due to the session based nature of the //Java Electronic Tool Integration (jETI)// platform that is being developed and maintained at the technical university of Dortmund ([[jeti.cs.uni-dortmund.de>>url:http://jeti.cs.uni-dortmund.de/||shape="rect"]]). |
|
11 |
+* the HTTP-based service which uses simple POST requests to retrieve the layout. We provide several language bindings to connect from any language. |
|
12 |
+* the SOAP web service uses the reference implementation of the //Java API for XML - Web Services (JAX-WS)//, which is being maintained by the Metro project ([[jax-ws.java.net>>url:http://jax-ws.java.net/||shape="rect"]]), and provides the layout on a sessionless basis |
|
13 |
+** //Clients// enable using the service-based layout inside existing applications. As a good starting point, try the [[command-line layout tool>>url:http://www.informatik.uni-kiel.de/rtsys/kieler/downloads/tools-and-libraries/||shape="rect"]]. |
| 17 |
17 |
|
| 18 |
|
-Additionally, //clients// enable using the service-based layout inside the Eclipse modeling environment or other platforms. As a good starting point, try the [[command-line layout tool>>url:http://www.informatik.uni-kiel.de/rtsys/kieler/downloads/tools-and-libraries/||shape="rect"]]. |
|
15 |
+The following subpages first show how we can download and set up a layout server on our own, e.g. to provide layout inside a companies network. Further pages discuss the specific properties of either the SOAP- or HTTP-based solution. There is also a page on the supported graph formats. |
| 19 |
19 |
|
| 20 |
|
-The following subpages first take a look at the way the service-based layout is integrated into the KIELER environment and what we need in order to use it. After that it is shown how we can download and set up a layout server on our own, e.g. to provide layout inside a companies network. Then we get to know the API provided by KWebS, after which the integration of the service-based layout with KWebS into our own projects is discussed. The last section gives us a list of configuration options supported by the server of KWebS. |
|
17 |
+\\ |
| 21 |
21 |
|
| 22 |
|
-1. [[Service-based layout in KIELER>>doc:Service-Based Layout in KIELER]] |
| 23 |
|
-1. [[Setting up your own server>>doc:Setting up Your Own Server]] |
| 24 |
|
-1. [[doc:The API of KWebS]] |
| 25 |
|
-1. [[How to use the service based layout in your project>>doc:How to Use the Service-Based Layout in Your Project]] |
| 26 |
|
-1. [[Configuration options for the server>>doc:Configuration Options for the Server]] |
|
19 |
+Then we get to know the API provided by KWebS, after which the integration of the service-based layout with KWebS into our own projects is discussed. The last section gives us a list of configuration options supported by the server of KWebS. |
|
20 |
+ |
|
21 |
+1. [[Setting up your own server>>doc:KIELER.Setting up Your Own Server]] |
|
22 |
+1. [[HTTP-based>>doc:KIELER.HTTP-based Service]] |
|
23 |
+1. [[SOAP-based>>doc:KIELER.SOAP-based Service]] |
|
24 |
+1. [[doc:KIELER.Graph Formats]] |
|
25 |
+ |
|
26 |
+[[doc:KIELER.Home.Discontinued Projects.Web Services (KWebS).Downloads - KIELER Layout Web Server.WebHome]] |
|
27 |
+ |
|
28 |
+{{excerpt-include/}} |