[OPEN-ILS-GENERAL] Installing OpenSRF

["Ing. Fabian Núñez Salcedo"]

Thanks s lot, now i understand and just got de step 8 done!

El 17/05/2011 11:13 a.m., Ben Shum escribió:
> Hi there,
>
> The opensrf_core.xml file is created based on the 
> opensrf_core.xml.example in the next step of the OpenSRF install (step 
> 9).  Creating the ejabberd users and passwords (step 8) is required to 
> define what you want those accounts to be when you configure them in 
> the next step.
>
> Those lines in step 8 are commands run as the root user.  They are not 
> lines to be added to the configuration file.
>
> -- Ben
>
> On 05/17/2011 12:03 PM, "Ing. Fabian Núñez Salcedo" wrote:
>> I just did it, but the file i found in /openils/conf/ is 
>> opensrf_core.xml.example, is this the correct file?
>>
>>
>> El 17/05/2011 10:56 a.m., Joseph Lewis escribió:
>>> Good day,
>>>
>>> Try doing:
>>> sudo updatedb
>>> then doing:
>>> locate opensrf_core.xml
>>>
>>> Mine ended up being here:
>>> /openils/conf/opensrf_core.xml
>>>
>>> I hope it helps,
>>>   Joe
>>> --
>>> Public Key: [0xF8462E1593141C16] 
>>> <http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xF8462E1593141C16>
>>>
>>> For a successful technology, reality must take precedence over 
>>> public relations, for nature cannot be fooled.
>>>   - Richard Feynman
>>>
>>>
>>>
>>> On Tue, May 17, 2011 at 9:47 AM, "Ing. Fabian Núñez Salcedo" 
>>> <coordinacionsistemas at coruniamericana.edu.co 
>>> <mailto:coordinacionsistemas at coruniamericana.edu.co>> wrote:
>>>
>>>     Hello,
>>>
>>>     I need some help. I´m trying to install OpenSRF in Ubuntu
>>>     10.04.2.  I can´t understand the step 8:
>>>
>>>     8. On each domain, you need two Jabber users to manage the
>>>     OpenSRF communications:
>>>
>>>        *
>>>           a “router” user, to whom all requests to connect to an
>>>           OpenSRF service will be routed; this Jabber user must be
>>>           named “router”
>>>        *
>>>           an “opensrf” user, which clients use to connect to OpenSRF
>>>           services; this user can be named anything you like, but we
>>>           will use “opensrf” in our examples
>>>
>>>       1.
>>>           Therefore, as the *root* user, register your “router” and
>>>           “opensrf” ejabber users for the OpenSRF router service on
>>>           each domain. The users should have different passwords on
>>>           each domain. These users will correspond to your
>>>           configuration in |opensrf_core.xml|:
>>>
>>>           # Syntax for registering a user with ejabberdctl
>>>           # ejabberdctl register<user>  <domain>  <password>
>>>           ejabberdctl register router private.localhost<password>
>>>           ejabberdctl register opensrf private.localhost<password>
>>>           ejabberdctl register router public.localhost<password>
>>>           ejabberdctl register opensrf public.localhost<password>
>>>
>>>           Note: There appears to be a problem with ejabberdctl in
>>>           that it does not escape input correctly, so a password
>>>           like |'0P3N$SRF|' will be created as |'0P3N|'. A bug
>>>           against ejabberd
>>>           <https://support.process-one.net/browse/EJAB-1399> has
>>>           been filed. To register a password using ejabberdctl with
>>>           special shell characters until such time as that bug is
>>>           resolved, the workaround is to specify a double-escaped
>>>           character at the command line, for example, |'0P3N\\\\$RF|'
>>>
>>>     I can´t find the |opensrf_core.xml file, i found
>>>     |opensrf_core.xml.example and if this is the correct file, where
>>>     do i have to put this lines:
>>>
>>>     # Syntax for registering a user with ejabberdctl
>>>     # ejabberdctl register<user>  <domain>  <password>
>>>     ejabberdctl register router private.localhost<password>
>>>     ejabberdctl register opensrf private.localhost<password>
>>>     ejabberdctl register router public.localhost<password>
>>>     ejabberdctl register opensrf public.localhost<password>
>>>
>>>
>>>     please hel me.
>>>
>>>
>>>     -- 
>>>     Coordialmente,
>>>
>>>     Ing. Fabian Núñez Salcedo
>>>     Coordinador de Sistemas de Información
>>>     Corporación Universitaria Americana
>>>     Barranquilla, Colombia
>>>     Tel:3608371 Ext  <tel:3608371%20Ext>. 121
>>>     Cel: 300 8149172
>>>
>>>
>>
>>
>> -- 
>> Coordialmente,
>>
>> Ing. Fabian Núñez Salcedo
>> Coordinador de Sistemas de Información
>> Corporación Universitaria Americana
>> Barranquilla, Colombia
>> Tel: 3608371 Ext. 121
>> Cel: 300 8149172
>
> -- 
> Benjamin Shum
> Open Source Software Coordinator
> Bibliomation, Inc.
> 32 Crest Road
> Middlebury, CT 06762
> 203-577-4070, ext. 113


-- 
Coordialmente,

Ing. Fabian Núñez Salcedo
Coordinador de Sistemas de Información
Corporación Universitaria Americana
Barranquilla, Colombia
Tel: 3608371 Ext. 121
Cel: 300 8149172

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://libmail.georgialibraries.org/pipermail/open-ils-general/attachments/20110517/cc7dd8a4/attachment-0001.htm