Client Services web applications run on the Lotus
® Expeditor platform. A primary difference between a Client Services web application and one that is deployed to run on a WAS or Tomcat runtime is that the Client Services web application must also be a valid OSGi bundle. The Lotus
Expeditor Toolkit automatically handles many of these bundle specific details, which is why developing the web application through a Client Services web project is the recommended development path for web applications that are to be run on the Lotus
Expeditor platform. Nevertheless, it is also possible to develop the web application through a Dynamic Web project, and subsequently test run it on the Lotus
Expeditor platform. Refer to Using a Client Services Web project versus a Dynamic Web project
for more details. It is also possible to transform an existing Web Application Archive (WAR) file into a Web Application Bundle (WAB) suitable for running on the Lotus
Expeditor platform through the use of the WAB Utility.
The following lists aspects of a Client Services web application that differ from a standard web application.
- The Lotus Expeditor platform does not support deploying Enterprise Applications through an EAR. The web application is directly deployed to the runtime.
- A Client Services web application has a manifest file, located in META-INF/MANIFEST.MF, that contains bundle information including package and bundle dependencies. This is associated with the bundle, and is separate from the manifest file found under the web application's content folder.
- A Client Services web application has a plugin.xml file that contains extension point contributions to lazily start the web application.
- A Client Services web application contains additional deployment information in wab.properties. This is located in the web content WEB-INF folder.
- JSP files are translated into their respective servlet classes before the web application is deployed to the runtime as a WAB.
In most cases, these artifacts and differences are handled transparently by the Lotus
Expeditor Toolkit. These differences do not affect the functionality of the web application. There are, however, some development considerations you should take into account depending on the web technologies you will be using. These are described in Developing Web Application logic
A Client Services web application can be developed using many of the same web development tools provided by the Web Tools Platform and Rational
® Software Delivery platform. The primary differences are:
Parent topic: Developing Web applications
- Use the Client Services Web project wizard to create a Client Services web project, as described in Creating a Client Services Web project.
- Since the Lotus Expeditor platform does not support EARs, EAR projects are ignored.
- When testing the project, target the Client Service runtime when using the Run As/Run on Server action. Or, use the Client Service launch configuration when using the Eclipse Run / Debug launch feature.
- When exporting the web application, use the Plug-in Development > Deployable plug-ins and fragments wizard, as described in Exporting Web Application bundles.