Re: [Koha-devel] Koha hosting - Zebra issues
I'm sorry, a step-by-step guide isn't something I have time to produce. In particular, the problem of already having Koha's installed is not one I have dealt with. We only do "dev" installs with the proper settings at outset, including zebra enabled, so we have not had to convert from nozebra to zebra for many instances in parallel. --Joe On Mon, Apr 27, 2009 at 3:34 PM, C W Nel <zang@zang.co.za> wrote:
Thanks Joe
Will you be so kind to help with a "step by step" procedure to accomplish this? Our hosted systems are running 100% on no-zebra, but at this stage we want to enable Zebra. Zebra is running and does function well on the default port and database when activated.
Thanks again for your help.
----- Original Message ----- *From:* Joe Atzberger <ohiocore@gmail.com> *To:* C W Nel <zang@zang.co.za> *Sent:* Monday, April 27, 2009 6:50 PM *Subject:* Re: [Koha-devel] Koha hosting - Zebra issues
No, the same database *name* (of "biblios" or "authorities") can be used when zebrasrv is running on a different port, with a different koha-conf.xml. The data would actually be in a distinct DB per instance.
--Joe
On Mon, Apr 27, 2009 at 12:38 PM, C W Nel <zang@zang.co.za> wrote:
Thanks Joe
Do I understand you correctly that the same zebra database is used for all the different instances?
-----Original Message----- *From:* Joe Atzberger [mailto:ohiocore@gmail.com] *Sent:* Monday, April 27, 2009 4:20 PM *To:* C W Nel *Cc:* koha-devel@lists.koha.org *Subject:* Re: [Koha-devel] Koha hosting - Zebra issues
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. -- Joe Atzberger LibLime - Open Source Library Solutions
2009/4/27 C W Nel <zang@zang.co.za>
Can anyone help with tips how to configure zebra in a hosted environment?
With other words, how to create another zebra database and what is to be changed in
the koha-conf.xml instances?
Thanks
Zang, We have run multiple instance of Zebra on a single machine this way. zebrasrv tcp:<firstip>:9999 <http://213.149.251.23:9999/> unix:/var/run/<firstkoha>/zebradb/bibliosocket -c /etc/<firstkoha>/zebradb/zebra-biblios.cfg zebrasrv tcp:<secondip>:9999 <http://213.149.251.3:9999/> unix:/var/run/<secondkoha>/zebradb/bibliosocket -c /etc/<secondkoha>/zebradb/zebra-biblios.cfg Hope this helps, Thanks, Savitra Sirohi Nucsoft OSS Labs http://www.osslabs.biz 2009/4/28 Joe Atzberger <ohiocore@gmail.com>
I'm sorry, a step-by-step guide isn't something I have time to produce. In particular, the problem of already having Koha's installed is not one I have dealt with. We only do "dev" installs with the proper settings at outset, including zebra enabled, so we have not had to convert from nozebra to zebra for many instances in parallel.
--Joe
On Mon, Apr 27, 2009 at 3:34 PM, C W Nel <zang@zang.co.za> wrote:
Thanks Joe
Will you be so kind to help with a "step by step" procedure to accomplish this? Our hosted systems are running 100% on no-zebra, but at this stage we want to enable Zebra. Zebra is running and does function well on the default port and database when activated.
Thanks again for your help.
----- Original Message ----- *From:* Joe Atzberger <ohiocore@gmail.com> *To:* C W Nel <zang@zang.co.za> *Sent:* Monday, April 27, 2009 6:50 PM *Subject:* Re: [Koha-devel] Koha hosting - Zebra issues
No, the same database *name* (of "biblios" or "authorities") can be used when zebrasrv is running on a different port, with a different koha-conf.xml. The data would actually be in a distinct DB per instance.
--Joe
On Mon, Apr 27, 2009 at 12:38 PM, C W Nel <zang@zang.co.za> wrote:
Thanks Joe
Do I understand you correctly that the same zebra database is used for all the different instances?
-----Original Message----- *From:* Joe Atzberger [mailto:ohiocore@gmail.com] *Sent:* Monday, April 27, 2009 4:20 PM *To:* C W Nel *Cc:* koha-devel@lists.koha.org *Subject:* Re: [Koha-devel] Koha hosting - Zebra issues
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. -- Joe Atzberger LibLime - Open Source Library Solutions
2009/4/27 C W Nel <zang@zang.co.za>
Can anyone help with tips how to configure zebra in a hosted environment?
With other words, how to create another zebra database and what is to be changed in
the koha-conf.xml instances?
Thanks
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
participants (2)
-
Joe Atzberger -
savitra sirohi