Re-enabling the shared mode for Talend Studio after disabling it

After disabling the shared mode for Talend Studio, the admin user can re-enable it.

About this task

Only the admin user can re-enable the shared mode.

Launch Talend Studio, create a local project and open it.
Relaunch Talend Studio, open the Manage Connections dialog box, click Delete Existing Project(s).
In the pop-up dialog box, select the local project you just created and click OK to delete it.
This makes the plugins to be fully initialized.
Add or update the following two parameters in the <studio>/configuration/config.ini file:
```
osgi.configuration.area=@user.home/studio/configuration
osgi.instance.area=@user.home/studio/workspace
```
These two properties specify the configuration and workspace locations of Talend Studio for each shared user.
Rename the p2 folder under the Talend Studio installation directory with a new name, p2_bak in this example.
Create the directory <studio>/p2/org.eclipse.equinox.p2.engine/profileRegistry.

After the admin user enables the shared mode, each individual user can get into the shared mode.

Delete the @user.home/studio/p2 folder.
Go to the @user.home/studio/configuration folder, which is defined using the osgi.configuration.area parameter, and clean up all folders and files except .m2 and connection_user.properties.
Copy the p2_bak folder under the Talend Studio installation directory into the @user.home/studio folder, and then rename the copied p2_bak folder to p2.
Copy the following folders and files under <studio>/configuration into the folder which is defined using the osgi.configuration.area parameter, @user.home/studio/configuration in this example.
- The .settings folder
- The org.eclipse.equinox.simpleconfigurator folder
- The org.eclipse.update folder
- The talend folder
- The config.ini file
Copy the <studio>/license file into the folder which is defined using the osgi.configuration.area parameter, @user.home/studio/configuration in this example.
Launch Talend Studio.

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!