Difference between revisions of "Profiles, Connections, and Filters"

From MidrangeWiki
Jump to: navigation, search
m (+category RDi)
 
(9 intermediate revisions by 3 users not shown)
Line 1: Line 1:
This is what profiles were designed for.   
+
Profile and preference information is stored in similar ways for [[WDSC]] and RDi/[[RDp]]However, there are<br>differences.  The information below was written for WDSC.  There is a link to information on<br>copying/moving settings and preferences in an IBM Technote.
*So one person could setup connections, filters, filter pools, user defined actions, and custom compile commands for a team and then share that with everyone else.
 
  
 +
Profiles were designed: 
 +
*So one person could setup connections, [[RSE_filter|filters]], filter pools, user defined actions, and custom compile commands for a team and then share that with everyone else.
  
*When you create connections, filters, filter pools, user defined actions and customized compile commands they are stored in a project inside of the WDSC workspace called RemoteSystemsConnections.   
+
*When you create connections, [[RSE_filter|filters]], filter pools, user defined actions and customized compile commands they are stored in a project inside of the WDSC workspace called RemoteSystemsConnections.   
 
*All of these things are also grouped by "profiles" (which are not the same thing as i5/OS user profiles).   
 
*All of these things are also grouped by "profiles" (which are not the same thing as i5/OS user profiles).   
*Ultimately this information is stored in directories and xml files on the local hard disk. *This information is also shown in the Team view of the RSE.   
+
*Ultimately this information is stored in directories and xml files on the local hard disk.
*The team view shows up in the same area as the main Remote Systems view (click on the Team tab to switch to the Team view).
+
*This information is also shown in the Team view of the RSE.   
 +
 
 +
*The Team View shows up in the same area as the main Remote Systems view (click on the Team tab to switch to the Team view).
  
 
*You can create multiple profiles and create connections, filters, etc.. under each one.   
 
*You can create multiple profiles and create connections, filters, etc.. under each one.   
 +
 
*You can then make profiles active / inactive via the pop-up menus in the team view.   
 
*You can then make profiles active / inactive via the pop-up menus in the team view.   
*When a profile is active the associated connections, filters, etc... show up in the Remote Systems view.   
+
 
 +
*When a profile is active the associated connections, [[RSE_filter|filters]], etc... show up in the Remote Systems view.   
 +
 
 
*When a profile is inactive then they don't show up (this is a handy way of keeping the Remote Systems view uncluttered if you start using multiple connections.)
 
*When a profile is inactive then they don't show up (this is a handy way of keeping the Remote Systems view uncluttered if you start using multiple connections.)
  
 +
*A profile is the only level that connections, user defined actions, [[RSE_filter|filters]], etc... should be copied between workspaces. 
  
*A profile is the only level that connections, user defined actions, filters, etc... should be copied between workspaces. 
 
 
*If you want to copy a profile from one workspace to the other, then you just rename the folder under the RemoteSystemsConnections project that represents the profile.   
 
*If you want to copy a profile from one workspace to the other, then you just rename the folder under the RemoteSystemsConnections project that represents the profile.   
  
 
*For example, say you want to copy profile "DEVELOPER" from workspaceA to workspaceB:
 
*For example, say you want to copy profile "DEVELOPER" from workspaceA to workspaceB:
  WARNING:  first make sure that workspaceB doesn't already contain a profile named "DEVELOPER" if it does, then rename it from the Team view.
+
  WARNING:  first make sure that workspaceB doesn't already contain a profile named "DEVELOPER"
 +
if it does, then rename it from the Team view.
 +
 
 +
'''For [[WDSC]]:'''
  
 
# Using Windows Explorer, copy the folder workspaceA\RemoteSystemsConnections\DEVELOPER to workspaceB\RemoteSystemsConnections\DEVELOPER  (just use the right click copy / paste actions, the folder name is case-sensitive!)
 
# Using Windows Explorer, copy the folder workspaceA\RemoteSystemsConnections\DEVELOPER to workspaceB\RemoteSystemsConnections\DEVELOPER  (just use the right click copy / paste actions, the folder name is case-sensitive!)
Line 26: Line 35:
 
*You may need to right click on it and make it active for the connections to show up.
 
*You may need to right click on it and make it active for the connections to show up.
  
 +
To move your settings from your old workspace in the default location (for Microsoft Windows XP),
 +
copy c:/Documents & Settings/[userid]/[old_workspace_name]/.metadata/.plugins
 +
/org.eclipse.core.runtime/.settings directory to the same location in the new workspace directory.
 +
 +
 +
'''For RDi/[[RDp]]:'''
 +
 +
To move your settings, preferences, and filters in RDi/RDP:
 +
 +
To move your settings from your old workspace in the default location (for Microsoft Windows XP),
 +
copy c:/Documents & Settings/[userid]/[old_workspace_name]/.metadata/.plugins
 +
/org.eclipse.core.runtime/.settings directory to the same location in the new workspace directory.
 +
 +
To move your filters and profile preferences,
 +
 +
  1. Find c:/Documents & Settings/[userid]/old_workspace_name]/.metadata/.plugins/org.eclipse.rse.core/profiles.
 +
      Identify the folder with the label similar to PRF.***_#. An example is PRF.johnspd_254.
 +
  2. If you do not wish to save any preferences from the new workspace, copy the profiles directory and overwrite the existing file, c:/Documents & Settings/[userid]/[new_workspace_name]/.metadata/.plugins/org.eclipse.rse.core/profiles.
 +
      If this workspace does have preferences you wish to save, you will need to copy the specific PRF file and paste it so that both the old profile and the new profile exist in the profiles directory.
 +
  3. Restart RDi using the new workspace.
 +
  4. Create a new IBM i connection.
 +
 +
You should now have the settings, preferences, and filters that you had available in your original workspace.
 +
 +
[http://www-01.ibm.com/support/docview.wss?uid=swg21421078 IBM Technote 1421078, RDi 7.5]
  
  
 
[[Category:WDSC]]
 
[[Category:WDSC]]
 +
[[Category:RDi]]

Latest revision as of 00:03, 11 October 2016

Profile and preference information is stored in similar ways for WDSC and RDi/RDp.  However, there are
differences. The information below was written for WDSC. There is a link to information on
copying/moving settings and preferences in an IBM Technote.

Profiles were designed:

  • So one person could setup connections, filters, filter pools, user defined actions, and custom compile commands for a team and then share that with everyone else.
  • When you create connections, filters, filter pools, user defined actions and customized compile commands they are stored in a project inside of the WDSC workspace called RemoteSystemsConnections.
  • All of these things are also grouped by "profiles" (which are not the same thing as i5/OS user profiles).
  • Ultimately this information is stored in directories and xml files on the local hard disk.
  • This information is also shown in the Team view of the RSE.
  • The Team View shows up in the same area as the main Remote Systems view (click on the Team tab to switch to the Team view).
  • You can create multiple profiles and create connections, filters, etc.. under each one.
  • You can then make profiles active / inactive via the pop-up menus in the team view.
  • When a profile is active the associated connections, filters, etc... show up in the Remote Systems view.
  • When a profile is inactive then they don't show up (this is a handy way of keeping the Remote Systems view uncluttered if you start using multiple connections.)
  • A profile is the only level that connections, user defined actions, filters, etc... should be copied between workspaces.
  • If you want to copy a profile from one workspace to the other, then you just rename the folder under the RemoteSystemsConnections project that represents the profile.
  • For example, say you want to copy profile "DEVELOPER" from workspaceA to workspaceB:
WARNING:  first make sure that workspaceB doesn't already contain a profile named "DEVELOPER"
if it does, then rename it from the Team view.

For WDSC:

  1. Using Windows Explorer, copy the folder workspaceA\RemoteSystemsConnections\DEVELOPER to workspaceB\RemoteSystemsConnections\DEVELOPER (just use the right click copy / paste actions, the folder name is case-sensitive!)
  2. In the Team view in worksapceB, right click on the RemoteSystemsConnections project and select "Refresh All', then right click and select "Reload Remote System Explorer".
  • The profile should now show up.
  • You may need to right click on it and make it active for the connections to show up.

To move your settings from your old workspace in the default location (for Microsoft Windows XP), copy c:/Documents & Settings/[userid]/[old_workspace_name]/.metadata/.plugins /org.eclipse.core.runtime/.settings directory to the same location in the new workspace directory.


For RDi/RDp:

To move your settings, preferences, and filters in RDi/RDP:

To move your settings from your old workspace in the default location (for Microsoft Windows XP), copy c:/Documents & Settings/[userid]/[old_workspace_name]/.metadata/.plugins /org.eclipse.core.runtime/.settings directory to the same location in the new workspace directory.

To move your filters and profile preferences,

  1. Find c:/Documents & Settings/[userid]/old_workspace_name]/.metadata/.plugins/org.eclipse.rse.core/profiles.
     Identify the folder with the label similar to PRF.***_#. An example is PRF.johnspd_254.
  2. If you do not wish to save any preferences from the new workspace, copy the profiles directory and overwrite the existing file, c:/Documents & Settings/[userid]/[new_workspace_name]/.metadata/.plugins/org.eclipse.rse.core/profiles.
     If this workspace does have preferences you wish to save, you will need to copy the specific PRF file and paste it so that both the old profile and the new profile exist in the profiles directory.
  3. Restart RDi using the new workspace.
  4. Create a new IBM i connection. 

You should now have the settings, preferences, and filters that you had available in your original workspace.

IBM Technote 1421078, RDi 7.5