Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Corrected typo.

WSO2 Enterprise Integrator (WSO2 EI) tooling provides capabilities of capabilities of a complete Eclipse-based development environment for the EI. You can develop services, features, and artifacts as well as manage their links and dependencies via the simplified graphical editor of WSO2 EI tooling. 

You can install tooling using any of the following methods:

Note

By default, some MacOS versions are shipped with JDK 1.9, which will not be compatible with WSO2 EI Tooling. Hence, you need to override it by installing Oracle JDK 1.8 and updating the folder path of the JDK 1.8 distribution in the Eclipse distribution when installing WSO2 EI Tooling.

For example, if you are using MacOS High Sierra (Version 10.13.4) with Oracle JDK 1.8.0_151, add the following properties to the <ECLIPSE_HOME>/Contents/Info.plist file.

Code Block
<string>-vm</string>
<string><JAVA_HOME>/Contents/Home/bin/java</string>

...

This method uses a complete plug-in installation with pre-packaged Eclipse so that you do not have to install Eclipse separately.

All you need to do is download download the distribution based on your operating system, extract, and run it. For  For earlier versions, click More Resources and then click Previous Releases.

Info

Getting an error message? See the troubleshooting tips given under Troubleshooting.

...

Tip
titleBefore you begin!

Install the  Eclipse IDE for Java EE Developers (Mars 2) distribution.

...

  1. Open Eclipse and click Help > Install New Software.
  2. On the dialog box that appears, click Add.
  3. Click Download and then click Install from P2 Repository to copy the URL of the P2 repository. 

    Tip

    For earlier versions, click More Resources and then click Previous Releases.

  4. Specify EI Tool as the Name, paste the URL you copied in the previous step as the Location and click OK.
    Add the P2 repository of EI Tooling
  5. Select all the check boxes and click Next.

  6. Read and accept the license agreements and click Finish.

  7. If a security warning appears saying that the authenticity or validity of the software cannot be established, click OK.

  8. Restart Eclipse to complete the installation.
Info
  • Getting an error message? See the troubleshooting tips given under Troubleshooting.
  • Want to update WSO2 EI tooling? Start Eclipse, click Developer Studio, click Check for Updates, select the required updates, and click Install.
    Image Added

Troubleshooting

Follow the steps given below, based on your OS, to resolve the errors you got and start using WSO2 EI tooling.

Localtabgroup
Localtab
activetrue
titleMac OS
Panel
borderColor#613B8F
bgColor#ffffff
borderWidth2
  • If you get an error message about the file being damaged or that you cannot open the file when you try to start Eclipse on a Mac, change the Mac security settings as described below.
    Follow the steps given below:
    1. Go to System Preferences, click Security & Privacy, and then click the General tab.
    2. Under Allow apps downloaded from, click Anywhere.
    3. Thereafter, start Eclipse by double-clicking the Eclipse icon and set your security settings back to the previous setting.
  • If you are running Mac OS Sierra, you must run Eclipse each time from the command line instead of double-clicking the Eclipse icon because this security setting (i.e., the Anywhere option) is not available in it. Follow the steps given below:
    1. Open a terminal and navigate into the <EI_TOOLING_LOCATION>/Eclipse.app/Contents/MacOS.

      Code Block
      cd <EI_TOOLING_LOCATION>/Eclipse.app/Contents/MacOS
    2. Start Eclipse.

      Code Block
      ./eclipse
Localtab
titleUbuntu 16.04
Panel
borderColor#613B8F
bgColor#ffffff
borderWidth2

If you are running WSO2 EI tooling on Ubuntu 16.04, add the following lines of code in the eclipse.ini file before the following line: --launcher.appendVmargs 

Code Block
--launcher.GTK_version
2

This makes you work smoothly with WSO2 EI. Also, this fix is required due to a known issue with the GTK version shipped with Ubuntu 16.04.