Gert,
Thanks for your reply. Messaging in enabled at both repos.

I'm not exactly sure what you mean by this.

"The user:password in the repository configurations must give apim access
to the respective repository."


I've removed (for testing) this file > deny-apim-if-not-localhost.xml

I've added a new updater folder in
webapps/fedoragsearch/WEB-INF/classes/fgsconfigFinal/updater/<new updater>
copying the existing and renaming accordingly

in updater/FgUpdaters (existing dir)
File: updater.properties

java.naming.factory.initial
=org.apache.activemq.jndi.ActiveMQInitialContextFactory
java.naming.provide.url = tcp://localhost:61616
connectin.factory.name = ConnectionFactory
topic.fedoreAPIM = fedora.apim.update
client.id = fedoragearch0

in updater/<newupdater> (new dir)
File: updater.properties

java.naming.factory.initial
=org.apache.activemq.jndi.ActiveMQInitialContextFactory
java.naming.provide.url = tcp://<ip>:61616
connectin.factory.name = ConnectionFactory
topic.fedoreAPIM = fedora.apim.update
client.id = fedoragearch1


I've updated
webapps/fedoragsearch/WEB-INF/classes/fgsconfigFinal/fedoragsearch.proprties
file with
fedoragsearch.updateName = FgsUpdaters <newupdater>


Here is what the fgs log says everytime I try to "updateIndex
fromfoxmlFile" at fedoragsearch/rest

DEBUG 2011-11-23 13:29:00,207 (Config)
/fgsconfigFinal/repository/<repo2>/repository.properties=
{fgsrepository.fedoraVersion=3.4.2, fgsrepository.fedoraPass=<password>,
fgsrepository.fedoraSoap=http://<ip>:8080/fedora/services,
fgsrepository.fedoraObjectDir=/usr/local/fedora/data/objectStore,
fgsrepository.fedoraUser=<user>, fgsrepository.repositoryName=<reponame>,
fgsrepository.defaultGetRepositoryInfoResultXslt=copyXml}



I've also received this error three times within the same second with 3
different ports on the repo2 box, but I can't seem to replicate.
repobox2/../server/logs/fedora.log
ERROR 2011-11-22 20:54:12.956 [ActiveMQ Transport Initiator:
/<ip_of_repo1>:58267/58267/58268]
(TransportConnector) Could not accept connection :
Channel was inactive for too long: /<ip_of_repo1>:58267/58267/58268


And I've received this error on my repo1 box
repobox1/../fedoragsearch.daily.log
WARN 2011-11-23 10:14:22,522 (UpdateListener) Messaging exception
encountered stopping the messaging client:
The JMS connection has failed: Channel was inactive for too long:
/<ip_of_repo2>:61616.
This error is expected and can be ignored if the message broker was shut
down prior to the UpdateListener.

It looks like I'm on the right path, but still missing something.

Thanks,
Nelson

On Mon, Nov 21, 2011 at 5:36 AM, Gert Schmeltz Pedersen <g...@dtic.dtu.dk>wrote:

> Hi Nelson,
>
> You want a many-repositories-to-one-index installation, which is possible.
> At both repositories you need to enable the messaging service in
> fedora.fcfg. At the Fgs configuration, besides the two repository
> configurations, that you have, you need two updater names at
> fedoragsearch.updaterNames in fedoragsearch.properties, and
> correspondingly two updater.properties files under config/updater. The
> user:password in the repository configurations must give apim access to the
> respective repository. Let me hear if it works, or if not, what you find in
> fedoragsearch.log and/or in catalina.out.
>
> In the upcoming GSearch 2.4 there will be examples
> of many-repositories-to-many-indexes cases.
>
> -Gert
>
> On 18/11/2011, at 20.07, Nelson Hart wrote:
>
> Hi,
>
> I'm trying to setup Fedora Gsearch 2.3 at ip1 to work with Fedora Repo
> 3.4.2 at ip2. I have Gsearch working with a local Fedora repo. When I add
> an additional repo in
> fedoragsearch/WEB-INF/classes/fgsconfigFinal/repository/<repo2> with
> the appropriate files (see below), it doesn't seem to throw any errors, but
> it doesn't work.
>
> repo2/repository.properties
> # $Id: repository.properties $
>
> fgsrepository.repositoryName    = repo2
>
> fgsrepository.fedoraSoap                = http://<ip>:8080/fedora/services
> fgsrepository.fedoraUser                = user
> fgsrepository.fedoraPass                = password
> fgsrepository.fedoraObjectDir   = /usr/local/......
> fgsrepository.fedoraVersion             = 3.4.2
> fgsrepository.defaultGetRepositoryInfoResultXslt = copyXml
>
> I also added repo2 to the list of repos in fedoragsearch.properties file.
>
> Couple of questions:
> - What security changes need to be made on Fedora Repo at ip2?
> - Does each repo need to have its own Fgs index?
> - What other configuration does Fgs need at ip1?
>
> Thanks,
> Nelson
>
>
> --
> Nelson Hart
> iPad Developer - Islandora / TourPad Project
> Robertson Library
> University of Prince Edward Island
> nh...@upei.ca
>  <ATT00001.c><ATT00002.c>
>
>
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure
> contains a definitive record of customers, application performance,
> security threats, fraudulent activity, and more. Splunk takes this
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> _______________________________________________
> Fedora-commons-users mailing list
> Fedora-commons-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
>
>


-- 
Nelson Hart
iPad Developer - Islandora / TourPad Project
Robertson Library
University of Prince Edward Island
nh...@upei.ca
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Fedora-commons-users mailing list
Fedora-commons-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fedora-commons-users

Reply via email to