If you have added a new primary host to multicluster's primary cluster to replace the
existing one, you will need to configure the SMCP service profile so that it points to the new primary cluster.
Procedure
-
Log on to your IBM® Spectrum Symphony
primary host.
-
Linux® hosts only: set your environment:
- For csh or tcsh, use cshrc.platform.
For example,
run:
source /opt/ibm/spectrumcomputing/multicluster/cshrc.platform
- For sh, ksh, or bash, use
profile.platform.
For example,
run:
. /opt/ibm/spectrumcomputing/multicluster/smc/profile.platform
-
Stop the multicluster proxy service:
-
Switch to the following directory:
- Linux:
$EGO_CONFDIR/../../eservice/esc/conf/services
- Windows:
%EGO_CONFDIR%\..\..\eservice\esc\conf\services
-
Edit the smcp.xml file as follows:
-
Change the value of the environment variable SMC_KD_MASTER_LIST to specify
the new primary cluster as
first in the list.
-
If you changed the port number for your primary cluster, change the value of
SMC_KD_PORT to the new port number.
-
Set the SMCP service to automatically start when the cluster starts or restarts by changing
MANUAL to AUTOMATIC for the service.
-
Save your changes.
-
Start the multicluster proxy service:
egosh service start SMCP
Note: If a repurposing request instance is running while you are specifying a new
multicluster
primary cluster, the request
instance will receive the status ERROR.
-
Shut down and restart IBM Spectrum Symphony
primary daemons:
egosh ego shutdown
egosh ego start