Basic

• Profile: Demo, small, medium, or large

  You can change the Controller profile from a smaller profile to a larger one. Before doing so, ensure that the host machine meets the requirements for the profile size you want to use.

  Note: The Enterprise Console checks the disk size for the transaction log dir and db data dir for medium and large profiles only. If the transaction log is in a separate mount, then it will check for half of the minimum recommended disk size.

  This process is not reversible, and you cannot move from a larger to a smaller profile size. If you tune the Controller heap settings or database configuration settings, even to be greater than the recommended settings for the new profile, those settings will be preserved. Otherwise, the default settings are applied.

  To increase the Controller profile size, navigate to AppServer Configurations by choosing the platform, Configurations, Controller Settings, and Appserver Configurations. At the top of the page, select a new profile, then click Save. Alternatively, you can also use the CLI to increase the Controller profile size to meet increased demand:

  bin/platform-admin.sh update-controller-profile --profile <profile size>

  For more information, see Controller System Requirements.

• Tenancy Mode
• External Load Balancer URL (HA only): This is the deep link URL.
• Internal Virtual IP Address (HA only)
• Ports: Server Port: 8090; Admin Port: 4848; SSL Port: 8181; IIOP Port: 3700; JMS Port: 7676 To change the Controller ports, navigate to AppServer Configurations by choosing the platform, Configurations, Controller Settings, and Appserver Configurations. Near the top of the page, specify new ports and scroll down to click Save. This will restart the Controller. Note that the new ports should be available.
• Glassfish Admin Password

• Database User Password

  If you do not specify this password, then it will use the default. For detailed steps, see Change the Controller root User Password.

  Note: After a fresh installation or upgrade, the database user password will be hidden in jetty xml files in the Appserver directory as an alias.

  Alternatively, you can also use the CLI to change your database user password:

  For MySQL DB:

  bin/platform-admin.sh submit-job --platform-name <platform_name> --service controller --job update-passwords --args newDatabaseUserPassword=<password>

• Advanced configurations
  • NUMA Controller Configuration: This setting is preserved upon upgrades.
  • NUMA Database Configuration: This setting is preserved upon upgrades.

JVM Options

• JVM Options: You can update the JVM options via this page without having to use the modifyJvmOptions utility or any other external scripts.
• HTTP Config
• SSL Config
• SSL Context Config
• Thread Pools Config
• DB Config
• JVM Config
• GC Config

You can also update the configuration settings using the CLI by following the steps below:

1. Download all four configurations to individual files. See Deploy the Controller on AWS for more information on the config file.
2. Create and load four variables:
   • new_http_config=`cat http_config.txt`
   • new_ssl_config=`cat ssl_confg.txt`
   • new_ssl_context_config=`cat sl_context_config.txt`
   • new_thread_pools_config=`catthread_pools_config.txt`
   • new_db_config=`cat db_config.txt`
   • new_jvm_config=`cat jvm_confg.txt`
   • new_gc_config=`cat gc_configtxt`

1. Go to platform-admin/bin and log in.

   cd platform-admin/bin

   ./platform-admin.sh login --user-name=admin --password=password

2. Run the following command on the Enterprise Console host:

   ./platform-admin.sh  update-service-configurations  --service controller --job update-configs --args appserverHttpConfig="$new_http_config" appserverSslConfig="$new_ssl_config" appserverSslContextConfig="$new_ssl_context_config" appserverThreadPoolConfig="$new_thread_pools_config" webAppCommonConfig="$new_db_config" jvmStartupConfig="$new_jvm_config" gcConfig="$new_gc_config"

SSL Certificate Management

• You can view and edit the SSL Certificate here.