Eclipse IDE Setup for WebSphere Application Server

This tutorial includes Java™ code that uses the Enterprise JavaBeans (EJB) transport to connect to the Content Platform Engine, hosted by WebSphere Application Server.

Learning objectives

  • Create and configure the Eclipse IDE project with the required IBM FileNet JARs.
  • Add connection code that uses the EJB transport.
  • Create the project's runtime environment.
  • Run the code to connect to Content Platform Engine.

Time required

Approximately 30 minutes.

Prerequisites

  • Content Engine version 4.5.1 or higher, deployed on a supported WebSphere Application Server. For supported application servers, see the FileNet P8 Hardware and Software Requirements .

    To test the connection to the Content Engine that you use to develop a FileNet P8 application, enter this URL in your web browser: http://<hostname>:<portnumber>/FileNet/Engine. (The default port is 9080 for WebSphere Application Server.) If the connection is good, the Content Engine returns an HTML page that describes the Content Engine startup context; otherwise, it returns a list of errors.

  • Content Engine can be deployed in either a local or remote development environment. In a remote environment, the Content Engine is deployed on a remote server, not on the same machine as your IDE.

    For a remote development environment, the WebSphere Application Client must be installed. The version and patch level of WebSphere Application Client and the WebSphere Application Server on which the Content Engine is deployed must match. You can get WebSphere Application Client from the installation media for WebSphere Application Server

    For a local development environment, there is no need to install WebSphere Application Client because the application server libraries exist on your local machine.

  • The following Content Engine Client software must be installed: Jace.jar, log4j.jar, p8cel10n.jar, and the JAAS configuration file, jaas.conf.WebSphere. See Finding Required Files.