WebSphere Application Server and EGL

When you run or debug an EGL-written, J2EE application in the Workbench, you are likely to use one of these IBM run-time environments:

• WebSphere v5.1 Test Environment, which supports Java servlet version 2.3 (and earlier) and EJB version 2.0 (and earlier)

• WebSphere Application Server v6.0, which supports Java servlet version 2.4 (and earlier) and EJB version 2.1 (and earlier)

If you are debugging or running code that does not use a J2EE data source, the processes for running code in the two environments are similar and require only a few mouse clicks.

If you require access to a J2EE data source, however, the situation is as follows:

• If you are working with the WebSphere v5.1 Test Environment, do the following two steps in any order:
  1. Identify the data source when you define the server configuration.

  2. Make sure that your application refers to the server-configuration entry for that data source.

     This second step involves specifying the JNDI name in the deployment descriptor that is specific to your project. You specify the JNDI name in either of these ways--

     • When you create the project; or

     • When you update the deployment descriptor.

     For details on server configuration, see Configuring WebSphere Application Server v5.x.

• If you are working with WebSphere Application Server v6.0, do the following two steps in any order:
  1. Identify the data source to the server, as is possible in either of these ways--
     • When you update the application deployment descriptor (application.xml), as is recommended; or

     • When you configure the server at the Administrative Console.

     For details on updating the application deployment descriptor, see Setting up a server to test data sources for WebSphere Application Server v6.0. For details on using the Administrative Console, see Configuring WebSphere Application Server v6.x.

  2. Make sure that your application refers to the server-configuration entry for that data source.

     This second step involves specifying the JNDI name in the deployment descriptor that is specific to your project. You specify the JNDI name in either of these ways--

     • When you create the project; or

     • When you update the deployment descriptor.

  The benefits of updating the application deployment descriptor rather than working at the Administrative Console are as follows:

  • You can deploy the enterprise application to any Web application server that supports J2EE version 1.4, with no additional server configuration necessary for identifying the data source.

  • You can update the application deployment descriptor regardless of whether the server is running.

  • You gain convenience because your actions are within the development component of your Rational Developer product rather than within the WebSphere Application Server component.

  However you update the data-source information, your change is available to the server almost immediately.

Related concepts
Web support

Related tasks
Configuring WebSphere Application Server v5.x
Configuring WebSphere Application Server v6.x
Setting up a server to test data sources for WebSphere Application Server v6.0