Points to remember when duplicate WAR files are used to generate images

While generating the images with more than two groups of WAR files, the om-app image is not generated.

For images with tag 10.0.2306.0-amd64 and later, when there is only one group, the generatImages.sh results in an image that is named with the value that is specified in --APP_REPO, and the default is om-app. For more than one group, the images are named with the WAR names and are sorted alphabetically and hyphenated as shown in the following example.
  • Running generateImages.sh with --WAR_FILES=smcfs,sbc,sma:wsc,smcfs:isccs,smcfs:isf,smcfs, generates following images:
    • om-app-sbc-sma-smcfs
    • om-app-smcfs-wsc
    • om-app-isccs-smcfs
    • om-app-isf-smcfs
    • For images before 10.0.2306.0-amd64, only om-app is generated.
  • Running generateImages.sh with --WAR_FILES=smcfs,sbc,sma,wsc,isccs,isf generates only om-app image.

While generating the images with more than two groups of WAR files, it does not generate the om-app image. By default, the image that is used for healthMonitor and restService is fetched from spec.image.oms.agentDefaultName (defaults to om-agent) and spec.image.oms.appDefaultName (defaults to om-app) respectively. These fields can be changed so that the healthMonitor and restService can fetch the right image to use. For more information, see Configuring image parameter.