The Eclipse Installer is a
stand-alone application that is used to install Eclipse products and to automatically keep product
installations at the latest version. As a TPF Toolkit administrator, you must customize the publicly
available Eclipse Installer to access the
TPF Toolkit product catalog on your internal host and make
the customized instance of Eclipse Installer
available on your internal host.
Ignore this topic if your organization chooses to install TPF Toolkit from a fix pack product archive file.
About this task
As an administrator, you must ensure that your users use a reasonably current version of
the customized Eclipse Installer. If the
Eclipse Installer has internet access, it can
automatically install updates. If the Eclipse Installer does not have internet access, you
must periodically repeat this procedure.
Procedure
- Take one of the following actions:
- Copy the compressed file to a directory on Linux on IBM Z, for example,
/home/myuserid/eclipse-inst-jre-win64.zip.
-
On Linux on IBM Z, extract the file to a
separate directory by using the unzip utility for the Windows version or by using the tar utility for the Linux version.
For example, for the Windows version, enter unzip -d
/home/myuserid/eclipseinstaller eclipse-inst-jre-win64.zip.
-
Go to the directory where the installer was extracted.
For example, /home/myuserid/eclipseinstaller.
-
Disable bundle pooling.
Bundle pooling is a caching mechanism that installs features and plug-ins into a location that is
shared by Eclipse products. In the directory where you extracted the installer, complete the
following steps:
-
Create a .settings directory under the configuration directory.
-
In the .settings directory, create a file named
org.eclipse.oomph.setup.installer.prefs.
For example,
/home/myuserid/eclipseinstaller/configuration/.settings/org.eclipse.oomph.setup.installer.prefs
-
Add the following lines to the created file:
eclipse.preferences.version=1
mode=SIMPLE
poolEnabled=false
-
Save the file.
-
Update the Eclipse Installer to access the
TPF Toolkit 4.6 product catalog.
In the directory where you extracted the installer, open the
eclipse-inst.ini file in an editor. Add the following line to the end of the
file:
-Doomph.redirection.setups=http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/->http://customer.server.com/tpftoolkit46/oomph/setups/
where
http://customer.server.com is the URL of your internal host.
- Optional: Configure the default root directory for the TPF Toolkit installation directory:
- Open the /home/myuserid/eclipseinstaller/eclipse-inst.ini
file.
- Add a line that configures the default TPF Toolkit installation root directory as the last
line.
For example, if you want to host the installation directory in the
C:\IBM directory, you can add the following
line:
-Doomph.setup.install.root=C:\IBM
- Save the file.
With this configuration, TPF Toolkit will be installed into the
C:\IBM\tpftoolkit-46\eclipse directory by default.
-
Create an archive of the customized Eclipse Installer to be used by Toolkit users to install
TPF Toolkit 4.6.
- For the Windows system, use the zip utility on Linux on IBM Z to generate the archive, for
example:
cd /home/myuserid/eclipseinstaller
zip -r --to-crlf HTTP document root/tpftoolkit46/installer/eclipse-inst-jre-win64-custom.zip ./*
- For the Linux system, use the tar utility on Linux on IBM Z to generate the archive, for
example:
cd /tmp/installer
tar -cvzf HTTP document root/tpftoolkit46/installer/eclipse-inst-jre-linux64-custom.tar.gz ./*
where
HTTP document root is the HTTP Server document root directory on your
internal host, for example,
/srv/www/htdocs/.
Note: Do not include the
downloaded compressed file in the archive.
What to do next
Make the archive available to your users, and instruct them to install TPF Toolkit by using this customized Eclipse Installer archive. The installation procedure is
the same as installing an administrator instance of TPF Toolkit by using the Eclipse Installer.