Tuesday, November 24, 2015

Can an Eclipse Plug-in be loaded into the SDI Config Editor?

In the past I've had customers ask how to use SDI with other code repository clients. CVS is the supported client supplied with the SDI Config Editor, though others could be more desirable by the client..  Over the past week I looked into this and found the SDI Config Editor fails to loaded the SVN client if installed though the Eclipse 'Install New Software' menu.

I will use the concept of “Links” to add an Eclipse Plug-in to the SDI Config Editor.  Instead of using the Eclipse Update Manager or copying resources into the <TDI>/ce/eclipsece directory structure, this third option is available.

This is a step by step procedure.  I believe these steps will work on TDI 7.1.1 also.
(In the example, we will use the Subversive Plug-in with SDI 7.2)

1.  Install SDI 7.2 and upgrade to at least 7.2.0-ISS-SDI-FP0003

2.  Download the desired plug-in.  Be sure the plug-in supports the Eclipse being used.
  • Tivoli Directory Integrator 7.1.1 (TDI) is build on Eclipse Helios SR1(v3.6.1)
  • Security Directory Integrator 7.2 (SDI) is built on Eclipse Juno SR1(v4.2.1)
3.  Create a folder named links inside the <SDI_Install_Directory>/ce/eclipsece folder



4.  Create a new file inside this folder and name it as 'svn.link'.  Note the file name can be any valid string, but the extension has to be link.

5.  Assume that I have unarchived the plug-in into the <TDI_Solution_Directory>/eclipseDropins directory as shown below. 
NOTE:  I found I had to create the eclipse subdirectory and copy all plugin content into the eclipse directory.


6.  The contents of svn.link (from step 4) will be:

For unix/linux:
     path=/opt/IBM/TDI/SolV72/eclipseDropins/Subversive-2.0.4.I20150123-1700

For Window:
     path=C:/IBM/TDI/SolV72/eclipseDropins/Subversive-2.0.4.I20150123-1700
     or
     path=C:\\IBM\\TDI\\SolV72\\eclipseDropins\\Subversive-2.0.4.I20150123-1700

7.  Start the TDI Config Editor.

8.  Verify that the SVN Plug-in has been loaded.  Reviewing the Perspective and Properties should validate this.

Windows > Open Perspective > Other


 Windows > Preferences


Points to Note:
  • The string should always start with “path=” keyword.
  • The path should point to a directory which has a “eclipse” folder which in turn has “features” and “plugins” as sub-folders.  For the svn plug-in, all content of the plug-in had to be moved into a sibling 'eclipse' directory.  This is shown in the image found in Step 5 above.
  • It is recommended to use forward slash ‘/’ in the path (If you want use Backslash, see that you use the escape character i.e. in Windows it should be “\”)
  • The file extension should end with “link
  • The file (i.e svn.link in our example) should exist in the “links” folder.
  • It is recommended to create link files only for big plugins/applications.  For small plugins you can create just one link file, say misc.link and copy all the small plugins to the path referred by this link.