Setting up IBM SDK for Java Technology Edition in your Eclipse IDE

  • Your Eclipse IDE should support Java development. Make sure you are running Eclipse IDE for Java Developers. If your Eclipse installation does not support Java development, you will need to download Eclipse Java development tools (JDT). You can learn more about JDT at

  • In order for Eclipse to automatically detect Java compile warnings and errors and provide content assist and other convenient features, you should have a copy of IBM SDK Java Technology Edition registered in your Eclipse environment. To obtain a copy of the latest release of the IBM Developer Kits for the Java Platform Standard Edition, go to and download the version appropriate for your operating system.

  • As mentioned earlier, the IBM Explorer for z/OS V3.0 Eclipse plugin is strongly recommended for interacting with z/OS from within your Eclipse IDE. Use the following Eclipse p2 update site to install this plugin:

  • If you’re just writing plain Java application in your Eclipse IDE environment, then you’re all set. But if you’re developing Java applications that make use of z/OS unique features using the JZOS Toolkit, you will need a copy of ibmjzos.jar. Without this jar file, Eclipse will not be able to resolve any JZOS related APIs in your Java application. This jar file is located in the /lib/ext directory of the z/OS version of the IBM SDK Java Technology Edition. Use your favorite FTP client to download a copy of this jar from z/OS into your local Eclipse development environment. Most z/OS systems install Java in /usr/lpp/java. If you do not have Java installed on z/OS, please see the “Deploy” section on how to setup your own copy of IBM Java SDK on z/OS.

Creating a Java Project

  1. Open the Package Explorer view.

    Right-click anywhere within the view, and select New -> Java Project.


  2. Let’s call our project “Insurance”, use the default project location, and use Java 8.0 as our execution environment, and click


  3. Here is what our Insurance project look like in Package Explorer.


Join The Discussion

Your email address will not be published. Required fields are marked *