Chapter 1 Preparing for Installation

Before beginning the installation process, you should be familiar with the components of the Sun ONE Meta-Directory 5.1.1 suite and verify that the system meets the recommended requirements.

Supported Platforms Overview

This section lists the supported operating systems and software requirements of Meta-Directory 5.1.1 software.

Operating Systems and Platforms

Table 1-1 List of supported operating systems
Operating System	Supported
Sun Solaris^TM 9 Operating System (SPARC® Platform Edition)	Yes
Sun Solaris^TM 8 Operating System (SPARC® Platform Edition)	Yes
Sun Solaris^TM 2.6 Operating System (SPARC® Platform Edition)	No
Microsoft Windows 2000 (Advanced) Server SP3	Yes
Microsoft Windows 2000 Server SP3	Yes
Microsoft Windows 2000 Professional	No
Microsoft Windows XP	No
Solaris^TM x86 Platform Edition	No
Sun Linux^TM5.0 Operating System	No

Supported Software Pre-requisites

The following software must be installed (depending on the connectors you are using) with the Sun ONE Meta-Directory 5.1.1 software:

Supported Connector Platforms

The following table lists the supported platforms for each connector on Solaris and Windows operating systems. The supported version for every operating system is also available in this table.

Table 1-2 List platforms supported for the various connector
Connector	Solaris 8 Solaris 9	Microsoft Windows 2000 (Advanced) Server SP3 Windows 2000 Server SP3	Comments
Universal Text Parser/Universal Text	Yes	Yes
NT Domain	No	Yes
Oracle Database	Yes	Yes	Oracle Database Connector requires Oracle 8.1.5, 8.1.7, or 9.2.0 (server and client). Oracle client software must be installed on the system running the Join Engine. The server (database) software can exist on a different machine.
Microsoft Windows Active Directory	No	Yes	Active Directory Connector database platforms requires ADSI 2.5 on the system running the Active Directory Connector. It connects to a system hosting the Active Directory (usually running the Windows 2000 platform). Active Directory on Windows 2000 is recommended.
Microsoft Exchange	No	Yes
Lotus Notes	Yes	Yes	Lotus Notes 4.x and 5.0.x should work but are not supported. Changelog is placed in a database using MySQL. Lotus Notes 5.0.10 and 5.0.12 connector synchronizes users and groups between Lotus Notes and CV.
Novell eDirectory	Yes	Yes	Novell eDirectory Server 8.6.2 or 8.7 is supported. Changelog is placed in a database using MySQL.

Meta-Directory Components

Table 1-3 List of components included in Meta-Directory and their description
Component	Description
Server Core Components	Are shared files that help Meta-Directory integrate with existing Sun ONE systems. The files include: Server Products Common files Core Java Classes Java Runtime Environment 1.4.1 or higher
Sun ONE Administration Services	Consists of the Sun ONE Administration Server and Sun ONE Console. Administration Server is the common interface for all Sun ONE servers. There is at least one Administration Server instance for each server root in which a Sun ONE server is installed. You can stop and start servers, install server instances, and manage user and group information using the Sun ONE Console. Note: Sun ONE Console can also be installed as a stand-alone application.
nsPerl	Is a version of Perl with enhancements made that are required by Meta-Directory. (The standard version of Perl, available at http://www.cpan.org/, is not sufficient.)
Join Engine	Is the core service of Meta-Directory. It links information from different external data sources to an LDAP directory server. In addition, it also tracks changes to the data.
Universal Connector	Is a generic text parser. A building block for various connectors that provide bi-directional flow of data between an external data source and its Connector View. It includes a Perl script and config files that, when manually configured, flow data in three standard file formats: LDAP Data Interchange Format (LDIF), Comma-Separated Values (CSV), and Name/Value Pairs (NVP). UTC coupled with the Perl script and the config file for one of these file formats is called the Universal Text Parser (UTP).
Sun ONE Console	Provides the user interface that helps configure Meta-Directory components and manage the flow of information between the external data source, Connector Views, and Meta View.
NT Domain Connector	Provides two-way flow of user and group data specifically between a Windows database and its Connector View.
Active Directory Connector	Provides two-way flow of user and group data specifically between the Windows Active Directory and its Connector View.
Microsoft Exchange Connector	Provides two-way flow of user and group data specifically between the Microsoft Exchange Server and its Connector View. Note: NT Domain, Active Directory, and Microsoft Exchange connectors are not installed on a machine that uses the Solaris Operating System.
Database Connector	Is a direct connector that provides the Join Engine with two-way access to a Oracle relational database server.
Novell Directory Connector	Provides two-way flow of user and group data specifically between a tree in Novell Directory Server and its Connector View. Default configurations allow you to synchronize Novell Directory Server's ‘inetOrgPerson’ objectclass with Sun ONE Directory Server's ‘inetOrgPerson’ objectclass and Novell Directory Server's ‘groupOfNames’ objectclass with Sun ONE Directory Server's ‘groupOfUniqueNames’ objectclass. However, it is not limited to synchronize entries that belong to only these two object classes. In addition, you can extend the schema at either the data source end and allow synchronization of entries belonging to any object class. A list of dependent components that must be selected with the ‘Novell Directory Connector’ during its installation are: Server Core Components Administration Services nsPerl Meta-Directory Console Note: If one or more of these are not selected, the installation fails.
Lotus Notes Connector	Provides two-way flow of user and group data specifically Lotus Notes directory (domino directory) and its Connector View. Default configurations allow you to synchronize Lotus Notes directory's ‘dominoPerson’ objectclass with Sun ONE Directory Server's ‘inetOrgPerson’ objectclass and Lotus Notes directory's ‘dominoGroup’ objectclass with Sun ONE Directory Server's ‘groupOfUniqueNames’ objectclass. However, it is not limited to synchronize entries belonging to only these two object classes. In addition, you can extend the schema at either data source end and allow synchronization of entries belonging to any object class. A list of dependent components that must be selected with the ‘Lotus Notes Connector’ during its installation are: Server Core Components Administration Services nsPerl Meta-Directory Console
PerLDAP	Provides the LDAP interface in PERL.

System Requirements for Solaris Systems

Before installing Meta-Directory on a Solaris-based machine, you should verify that the machine meets the requirements described in this section.

Hardware Requirements

The disk space allocation for Meta-Directory must allow for users supported on the server, changelogs, and other generated files. A minimum of 1 GB disk space is highly recommended for any Meta-Directory installation.

The minimum RAM requirements are 512 MB for machines dedicated to running Meta-Directory processes. If you install Sun ONE Directory Server on the same machine as Meta-Directory, 1 GB of RAM is recommended.

Software Requirements

Sun ONE Meta-Directory runs Sun Solaris^TM 8 Operating System (SPARC® Platform Edition) or Sun Solaris^TM9 Operating System (SPARC® Platform Edition). Successful installation of Meta-Directory requires that a series of patches be installed. For a list of these patches and installation instructions, see "Performing the Installation".

System Requirements for Windows Systems

Before installing Meta-Directory on a machine running Windows, you should verify that it meets the recommended requirements described in this section.

Hardware Requirements

An Intel Pentium II-based computer with a 300Mhz or higher CPU and 100 MB of disk space is recommended for the basic installation of the Join Engine and connectors; however, optimal operation of these components requires much more. (The disk space allocation for Meta-Directory must allow for users supported on the server, changelogs, and other generated files.) A minimum of 1 GB disk space is highly recommended for any Meta-Directory installation.

The minimum RAM requirements is 256 MB for machines dedicated to running Meta-Directory processes. If you install Sun ONE Directory Server on the same machine as Meta-Directory, 1 GB of RAM is recommended.

Software Requirements

In addition, installation requires administrator or domain administrator privileges. Windows should also be configured to include TCP/IP transport and use DNS, LMHOSTS, or WINS to resolve host names.

Installation Privileges

It is recommended to install Meta-Directory as root (for Solaris) or Administrator (for Windows).

Required Installation Information

During installation, you will be prompted for the following configuration information:

Standard Deployment Sequence

The standard deployment sequence for Meta-Directory includes the installation of a directory server and the core Meta-Directory components (including one of each type of connector) on a single machine.

Install and configure an LDAP directory server, creating a directory information tree (DIT) structure.

For more information, see the Sun ONE Directory Server documentation.



Note	Meta-Directory must be configured to work with a Directory Server that has a changelog feature. In Directory Server 5.x this changelog uses the Retro-Changelog plug-in that is configured from the Directory Server console. This plug-in is backward compatible with the changelog implementation in Netscape/iPlanet Directory Server 4.16, both changelogs are supported. After the creating the retro-changelog, you must restart the directory server. The changelog can be queried using ldap://hostname:port:/cn=changelog

Type the following URLs to verify that the directory server is responding to LDAP:

Table 1-4 LDAP Verification URLs
Type This URL	To Display
ldap://hostname:port	Information about the LDAP server
ldap://hostname:port/your_suffix	Everything under the given suffix that has anonymous access
ldap://hostname:port/cn=schema	The directory server’s schema
ldap://hostname:port/cn=monitor	Directory server statistics

Start the administration server, accessing the directory server as Directory Manager.

Enable the changelog.

For more information, see the Directory Server documentation.

Modify the configuration parameters to optimize the directory server configuration for estimated directory tree size and load.

For more information, see the Directory Server documentation.

Populate the directory server database with user entries. (Usually, you can import a LDIF file to complete this.)

Execute setup.sh on Solaris or setup.bat on Windows from the installation directory to install Meta-Directory.

The setup script installs the necessary components. For more information, see Chapter 2, "Installing on Solaris Systems" or Chapter 3, "Installing on Windows Systems".

The Configuration Administrator creates and manages the information stored in the server configuration directory. The user name and password entered is verified during the installation process.

Before starting the Meta-Directory 5.1.1 Administration console, the online Help requires these:

If running console on a different machine or as a different user, then the xhost + command must be executed and the DISPLAY environment variable set appropriately.

The ‘netscape’ executable for the Netscape browser must be in the PATH.

While logging onto the console, you must make sure that the URL points to the hostname and port where the administration server of Meta-Directory is installed.

Start Meta-Directory 5.1.1 and create an instance of the Join Engine.

Meta view, where the Join Engine stores the entries, is created during this process. For more information, see the Sun ONE Meta-Directory Administration Guide.

Connector instances are created and configured.

Use Meta-Directory console to configure connectors, define connector tasks, and configure Connector View setup in the Join Engine. Procedures depend on the type of connector being installed. For more information, see the Sun ONE Meta-Directory Administration Guide.

Test the system.