Changes between Version 8 and Version 9 of ServiceProviderFederation/Discovery

Timestamp:

07/13/12 15:53:08 (12 years ago)

Author:

dietuyt

Comment:

--

ServiceProviderFederation/Discovery

@@ -59 +59 @@
 == Old situation ==
 
+[[Image(http://trac.clarin.eu/attachment/wiki/ServiceProviderFederation/Discovery/disco-old.png)]]
+
 In the old situation the tomcat-clarin was running as a single instance behind apache. The path /mw/* is mounted in apache by mod_jk and all requests here are forwarded to the tomcat-clarin via the AJP13 protocol. The idp location “/discojuice/idp.html” is rewritten to “/mw/…” to provide a stable entry point for users of the service and remain flexible in the backend. This setup does not provide any redundancy and maintenance has to be performed in the running production service.
 
 == New situation ==
 
-To overcome the effects of maintenance on the running production service we propose the following setup (with options for more enhancements in the future), as shown in Figure 2: new setup.
+
+[[Image(http://trac.clarin.eu/attachment/wiki/ServiceProviderFederation/Discovery/disco-new.png)]]
+
+To overcome the effects of maintenance on the running production service we propose the following setup (with options for more enhancements in the future).
 
 In this setup two tomcat instances (tomcat-clarin1 and tomcat-clarin2) are mounted in apache with mod_jk as /mw1/* and /mw2/*.  With the apache rewrite rule we can choose which of the two instance is active and this allows us to perform maintenance and testing on the other instance without disruption of the live instance. When maintenance is completed the rewrite rule is changed to point to the updated instance which then becomes live and we can easily update the other instance.