The original Eclipse-Plugin code used a plugin.xml file for defining an Eclipse-Plugin. There are some older user-defined nodes that use the old style definition and that is no longer supported by the Eclipse level used by the IBM App Connect Enterprise Toolkit.    

This article provides you with the steps needed to fix the issue and allow the user-defined extension to be shown in the IBM App Connect Enterprise Toolkit.

The following steps are based on the sample that has been shipped in the IBM App Connect Enterprise product under <install>\servers\samples\extensions\nodes\com.ibm.samples.nodes.

Step 1

• Unzip the SampleNodesProject.zip.
• Open the MANIFEST.MF file inside the META-INF directory.
  The current MANIFEST.MF file looks like this:

Manifest-Version: 1.0

Ant-Version: Apache Ant 1.7.1

Created-By: 2.6 (IBM Corporation)

Step 2

• Replace the current MANIFEST.MF file with the following;

Manifest-Version: 1.0

Bundle-SymbolicName: com.ibm.samples.nodes; singleton:=true

Bundle-Name: samples Plug-in

Bundle-Version: 1.0.0

Require-Bundle: com.ibm.etools.mft.api,com.ibm.etools.mft.util.ui,com.

ibm.etools.mft.config

Bundle-ManifestVersion: 2

Bundle-RequiredExecutionEnvironment: JavaSE-1.6

Bundle-Vendor: IBM Provider

Note: You need to ensure that the following match your user-defined node:

Bundle-SymbolicName

Bundle-Version

Step 3

• Update the JAR file with the new MANIFEST.MF file.
• Copy the file into the <install>\tools\dropins folder.
• Open the Toolkit from the IBM App Connect console and navigate to the tools directory.
• Run eclipse-clean and you will be able to see the nodes in the Toolkit palette.  

#AppConnectEnterprise(ACE)