Environment
Novell Cluster Services 1.8.4
Novell Identity Manager iManager Plug-ins
Business Continuity Clustering 1.2
Novell Identity Manager iManager Plug-ins
Business Continuity Clustering 1.2
Situation
In section 4.1.8 of BCC documentation, it states:
"The Identity Manager management utilities must be installed on the same server as iManager. You can install iManager and the Identity Manager utilities on a cluster node, but installing them on a non-cluster node is the recommended configuration."
In the recommended configuration, running iManager on a non-clustered node, installing the "novell-business-continuity-cluster-idm.rpm" will normally fail, as it checks for the normal Novell Cluster Services (NCS) rpm's first.
"The Identity Manager management utilities must be installed on the same server as iManager. You can install iManager and the Identity Manager utilities on a cluster node, but installing them on a non-cluster node is the recommended configuration."
In the recommended configuration, running iManager on a non-clustered node, installing the "novell-business-continuity-cluster-idm.rpm" will normally fail, as it checks for the normal Novell Cluster Services (NCS) rpm's first.
Resolution
1. With the release of BCC 1.2 code, you should be able to just run an rpm -ivh on the novell-business-continuity-cluster-idm.rpm.
2. If that fails, you can use --force --nodeps to force the rpm to install.
3. You can also use rpm2cpio. For example:
# rpm2cpio <name_of_rpm> |cpio -ivd
Then drill down to the xml files created under the ~var/opt/novell/iManager/nps/DirXML.Drivers/ directory and copy them into the corresponding directory on your iManager server.
2. If that fails, you can use --force --nodeps to force the rpm to install.
3. You can also use rpm2cpio. For example:
# rpm2cpio <name_of_rpm> |cpio -ivd
Then drill down to the xml files created under the ~var/opt/novell/iManager/nps/DirXML.Drivers/ directory and copy them into the corresponding directory on your iManager server.