About files naming
When producing and managing a large number of setup and patch files, it is important to have a good naming convention for these files so that an installer can quickly and precisely identify what a file contains, regardless of where it is stored.
The naming convention for the files is the following:
product-component-what-version-opts.ext
product
: Is the name of the product such as safex3 for the platform, erpx3 for Sage X3, hrx3 for Sage X3 People.component
: Is the name of the component such as runtime, appserver, webserver, javabridge, syracuse, and so forth.what
: Indicates what the file is such as installer, patch, doc, readme, and so forth.version
: Is the version, formatted as major.minor.build. The .build part is optional.opts
: Are options that apply to the file.
Several options may be specified and separated by ' - ':
ext
: Is the extension.The component
, what
, and version
elements do not contain any ' - ' or space characters. The names can be parsed and there is no issue with spaces. Additionally, they are all lowercase to avoid potential mismatches on Unix.
safex3-runtime-installer-7.0.19-win32-x86_64.jar
: build 19 of 7.0 runtime installer for win32 archi x86_64, assuming that there are archi specific installers, which may not be the case.erpx3-appserver-installer-7.0.11.jar
: build 11 of X3 version 7.0 application server installer.erpx3-appserver-patch-7.0-5.dat
: patch 5 of X3 version 7.0 of the application server.safex3-syracuse-installer-7.0.22-test.jar
: build 22 of 7.0 Syracuse installer for test branch.