...
| Info |
|---|
Use of MZ_HOME backupThe MZ_HOME backup is needed in case the upgrade fails. |
Create a directory to use when unpacking this release and future releases. For the purpose of these instructions, this designated directory is referred to as the staging directory.
| Note | ||
|---|---|---|
| ||
The staging directory should not be the same directory as the one you created and set up as the MZ_HOME directory. |
Place the *.tgz file from your release delivery into the staging directory.
Use a command line tool, go to the staging directory, and unpack the *.tgz file by running the following command:
Code Block $ tar xvzf <filename>.tgz
A directory is then created in the staging directory, containing the software to be installed. For the purpose of these instructions, this directory is referred to as the release content directory.
Now copy the MZ license file into the release content directory.
...
| Code Block |
|---|
$ cp mz.license <release content directory> |
Enter the release content directory and prepare the
install.xmlfile by running the following command:
| Code Block |
|---|
$ cd <release content directory>
$ ./setup.sh prepare |
The *.mzp packages have now been extracted, and the install.xml has been extracted into the release content directory. The install.xml file will automatically be populated with information from your existing installation.
| Note |
|---|
Refer Platform Properties to know more about these properties and their default values. |
...