- About PTK
- Quick Start
- Guidance
- Preparing Configuration File
- Checking the System
- Deploy Database Cluster
- Manage Clusters
- Show Cluster List
- Show Cluster Status
- Start Database
- Stop Database
- Restart Database
- Rebuild Database
- Switchover
- Failover
- Show Plugin Information
- Install Plugins
- Upgrade Database
- Scale-out Cluster
- Scale-in Cluster
- Show Database HBA
- Set Database HBA
- Show Database Parameters
- Set Database Parameters
- Show Cluster Topology Configuration
- Show Cluster Meta Information
- Update Cluster Comment
- Update Database IP
- Role Management
- Install CM
- Uninstall CM
- Manage Cluster VIP
- Install MogHA Service
- Uninstall MogHA Service
- Rename Cluster
- Create Empty Cluster
- Throw Out A Node
- Takeover A Node
- Manage Cluster
- Uninstall Database Cluster
- Collect OS Information
- Download MogDB Installer
- Encrypt Sensitive Information
- Upgrade PTK
- PTKC
- Compatible With Higher Versions of MogDB
- Reference
- Samples of Configuration Files
- Commands
- ptk
- ptk completion
- ptk view-static-config
- ptk init-cluster
- ptk collect
- ptk rec-guc
- ptk cache
- ptk gen-ptkc
- ptk manage
- ptk demo
- ptk meta
- ptk version
- ptk self
- ptk gen-om-xml
- ptk env
- ptk gen-static-config
- ptk cluster
- ptk cluster createdb
- ptk cluster uninstall-compat-tools
- ptk cluster install-compat-tools
- ptk cluster install-mogila
- ptk cluster rename
- ptk cluster throwout
- ptk cluster takeover
- ptk cluster uninstall-cm
- ptk cluster install-cm
- ptk cluster gen-cert-files
- ptk cluster load-cm-vip
- ptk cluster del-kerberos-auth
- ptk cluster add-kerberos-auth
- ptk cluster uninstall-kerberos-server
- ptk cluster install-kerberos-server
- ptk cluster is-in-upgrade
- ptk cluster upgrade-rollback
- ptk cluster upgrade-commit
- ptk cluster upgrade
- ptk cluster demote
- ptk cluster promote
- ptk cluster refresh
- ptk cluster shell
- ptk cluster modify-comment
- ptk cluster show-config
- ptk cluster set-guc
- ptk cluster show-guc
- ptk cluster set-hba
- ptk cluster show-hba
- ptk cluster scale-out
- ptk cluster scale-in
- ptk cluster uninstall-mogha
- ptk cluster install-mogha
- ptk cluster list-plugins
- ptk cluster install-plugin
- ptk cluster inspect
- ptk cluster failover
- ptk cluster switchover
- ptk cluster build
- ptk cluster status
- ptk cluster restart
- ptk cluster stop
- ptk cluster start
- ptk uninstall
- ptk ls
- ptk install
- ptk exec
- ptk template
- ptk encrypt
- ptk checkos
- ptk download
- ptk candidate
- Troubleshooting
- FAQ
- Release Notes
- Community
- Appendix: YAML Syntax
Install CM
CM（Cluster Manager） is a database high-availability management software developed for MogDB. PTK supports to install CM together with the --install-cm option in the command line when installing MogDB database cluster. PTK also provides the function of installing CM to facilitate the standalone installation if CM is not installed when installing database cluster.
Search For Installer
By default, if you do not specify a CM installer, PTK searches for the CM installer in the database cluster's tools directory ($GPHOME), because normally the installer that PTK unpacks after installing the database cluster stays in this directory. If the CM installer is found, the installation will be completed automatically.
By default, the installation directory of CM will be installed to the cm directory under the global.base_dir directory in the cluster configuration file. If you have not configured the global.base_dir directory, or if you want to specify the installation directory, you need to specify it with the --cmdir parameter.
The installation command is as follows:
ptk cluster -n <CLUSTER_NAME> install-cmSpecify Local Installer
ptk cluster -n <CLUSTER_NAME> install-cm -p <installer path>Configure the Parameters of CM Agent or CM Server
If you want to change the default configuration in the configuration file of CM agent or CM server when installing CM, you can specify it via --agent-conf and -server-conf in the command line, and you need to specify it multiple times to configure multiple parameters:
ptk cluster -n <CLUSTER_NAME> install-cm --agent-conf <KEY1>=<VALUE1> --agent-conf <KEY2>=<VALUE2> --server-conf <KEY3>=<VALUE3> --server-conf <KEY4>=<VALUE4>More parameters can be found in the install-cm command documentation.