Netcool/Impact core server config configmap

Edit online

Learn about the structure of the configmap for the Netcool®/Impact core server pod, nciserver. Edit this configmap to customize the properties, logging features, and memory settings for the primary and backup Netcool/Impact core server pods. You can also customize the Derby database that runs inside the Netcool/Impact server pod.

Contents

The following table lists the data elements that are contained in the Netcool/Impact core server config configmap (<release_name>-nciserver-config):
Table 1. Data elements in the Netcool/Impact core server config configmap (<release_name>-nciserver-config)
Data elements Description More information

impactcore-server-props-update

Properties that are listed in this data element are used to update the NCI_*_server.props file on pod restart.

To find information on the parameters that can be configured by using the NCI_server.props file, go to the Netcool/Impact documentation Welcome page and search for "NCI_server.props". Scroll down to the properties that are of interest to you.

impactcore-log4j-props-update

Properties that are listed in this data element are used to update the impactserver-log4j.properties file on pod restart.

Netcool/Impact documentation: Log4j properties files

impactcore-jvm-options-replace

Properties that are listed in this data element are used to replace the properties in the jvm.options file on pod restart.

Netcool/Impact documentation: Memory status monitoring

impactcore-derby-sql-extension

The SQL recorded in this data element is applied to the Netcool/Impact Derby database on pod restart.

Netcool/Impact documentation: Managing the database server

Examples of each of the data elements in this configmap are provided.

Data element: impactcore-server-props-update

Properties that are listed in this data element are used to update the NCI_*_server.props file on pod restart.
  impactcore-server-props-update: |
    impact.server.timeout=123456
    impact.servicemanager.storelogs=false
    # the following should just be appended
    fred=banana

Data element: impactcore-log4j-props-update

Properties that are listed in this data element are used to update the impactserver-log4j.properties file on pod restart.
  impactcore-log4j-props-update: |
    log4j.rootCategory=DEBUG
   
    log4j.appender.NETCOOL=org.apache.log4j.RollingFileAppender
    log4j.appender.NETCOOL.threshold=DEBUG
    log4j.appender.NETCOOL.layout=org.apache.log4j.PatternLayout
    log4j.appender.NETCOOL.layout.ConversionPattern=%d{DATE} %-5pC3PO [%c{1}] %m%n
    log4j.appender.NETCOOL.append=false 
    log4j.appender.NETCOOL.file=/opt/IBM/tivoli/impact/logs/impactserver.log
    log4j.appender.NETCOOL.bufferedIO=true
    log4j.appender.NETCOOL.maxBackupIndex=4
    log4j.appender.NETCOOL.maxFileSize=21MB

Data element: impactcore-jvm-options-replace

Properties that are listed in this data element are used to replace the properties in the jvm.options file on pod restart.
  impactcore-jvm-options-replace: |
    -Xms512M
    -Xmx4096M
    -Dclient.encoding.override=UTF-8
    -Dhttps.protocols=SSL_TLSv2
    #-Xgc:classUnloadingKickoffThreshold=100
    -Dcom.ibm.jsse2.overrideDefaultTLS=true

Data element: impactcore-derby-sql-extension

The SQL recorded in this data element is applied to the Netcool/Impact Derby database on pod restart.
impactcore-derby-sql-extensions: |
    CREATE SCHEMA MYSCHEMA;
    SET SCHEMA MYSCHEMA;

    CREATE TABLE MYTABLE (
      keyvalue character varying (256),
      value character varying (256)
    );
    INSERT INTO MYTABLE VALUES ('mykey1', 'myvalue1');