...
This section describes two strategies for enabling multiple user installations, either via a shared master primary configuration or user-specific configuration. The shared configuration is the recommended installation scenario implementing a multi-user installation of SOAtest and/or Virtualize. Refer to the Eclipse documentation for additional information.
...
In this scenario, users share both the installation area and the master primary configuration area. The system administrator initializes the master primary configuration (typically, in the installation location) and ensures the installation and configuration areas are read-only to users. This prevents the user from installing new components into SOAtest and/or Virtualize.
By default, when users run Eclipse from the shared installation location, Eclipse automatically creates a local configuration area for each user in the following location: <HOME>/.eclipse/<VERSION>. If the master primary configuration area has been fully initialized, the user-specific configuration areas do not contain any relevant data.
- The administrator installs SOAtest and/or Virtualize.
The administrator launches SOAtest and/or Virtualize to initialize the master primary configuration area.
The administrator adds a new entry to the config.ini file in the following location:
For SOAtest and/or Virtualize installed as a plugin:
<ECLIPSE_INSTALL_DIR>/configurationCode Block language text title config.ini [email protected]/<Eclipse configuration directory>
The administrator modifies the following entry in the config.ini file:
SOAtest and Virtualize Standalone:
Code Block language text title config.ini eclipse.p2.data.area=<SOAVIRT_INSTALL_DIR>/p2
SOAtest and/or Virtualize installed as a plugin:
Code Block language text title config.ini eclipse.p2.data.area=<ECLIPSE_INSTALL_DIR>/p2
- The user launches SOAtest and/or Virtualize as normal.
...