Release Notes for iPlanet Meta-Directory




Version 5.0, SP1 Patch 2

---

Solaris 2.6 Build 02.291.1507

Windows NT 4.0 Build 02.291.1303

These release notes contain important information available at the time of the version 5.0 SP1 Patch 2 release of iPlanet Meta-Directory. Read this document before you begin using iPlanet Meta-Directory.

These release notes contain the following sections:

• Installation Notes

• Problems Solved
  • Event Script Interface

  • Cascading Meta Views

  • Steps for setting up Cascading Meta views

  • Recommendations

  • Limitations

• For More Information

Installation Notes

---

For background information on installing the version 5.0, SP1 Patch 2 release of Meta-Directory 5.0, see the iPlanet Meta-Directory Installation Guide listed in the reference below:

http://docs.sun.com/db?p=coll/S1_ipMetaDir_50sp1

Problems Solved

---

This section lists and describes the problems reported for this version 5.0, SP1 Patch 2 release of iPlanet Meta-Directory.

Event Script Interface

In Meta-Directory 5.0 SP1 Patch 1, attribute names and values were not being passed to the Event Script Interface. This problem (#4766429) is now fixed in Meta-Directory 5.0 SP1 Patch 2

Cascading Meta Views

The idea of cascading metaview comes into use, when there is a need to synchronize data from various metadirectory installations into one single repository. The diagram below illustrates a typical setup with three Meta Directory Installations.Two subordinate or delegate Meta installations connected to one main Corporate Meta installation.

Each entry in a Meta-Directory installation is owned by a particular view. This ownership information is stored in the attribute mdsEntityOwner. Any modifications made to an entry in any of the views flows to all the views. However, only the owner view has the right to delete an entry. If an entry is deleted from any other view, it should get added back. A non-owner, however, can modify an entry. In a cascading Meta-View setup, such as the one shown above in the figure, deletion of entries even by owner views was not happening in the previous release.

This was reported in the problem (#4636032) "Entries failed to delete from cascade meta view setting". This problem has now been fixed. Now entries can be deleted from the owner views, across all the Meta-Directory installations. If an entry is deleted by a non-owner, it gets added back.

Steps for setting up Cascading Meta views

This set up consists of 2 Delegation Installations and 1 Corporate Installation. The idea is to synchronise the data from various views to Corporate Meta View. All these 3 installations have separate iPlanet Directory Server installations.

1. Install Metadirectory on the first machine (refer this installation as delegation 1 installation) and create the Join Engine instance and give the view name as Del1MV.

Table 1    Del1MV

2. Create a Connector view 1 (refer this as Del1CV1 or UTC CV1, use any UTC connector or Oracle connector) and populate data into connector view.

Table 2    Del1CV1

3. Create a Connector view 2 (refer this as Del1CV2 or UTC CV2, use any UTC connector or Oracle connector) and populate data into connector view.

Table 3    Del1CV2

4. Add Del1CV1 & Del1CV2 as JoinEngine's participating views and enable the participating views. Assume contents of Del1MV is present under suffix o=Del1MV.

Table 4    Del1 Particpating View

5. Do another Delegation installation of metadirectory on the second machine (refer this as Delegation 2 installation) and create the Join Engine instance and give the view name as Del2MV.

Table 5    Del2MV

6. Create a Connector view 3 (refer this as Del2CV1 or UTC CV3, use any UTC connector or Oracle connector) and populate data into connector view.

Table 6    Del2CV1

7. Create a Connector view 3 (refer this as Del2CV2 or UTC CV4, use any UTC connector or Oracle connector) and populate data into connector view.

Table 7    Del2CV2

8. Add Del2CV1 & Del2CV2 as JoinEngine's participating views and enable the participating views. Assume contents of Del2MV is present under suffix o=Del2MV.

Table 8    Del2 Participating View

9. Now, Do Corporate Installation of metadirectory on the third machine (refer this as Corporate installation) and create the Join Engine instance and give the view name as CorpMV.

Table 9    CorpMV

10. Create a Corporate Connector view1 (refer this as CorpCV1) and populate data into connector view. To create the Connector View, you have two options

Either (a) Create a ldap data server from Metadirectory - Data Servers, and use this URL while creating the CorpCV1

host name -- host name of the system where delegation mds installation(Del1MV) is running.

port -- port number for ids which stores contents of o=Del1MV.

Bind dn and password for that ids instance. (Assume that data server created as a result of this operation as baba.india.sun.com:389)

or (b) Create a new connector (refer this cv as CorpCV1 ) on corporate mds installation which actually points to delegation 1 installation's MV (For example, give baba.india.sun.com:389 as data server url. enter o=Del1MV as base view dn).

Table 10    CorpCV1

11. Create a Corporate Connector view1 (refer this as CorpCV2) and populate data into connector view. To create the Connector View, you have two options

Either (a) Create a ldap data server from Metadirectory - Data Servers, and use this URL while creating the CorpCV2

host name -- host name of the system where delegation mds installation(Del2MV) is running.

port -- port number for ids which stores contents of o=Del2MV.

Bind dn and password for that ids instance. (Assume that data server created as a result of this operation as baba.india.sun.com:389)

or (b) Create a new connector (refer this cv as CorpCV2 ) on corporate mds installation which actually points to delegation 2 installation's MV (For example, give baba.india.sun.com:389 as data server url. enter o=Del2MV as base view dn).

Table 11    CorpCV2

12. Add CorpCV1 & CorpCV2 as participating views of corporate mds installation and enable the participating views. Assume contents of CorpMV is present under suffix o=CorpMV

Table 12    Corporate Participating View

With this configuration, data flows properly between Del1MV, Del1CV1, Del1CV2, Del2MV, Del2CV1, Del2CV2, CorpMV, CorpCV1 and CorpCV2.

Recommendations

1. It is recommended that the view IDs of all the Connector-Views be unique across all the Meta-Directory installations.

2. The cascaded view functionality requires that the capabilities to be on in both sides; i.e. the Connector View as well as the Meta View. This is required for the add backs to happen when an entry, owned by a view outside this Meta-Directory installation, is deleted.

3. Make sure that the patch you have installed corresponds to the numbers mentioned in the title of this document. You can check this by going to the main Meta-Directory menu as illustrated in the Solaris patch below:

Table 13    Meta-Directory Main Screen

This should also be distinguished from the Patch 1 build numbers:

5.0 SP1 Patch1 Solaris 02.240.1026

5.0 SP1 Patch1 NT 02.240.1014

Limitations

1. Deletion of entries owned by delegation Meta-Views or Corporate Connector-Views results in inconsistent behaviour. However, by default, the entries are owned by the data source connector views and as such this limitation should not normally affect use.

2. All the View IDs of the Meta-Views of all the Meta-Directory installation in the cascaded setup must be unique.

For More Information

---

Useful iPlanet information can be found at the following Internet locations:

• iPlanet Meta Directory Documentation --- http://docs.sun.com/db?p=coll/s1_meta

• iPlanet Product status --- http://www.iplanet.com/support/technical_resources/

• iPlanet Professional Services information --- http://www.iplanet.com/services/professional_services_3_3.html

• iPlanet Developer information --- http://developer.iplanet.com/

• iPlanet Learning solutions --- http://www.iplanet.com/learning/index.html

• iPlanet Product data sheets --- http://www.iplanet.com/products/index.html