Pranab Panda (pkpanda) wrote:
> Thanks But then everyone has to use the /etc/opengrok pathname
> To install Which is not always desirable.
> I got opengrok installation files under /usr/local
> And installed under /opt/opengrok/... 
>
> If it's just question of putting the configuration.xml
> File under /etc/.... , it is ok, but having the whole
> Setup of opengrok/source, opengrok/data under /etc
> Is not ideal for various reasons
>   

you just need the configuration there ( ... even a symlink is enough),
the rest can be in any directory, just the source.war needs to be
deployed to wherever your glassfish is

I think we might change the default config location to 
/var/opengrok/etc/configuration.xml

will see

--
Lubos

> Please advise
> Thanks
> Pranab
>
>
> -----Original Message-----
> From: Lubos.Kosco at Sun.COM [mailto:Lubos.Kosco at Sun.COM] 
> Sent: Wednesday, March 18, 2009 1:51 AM
> To: Pranab Panda (pkpanda)
> Cc: opengrok-discuss at opensolaris.org
> Subject: Re: [opengrok] lssues with localhost:2424
>
> Pranab Panda (pkpanda) wrote:
>   
>> Thanks, 
>> The deploy of source.war is not an issue
>> But the zip unzip of web.xml is not clear
>>   
>>     
>
> well, I hope we will get rid of this too,
> you can already avoid it, if you store your configuration.xml in
> /etc/opengrok/configuration.xml (or symlink to it)
> - in such case, just deploying the war is enough, since it will pick up
> the file from proper location (the war is hardcoded for above path)
>
> --
> L
>
>   
>> Regards
>> Pranab
>>
>> -----Original Message-----
>> From: Lubos.Kosco at Sun.COM [mailto:Lubos.Kosco at Sun.COM] 
>> Sent: Tuesday, March 17, 2009 7:26 AM
>> To: Pranab Panda (pkpanda)
>> Cc: opengrok-discuss at opensolaris.org
>> Subject: Re: [opengrok] lssues with localhost:2424
>>
>> Pranab Panda (pkpanda) wrote:
>>   
>>     
>>> Thanks
>>> I have successfully installed glassfish and am using the
>>> Default domain there is no issue with glassfish.
>>> This is what my Application server displays
>>> And I am successfully able to logon to admin interface
>>> At http://hostname:4848
>>>
>>> Name: HOSTNAME
>>>   
>>>     
>>>       
>>>> HTTP Ports : 4848,8181,8080
>>>> IIOP ports 3820, 3700,3920
>>>> JVM:       JVM Report
>>>> Configuration Directory /opt/SDK/domains/domain1/config 
>>>> Installed Version Sun GlassFish Enterprise Server v2.1(9.1.1) (build
>>>> b60e-fcs)
>>>> Debug      Not Enabled
>>>>     
>>>>       
>>>>         
>>> The main issue with opengrok documentation is twofold,
>>> It is not clear on How the configuration.xml file is created
>>>   
>>>     
>>>       
>> it's generated, I just updated the install doc to say indexer will
>> generate it ;)
>>
>>   
>>     
>>> and how to deploy The source.war (the zip/unzip part)
>>>   
>>>     
>>>       
>>     * *Option 1:* Use browser and log into |glassfish web
>>     
> administration
>   
>>       interface|: Common Tasks / Applications / Web Applications ,
>>       button *Deploy* and point it to your source.war webarchive
>>     * *Option 2:* Copy the source.war file to
>>       /GLASSFISH//domains//YOURDOMAIN//autodeploy directory, glassfish
>>       will try to deploy it "automagically".
>>     * *Option 3:* Use cli from /GLASSFISH/ directory:
>>
>>       # ./bin/asadmin deploy /path/to/source.war
>>
>>
>> which one of above is problematic ?
>>
>>
>>   
>>     
>>> I didn't saw configuration.xml in the opengrok installation
>>> And had no clue whether it is part of installation or it is created
>>> And the documentation is very unclear. I saw the configuration.xml
>>> Only When I ran
>>> java -Xmx1524m -jar opengrok.jar -W ${DATA_ROOT}/configuration.xml -P
>>>     
>>>       
>> -S
>>   
>>     
>>> -v -s ${SRC_ROOT} -d ${DATA_ROOT}
>>>  
>>> I have updated web.xml with location of configuration.xml as well.
>>>   
>>>     
>>>       
>> I admit one has to read
>>
>>     
> http://src.opensolaris.org/source/xref/opengrok/trunk/src/org/opensolari
>   
>> s/opengrok/index/CommandLineOptions.java#69
>> before passing any options to indexer + one has to know indexer (e.g.
>> from  http://src.opensolaris.org/source/xref/opengrok/trunk/run.sh )
>>
>> and I hope we can get rid of this and just have some simple to use cli
>> which just does the job in future releases of opengrok ...
>>
>>
>>   
>>     
>>> I am not sure what I am doing wrong. Please advise
>>>   
>>>     
>>>       
>> I am not sure what you're doing wrong, since I don't know what you're
>> doing.
>> You can try to write down all steps you do (maybe compare them to
>> http://opensolaris.org/os/project/opengrok/manual/installdescription/
>>     
> )
>   
>> and write them here, so we will be able to see what you actually do ;)
>>
>> xing the fingers
>> L
>>
>>   
>>     
>>> Thanks
>>> Pranab
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: Lubos.Kosco at Sun.COM [mailto:Lubos.Kosco at Sun.COM] 
>>> Sent: Tuesday, March 17, 2009 1:18 AM
>>> To: Pranab Panda (pkpanda)
>>> Cc: opengrok-discuss at opensolaris.org
>>> Subject: Re: [opengrok] lssues with localhost:2424
>>>
>>>
>>> Glassfish management skills are out of scope of opengrok docs, the
>>> assumption is that one can manage web container servers (ask local
>>>       
> Sun
>   
>>> learning center for training)
>>> but let me give you some pointers:
>>>
>>> 1) https://glassfish.dev.java.net/downloads/v2.1-b60e.html
>>> 2) cd whatever was your installation dir ;  ./bin/asadmin
>>>       
> start-domain
>   
>>> domain1  ( unless you created a different default domain than domain1
>>>     
>>>       
>> ,
>>   
>>     
>>> check in ls ./domains )
>>> 2a) your management interface is on http://YOUR_IP:4848  and default
>>> credentials are admin / adminadmin
>>> 3) create index and deploy the webapp as written in
>>> http://opensolaris.org/os/project/opengrok/manual/installdescription/
>>> 3a) http://YOUR_IP:8080/source will be opengrok, unless you changed
>>>     
>>>       
>> the
>>   
>>     
>>> path (and provided -w to indexer), also note
>>> /etc/opengrok/configuration.xml has to exist (or symlink to wherever
>>>     
>>>       
>> you
>>   
>>     
>>> pointed your configuration to be generated) for opengrok to work
>>> seamlessly (or feel free to edit web.xml in the opengrok webapp)
>>>
>>> xing the fingers
>>> L
>>>
>>> P.S.  localhost:2424  is a port opengrok uses for listening to
>>> configuration changes from indexer
>>>
>>> Pranab Panda (pkpanda) wrote:
>>>   
>>>     
>>>       
>>>> Hi Trond
>>>>
>>>> When I do 
>>>> http://hostname:8080
>>>> I get a message like
>>>> Your Glassfish server is running
>>>>
>>>> When I do
>>>> http://hostname:8080/source
>>>> I get 
>>>> HTTP Status 503 - 
>>>>
>>>>
>>>>     
>>>>       
>>>>         
> ------------------------------------------------------------------------
>   
>>   
>>     
>>>   
>>>     
>>>       
>>>> --------
>>>>
>>>> type Status report
>>>>
>>>> message
>>>>
>>>> descriptionThe requested service () is not currently available.
>>>>
>>>>
>>>>
>>>>     
>>>>       
>>>>         
> ------------------------------------------------------------------------
>   
>>   
>>     
>>>   
>>>     
>>>       
>>>> --------
>>>>
>>>> Sun GlassFish Enterprise Server v2.1
>>>>
>>>> Please advise
>>>> Thanks
>>>> Pranab
>>>> -----Original Message-----
>>>> From: opengrok-discuss-bounces at opensolaris.org
>>>> [mailto:opengrok-discuss-bounces at opensolaris.org] On Behalf Of
>>>>         
> Pranab
>   
>>>> Panda (pkpanda)
>>>> Sent: Monday, March 16, 2009 3:01 PM
>>>> To: Trond.Norbye at Sun.COM
>>>> Cc: opengrok-discuss at opensolaris.org
>>>> Subject: Re: [opengrok] lssues with localhost:2424
>>>>
>>>> Actually 
>>>> On my glassfish application server page I have the
>>>> Following
>>>>
>>>> Name: HOSTNAME
>>>> HTTP Ports : 4848,8181,8080
>>>> IIOP ports 3820, 3700,3920
>>>> JVM:       JVM Report
>>>> Configuration Directory /opt/SDK/domains/domain1/config 
>>>> Installed Version Sun GlassFish Enterprise Server v2.1(9.1.1) (build
>>>> b60e-fcs)
>>>> Debug      Not Enabled
>>>>
>>>>
>>>> I tried http://hostname/source or http://hostname:8080/source
>>>> As you suggested but it did not wrok either
>>>> Regards
>>>> Pranab
>>>>
>>>> -----Original Message-----
>>>> From: Trond.Norbye at Sun.COM [mailto:Trond.Norbye at Sun.COM] 
>>>> Sent: Monday, March 16, 2009 2:49 PM
>>>> To: Pranab Panda (pkpanda)
>>>> Cc: opengrok-discuss at opensolaris.org
>>>> Subject: Re: [opengrok] lssues with localhost:2424
>>>>
>>>> Pranab Panda (pkpanda) wrote:
>>>>   
>>>>     
>>>>       
>>>>         
>>>>> Thanks for you rprompt response trond,
>>>>> Pardon my ignorance but the opengrok documentation
>>>>> Is not very clear on step by step instructions.
>>>>> I think http://hostname:2424/ is where opengrok
>>>>> Sources will be available.
>>>>>
>>>>> What I have done so far is checked out my cvs tree under
>>>>> /opt/opengrok/source and I ran run.sh and I expect that
>>>>> All the Developers can point their browsers to the opengrok server
>>>>> By doing http://hostname:2424/source to use opengrok features.
>>>>>
>>>>>   
>>>>>     
>>>>>       
>>>>>         
>>>>>           
>>>> Have you configured your webserver to listen to port 2424??? The
>>>>     
>>>>       
>>>>         
>>> normal 
>>>   
>>>     
>>>       
>>>> port for webservers would be port 80 (or 8080).
>>>>
>>>> You should try http://hostname/source or http://hostname:8080/source
>>>>
>>>> Cheers,
>>>>
>>>> Trond
>>>>
>>>> _______________________________________________
>>>> opengrok-discuss mailing list
>>>> opengrok-discuss at opensolaris.org
>>>> http://mail.opensolaris.org/mailman/listinfo/opengrok-discuss
>>>> _______________________________________________
>>>> opengrok-discuss mailing list
>>>> opengrok-discuss at opensolaris.org
>>>> http://mail.opensolaris.org/mailman/listinfo/opengrok-discuss
>>>>   
>>>>     
>>>>       
>>>>         
>>>   
>>>     
>>>       
>>   
>>     
>
>   


Reply via email to