Configuring Control Center Ready to Deploy Using a Kubernetes Cluster

To pass the IBM Control Center configuration to the container, create a Kubernetes ConfigMap with the following details:

Sample ibm-sccm-cm.yaml file

kind: ConfigMap 
apiVersion: v1 
metadata:
  name: ibm-sccm-cm
  labels:
    app.kubernetes.io/name: ibm-sccm
    app.kubernetes.io/instance: ibm-sccm
data:
# Configuration values can be set as key-value properties 
  scc_param_file: |
    appUserUID=<user id of container>
    ccInterval=<wait time of container to restart if service not running>
    engineName=<Engine name prefix>
    dbDrivers=<path of database drivers from user_inputs if pvc or wrapper image is used otherwise from /app/conf/ if init container image is used>
    productEntitilement=<CCD,CCM or CCM or CCD> 
    dbType=<Database type i.e. MSSQL, Oracle or DB2> 
    dbHost=<Database hostname>
    dbPort=<Database port number> 
    dbUser=<Database Username> 
    dbName=<Database name>
    dbLoc=<yes or no whether database localization should do or not> 
# If this flag is set to 'true', only monitored server activities will be deleted. Change this to 'true' only if you need to delete all monitored server activities.  
# Even when this flag is 'true', summary data (CC_PROCESS, CC_FILE_TRANSFER) will not be deleted. Additionally, no configuration data, such as rules, SLCs, or monitored server connection details, will be removed.
    dbInit=<true or false whether database initialization has been done or not> 
    dbPartition=<true or false whether database partition has to do or not >
# Globalization is required only if the stored data contains multi-byte characters, such as those in character sets like Kanji.
# Selecting globalization support may significantly degrade database I/O performance. It is NOT recommended for use with MSSQL.
# If the 'mssqlGlobal' variable is set to 'true', the database size may increase significantly.
    mssqlGlobal=<true or false whether MSSQL globalization has to do or not> 
    
    #Port numbers of Control centers
    httpPort=<HTTP port number for swing UI> 
    webHttpPort=<HTTP port number for web UI> 
    httpsPort=<HTTPS port number for swing UI> 
    webHttpsPort=<HTTPS port number for web UI>
    
    weblistenAddress= 
    webHost=
    autoStopJavaWebAppServer=<true or false whether java web server will be stopped automatically when control center engine will be stopped>
    eventRepositoryAuth=<true or false>
    
    #Email related details 
    emailHostname=<Email server hostname> 
    emailPort=<email server port number> 
    emailUser=<email username> 
    emailRespond=<email id to respond emails>
    ccAdminEmailAddress=<cc admin email address>
    emailTLSEnabled=<SMTP is enabled or not for email, value will be true or false>
    oracleRacOrScan=<true or false> 
    
    #JMS related details
    jmsEnable= 
    jmsType= 
    jmsHost= 
    jmsPort= 
    jmsQueueManager= 
    jmsChannel= 
    jmsSubject= 
    jmsTopic= 
    jmsEmbedBroker=
    jmsDataDirectory= 
    jmsTimeToLive= 
    jmsRetries= 
    jmsRetryWait= 
    jmsBrokerName=
    #Secure parameters
    dbSSL=<Y or N whether DB secure SSL connection requires or not>
    
    #JRE certificate details 
    keyStore=<keystore file path> 
    trustStore=<truststore file path> 
    keyAlias=<certificate key alias>
    adminEmailAddress=<admin email address>
    
    #seas parameters 
    packagePath=../package
    seasPrimaryAddress=<SEAS Primary address> 
    seasPrimaryPort=<SEAS Primary port number> 
    seasAlternativeAddress=<SEAS Alternate Email Address> 
    seasAlternativePort=
    seasSecureConnection=N 
    seasProfileName=test 
    seasPersistentConnection=N 
    seasSecureProtocol=

Note:

Globalization is only needed if data to be stored contains multi-byte characters, which are common in character sets such as Kanji.

Database I/O performance may drop multiple orders of magnitude if globalization support is selected, so it is NOT recommended you do so with MSSQL.

If the dbinit flag is set to true, only monitored server activities will be deleted. Set this flag to true only if you need to delete all monitored server activities. Even when this flag is true, no summary data (CC_PROCESS, CC_FILE_TRANSFER) or configuration data (such as Rules, SLCs, and Monitored Server connection details) will be deleted.

After preparing the configmap file, create a Kubernetes ConfigMap resource using the following command:

$ oc create -f ibm-sccm-cm.yaml -n ibm-sccm

Now, configmap can be verified with following command:

$ oc describe cm ibm-sccm-cm -n ibm-sccm