If you just run the separate zebrasrv process as a different user, on a different port, then it can use the stock DB name as normal.  This also helps keep one instance from taxing the others directly during execution.<br>-- <br>
Joe Atzberger<br>LibLime - Open Source Library Solutions<br><br><div class="gmail_quote">2009/4/27 C W Nel <span dir="ltr">&lt;<a href="mailto:zang@zang.co.za">zang@zang.co.za</a>&gt;</span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">






<div bgcolor="#ffffff">
<div><font face="Arial" size="2">Can anyone help with tips how to configure zebra in 
a hosted environment?</font></div>
<div><font face="Arial" size="2">With other words, how to create another zebra 
database and what is to be changed in</font></div>
<div><font face="Arial" size="2">the koha-conf.xml instances? </font></div>
<div><font face="Arial" size="2"></font> </div>
<div><font face="Arial" size="2">Thanks</font></div></div>
</blockquote></div><br>