On 12/30/21 3:01 PM, Joe Fletcher wrote:
Thanks for the reply. Is it possible to find out exactly what the
“create browsing index” feature in management console actually did?
Whatever it was it worked for us and I’m having a hard time recreating
the function.
The old java console created specific VLV indexes for "itself" (not for
other clients). So you could browse the Directory Tree in the java
console without terrible performance hits. So the VLV search/indexes it
created were specific to the forms the console used. Of course clients
could use these VLV indexes, but they were only designed to be used by
the console.
HTH,
Mark
*From:*Marc Sauton <msau...@redhat.com>
*Sent:* 30 December 2021 01:51
*To:* General discussion list for the 389 Directory server project.
<389-users@lists.fedoraproject.org>
*Subject:* [389-users] Re: Default browsing index generation
**** The e-mail below is from an external source. Please do not open
attachments or click links from an unknown or suspicious origin. ****
in the web UI, it should be under "Database | Suffixes | dc=xx | VLV
Indexes"
to create a VLV index "Database | Suffixes | dc=xx | VLV Indexes |
Create VLV Index"
to re-index an existing VLV index "Database | Suffixes | dc=xx | VLV
Indexes | select an existing VLV index | Action=Reindex VLV Index"
-> popup window "Are you sure you want to reindex this VLV index?
carlicense
NO YES
->
Successfully completed VLV indexing
using the command line, for example with an instance-name called m1:
create some "dummy-non-sense-example" VLV index:
dsconf m1 backend vlv-index add-search --name=test1
--search-base=ou=people,dc=example,dc=test
--search-filter=carlicense=6ZBC246 --search-scope=2 dc=example,dc=test
dsconf m1 backend vlv-index add-index --sort roomNumber --parent-name
test1 --index-name indextest1 userroot
dsconf m1 backend vlv-index list userroot
( nothing )
dsconf m1 backend vlv-index reindex --index-name carlicense-index
--parent-name carlicense userroot
Index task index_vlv_12292021_162709 completed successfully
Successfully reindexed VLV indexes
[root@m1 ~]#
dsconf m1 backend vlv-index list userroot
dn: cn=test1,cn=userroot,cn=ldbm database,cn=plugins,cn=config
cn: test1
vlvbase: ou=people,dc=example,dc=test
vlvscope: 2
vlvfilter: (carlicense=1ABC123)
Sorts:
- dn: cn=indextest1 ,cn=test1,cn=userroot,cn=ldbm
database,cn=plugins,cn=config
- cn: indextest1
- vlvsort: roomNumber
- vlvenabled: 1
- vlvuses: 0
Error: info() missing 1 required positional argument: 'msg'
[root@m1 ~]#
On Wed, Dec 29, 2021 at 2:56 PM Joe Fletcher <jflet...@sscinc.com> wrote:
Hi,
We’re looking at 389 DS v1.4. Is there an equivalent in the linux
8 cockpit to the feature that used to exist in the v 1.3
management console such that it can create default browsing indexes?
In the old GUI it was simply a case of right-click and go which
did offer a certain level of convenience. So far I have not found
an equivalent in cockpit.
Currently most of my potential LDAP clients are unable to browse
the directory with the usual “Unwilling to perform: search is not
indexed”.
TIA
Joe
This email with all information contained herein or attached
hereto may contain confidential and/or privileged information
intended for the addressee(s) only. If you have received this
email in error, please contact the sender and immediately delete
this email in its entirety and any attachments thereto.
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to
389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
<https://urldefense.com/v3/__https:/docs.fedoraproject.org/en-US/project/code-of-conduct/__;!!JE2nyJ8!hB9UXFQTenaTdmIwvtWRAJjZNWJ2OKP6oSFewt9C6xsy9Y9ZctDs1WyGGT4zDMQ$>
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
<https://urldefense.com/v3/__https:/fedoraproject.org/wiki/Mailing_list_guidelines__;!!JE2nyJ8!hB9UXFQTenaTdmIwvtWRAJjZNWJ2OKP6oSFewt9C6xsy9Y9ZctDs1WyGxvoXYk8$>
List Archives:
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
<https://urldefense.com/v3/__https:/lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org__;!!JE2nyJ8!hB9UXFQTenaTdmIwvtWRAJjZNWJ2OKP6oSFewt9C6xsy9Y9ZctDs1WyGt9drdJQ$>
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
<https://urldefense.com/v3/__https:/pagure.io/fedora-infrastructure__;!!JE2nyJ8!hB9UXFQTenaTdmIwvtWRAJjZNWJ2OKP6oSFewt9C6xsy9Y9ZctDs1WyGukPrOW4$>
This email with all information contained herein or attached hereto
may contain confidential and/or privileged information intended for
the addressee(s) only. If you have received this email in error,
please contact the sender and immediately delete this email in its
entirety and any attachments thereto.
_______________________________________________
389-users mailing list --389-users@lists.fedoraproject.org
To unsubscribe send an email to389-users-le...@lists.fedoraproject.org
Fedora Code of
Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines
List
Archives:https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam on the list, report
it:https://pagure.io/fedora-infrastructure
--
Directory Server Development Team
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
