How do you configure the Information Server installation temporary directory for base, fix pack, and patch installations?

-

Question

How do you configure the Information Server installation temporary directory for base, fix pack, and patch installations?

Answer

Information Server temporary directory controls where installation logs are written, where the installation tools generate temporary files and scripts, and where the installation tools unpack archives prior to installing their contents. It does not affect the use of temporary storage space by the run time Information Server products.

Information Server 8.5 and 8.7:

Base Install:
Create a file .jvm_args in the is-suite or is-client directory The top level directory of the expanded software distribution archive is either is-suite or is-client. The archive is a .ZIP file on Windows, but for UNIX and Linux platforms it is a .tar.gz compressed tar file. Add the line -Djava.io.tmpdir=temp_dir
Example: -Djava.io.tmpdir=/isinstalls/temp

Update Installer:
Create a file .jvm_args in the InformationServer/_uninstall directory and add the line
-Djava.io.tmpdir=temp_dir

Information Server 8.0.1 and 8.1:

Base Install:
supply the command line arg -is:tempdir temp_dir
Example:
install.exe -is:tempdir temp_dir
./install.sh -is:tempdir temp_dir

Update Installer:
java-path/java -Djava.io.tmpdir=temp_dir -jar updater.jar updater-args

Alternatively
-Djava.io.tmpdir=temp_dir argument can be added to the InformationServer/Updates/bin/InstallUpdate.bat or InstallUpdate.sh script to make the temporary directory permanent.





Popular posts from this blog

Shrink you container size up to 95%.

-
BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file
Read more

alma linux: dnf Module yaml error: Unexpected key in data

-
While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.
Read more