Java Development Kit

A version of the Java Development Kit (JDK) is required for use with JPOs, qualified Application Servers, the ENOVIA Live Collaboration Server, and the ENOVIA Studio Customization Toolkit. For complete details, see the Program Directory for the given release.

Note: Do not install the JDK to a directory with spaces in the name, or you will be unable to install ENOVIA Live Collaboration software.

You can test the Java installation by opening the JDK_INSTALL\demo\applets\nervoustextexample1.html file. If the text is "dancing" in a Web browser window, the installation is OK.

Related Topics
Installing WebSphere
Installing a WebLogic Server
Installing a Web or Application Server

Java Options

When the ENOVIA Live Collaboration Server is installed, recommended Java options are set by default. Refer to "JVM Options" for details.

JDK Notes

Each UNIX O/S vendor has their own version of the JDK and Sun, IBM, and BEA have JDKs for Windows. WebLogic, WebSphere, and the Sun Java Live Collaboration Server all include a JDK when they are installed. In most cases, Sun's JDK should be used. The exceptions are as follows:


  • The JDK embedded with the WebSphere Application Server (on AIX and Windows, IBM's JDK is included; on Solaris, Sun's JDK is included) can only be used to run ENOVIA [Collaborative Business Process (CBP) and VPM Central] applications deployed by this Application Server. This JDK cannot be used to run other non-Application Server based ENOVIA tools or applications (MQL command line, etc.).

    To support this requirement, you must specify the operating system level JDK (and not the JDK embedded with WebSphere) during ENOVIA Live Collaboration Server installation. This JDK will be used to run non-Application Server based applications while the JDK embedded with WebSphere will be used to run the applications deployed by it. The operating system JDK you specify must be supported by ENOVIA and correspond to the JDK requirement listed in "Prerequisites" in the Program Directory for the given release.

  • When using WebLogic on AIX, use IBM's JDK.
  • When using WebLogic on Windows the embedded JDK is JRockit. This means if you are also running a stand-alone ENOVIA Live Collaboration Server, you must configure it to use the JRockit JDK and not the Sun JDK.

Sun's JDK should be used with all other Application Servers.

  • If the ENOVIA Live Collaboration Server's first connection to the database fails, you should be suspicious of the JDK version. Use the java -version command and if it indicates a JDK mismatch, install and point to the correct vendor's JDK.
  • Programs (JPOs or custom applications) that will be run through the ENOVIA Live Collaboration Server must be written with the same (or lower) version of JDK as the Application Server uses. Ideally in a production environment, all components (application and Live Collaboration Server, as well as Studio Modeling Platform clients) will use the same version of the JDK.
  • When using the ENOVIA Live Collaboration Server in RIP mode, the same instance of Java used by the Application Server is used by the Live Collaboration Server. Use the path to this Java during ENOVIA Live Collaboration Server installation). If, however, you are using the RMI Gateway configuration, you can optionally install and use a separate JDK instance. You may want to do so if your JPOs, beans, or custom JSPs rely on a newer version of the JDK. You must also install the JDK if you are installing and using a Tomcat server, since one is not bundled with it.

Note: Supported Application Servers and JDKs listed are for both 32-bit and 64-bit versions.