Removing
a remote domain from the search scope |
 |
If you originally configure several remote domains without
configuring the GCS, and you want to exclude a domain from the search
scope, there are two options:
Run the setup tool (/opt/ldapux/config/setup)
to re-configure multiple domains and exclude the one you want to
remove.
Manually edit /etc/opt/ldapux/ldapux_client.conf to
remove the configuration for that specific domain and remove its
corresponding profiles (/etc/opt/ldapux/domain_profiles/ldapux_profile.ldif.<domain> and /etc/opt/ldapux/domain_profiles/ldapux_profile.bin).
Option 2 is not recommended unless you fully understand how LDAP-UX
works in the ADS multiple domain environment.
Both options require you to re-start the client daemon (/opt/ldapux/bin/ldapclientd)
for the change to take effect.
Adding
a remote domain to the search scope |
 |
If you originally configure several remote domains without
configuring the GSC, and you want to add a new remote domain into
the search scope, you have to run the setup tool to re-configure
the multiple domains and include the new domain in your configuration,
at the end of setup, choose to restart the daemon.
Re-ordering
remote domains’ search sequence |
 |
The search sequence is based on the sequence you configure
remote domains from running setup, which is also the same sequence
shown in /etc/opt/ldapux/ldapux_client.conf.
To re-order to remote domain search sequence, you either run setup
to re-configure or manually edit /etc/opt/ldapux/ldapux_client.conf to
re-arrange the order. Again, you have to restart the client daemon /opt/ldapux/bin/ldapclientd for
the change to take effect.
Adding
the GCS into the search scope |
 |
The only way that you can add the GCS into the search scope
is to run setup and add the GCS as your multiple domain support.
Again, you have to restart the client daemon for the change to take
effect.
Removing
the GCS from the search scope |
 |
The process is the same as for removing a remote domain. You
can either run setup to re-configure, or manually edit /etc/opt/ldapux/ldapux_client.conf to
remove the "gc" section, its corresponding
profiles (/etc/opt/ldapux/domain_profiles/ldapux_profile.bin.gc and ldapux_profile.ldif.gc) and
all entries to the end of the file.
Again, you have to restart the client daemon for the change
to take effect.