Hi Andrea and Gabriel,

We rely on using parameterFilters for our GWC-layers, so I guess that means 
that we cannot disable the metastore-functionality.
Does that mean that our only option is to use a single GWC-instance with 
multiple GeoServer-instances? Would not this result in a single point of 
failure?

Does anyone use multiple GWC-instances on Weblogic with a shared data 
directory? Is it perhaps possible to configure the servers so that each 
instance can use a seperate blob store directory?

Best regards,
Sebjørn Birkeland


SEBJØRN SÆTHER BIRKELAND
SENIOR CONSULTANT
+47 982 19 301

[email protected] | www.bekk.no | open.bekk.no

________________________________
Fra: [email protected] [[email protected]] på vegne av Andrea Aime 
[[email protected]]
Sendt: 15. februar 2012 12:17
To: Gabriel Roldan
Cc: Sebjørn Birkeland; [email protected]
Emne: Re: [Geoserver-users] Using GeoServer with shared data directory

On Tue, Feb 14, 2012 at 7:23 PM, Gabriel Roldan 
<[email protected]<mailto:[email protected]>> wrote:
Hi Andrea,

Thank you for your answer.

We have tried removing all the jar-files related to GWC, and this seems to 
work. For the moment, this is ok, but we are not sure how we can find good long 
term solution to this. At some point we need to be able to run GS with GWC on 
our Weblogic-servers. Is the solution to use stand-alone GWC-s, or will this 
give us the same result? Perhaps someone else has GS/GWC running on Weblogic 
and can give us some input?
Yes, use standalong gwc as front end to your clustered geoservers. A single gwc 
instance can round robin requests to various wms's. Just add multiple elements 
to the wmsLayer wmsUrl property:

<wmsUrl>
   <string>http://geoserver1/geoserver/wms</string>
   <string>http://geoserver2/geoserver/wms</string>
</wmsUrl>

This works, but mind two downsides:
* you cannot cluster it if you need the metastore and the disk quota, if you 
cluster it in order to get HA you'll have to disable them and use a fallback 
configuration for it (not round robit)
* cache seeding will be slower as GWC has to ask for PNG meta-tiles to 
GeoServer, and then decode them, slice them in tiles and save them on disk, 
with the integrated version
  the png encoding/decoding is dodged

We normally go for the former (two GWC in fallback) and if we have big pre-seed 
jobs we use a separate GeoServer+integrated GWC dedicated to build the tiles 
quickly (this also
avoids loading the machines that are supposed to serve the end user requests).

Cheers
Andrea

--
-------------------------------------------------------
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead

Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy

phone: +39 0584 962313
fax:      +39 0584 962313
mob:    +39 339 8844549

http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf

-------------------------------------------------------
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to