Introduction to Application Configurator

Application Configurator is a web application to configure different application entities and generate application configuration YAML file. Application configuration YAML file is required to containerize an application. You can also generate the Log4j configuration file and the JVM configuration file for an application.

The generated configuration is used to create a Docker image of the application. Application Configurator runs as a Docker container. The script to build Application Configurator image is provided at amsgce-runtime-<version>\applicationConfigurator\build. For more information about building Application Configurator container and running it, see Building Application Configurator Docker Image. You must upload the application DAA to generate its configuration file in YAML format.

By using the Application Configurator, you can configure service bindings, resource templates, substitution variables, and so on. You can download the generated YAML file, DAA, Log4j configuration, and JVM configuration files as a .zip file.

Accessing Application Configurator

The Application Configurator provides access to all application configuration functions.

  1. Ensure that the Application Configurator container is running. For more information, see Running Application Configurator in Docker.

  2. To open the Application Configurator, access the following URL: http://hostname:port/appconfig.

    • Use the same host port you specified when running the Application Configurator container.

    • Default URL: http://<hostname>:8087/appconfig or http://<IP Address>:8087/appconfig.

    • To run the Application Configurator on Kubernetes cluster setup, access the following URL: http://hostname:31087/appconfig/. Here, 31087 is the nodePort configured in the sample Kubernetes deployment file, which you can change.

    • Login credentials are not required because the Application Configurator does not store any confidential information.

To get more information about Application Configurator like version, Java version, Operating System version, Custom Features, click About in the upper-right corner.

Miscellaneous Details

Guided Tour

To get started, you can take a guided tour of the Application Configurator UI. To start the guided tour, click Help > Start Tour in the upper-right corner.

To get more information about any of the features, click Help > Documentation in the upper-right corner. You can also view information about the fields on the UI from the right sidebar.

Light and Dark Theme

You can switch between light and dark theme by clicking the theme icon in the upper-right corner. By default, the light theme is enabled.

Session Timeout

By default, an Application Configurator session times out after 30 minutes. If the session remains idle for 25 minutes, a warning is displayed to reset the timeout. The configuration is not saved; you must download the configuration before session timeout.

To update the default session timeout value, specify the sys.sessionTimeout environment variable when running the Application Configurator container. The sessionTimeout takes milliseconds as unit.

Example:

docker run --rm -p 8087:8087 -p 9998:9998 -e sys.sessionTimeout=3600000 --name amxce_ac amxce_ac:1.0

In this example, Application Configurator session timeout of 60 minutes is set. To check the sessionTimeout is enabled, you can view the container logs by checking the following logging lines:

09 Dec 2020 20:29:32,718 a9d4ffaba4b0 [ComponentFrameworkDelegate] [INFO ] com.tibco.amx.admin.api.application - Set session timeout to 3600000 using environment variable.