4.1 Before You Install OES Services on an Existing Server

In addition to the information in Planning Your OES 2 Implementation in the OES 2 SP3: Planning and Implementation Guide, the following apply when you install OES on an existing server.

4.1.1 Always Use YaST to Install and Initially Configure OES Services

Linux administrators sometimes wrongly assume that OES services can be installed or uninstalled by simply installing the associated RPMs. OES services require additional configuration that is only supported as an add-on product installation in YaST.

IMPORTANT:You must always install OES as an add-on product using the YaST install. For more information, see Section 2.11, Always Install OES as an Add-On Product.

4.1.2 Don’t Install OES While Running the Xen Kernel

If you are adding supported OES 2 components to a server that is running the Xen kernel, you must reset the boot loader to boot the standard kernel before adding the OES 2 SP3 components.

  1. In YaST, select System > Boot Loader > SuSE Linux Enterprise Server 10 SP4 > Set As Default > Finish.

  2. Reboot the server.

After adding the supported OES 2 components, reset the boot loader option to Xen.

  1. In YaST, select System > Boot Loader > XEN > Set As Default > Finish.

  2. Reboot the server.

Be sure to add only those OES 2 SP3 components that are supported on a VM host server. For more information, see Step 3.

4.1.3 If You Want eDirectory to Use a Local Database on the Server

If you want the OES components to use a local eDirectory database, you should install eDirectory by itself first, then rerun the installation for the other OES components.