Installation using Command Line
Users can install DevOps Model Architect from the command line.
-
Download the DMA_V1.0.2_Setup.zip file.
-
In the same folder location where you saved the DMA_V1.0.2_Setup.zip file, add the installation script file, let’s say the file name is installationScript.sh.
-
Run the following command to install DMA.
For example:
./DMA_InstallationScript.sh DMA_V1.0.2_Setup.zipThe above command should be in this format:
installScript_filename <DMA_P2_zip_filename> [<Installation_location>]
In the above script, there are some parameters used, which are described below:Parameters Description installScript_filename Installation Script file DMA_P2_zip_filename Path to DMA_V1.0.2_Setup.zip file Installation_location [Optional] Path to the folder in which the product will be installed. If this parameter is unspecified, then the default path to installation will be used - The terminal will ask whether you want to install DMA on Eclipse for Java or Eclipse for JEE. Select any one option. The installation will begin. Note that the installation script is designed to first download the Eclipse installer, extract the zip file and then install DMA.
The script can be used on Windows, Linux and Mac with the following scripting interfaces:
| Device | Bash Interface |
|---|---|
| Windows | GitBash |
| Linux | Terminal |
| Mac | Terminal |
There are some settings that can be configured before running the installation script. If the configuration setting is skipped, then the default paths will be used, and the missing Java and Eclipse packages will be downloaded from the internet itself.
The following list enumerates the various configurable environment variables:
-
DMA_DOWNLOADS: Full path to the folder containing all the zip files required for DMA installation. The script will search for Eclipse installation files in the specified path or download it from eclipse.org to the specified location. By default, the current working directory will be used
-
DMA_INSTALL_BASE: Full path to the top folder with the existing DMA installation. The default value is “Current Working Directory/Install”
-
DMA_INSTALL: Full path to the location for a fresh installation. The path can be a pattern containing special @identifiers@ that will be replaced with the actual values by the installation script:
-
@PRODUCT@: the name of the product in upper case, for example, DMA
-
@product@: the name of the product in lower case, for example, dma
-
@VERSION@: version number, for example, 1.0
-
@RELEASE@: identifier of the release, for example, 2023.04
@BUILD@: build number
Default value is “Current Working Directory” /@PRODUCT@_@VERSION@_@RELEASE@ For example, if DMA_InstallationScript.sh is executed from “C:\User\Downloads” to install DMA_1.0.zip, it will be installed into “C:\User\Downloads\DMA_1.0”
-
-
DMA_INSTALL_COMPONENTS: comma separated list of components to be installed. By default, components like core, extra and integrations are installed.
-
DMA_INSTALL_FORCE_OVERWRITE: during installation, if the folder already exists and has files in it, then if this attribute is set, no prompt will be made, and the new installation will proceed by overwriting the old contents
-
DMA_JAVA17_BIN: full path to Java 17 binary. If this is not specified and JAVA 17 is not found under $DMA_INSTALL_BASE, then it will be downloaded and installed automatically
-
DMA_START_AFTER_INSTALL: It can be set to some value if the product needs to be started immediately after the installation
-
DMA_TEST: full path to the folder where the workspace for running the tool after installation will be created. If START_AFTER_INSTALL is not set, then DMA_TEST can be omitted.
Alternatively, similar settings can be updated on top of the script file:DOWNLOADS=$DMA_DOWNLOADS INSTALL_BASE=$DMA_INSTALL_BASE INSTALL=$DMA_INSTALL START_AFTER_INSTALL=$DMA_START_AFTER_INSTALL TESTS=$DMA_TESTInstallation Logs
By default, Installation logs are written into a file “install.log” in the current working directory.