By default, a CMS cluster name reflects the name of the first CMS that you install, but the cluster name is prefixed by the @ symbol. For instance, if your existing CMS is called BUSINESSOBJECTSCMS
, then the default cluster name is @BUSINESSOBJECTSCMS
.
This procedure allows you to change the name of a cluster that is already installed and running. To change the cluster name, you need only stop one of the CMS cluster members. The remaining CMS cluster members are dynamically notified of the change.
For optimal performance, after changing the name of the CMS cluster reconfigure each Business Objects server so that it registers with the CMS cluster, rather than with an individual CMS.
The CMS cluster name is now changed. All other CMS cluster members are dynamically notified of the new cluster name (although it may take several minutes for your changes to propagate across cluster members).
Use the cmsdbsetup.sh
script. For reference, see the BusinessObjects Enterprise Administrator's Reference Guide.
The name of the cluster begins with the @
symbol. For example, if the cluster name was changed to ENTERPRISE
, type @ENTERPRISE
in the box.
ccm.sh
to stop each server.vi to
open the ccm.config
file found in the root directory of your BusinessObjects Enterprise installation. -n s
command in the launch string for each server, and change the name of the CMS to the name of the CMS cluster.The name of the cluster begins with the @
symbol. For example, if the cluster name was changed to ENTERPRISE
, type @ENTERPRISE
. Do not include a port number with the cluster name.
ccm.sh
to restart the servers.Business Objects http://www.businessobjects.com/ Support services http://www.businessobjects.com/services/support/ Product Documentation on the Web http://support.businessobjects.com/documentation/ |