|
Home > Archive > WebSphere HTTP Server > January 2004 > Apache search index
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Apache search index
|
|
| Steve McKay 2004-01-19, 8:21 am |
| Greetings All!
We have built and implemented a search index over our Intranet website using
the Apache search index feature. The site runs on an iSeries with OS/400
V5R2.
We wish to delete and re-create the search index from a job schedule entry
on a weekly basis but there appears to be some difference between the
process that occurs when you delete and create from the ADMIN server and the
process that occurs when you use the CFGHTTPSCH CL command with the *DLTIDX
and *CRTIDX options. It appears that, if you use the web interface,
everything gets deleted and created successfully but, if you use the
CFGHTTPSCH command, the *DLTIDX option does not delete everything. I say
this because, when we use *DLTIDX and review the indices listed in the
Apache Admin drop-down box, the index that we supposedly deleted is still
listed.
Is anyone else using the search index feature of the Apache server? If so,
are you seeing any problems re-creating the search index? How are you doing
it?
TIA,
Steve
| |
| Katherine 2004-01-19, 8:21 am |
| Be sure to refresh the left frame after you use the CFGHTTPSCH command
to delete the index.
"Steve McKay" <nospammers1@yahoo.com> wrote in message news:<botmmv$553e$1@news.boulder.ibm.com>...quote:
> Greetings All!
>
> We have built and implemented a search index over our Intranet website using
> the Apache search index feature. The site runs on an iSeries with OS/400
> V5R2.
>
> We wish to delete and re-create the search index from a job schedule entry
> on a weekly basis but there appears to be some difference between the
> process that occurs when you delete and create from the ADMIN server and the
> process that occurs when you use the CFGHTTPSCH CL command with the *DLTIDX
> and *CRTIDX options. It appears that, if you use the web interface,
> everything gets deleted and created successfully but, if you use the
> CFGHTTPSCH command, the *DLTIDX option does not delete everything. I say
> this because, when we use *DLTIDX and review the indices listed in the
> Apache Admin drop-down box, the index that we supposedly deleted is still
> listed.
>
> Is anyone else using the search index feature of the Apache server? If so,
> are you seeing any problems re-creating the search index? How are you doing
> it?
>
> TIA,
>
> Steve
|
|
|
|
|