Retaining Configuration Changes

The Enterprise Console recognizes and retains many common customizations to the jetty xml files, db.cnf, and other configuration files, but is not guaranteed to retain them all. If you have made manual configuration changes to the files, verify the configuration after updating.

You can also remove the Controller from the Enterprise Console and rediscover it to preserve the configuration changes:

  1. Go to platform-admin/bin and log in.
    CODE 
    cd platform-admin/bin
    CODE 
    ./platform-admin.sh login --user-name=admin --password=password
  2. On the Controller page, click on Remove Controller, or run the following commands on the Enterprise Console host:
    Unix
    CODE 
    ./platform-admin.sh submit-job --job remove --service controller --platform-name=PLATFORM-NAME --args removeBinaries=false
    Windows
    CODE 
    ./platform-admin.exe cli submit-job --job remove --service controller --args removeBinaries=false
    High Availability
    CODE 
    ./platform-admin.sh submit-job --job remove --service controller --platform-name=PLATFORM-NAME --args removeBinaries=false entireCluster=true
    Note: If removeBinaries=false then the Enterprise Console forgets the Controller without impacting or uninstalling the Controller.
  3. Discover the Controller by using the Discover & Upgrade feature as if you were upgrading the Controller using the Enterprise Console, or run the following command on the Enterprise Console host:
    Unix
    CODE 
    ./platform-admin.sh submit-job --service controller --job discover-upgrade --platform-name <name_of_the_platform> --args destinationDirectory=<path_to_controller> controllerRootUserPassword=<controller_root_password> controllerPrimaryHost=<hostname> controllerDBPassword=<controller_db_user_password>
    Windows
    CODE 
    bin/platform-admin.exe cli submit-job --service controller --job discover-upgrade --platform-name <name_of_the_platform> --args destinationDirectory=<path_to_controller> controllerRootUserPassword=<controller_root_password> controllerPrimaryHost=<hostname> controllerDBPassword=<controller_db_user_password>
    High Availability
    CODE 
    ./platform-admin.sh submit-job --service controller --job discover-upgrade --platform-name <name_of_the_platform> --args destinationDirectory=<path_to_controller> controllerRootUserPassword=<controller_root_password> controllerPrimaryHost=<hostname> controllerSecondaryHost=<hostname> controllerDBPassword=<controller_db_user_password>
    Note: You must specify and provide the full path to the existing Controller directory.