Validating Application Configuration

The application configuration artifacts (YAML file, JVM arguments, Log4j configuration) generated directly by Application Configurator, DAA2Config, or Application Extractor are error free. You can use a text editor to further update these artifacts. This manual step may introduce inconsistencies in the configurations. In such a case, you can use checkConfig command to validate the configuration. You must fix errors reported by the checkConfig command, otherwise, the Image building step fails.

The checkConfig command validates the application configuration including the YAML file, JVM arguments file, and Log4j configuration file. You can validate the configuration before containerizing an application. When running the checkConfig command, you must specify the location of the folder that contains the DAA, YAML file, JVM arguments file, and Log4j configuration file.

Procedure
1. Navigate to amsgce-runtime-<version>\daautil\bin folder.

2. Run the following command to validate an application configuration:

   For Linux Platform:

   ./checkConfig.sh -daaFolder <location of folder that contains DAA and configuration files> -debug  <Boolean (true/false)>

   For Windows Platform:

   checkConfig.bat -daaFolder <location of folder that contains DAA and configuration files> -debug  <Boolean (true/false)>

   Example:

   ./checkConfig.sh -daaFolder "/home/apps/helloworld" -debug true

   For more information about arguments, which you can specify when running the command, see checkConfig Command Reference.

   Sample CLI Output

   In the following sample CLI output, you can see that the validation of application configuration is successful.

   C:\tibco\amxce\amsgce-runtime-1.0.0\daautil\bin>checkConfig.bat -daaFolder C:\tibco\amxce\helloWorld_REST_SOAP_SSL_GlobalTransation
   DDA2Config Path : C:\tibco\amxce\amsgce-runtime-1.0.0\daautil\bin\
   ------------------------------------------------------
   Checking Java installation on machine.
   ------------------------------------------------------
   Found java executable in PATH
   
   15 Sep 2020 12:08:03,805 [main] [INFO ] com.tibco.amxce.rdacompiler - RDACompiler 5.0.0
   Invoking validateConfigFile
   -daaFolder C:\tibco\amxce\helloWorld_REST_SOAP_SSL_GlobalTransation
   
   15 Sep 2020 12:08:11,394 [main] [WARN ] com.tibco.amxce.rdacompiler - Property '[Reference]HelloWorldPT/EntryREST/httpConnectorName' has been skipped since it is not used.
   15 Sep 2020 12:08:11,458 [main] [INFO ] com.tibco.amxce.rdacompiler - --------------------------------------------------
   15 Sep 2020 12:08:11,458 [main] [INFO ] com.tibco.amxce.rdacompiler - 1 DAA(s) are found under application folder:
   15 Sep 2020 12:08:11,461 [main] [INFO ] com.tibco.amxce.rdacompiler - AMXCE-SOA_sslClient_sslServer.daa
   15 Sep 2020 12:08:11,462 [main] [INFO ] com.tibco.amxce.rdacompiler - The following DAA will be deployed,
   15 Sep 2020 12:08:11,471 [main] [INFO ] com.tibco.amxce.rdacompiler - DAA: AMXCE-SOA_sslClient_sslServer.daa
   15 Sep 2020 12:08:11,478 [main] [INFO ] com.tibco.amxce.rdacompiler - Config File: AMXCE-SOA_sslClient_sslServer.config.yaml
   15 Sep 2020 12:08:11,480 [main] [INFO ] com.tibco.amxce.rdacompiler - --------------------------------------------------
   15 Sep 2020 12:08:11,635 [main] [INFO ] com.tibco.amxce.config.lint - Config file has been validated successfully.