2012/6/15 Sharad Singla <ssin...@sandvine.com>

>  Thanks Pietro.
>
>
>
> We generally use dynamic views for our day-to-day development but we have
> the option of using the snapshot views as well for OpenGrok. Space
> shouldn’t be an issue.
>
>
>
> I think you missed sending me the script … can you please resend it.
>
>
>
> Regards
>
> Sharad
>
>
>
Hi Sharad,

I re-attached update_idx.ksh script.

Here is brief howto (most likely it's over complex and to use bin/OpenGrok
script would much simpler ;-)   :
0) Setup clearcase snapshot view and point to it env variable $SRC_ROOT
1) Create directory for storing OpenGrok's indexes: export
DATA_ROOT=/local/idx ; mkdir -p $DATA_ROOT
2) I attached small script with env. variables used by update_idx.ksh. You
will need to update it to match your case.
    After you will customize it source it with ". ./prod.grok"
3) Customize script update_idx.ksh to have correct paths to your
installation of OpenGrok and ports, which you desire.
4) Run indexer: "./update_idx.ksh" .
    At the end it will complain that it can't upload configuration to web
application. You can ignore this error for now.
    It should generate configuration file $WRITE_CONF
5) Unzip source.war from OpenGrok installation dir and modify web.xml:
      - To point to newly generated configuration file ($WRITE_CONF):
<context-param>
      <param-name>CONFIGURATION</param-name>
      <param-value>/srv/opengrok/config/prod.conf</param-value>
      <description>Full path to the configuration file where OpenGrok can
read it's configuration</description>
</context-param>

     - And port where OpenGrok will wait for new config:
<context-param>
      <param-name>ConfigAddress</param-name>
      <param-value>localhost:10500</param-value>
      <description>An address where OpenGrok can receive new
configuration</description>
</context-param>

6) Zip back web.xml to source.war (zip -u source.war WEB-INF/web.xml)
7) Deploy source.war in your application server.

-- 
Cheers,
Petr Sobotka aka Pietro

Attachment: update_idx.ksh
Description: Binary data

Attachment: prod.grok
Description: Binary data

_______________________________________________
opengrok-discuss mailing list
opengrok-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/opengrok-discuss

Reply via email to