In January 2010, a BCC 1.2.1 patch is available through the OES 2 SP2 Linux patch channel (OES2 SP2 January 2010 Scheduled Maintenance 20100130). For information about applying the BCC 1.2.1 patch, see Section 5.0, Updating (Patching) BCC 1.2.1 on OES 2 SP2 Linux.
The major changes for BCC 1.2.1 are described in the following sections:
The minimum system requirements for BCC 1.2.1 are:
OES 2 SP2 Linux with the January 2010 maintenance patches applied.
For system requirements, see Preparing to Install OES 2 SP3
in the OES 2 SP3: Installation Guide.
Novell eDirectory 8.8.5
Novell Cluster Services 1.8.7 for OES 2 SP2 Linux with the January 2010 patches applied, including the latest Clusters plug-in
Novell iManager 2.7.3
Identity Manager 3.6.1 (32-bit or 64-bit) installed on the Identity Manager node in every peer cluster.
For information about upgrading the Identity Manager node, see Section 7.0, Upgrading the Identity Manager Nodes to Identity Manager 3.6.1.
The BCC 1.2.1 patch includes the following benefits and changes for the BCC engine:
Support for OES 2 SP2 Linux with the latest patches applied.
Support for Novell Cluster Services 1.8.7 (the version released with OES 2 SP2 Linux) with the latest patches applied, including the latest Clusters plug-in.
Support for Novell iManager 2.7.3 with the latest patches applied.
Bug fixes.
The fixes in the BCC 1.2.1 patch address the same issues as those in the January 2010 patch for BCC 1.2.0 on OES 2 SP1 Linux, but with the focus on the OES 2 SP2 Linux (with latest patches) environment. For a description of the major bugs addressed, see Section 2.3.1, BCC Engine.
In the BCC 1.2.1 patch for OES 2 SP2 Linux, the BCC resource driver template for Identity Manager is the same as the template delivered in the BCC 1.2.0 patch for OES 2 SP1 Linux. It has a different version number, but it is functionally the same. For information about the changes in the new template, see Section 2.3.2, BCC Resource Driver Template for Identity Manager.
The new BCC resource driver template is not automatically applied to existing drivers. To take advantage of the new feature and fixes in the template, you must delete the old drivers, then re-create them with the new template.
IMPORTANT:If you have previously updated the Identity Manager node in every peer cluster to use Identity Manager 3.6.1, then deleted and re-created the drivers with the template from the BCC 1.2.0 patch, it is not necessary to delete and re-create the drivers again when you apply the BCC 1.2.1 patch.