CLI and ImageMaster configuration basics

ImageMaster script package “configureAppServer”

The configuration for ImageMaster is based on a script approach, which internally relies on the command line interface (CLI) provided by the application server (JBoss or WildFly). The ImageMaster script package is located in a subdirectory of the delivery file:

  • Directory with script package:

    ima-assembly-9.x.y.z\support\configureAppServer

Files and “cli” directory in package:

  • ImageMaster configuration script (configureAppServer.sh)

  • ImageMaster configuration file (configureAppServer.config)

  • The directory “cli” is required by the above “.sh” script.

All parameters that are required by the base configuration to enable a running ImageMaster can directly be set in the configuration file. In the ending of this file you can specify one custom CLI script to further tune the configuration (see option “customCliPath=” in next chapter). Consider the following rules:

  • Only tune such settings via a custom CLI script, which are not represented by other parameters that must be set directly in the ImageMaster configuration file!

  • You must not delete or comment out any parameters in the ImageMaster configuration file!

    The script fails if you delete any parameters because it also conducts a plausibility check before it executes the setup.

Application server base configuration “standalone.conf”

Beside the above listed ImageMaster configuration script and ImageMaster configuration file there is another application server configuration file included in the application server packages, which is also covered in a later chapter. Within this file a few low-level system settings are covered that can be required for the Java Virtual Machine (JVM):

  • application server configuration file (standalone.conf)

If you are not familiar with application server administration, consider to consult further sources on the Internet. Specific instructions related to the configuration of ImageMaster are covered in later chapters.

Keep your configuration file aligned with any manual changes that are intended to be permanent!

If you change a setting via a CLI command in a running environment, it is strongly recommended also changing the configuration in the ImageMaster configuration file (configureAppServer.config), respectively! Otherwise such changes are lost if you have to reinstall the server or in case of an upgrade to a newer ImageMaster version because these measures rely on the configuration file.