Testing and publishing on your server
The testing and publishing tools provides runtime environments where you can test JSP files, servlets, HTML files, enterprise beans
and Java™ classes.
You can use the workbench to test and publish resources from the following types of projects:
- Dynamic Web projects, which typically contain JSP files, HTML files, servlets,
and JavaBeans™
- Static Web projects, which typically contain HTML files and graphic files
- Enterprise Applications projects, which may contain Java Archive
(JAR) files or Web Archive (WAR) files or both, and pointers to other Web
or EJB projects
- EJB projects, which contain enterprise beans
- Application client projects
After testing your application locally, you can use the tools to publish the application.
Supported runtime environments
The server tools provided in this product allow you to test your applications in different local or remote runtime environments. Where indicated, you can also use the tools to publish to these environments:
- WebSphere test environment. One or more
versions of the WebSphere® Application Server runtime environment, which you can use to test your applications
directly from the development environment. Each test environment provides
all the function of the full runtime environment, but eliminates dependencies
on remote network connections. The tool automatically creates the
corresponding runtime environments and servers when starting the workbench
the first time. The WebSphere test
environment is described in more detail as another topic in this documentation.
-
WAS. You can also test on and publish to one or more separately installed versions of WAS that reside either locally or on a remote machine.
There is a WebSphere File Transfer servlet application, filetransfer.ear, available in the WAS v6.0 and v6.1, but is no longer needed for WAS v7.0. If the WAS v6.x is set with security enabled, run this WebSphere File Transfer servlet (filetransfer.ear) application. By default, this application is installed and started on the WAS v6.x.
The workbench no longer supports tooling for WAS v5.1 or WAS Network Deployment environment. However, for WAS Network Deployment you can continue run the Profile Management Tool from the workbench to create and augment profiles.
-
Apache Tomcat You can test on the Apache Tomcat runtime environment, running locally. With Tomcat, you can only test Web projects that contain servlets and JSPs. For more information on Tomcat, go to jakarta.apache.org/tomcat
- Static Web publishing server. You can publish
static Web projects to an HTTP Web server.
- J2EE publishing server. You can publish J2EE projects to a generic J2EE server.
Specification level summary
The workbench provides the appropriate server selection based on the specification level you have defined for your project. The following table summarizes the specification level each server supports:
| Servers | Specification-Level | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| EAR | EJB | Web | Application Client | |||||||||||||
| 1.2 | 1.3 | 1.4 | 5.0 | 1.1 | 2.0 | 2.1 | 3.0 | 2.2 | 2.3 | 2.4 | 2.5 | 1.2 | 1.3 | 1.4 | 5.0 | |
| WAS V6.0 | 
|
|
| 
|
|
|
|
|
|
|
|
|
|
|
|
|
| WAS V6.0 with Feature Pack for Web 2.0 | ||||||||||||||||
| WAS V6.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| WAS V6.1 with Feature Pack for Web 2.0 | ||||||||||||||||
| WAS V6.1 with Feature Pack for Web Services |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| WAS V6.1 with Feature Pack for Web Services and Web 2.0 | ||||||||||||||||
| WAS V6.1 with Feature Pack for EJB 3.0 |
|
|
| The server does not fully support JEE 5 specification-level. It supports an EAR 5.0 application containing EJB 3.0 modules mixed in with Web or Application Client modules at J2EE 1.4 (or earlier) specification-level. |
|
|
|
However, CMP 2.1, 2.0 or 1.1 are not supported |
|
|
|
JEE 5 specification level is not supported. In other words, Web 2.5 is not supported. |
|
|
|
JEE 5 specification level is not supported. In other words, Application Client 5.0 is not supported. |
| WAS V6.1 with Feature Pack for EJB 3.0 and Web 2.0 | ||||||||||||||||
| WAS V7.0 |
|
|
|
|
|
|
|
However, CMP 2.1, 2.0 or 1.1 are not supported |
|
|
|
|
|
|
|
|
| WAS V7.0 with Feature Pack for Web 2.0 | ||||||||||||||||
| J2EE Publishing Server |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Static Web Publishing Server |
|
|
|
|
|
|
|
| Supports only static Web modules. |
|
|
|
| |||
| Tomcat V6.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Tomcat V5.5 or V5.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Tomcat V4.1 or V4.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Tomcat V3.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
WAS v6.1 with Feature Pack for EJB 3.0
When publishing an application to a WAS v6.1 with Feature Pack for EJB 3.0, Java Platform, Enterprise Edition (Java EE) 5 support is available for both Enterprise archive (EAR) and Enterprise JavaBeans (EJB) modules; however, container-managed persistence (CMP) beans at 2.1, 2.0 or 1.1 specification-levels are not supported in an EJB 3.0 module. In addition, the Web module must remain at Web 2.4, 2.3 or 2.2 specification-levels and the application client module must remain at Java 2 Platform Enterprise Edition (J2EE) 1.4, 1.3 or 1.2 specification-level.
Although, the WAS v6.1 with Feature Pack for EJB 3.0 does not support Servlet 2.5 Web archive (WAR) files and Java EE 5 application client modules, the application server does support annotated injections for Servlet 2.4 WAR files and J2EE 1.4 application clients as a Common Annotations extension.
WAS with Feature Pack for Web 2.0
The WAS with Feature Pack for Web 2.0 can be installed on top of any of the following WAS release:
- WAS V6.0
- WAS V6.1
- WAS V6.1 with Feature Pack for Web Services
- WAS V6.1 with Feature Pack for EJB 3.0
- WAS V7.0
Although the WAS with Feature Pack for Web 2.0 can be installed on top of WAS V6.0.2, the IBM® Rational® Software Delivery Platform, currently does not support this runtime configuration.
The WAS with Feature Pack for Web 2.0 contains the same specification-level support as the WAS release upon which it is installed.
WAS v7.0
When publishing an application to a WAS v7.0, Java Platform, Enterprise Edition (Java EE) 5 support is available; however, container-managed persistence (CMP) beans at 2.1, 2.0 or 1.1 specification-levels are not supported in an EJB 3.0 module.
Server definitions
The server tools use servers to test and publish your projects. Servers are definitions that identify where you want to test your projects. You can either have the development environment create the servers automatically for you, or you can create them using a wizard.