Server Console on the second server (server2) so that it writes its own Console instance instead of server1's.

1.Shut down the Administration Server and Directory Server.

2.Change the adm.conf file for the Administration Server to reflect server2 Directory Servers values:

ldapurl: ldap://server2.example.com:389/o=NetscapeRoot

3.Change the dse.ldif for the Directory Server to reflect server2 Directory Servers values:

serverRoot/slapd-serverID/config/dse.ldif:nsslapd-pluginarg0: ldap:///server2.example.com:389/o=NetscapeRoot

4.Turn off the Pass-through Authentication Plug-in on server2by editing its dse.ldif file and setting the nsslapd-pluginEnabledvalue to off.

serverRoot/slapd-serverID/config/dse.ldif

dn: cn=Pass Through Authentication,cn=plugins,cn=config

nsslapd-pluginEnabled: off

5.Restart the Directory Server and Administration Server.

6.1.2Migration script

Migration is performed with the migration script, /opt/dirsrv/sbin/migrate-ds-admin.pl. This script has flexible options that allow a variety of different migration scenarios. Table 6-1lists the options and arguments for this executable script.

Table 6-1 migrate-ds-admin Options and Argument

Option or argument

Alternate

Description

 

options

 

(Required) --oldsroot

-o

Specify the path to the server root directory in the legacy

 

 

Directory Server installation. The default path in 7.x servers

 

 

is /var/opt/netscape/server7, and the default path in

 

 

6.x servers is /var/opt/netscape/servers.

 

 

IMPORTANT: This is a required option.

(Optional) --actualsroot

-a

When migrating between two machines, and the current

 

 

server root directory in the old 6.x or 7.x Directory Server

 

 

installation is mounted on a networked drive, or tarballed

 

 

and moved to a relative directory, use this to specify the

 

 

original path to that directory. The oldsroot parameter sets

 

 

the directory from which the migration is run (such as

 

 

machine_new:/migrate/server7), while the

 

 

actualsroot parameter sets the server root, (/var/opt/

 

 

netscape/server7).

(Optional) --instance

-i

This parameter specifies a specific instance to migrate. This

 

 

parameter can be used multiple times to migrate several

 

 

instances simultaneously. By default, the migration script

 

 

migrates all Directory Server instances on the machine.

(Optional) --file=name

-fname

This sets the path and name of a setup file provided with the

 

 

migration script. The migration script uses the parameters

 

 

defined in the file. The only valid parameter is the

 

 

General.ConfigDirectoryAdminPwd parameter, which

 

 

is the configuration directory administrator's password.

48 Migrating or upgrading to HP-UX Directory Server from Netscape or Red Hat Directory Server

Page 48
Image 48
HP UX Direry Server manual Migration script, Migrate-ds-admin Options and Argument

UX Direry Server specifications

HP UX Directory Server is a robust and scalable solution designed for managing directory information within enterprise networks. Developed by Hewlett-Packard (HP), this server offers an extensive set of features tailored to meet the needs of organizations that require an efficient way to store, manage, and retrieve identity and access data.

One of the key features of HP UX Directory Server is its ability to handle large directories with significant volumes of data. Built on a highly optimized architecture, it provides excellent performance and can support millions of entries without sacrificing speed or reliability. This capability makes it an ideal choice for large-scale deployments in enterprises that require high availability and responsiveness.

In addition to its scalability, HP UX Directory Server supports a wide range of protocols, including LDAP (Lightweight Directory Access Protocol), which ensures seamless integration with diverse applications and systems across various platforms. The server maintains standards compliance, which facilitates interoperability and simplifies administration tasks.

Security is a top priority for HP UX Directory Server, offering an array of features to protect sensitive information. It supports secure data transmission via TLS/SSL protocols, ensuring encrypted communication between clients and servers. Advanced access controls allow administrators to define fine-grained permissions, helping to safeguard directory data against unauthorized access.

Another salient feature of HP UX Directory Server is its replication capabilities. The server can replicate directory data across multiple instances, ensuring data consistency and availability in distributed environments. This feature is essential for businesses operating across different geographical locations or requiring failover solutions for disaster recovery.

HP UX Directory Server also comes equipped with tools for data management, including an intuitive administration console for configuring and monitoring the server. Additionally, it offers customizable schema capabilities, enabling organizations to tailor the directory structure to fit their specific needs.

Integration with existing identity management solutions is streamlined through connectors and APIs, allowing organizations to extend their directory services and enhance user experience.

In summary, HP UX Directory Server is a powerful directory management solution that combines scalability, security, and integration flexibility. Its support for industry standards, advanced replication, and comprehensive administrative tools makes it an essential asset for organizations seeking to manage identity and access efficiently. By leveraging this technology, businesses can improve their operational efficiency and ensure a secure and organized approach to directory management.